Personally, I don't mind having all the projects in the same mailing list. I just don't like being forced to read the notification messages.
I propose 2 mls: one for all the projects (until it becomes too large to handle) and another one for notification messages for all projects (unless others want those split up, too). Cheers, Dave > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Niclas Hedhman > Sent: 16 April 2007 21:52 > To: General OPS4J > Subject: Re: Time to move [issues] to new ml > > > On Monday 16 April 2007 14:25, Peter Neubauer wrote: > > On 4/16/07, David Leangen <[EMAIL PROTECTED]> wrote: > > > I think the time has come to move the issue tracking messages to a new > > > ml. > > > I find this rather smooth, since I can track all activity via > > subscriptions and don't have to go in and frequently poll some other > > system. You can always filter the incoming messages on subject. But of > > course that is only my perception. > > There are suddenly two separate items on the table; > > 1. Should [issues] go to main mailing list or to [EMAIL PROTECTED] > > 2. Should general@ be used for all projects or should it be split up? > > > Personally, I prefer a small number of mailing lists, and with prefix in > subject, since all modern mail clients are capable of filtering/labelling > giving people a lot of choice. > > WDOT? > > Cheers > Niclas > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
