Re: [PROPOSAL] One development list

Quick recap so far is that there have been a variety of views
expressed on the topic of one dev@ (and commits@/notifications@), and
it seems there is some positive interest in moving ahead. Therefore,
as noted towards the end of the email below, I'll be moving to the
next step of calling a vote on the topic on Monday -- IOW, this is
also a reminder to bring up pending discussion points on the topic, if
any, between now and then.

This thread has also generated a number of other items of interest,
which I'm suggesting we discuss separately if further discussion is
needed. These include, in the order they came up:
 * Merging of user lists
 * Viability of a JMeter TLP
 * Moving ecs, oro and regexp to Commons

Of the three items above, I'll pick up on the ecs, oro and regexp move
to Commons in a new thread, in another week or two.

-Rahul


On Fri, Oct 9, 2009 at 5:43 PM, Rahul Akolkar <[email protected]> wrote:
> [Out of necessity, this is heavily cross-posted. Suggestion is to send
> any replies to the general@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.
>
> Thoughts?
>
> Lets say a little over a week (10 days, which should give us two
> weekends) for initial feedback and opinions please.
>
> -Rahul
>