You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Rahul Akolkar <ra...@gmail.com> on 2009/10/09 23:43:43 UTC
[PROPOSAL] One development list
[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
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
RE: [PROPOSAL] One development list
Posted by Gary Gregory <GG...@seagullsoftware.com>.
> -----Original Message-----
> From: Rahul Akolkar [mailto:rahul.akolkar@gmail.com]
> Sent: Friday, October 09, 2009 14:44
> To: Jakarta General List
> Cc: bcel-dev@jakarta.apache.org; bsf-dev@jakarta.apache.org; cactus-
> dev@jakarta.apache.org; ecs-dev@jakarta.apache.org; jcs-
> dev@jakarta.apache.org; jmeter-dev@jakarta.apache.org; oro-
> dev@jakarta.apache.org; regexp-dev@jakarta.apache.org; slide-
> dev@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 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.
>
+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-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by Rahul Akolkar <ra...@gmail.com>.
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 <ra...@gmail.com> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists (was: [PROPOSAL] One development list)
Posted by Brett Porter <br...@apache.org>.
http://mail-archives.apache.org/mod_mbox/attic-general/200902.mbox/%3CA3AF8739-D168-44B6-8544-201F8D5B5948@dslextreme.com%3E
On 13/10/2009, at 6:18 AM, Rahul Akolkar wrote:
> On Sun, Oct 11, 2009 at 9:06 PM, Brett Porter <br...@apache.org>
> wrote:
>> A related side note - some time back I think there was a request to
>> shut
>> down the slide user and dev lists, but that slipped off the radar.
>> Is that
>> desired now?
>>
> <snip/>
>
> ISTR some discussion but its been a while. Before I go digging in the
> archives, do you happen to have a pointer to a conclusive post / JIRA
> on this?
>
> (if nothing else, slide-dev folds into the proposal here, slide-user
> fate can be discussed thereafter)
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists (was: [PROPOSAL] One development list)
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sun, Oct 11, 2009 at 9:06 PM, Brett Porter <br...@apache.org> wrote:
> A related side note - some time back I think there was a request to shut
> down the slide user and dev lists, but that slipped off the radar. Is that
> desired now?
>
<snip/>
ISTR some discussion but its been a while. Before I go digging in the
archives, do you happen to have a pointer to a conclusive post / JIRA
on this?
(if nothing else, slide-dev folds into the proposal here, slide-user
fate can be discussed thereafter)
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists
Posted by Brett Porter <br...@apache.org>.
On 14/10/2009, at 5:37 AM, Rahul Akolkar wrote:
> On Tue, Oct 13, 2009 at 2:11 PM, Roland Weber <os...@dubioso.net>
> wrote:
>> Brett Porter wrote:
>>>
>>> A related side note - some time back I think there was a request
>>> to shut
>>> down the slide user and dev lists, but that slipped off the radar.
>>> Is that
>>> desired now?
>>
>> At the time when we retired Slide, the idea was to keep the
>> lists open in case somebody picks up interest. Based on this
>> year's activity on the lists, I'd say there is no interest.
>> The lists can be shut down.
> <snip/>
>
> Unless Brett sees this over the next few days, I suggest sending an
> email / adding a JIRA for infra. I think we'd want a last post for the
> archives asking further communication to be on general@j and then we
> can close the lists.
Seen, but I still prefer it be added to JIRA by someone.
>
>
>> Since there are still automated mails being sent to slide-dev
>> from Bugzilla and Gump, that address should be forwarded to
>> an existing mailing list.
>>
> <snap/>
>
> Or point Bugzilla and Gump to general@j (even discontinue Gump if the
> nags are bound to fall on deaf ears).
Notifications should be turned off for slide, IMO.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists
Posted by David Fisher <df...@jmlafferty.com>.
Hi -
> Or point Bugzilla and Gump to general@j (even discontinue Gump if the
> nags are bound to fall on deaf ears).
Please do not - this discussion is a lot of traffic for general@j.
Or, maybe this Apache POI person should finish his migration and
unsubscribe?
Best Regards,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists
Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Oct 13, 2009 at 2:11 PM, Roland Weber <os...@dubioso.net> wrote:
> Brett Porter wrote:
>>
>> A related side note - some time back I think there was a request to shut
>> down the slide user and dev lists, but that slipped off the radar. Is that
>> desired now?
>
> At the time when we retired Slide, the idea was to keep the
> lists open in case somebody picks up interest. Based on this
> year's activity on the lists, I'd say there is no interest.
> The lists can be shut down.
<snip/>
Unless Brett sees this over the next few days, I suggest sending an
email / adding a JIRA for infra. I think we'd want a last post for the
archives asking further communication to be on general@j and then we
can close the lists.
> Since there are still automated mails being sent to slide-dev
> from Bugzilla and Gump, that address should be forwarded to
> an existing mailing list.
>
<snap/>
Or point Bugzilla and Gump to general@j (even discontinue Gump if the
nags are bound to fall on deaf ears).
-Rahul
> cheers,
> Roland
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists
Posted by Roland Weber <os...@dubioso.net>.
Brett Porter wrote:
> A related side note - some time back I think there was a request to shut
> down the slide user and dev lists, but that slipped off the radar. Is
> that desired now?
At the time when we retired Slide, the idea was to keep the
lists open in case somebody picks up interest. Based on this
year's activity on the lists, I'd say there is no interest.
The lists can be shut down.
Since there are still automated mails being sent to slide-dev
from Bugzilla and Gump, that address should be forwarded to
an existing mailing list.
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Slide lists (was: [PROPOSAL] One development list)
Posted by Brett Porter <br...@apache.org>.
A related side note - some time back I think there was a request to
shut down the slide user and dev lists, but that slipped off the
radar. Is that desired now?
On 10/10/2009, at 8:43 AM, Rahul Akolkar 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by sebb <se...@gmail.com>.
On 11/10/2009, Rahul Akolkar <ra...@gmail.com> wrote:
> On Sat, Oct 10, 2009 at 2:04 PM, Torsten Curdt <tc...@vafer.org> wrote:
> >> Care to elaborate a bit?
> >
> > I'd argue that for the people who care it's no big deal to subscribe
> > to the various lists. So tuning in is no problem, tuning out once
> > consolidated indeed is. It's an all-or-nothing. How is oversight
> > better when everyone (or at least all PMC members) are subscribed to
> > all dev list as opposed to just the one?
> >
>
> <snip/>
>
> Its not. But expecting all PMC members to be on one dev list
> constitutes a much gentler forcing function.
>
>
>
> > While the one dev list might work OK for Commons I have the feeling
> > that these projects are just too different. In Commons one could
> > imagine to step up for another component. I don't see that with the
> > rest that is left at jakarta.
> >
> > If there are many cross-posting (that would be a sign for
> > cross-concerns) I haven't noticed any.
> >
> > At least I don't see the benefits of a consolidation. I would rather
> > ask all PMC members to subscribe to all dev list than merging the
> > lists. Not to talk about the mailing list archive confusions and
> > hassle this might create.
> >
>
> <snap/>
>
> My claim is that sharing a mailing list is a solved problem. sebb
> pushing out BSF 3.0 is an example of someone stepping up for another
> component -- more exception than rule, yes.
BTW, I was already subscribed to BSF-dev because JMeter uses BSF.
Likewise I'm subvscribed to Commons-dev.
>
>
> > ....but well - that's just my opinion and the -1 should not be
> > blocking. Just saying that I don't like the idea.
> >
>
> <snip/>
>
> Sure, and I'm not trying to get you to like it, rather to understand
> your initial response a little better. Thanks for elaborating.
>
>
> -Rahul
>
>
>
>
> > cheers
> > --
> > Torsten
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sat, Oct 10, 2009 at 2:04 PM, Torsten Curdt <tc...@vafer.org> wrote:
>> Care to elaborate a bit?
>
> I'd argue that for the people who care it's no big deal to subscribe
> to the various lists. So tuning in is no problem, tuning out once
> consolidated indeed is. It's an all-or-nothing. How is oversight
> better when everyone (or at least all PMC members) are subscribed to
> all dev list as opposed to just the one?
>
<snip/>
Its not. But expecting all PMC members to be on one dev list
constitutes a much gentler forcing function.
> While the one dev list might work OK for Commons I have the feeling
> that these projects are just too different. In Commons one could
> imagine to step up for another component. I don't see that with the
> rest that is left at jakarta.
>
> If there are many cross-posting (that would be a sign for
> cross-concerns) I haven't noticed any.
>
> At least I don't see the benefits of a consolidation. I would rather
> ask all PMC members to subscribe to all dev list than merging the
> lists. Not to talk about the mailing list archive confusions and
> hassle this might create.
>
<snap/>
My claim is that sharing a mailing list is a solved problem. sebb
pushing out BSF 3.0 is an example of someone stepping up for another
component -- more exception than rule, yes.
> ....but well - that's just my opinion and the -1 should not be
> blocking. Just saying that I don't like the idea.
>
<snip/>
Sure, and I'm not trying to get you to like it, rather to understand
your initial response a little better. Thanks for elaborating.
-Rahul
> cheers
> --
> Torsten
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by Torsten Curdt <tc...@vafer.org>.
> Care to elaborate a bit?
I'd argue that for the people who care it's no big deal to subscribe
to the various lists. So tuning in is no problem, tuning out once
consolidated indeed is. It's an all-or-nothing. How is oversight
better when everyone (or at least all PMC members) are subscribed to
all dev list as opposed to just the one?
While the one dev list might work OK for Commons I have the feeling
that these projects are just too different. In Commons one could
imagine to step up for another component. I don't see that with the
rest that is left at jakarta.
If there are many cross-posting (that would be a sign for
cross-concerns) I haven't noticed any.
At least I don't see the benefits of a consolidation. I would rather
ask all PMC members to subscribe to all dev list than merging the
lists. Not to talk about the mailing list archive confusions and
hassle this might create.
....but well - that's just my opinion and the -1 should not be
blocking. Just saying that I don't like the idea.
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sat, Oct 10, 2009 at 4:12 AM, Torsten Curdt <tc...@vafer.org> wrote:
>>> >>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?
>
> Not at fan.
>
> -1
>
Care to elaborate a bit?
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by Torsten Curdt <tc...@vafer.org>.
>> >>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?
Not at fan.
-1
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by sebb <se...@gmail.com>.
On 10/10/2009, Rahul Akolkar <ra...@gmail.com> wrote:
> On Fri, Oct 9, 2009 at 8:42 PM, Daniel F. Savarese <df...@savarese.org> wrote:
> >
> > In message <ce...@mail.gmail.com>, 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 cvs@jakarta.apache.org
> > 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
> > dev@jakarta.apache.org (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.
+0 to dev lists merging
+1 to commits merging (but not to same list as dev)
-1 to user lists merging
>
> -Rahul
>
>
>
> > daniel
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [PROPOSAL] One development list
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Oct 9, 2009 at 8:42 PM, Daniel F. Savarese <df...@savarese.org> wrote:
>
> In message <ce...@mail.gmail.com>, 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 cvs@jakarta.apache.org
> 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
> dev@jakarta.apache.org (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: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org