-1 (I have my filters already setup :-)
On Thu, 17 Mar 2005 01:26:42 -0700, Richard Feit <[EMAIL PROTECTED]> wrote: > I guess the bottom line here is that the Struts dev list -- with > *massively* higher volumes of mail -- is successful. We're just a bit > sensitive now at this early stage, and losing list members is > frustrating. But it really isn't that hard to set up the filters... > > Based on Cliff's and Craig's comments, I'm changing my vote to -1 > (assuming we don't have some arcane rule that says you can't change your > vote :) ). > > I do think that filtering isn't "incorrect", as long as the filtered > emails aren't ignored (just put in a different and more discernible queue). > > Rich > > Craig McClanahan wrote: > > >I'm not a committer, just a long-time Apache developer, so take my > >opinions as just that ... but there is an important process issue > >here. > > > >When Beehive graduates, it will be the PMC's ultimate responsibility > >to ensure that the code being produced by the product is ready for > >release. An important part of that responsibility is monitoring both > >commit messages (from CVS or SVN as appropriate) and bug reports -- > >along with, of course, the usual development conversations. In turn, > >because the PMC will (in most projects) be comprised of all or a very > >large percentage of the committers, it is *not* a good idea to > >encourage individual committers to listen to only a subset of the > >necessary input into making good decisions. > > > >In Struts, we have historically merged all of these sources into the > >dev list, to ensure that all of the required information was made > >available -- both to the committers and to anyone else that was > >interested in the evolution of the product. Certainly people can > >filter on their own, but they are taking personal responsibility for > >ignoring certain information at that point -- it's not the overall > >system that enables this "incorrect" (IMHO) behavior.. > > > >Craig McClanahan > > > > > >On Tue, 15 Mar 2005 01:02:39 -0700, Richard Feit <[EMAIL PROTECTED]> wrote: > > > > > >>Seems like there have been some people who have been overwhelmed with > >>the amount of jira traffic on the dev list, and who have unsubscribed > >>because of it. I'm a fan of filtering myself, and I wouldn't want to > >>lose much of the bug mail itself, but how would everyone feel about > >>Cliff's second suggestion (reroute it to the commits list)? I know that > >>"commits" doesn't describe it so well, but having most automated mail on > >>a different list might cause fewer people to unsubscribe in despair. I > >>guess not everyone wants to set up filters... > >> > >>Rich > >> > >>Heather Stephens wrote: > >> > >> > >> > >>>I think we get too much mail too. I am filtering it out but it would > >>>be nice to cut it down some if we could. > >>> > >>>Looking in jira admina, another option is to send mail on fewer jira > >>>actions (open, comment, etc.) or not at all... > >>> > >>> > >>>On Mon, 14 Mar 2005 18:14:46 -0800, Cliff Schmidt <[EMAIL PROTECTED]> > >>>wrote: > >>> > >>> > >>> > >>> > >>>>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: > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>beehive-dev@incubator.apache.org 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. > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >>> > > > > > > >
