Oh, and -1 on disabling our GitHub email integration Justification: it would break the "decisions are made on the mailing lists" rule
On 16 March 2015 at 16:58, Noah Slater <nsla...@apache.org> wrote: > +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 -- Noah Slater https://twitter.com/nslater
