> -----Original Message----- > From: Rahul Akolkar [mailto:rahul.akol...@gmail.com] > Sent: Friday, October 09, 2009 14:44 > To: Jakarta General List > Cc: bcel-...@jakarta.apache.org; bsf-...@jakarta.apache.org; cactus- > d...@jakarta.apache.org; ecs-...@jakarta.apache.org; jcs- > d...@jakarta.apache.org; jmeter-...@jakarta.apache.org; oro- > d...@jakarta.apache.org; regexp-...@jakarta.apache.org; slide- > d...@jakarta.apache.org; Jakarta Project Management Committee List > Subject: [PROPOSAL] One development list > > [Out of necessity, this is heavily cross-posted. Suggestion is to send > any replies to the gene...@jakarta list only to keep any discussion in > one place.] > > 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. > > Motivations (not in any order): > * Flattens and simplifies oversight - Not much else to be said on > that. > * Communication - Subprojects can often have various touch points. > So, Rony's surprise today at the BSF taglib being retired is one > example. Lets have all dev discussions on one list. > * Cross-pollination - Most subprojects are at the point where it > certainly wouldn't hurt to have the active folks from all of Jakarta > around for dev discussions, votes etc. > * Manageable overhead - More on this later, but we have a number of > usual suspects showing up on many of the dev lists, they'd barely > notice a difference. Others can manage, IMO/hopefully. > > Operationally: > * The combined list traffic will obviously be more than any one of > the separate lists. However, development tends to be in spurts on > these lists and the probabilistic chances of more than a couple of > subproject spurts happening at the same time seems quite low. Overall, > combined traffic is not at all overpowering IMO. > * The proposal will include closing current dev lists and adding all > subscribers to the one new dev list. We'll post a heads up on these > 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. >
+1 to merging into one dev list. > Thoughts? > > Lets say a little over a week (10 days, which should give us two > weekends) for initial feedback and opinions please. > > -Rahul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org > For additional commands, e-mail: general-h...@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
