On Fri, Oct 9, 2009 at 8:42 PM, Daniel F. Savarese <[email protected]> wrote: > > In message <[email protected]>, > Rahul > Akolkar writes: >>We currently have 8 active development lists at Jakarta, each devoted >>to a subproject. I've been subscribed to all for a while and based on >>my observations and the overall benefits of doing so, I think its time >>to consolidate them into a single development list at Jakarta. > ... >>Thoughts? > > No objections from me. That's been my preferred course of action > for many years now (along with opening commit access for all Jakarta > projects to all Jakarta committers, if we haven't already done so). > <snip/>
Cool (SVN restrictions were removed in April 2006). >>lists before that. Throw in site-cvs@ as well for good measure. >>* We could repurpose general@ as the one dev list, but OTOH, seems >>worthwhile to maintain the dev / general separation. >>* No changes proposed to the user lists. > > I'd rather site-cvs be rolled into a single [email protected] > containing commit traffic for all Jakarta projects. Redesignate > general@ as user@ to contain user traffic for all Jakarta projects, > retiring all the -user lists in the process. People can specify the > specific project referred to in the subject a la Commons (e.g., > Subject: [oro] how do glob expressions work?). Then add > [email protected] (also like commons). > <snap/> All this certainly seems worth considering. The dev lists are low-hanging fruit IMO, so makes sense to start there (as dev@ and commits@ as you note). If there is overwhelming support for merging user lists as well now, thats fine -- if not, lets separate the discussions and get the easier parts done. -Rahul > daniel > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
