I don't have strong feelings for whether we have one list of two, i.e. issues@ and builds@ - I'll subscribe to them anyways. A benefit of the latter is that the list names are intuituve and self describing. I guess the strongest argument against would be that many will not subscribe and miss out on important events. But what I think will happen is that a majority of committers will follow the new lists and should there be events that require disussion, bring those to dev@.
In fact I'd argue that the new list(s) be announce only, not accepting email from others than the bots. This would force discussions over to dev@ to the benefit of all. Wrt a commit breaking the build, I would assume that Jenkins is able to email all committers that did a commit in a broken build? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 8. aug. 2019 kl. 00:17 skrev Shawn Heisey <[email protected]>: > > On 8/6/2019 5:17 PM, Jan Høydahl wrote: >> Personally I think the ratio of notifications vs human emails is a bit too >> high. I fear external devs who just want to follow the project may get >> overwhelmed and unsubscribe. >> One suggestion is therefore to add a new list where detailed JIRA comments >> and Github comments / reviews go. All committers should of course subscribe! >> I saw the Zookeeper project have a notifications@ list for GitHub comments >> and issues@ for JIRA comments (Except the first [Created] email for a JIRA >> will also go to dev@) >> The Maven project follows the same scheme and they also send Jenkins mails >> to the notifications@ list. The Cassandra project seems to divert all jira >> comments to the commits@ list. >> The HBase project has keeps only [Created]/[Resolved] mails on dev@ and all >> other from Jira/GH on issues@ list and Jenkins mails on a separate builds@ >> list. >> Is it time we did something similar? I propose a single new notifications@ >> list for everything JIRA, GitHub and Jenkins but keep [Created|Resolved] >> mails on dev@ > > If it weren't for server-side filtering on my mail server (sieve/dovecot), > I'd probably have brought this up a LONG time ago. :) The filtering separates > all those things out into their own folders so my "lucene-dev" folder shows > only human-generated traffic for the most part. > > I'm also subscribed to commits, and that goes to its own folder too. > > +1 to this idea. Having separate lists would mean my filters will be more > reliable, and people who have an interest in dev discussions without tons of > computer-generated junk can join us. > > Here's my bikeshed paint: > > issues@ for detailed Jira/GH activity. > builds@ for things like Jenkins. > I'm ambivalent about whether dev should get the created/resolved activity > from Jira/GH. I can see arguments both ways. > > Thanks, > Shawn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
