I agree with all of this. I'd be in support of an automated email monthly to dev@ that reminds people where to go to look for GH PRs, JIRA ticket updates, etc.
-Joan ----- Original Message ----- From: "Noah Slater" <nsla...@apache.org> To: dev@couchdb.apache.org Sent: Monday, March 16, 2015 11:58:35 AM Subject: Re: [PROPOSAL] Move transactional email out of dev@ +1 for JIRA -> issues@ -1 for GitHub PRs -> commits@ > Justification: PR comments are dev discussion, not changesets I am +0 for GitHub PRs remaining on dev > Justification: I also get that they're noisy I am +1 for GitHub PRs moving to something like reviews@ On 16 March 2015 at 15:42, Alexander Shorin <kxe...@gmail.com> wrote: > On Mon, Mar 16, 2015 at 5:00 PM, Robert Kowalski <r...@kowalski.gd> wrote: >> Alex: I think people who are not interested in reviewing PRs now will >> not be interested anyway, no matter which channels we try to enforce. >> We are currently channeling all mails for PRs to dev and since months >> I am getting reviews from the same group of persons. > > Indeed, but those who are shouldn't suffer from the spam which happens > in commits@ . Please note, the GH notifications aren't just > automatically generated emails: you can reply on them and those > replied will be synced with GH. So you're able to lead a discussion > right from your email client. > > The most compromise solution looks for me as a separate ML. We > collection the stats for every board report. If it won't be much > popular/useful we'll just shut it down and move these stuff to > commits@, but with really insurance that nobody cares/use ML for GH > conversations. > > What's the reviews are constantly made by the same group of persons is > a separate issue. > > -- > ,,,^..^,,, -- Noah Slater https://twitter.com/nslater
