I'm in favour of that too. Taking your sentence out of context, 'the torrent of machine-generated messages discourages casual committers (...)' from keeping up to date with the posts to the mailing list: I have 1056 unread e-mails in the jclouds mailing lists and only read ten a day or so that somehow slip pass my mail filter.
Cheers, Dies -----Original Message----- From: Andrew Gaul [mailto:[email protected]] Sent: Wednesday, August 28, 2013 8:16 PM To: [email protected] Subject: Re: notifications@ and/or commits@ lists? On Wed, Aug 28, 2013 at 08:09:50PM +0200, Andrew Phillips wrote: > >Based on the options listed at [1], I was wondering whether a > >"notifications@" and/or a separate "commits@" list would make sense > >for us? > > Just to bring this one up again: what are the thoughts around > > 1) Creating a new "[email protected]" mailing list > 2) Moving all JIRA, GitHub, ASF Git, BuildHive and DEV@cloud traffic > to that list > > Or does anyone currently have any other efficient strategies (simply > good email filtering rules?) to suggest in order to handle this > <strike>flood</strike>traffic? Overwhelmingly in favor of this; the torrent of machine-generated messages discourages casual committers from subscribing. -- Andrew Gaul http://gaul.org/
