Is this really necessary? Don't standard email filters solve this problem? If most of the subscribers would be the same group, I have to wonder if it's necessary.
Believe it or not, adding an extra mailing list isn't free, in terms of effort. It means some person who volunteers for the infrastructure team needs to set up the new distribution, the archive, the web interface for the archive, and a moderator. The moderator will have to filter out spam against yet another list. The other thing is that we can't think of the effort in terms of just the Beehive project. The same infrastructure people will be responding to the ~100 other projects that may decide to follow the trend of adding a fourth mailing list per project (in addition to user, dev, and cvs/svn/commits). AFAIK, only the httpd project has a list dedicated to bugs. Another option could be to send jira to -commits, instead of -dev. Cliff On Monday, March 14, 2005 3:22 PM, Ken Tam wrote: > [email protected] is often swamped by JIRA mail, making > it hard to follow threads of actual discussion. I propose the > following: > > 1) Define a new mailing list [EMAIL PROTECTED] and > direct JIRA-generated mail solely to that list > 2) Seed the new list with all present subscribers to beehive-dev.
