Re: [PROPOSAL] Move transactional email out of dev@
On 17 Mar 2015, at 22:22, Alexander Shorin kxe...@gmail.com wrote: On Wed, Mar 18, 2015 at 12:14 AM, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 22:06, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 19:19, Alexander Shorin kxe...@gmail.com wrote: This point has a drawback as JIRA notifies not only about discussion bits, but for any issue change what is causing a lot of spam in ML. Maybe that can be changed in JIRA? Yes we can: https://issues.apache.org/jira/plugins/servlet/project-config/COUCHDB/notifications Actual setting has to be done by INFRA, I’d say we only keep Issue Created and Issue Commented. Resolved, Reopened and Closed are important as well. Others are not, imho. Agreed: https://issues.apache.org/jira/browse/INFRA-9295 Best Jan -- -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [PROPOSAL] Move transactional email out of dev@
I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org wrote: 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. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater
Re: [PROPOSAL] Move transactional email out of dev@
On 17 Mar 2015, at 19:19, Alexander Shorin kxe...@gmail.com wrote: This point has a drawback as JIRA notifies not only about discussion bits, but for any issue change what is causing a lot of spam in ML. Maybe that can be changed in JIRA? -- ,,,^..^,,, On Tue, Mar 17, 2015 at 8:45 PM, Noah Slater nsla...@apache.org wrote: That's a good point. Why not combine JIRA and GitHub PRs? We do have quite a lot of mailing lists already. :) On 17 March 2015 at 17:24, Russell Branca russ...@chewbranca.com wrote: Seems a bit odd to separate github PR comments from JIRA comments as the overlap on development related discussion can be large. As for actually separating out the messages, I'm -0. Email filters work really well for this sort of thing. -Russell On Tuesday, March 17, 2015, till t...@php.net wrote: We use this in-house: https://github.com/heroku/devdigest/ Gives you the daily run-down on what happened on a set of given repos or in an org. It's tweak-able (= open source, Ruby code). Till On Tue, Mar 17, 2015 at 4:40 PM, Noah Slater nsla...@apache.org javascript:; wrote: I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com javascript:; wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com javascript:; wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org javascript:; wrote: 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. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [PROPOSAL] Move transactional email out of dev@
We use this in-house: https://github.com/heroku/devdigest/ Gives you the daily run-down on what happened on a set of given repos or in an org. It's tweak-able (= open source, Ruby code). Till On Tue, Mar 17, 2015 at 4:40 PM, Noah Slater nsla...@apache.org wrote: I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org wrote: 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. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater
Re: [PROPOSAL] Move transactional email out of dev@
That's a good point. Why not combine JIRA and GitHub PRs? We do have quite a lot of mailing lists already. :) On 17 March 2015 at 17:24, Russell Branca russ...@chewbranca.com wrote: Seems a bit odd to separate github PR comments from JIRA comments as the overlap on development related discussion can be large. As for actually separating out the messages, I'm -0. Email filters work really well for this sort of thing. -Russell On Tuesday, March 17, 2015, till t...@php.net wrote: We use this in-house: https://github.com/heroku/devdigest/ Gives you the daily run-down on what happened on a set of given repos or in an org. It's tweak-able (= open source, Ruby code). Till On Tue, Mar 17, 2015 at 4:40 PM, Noah Slater nsla...@apache.org javascript:; wrote: I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com javascript:; wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com javascript:; wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org javascript:; wrote: 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. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater
Re: [PROPOSAL] Move transactional email out of dev@
On Wed, Mar 18, 2015 at 12:06 AM, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 19:19, Alexander Shorin kxe...@gmail.com wrote: This point has a drawback as JIRA notifies not only about discussion bits, but for any issue change what is causing a lot of spam in ML. Maybe that can be changed in JIRA? That's would be extremely cool. -- ,,,^..^,,,
Re: [PROPOSAL] Move transactional email out of dev@
On Wed, Mar 18, 2015 at 12:14 AM, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 22:06, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 19:19, Alexander Shorin kxe...@gmail.com wrote: This point has a drawback as JIRA notifies not only about discussion bits, but for any issue change what is causing a lot of spam in ML. Maybe that can be changed in JIRA? Yes we can: https://issues.apache.org/jira/plugins/servlet/project-config/COUCHDB/notifications Actual setting has to be done by INFRA, I’d say we only keep Issue Created and Issue Commented. Resolved, Reopened and Closed are important as well. Others are not, imho. -- ,,,^..^,,,
Re: [PROPOSAL] Move transactional email out of dev@
This point has a drawback as JIRA notifies not only about discussion bits, but for any issue change what is causing a lot of spam in ML. -- ,,,^..^,,, On Tue, Mar 17, 2015 at 8:45 PM, Noah Slater nsla...@apache.org wrote: That's a good point. Why not combine JIRA and GitHub PRs? We do have quite a lot of mailing lists already. :) On 17 March 2015 at 17:24, Russell Branca russ...@chewbranca.com wrote: Seems a bit odd to separate github PR comments from JIRA comments as the overlap on development related discussion can be large. As for actually separating out the messages, I'm -0. Email filters work really well for this sort of thing. -Russell On Tuesday, March 17, 2015, till t...@php.net wrote: We use this in-house: https://github.com/heroku/devdigest/ Gives you the daily run-down on what happened on a set of given repos or in an org. It's tweak-able (= open source, Ruby code). Till On Tue, Mar 17, 2015 at 4:40 PM, Noah Slater nsla...@apache.org javascript:; wrote: I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com javascript:; wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com javascript:; wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org javascript:; wrote: 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. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater
Re: [PROPOSAL] Move transactional email out of dev@
I like the idea of a weekly digest, but just if we find anyone who implements it. It should not block us in a mid-term to remove the autogenerated spam from the main dev ML that so many folks dislike. I really like all the ideas and discussions around that topic and I would really like to get to a solution in the short term. We still can change our solution if we get a lot of feedback that the proposed solutions don't work, but I think it is a good start just to move the automatic traffic away from dev. My perspective and persona: Robert, as a paid developer working ~8hrs/day on CouchDB as part of his job he does not read that auto generated mails. If he is interested in changes, he watches the repos. Robert puts a lot of effort into the project after work in his spare time. The automated mails makes it hard for him to navigate between discussions for Fauxton, Erlang or the Website in his private mailbox. After work he deletes ~10-20 mails that are redundant (notifications via github watch, dev, jira, irc-channel) every day. Robert likes if proposals from the Fauxton group (e.g. coding guidelines) are also visible to the Erlang folks and are sparking discussions there too. To be honest I have no real opinion if all auto-mails should go to commits@, an additional gh@-list or somewhere else. I would just like to have real human input for ideas, proposals, discussions, votes etc. on the ML. Current problem: many folks complain about spamming from jira and github at dev Solution: don't spam on dev mailing list Experiment: I would like to get feedback in max 72hrs from someone who really depends in real life, on a daily basis on the auto-generated mails on dev, and if so, is not able to sign up for a separate new list or take care in another way to find out what happens in the project. I think that is the problem we try to find a solution for, and so far I haven't met someone who has that problem, but it might be my personal bias. On Tue, Mar 17, 2015 at 10:22 PM, Alexander Shorin kxe...@gmail.com wrote: On Wed, Mar 18, 2015 at 12:14 AM, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 22:06, Jan Lehnardt j...@apache.org wrote: On 17 Mar 2015, at 19:19, Alexander Shorin kxe...@gmail.com wrote: This point has a drawback as JIRA notifies not only about discussion bits, but for any issue change what is causing a lot of spam in ML. Maybe that can be changed in JIRA? Yes we can: https://issues.apache.org/jira/plugins/servlet/project-config/COUCHDB/notifications Actual setting has to be done by INFRA, I’d say we only keep Issue Created and Issue Commented. Resolved, Reopened and Closed are important as well. Others are not, imho. -- ,,,^..^,,,
Re: [PROPOSAL] Move transactional email out of dev@
Seems a bit odd to separate github PR comments from JIRA comments as the overlap on development related discussion can be large. As for actually separating out the messages, I'm -0. Email filters work really well for this sort of thing. -Russell On Tuesday, March 17, 2015, till t...@php.net wrote: We use this in-house: https://github.com/heroku/devdigest/ Gives you the daily run-down on what happened on a set of given repos or in an org. It's tweak-able (= open source, Ruby code). Till On Tue, Mar 17, 2015 at 4:40 PM, Noah Slater nsla...@apache.org javascript:; wrote: I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com javascript:; wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com javascript:; wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org javascript:; wrote: 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. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater
Re: [PROPOSAL] Move transactional email out of dev@
I am +1 on Jans proposal. 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. The current state is that folks are avoiding the dev ML because of this noise. On Mon, Mar 16, 2015 at 2:20 PM, Alexander Shorin kxe...@gmail.com wrote: On Mon, Mar 16, 2015 at 4:08 PM, Jan Lehnardt j...@apache.org wrote: On 16 Mar 2015, at 14:00, Alexander Shorin kxe...@gmail.com wrote: +1 for JIRA -1 for GitHub I think we need another ML for PRs and related conversation there OR somehow automagically add all the committers to watchers list on GitHub of our projects to let them receive notification by using GitHub system. People how don't want to follow all the projects may unwatch those manually. But commits@ isn't the place where you should go for the PRs without MUA filters while PRs isn't a thing to receive lack of attention. Can you make a concrete proposal e.g. “emails so and so should go to foo@c.a.o”? I'm not sure that they should since I have multiple views on this: 1. GitHub notification remains on dev@. Pros: - Everyone reads the dev@; - You can participant in GH discussion by replying on related the email; - Nothing need to do; Cons: - It's automatically generated email; - Not at all people are interested in all our subprojects (fauxtoners may'd like to receive www- related mails, but www- folks unlikely would be interested in fabric changes etc.); 2. Move GitHub notifications to gh@ ML. Pros: - Less noise on dev@; Cons: - If you're not subscribed on gh@ and doesn't watch project on GitHub, you could easily miss the notification about pull request; 3. Disable GitHub emails at all on ASF MLs, add all the folks as watchers of all our subprojects and let them unscribe from those they don't like to follow. Pros: - Everyone follows things they likes; - No Pull Requests lacks of attention (theoretically); - No automatically generated emails; Cons: - All the related conversation happens not on ASF baseground, but GitHub one; - Daniel will be sad; Not sure which one is the best since it's very depends on overall people workflow and ASF rules. -- ,,,^..^,,,
Re: [PROPOSAL] Move transactional email out of dev@
+1 On 16 Mar 2015, at 2:47 PM, Jan Lehnardt j...@apache.org wrote: Hey all, we should move transactional email out of dev@ into separate mailing lists. I propose this: JIRA email - issues@c.a.o (new mailing list) GitHub email - commits@c.a.o (which already exists) Am I missing anything? Best Jan -- -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
Re: [PROPOSAL] Move transactional email out of dev@
On Mon, Mar 16, 2015 at 4:08 PM, Jan Lehnardt j...@apache.org wrote: On 16 Mar 2015, at 14:00, Alexander Shorin kxe...@gmail.com wrote: +1 for JIRA -1 for GitHub I think we need another ML for PRs and related conversation there OR somehow automagically add all the committers to watchers list on GitHub of our projects to let them receive notification by using GitHub system. People how don't want to follow all the projects may unwatch those manually. But commits@ isn't the place where you should go for the PRs without MUA filters while PRs isn't a thing to receive lack of attention. Can you make a concrete proposal e.g. “emails so and so should go to foo@c.a.o”? I'm not sure that they should since I have multiple views on this: 1. GitHub notification remains on dev@. Pros: - Everyone reads the dev@; - You can participant in GH discussion by replying on related the email; - Nothing need to do; Cons: - It's automatically generated email; - Not at all people are interested in all our subprojects (fauxtoners may'd like to receive www- related mails, but www- folks unlikely would be interested in fabric changes etc.); 2. Move GitHub notifications to gh@ ML. Pros: - Less noise on dev@; Cons: - If you're not subscribed on gh@ and doesn't watch project on GitHub, you could easily miss the notification about pull request; 3. Disable GitHub emails at all on ASF MLs, add all the folks as watchers of all our subprojects and let them unscribe from those they don't like to follow. Pros: - Everyone follows things they likes; - No Pull Requests lacks of attention (theoretically); - No automatically generated emails; Cons: - All the related conversation happens not on ASF baseground, but GitHub one; - Daniel will be sad; Not sure which one is the best since it's very depends on overall people workflow and ASF rules. -- ,,,^..^,,,
Re: [PROPOSAL] Move transactional email out of dev@
+1 for JIRA -1 for GitHub I think we need another ML for PRs and related conversation there OR somehow automagically add all the committers to watchers list on GitHub of our projects to let them receive notification by using GitHub system. People how don't want to follow all the projects may unwatch those manually. But commits@ isn't the place where you should go for the PRs without MUA filters while PRs isn't a thing to receive lack of attention. -- ,,,^..^,,, On Mon, Mar 16, 2015 at 3:54 PM, Garren Smith gar...@apache.org wrote: +1 On 16 Mar 2015, at 2:47 PM, Jan Lehnardt j...@apache.org wrote: Hey all, we should move transactional email out of dev@ into separate mailing lists. I propose this: JIRA email - issues@c.a.o (new mailing list) GitHub email - commits@c.a.o (which already exists) Am I missing anything? Best Jan -- -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
Re: [PROPOSAL] Move transactional email out of dev@
On 16 Mar 2015, at 14:00, Alexander Shorin kxe...@gmail.com wrote: +1 for JIRA -1 for GitHub I think we need another ML for PRs and related conversation there OR somehow automagically add all the committers to watchers list on GitHub of our projects to let them receive notification by using GitHub system. People how don't want to follow all the projects may unwatch those manually. But commits@ isn't the place where you should go for the PRs without MUA filters while PRs isn't a thing to receive lack of attention. Can you make a concrete proposal e.g. “emails so and so should go to foo@c.a.o”? Best Jan -- -- ,,,^..^,,, On Mon, Mar 16, 2015 at 3:54 PM, Garren Smith gar...@apache.org wrote: +1 On 16 Mar 2015, at 2:47 PM, Jan Lehnardt j...@apache.org wrote: Hey all, we should move transactional email out of dev@ into separate mailing lists. I propose this: JIRA email - issues@c.a.o (new mailing list) GitHub email - commits@c.a.o (which already exists) Am I missing anything? Best Jan -- -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ signature.asc Description: Message signed with OpenPGP using GPGMail
[PROPOSAL] Move transactional email out of dev@
Hey all, we should move transactional email out of dev@ into separate mailing lists. I propose this: JIRA email - issues@c.a.o (new mailing list) GitHub email - commits@c.a.o (which already exists) Am I missing anything? Best Jan -- -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [PROPOSAL] Move transactional email out of dev@
Thanks for your support Garren :) No need for the others +1 this (let’s keep emails down, eh? :). I think we have consensus on this, I just want to get the details nailed down, so I can request INFRA to do the changes. Best Jan -- On 16 Mar 2015, at 13:54, Garren Smith gar...@apache.org wrote: +1 On 16 Mar 2015, at 2:47 PM, Jan Lehnardt j...@apache.org wrote: Hey all, we should move transactional email out of dev@ into separate mailing lists. I propose this: JIRA email - issues@c.a.o (new mailing list) GitHub email - commits@c.a.o (which already exists) Am I missing anything? Best Jan -- -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [PROPOSAL] Move transactional email out of dev@
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
Re: [PROPOSAL] Move transactional email out of dev@
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. -- ,,,^..^,,,
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
Re: [PROPOSAL] Move transactional email out of dev@
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
Re: [PROPOSAL] Move transactional email out of dev@
On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org wrote: 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. Good idea btw. +1 -- ,,,^..^,,,
