This will be a huge improvement. Thanks for taking on this task! On Fri, Jan 10, 2014 at 11:53:58PM +0100, Andrew Phillips wrote: > Just to resurrect this one, after seeing an interesting comment [1] in a > podling review about how a low signal-to-noise ratio on the dev@ list could > also deter committers. > > According to infra, we should just be able to file a ticket: > > 17:47] <gmcdonald> up to the project to choose. 1. create a notfications > list and keep issues or 2. rename and get all stuff go to notifications. > [17:47] <gmcdonald> it is easy to rename a list > [17:48] <gmcdonald> we'd then need to tell jira the new name > [17:48] <andrewp> Good to hear. That's the option we were planning to go > for, as per http://markmail.org/message/jvkcwfk6psk24at5 > [17:48] <gmcdonald> ok > [17:48] <andrewp> But somehow we didn't file the right request, or something. > [17:48] <gmcdonald> create a ticket when you've decided > [17:48] <andrewp> Just an INFRA ticket? > [17:48] <gmcdonald> yep > [17:49] <andrewp> Will do, then...thanks! > [17:49] <gmcdonald> np > > I'm about to go ahead and open this ticket. Next step would be [2]: > > 1) Rename issues@ to notifications@ > 3) Use notifications@ in place of dev@ for all JIRA, GitHub, BuildHive and > DEV@cloud alerts, as well as Disqus comments and the like > 4) Leave it up to individual developers to sign up for notifications@, > i.e. *not* to subscribe dev@ to that list by default > > Please ping if there are any objections! > > ap > > [1] > http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E > [2] http://markmail.org/message/xfiax4wawe6xxcdu
-- Andrew Gaul http://gaul.org/
