Re: [PROPOSAL] One development list
On 15.10.09 00:49, Henri Yandell wrote: Slightly less tongue in cheek - maybe now is the time to move ORO, Regexp and ECS over to Commons. I thought, Attic was the correct place, at least for ECS? Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
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 wrote: > [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. > > 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
Re: [PROPOSAL] One development list
Daniel F. Savarese wrote: In my opinion, JMeter should really go top-level, but the community has not yet (and may never) come to that conclusion. JMeter used to be just at the brink of being viable as a TLP. Mailing list traffic is stable and high, but the number of active developers was very close or maybe below the minimum three. There were a few occasions where Sebastian had to beg for additional reviewers to make a release. But I don't know whether that changed in the last year or so. Sebastian considered JMeter to be a part of the Jakarta community, and had to watch the rest of Jakarta dissolve around it. Unless the development community has grown beyond three, there is no natural or easy way out for JMeter. Perhaps we could combine all user lists except for JMeter. Yes, that would send a clear message: You're the odd man out. Like HttpClient getting a separate mailing list in Commons. ;-) cheers, Roland - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
Henri Yandell wrote: > On Wed, Oct 14, 2009 at 3:40 PM, Henri Yandell wrote: >> On Tue, Oct 13, 2009 at 12:31 PM, Daniel F. Savarese >> wrote: >>> >> >>> >>> Although I think we need to discuss and resolve what the future of >>> Jakarta is to be, I agree with Rahul that it should be a separate >>> discussion after resolving his more narrowly scoped dev@/commits@ >>> proposal. The only reason I haven't resigned from the Jakarta PMC >>> (after attic'ing ORO, now that there's an attic) is because JMeter >>> continues to use ORO and someone needs to be willing and able to >>> fix any issues that may arise. At least with a combined dev list, >>> there can be some assurance that other committers will be alerted >>> to any problems that require fixing (not that there have been any >>> for the better part of a decade). >> >> Help migrate JMeter off of ORO? :) > > Slightly less tongue in cheek - maybe now is the time to move ORO, > Regexp and ECS over to Commons. +1 > I'm happy to help out with the move if desired. If active projects > then moving to a new site style and JIRA would come up, but given the > lack of activity I think a gentler migration would imo be fine. > > Hen - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
On Wed, Oct 14, 2009 at 6:49 PM, Henri Yandell wrote: > Slightly less tongue in cheek - maybe now is the time to move ORO, > Regexp and ECS over to Commons. > > I'm happy to help out with the move if desired. If active projects > then moving to a new site style and JIRA would come up, but given the > lack of activity I think a gentler migration would imo be fine. > +1 - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
On Wed, Oct 14, 2009 at 3:40 PM, Henri Yandell wrote: > On Tue, Oct 13, 2009 at 12:31 PM, Daniel F. Savarese > wrote: >> > >> >> Although I think we need to discuss and resolve what the future of >> Jakarta is to be, I agree with Rahul that it should be a separate >> discussion after resolving his more narrowly scoped dev@/commits@ >> proposal. The only reason I haven't resigned from the Jakarta PMC >> (after attic'ing ORO, now that there's an attic) is because JMeter >> continues to use ORO and someone needs to be willing and able to >> fix any issues that may arise. At least with a combined dev list, >> there can be some assurance that other committers will be alerted >> to any problems that require fixing (not that there have been any >> for the better part of a decade). > > Help migrate JMeter off of ORO? :) Slightly less tongue in cheek - maybe now is the time to move ORO, Regexp and ECS over to Commons. I'm happy to help out with the move if desired. If active projects then moving to a new site style and JIRA would come up, but given the lack of activity I think a gentler migration would imo be fine. Hen - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
On Tue, Oct 13, 2009 at 12:31 PM, Daniel F. Savarese wrote: > > > Although I think we need to discuss and resolve what the future of > Jakarta is to be, I agree with Rahul that it should be a separate > discussion after resolving his more narrowly scoped dev@/commits@ > proposal. The only reason I haven't resigned from the Jakarta PMC > (after attic'ing ORO, now that there's an attic) is because JMeter > continues to use ORO and someone needs to be willing and able to > fix any issues that may arise. At least with a combined dev list, > there can be some assurance that other committers will be alerted > to any problems that require fixing (not that there have been any > for the better part of a decade). Help migrate JMeter off of ORO? :) Hen - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
In message <4ad4c6e2.2090...@dubioso.net>, Roland Weber writes: >Have you noticed how much traffic there is on jmeter-user? >It will easily drown all other communication on a combined >user list. Subscribers to any other Jakarta user list will >*not* be amused about getting all that into their inboxes. In my opinion, JMeter should really go top-level, but the community has not yet (and may never) come to that conclusion. It's similar to the relationship httpclient/httpcomponents once had vis a vis jakarta-commons. Perhaps we could combine all user lists except for JMeter. In any case, it was a suggestion meant to provoke exactly this kind of discussion (but it's clear now I should have started a separate thread). How one feels about the various ideas that have surfaced in this thread depends on whether one believes Jakarta should or can be revived, retired, or continue as is. Provoking discussion helps sort out exactly what we're trying to accomplish beyond administrative simplification. As you say, combining jmeter-user with a u...@jakarta list is probably not a good idea. But from my point of view, it's not because combining user lists is inherently unworkable. Instead, it's because JMeter is a vibrant project that should go top-level instead of residing in what some may view as Jakarta's almost-dead carcass. Another point of view might be that JMeter shouldn't go top-level at all and can serve as a focal point for reviving Jakarta. Although I think we need to discuss and resolve what the future of Jakarta is to be, I agree with Rahul that it should be a separate discussion after resolving his more narrowly scoped dev@/commits@ proposal. The only reason I haven't resigned from the Jakarta PMC (after attic'ing ORO, now that there's an attic) is because JMeter continues to use ORO and someone needs to be willing and able to fix any issues that may arise. At least with a combined dev list, there can be some assurance that other committers will be alerted to any problems that require fixing (not that there have been any for the better part of a decade). daniel - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
Daniel F. Savarese wrote: 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 That may work for Commons, because it is the established procedure there. It will not work as a newly defined procedure for a new all-Jakarta user list. Have you noticed how much traffic there is on jmeter-user? It will easily drown all other communication on a combined user list. Subscribers to any other Jakarta user list will *not* be amused about getting all that into their inboxes. Subscribers to jmeter-user will probably not even notice the additional traffic. http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-user/ cheers, Roland - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: Slide lists (was: [PROPOSAL] One development list)
http://mail-archives.apache.org/mod_mbox/attic-general/200902.mbox/%3ca3af8739-d168-44b6-8544-201f8d5b5...@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 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? 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-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
Re: Slide lists (was: [PROPOSAL] One development list)
On Sun, Oct 11, 2009 at 9:06 PM, 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? > 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-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: Slide lists (was: [PROPOSAL] One development list)
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 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. 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
Re: [PROPOSAL] One development list
On 11/10/2009, Rahul Akolkar wrote: > On Sat, Oct 10, 2009 at 2:04 PM, Torsten Curdt 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? > > > > > > 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. > > > > > > 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. > > > > > > 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-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
Re: [PROPOSAL] One development list
On Sat, Oct 10, 2009 at 2:04 PM, Torsten Curdt 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? > 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. > 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. > 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-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
> 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-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [PROPOSAL] One development list
> -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
Re: [PROPOSAL] One development list
On Sat, Oct 10, 2009 at 4:12 AM, Torsten Curdt 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-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
>> >>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-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
On 10/10/2009, Rahul Akolkar wrote: > On Fri, Oct 9, 2009 at 8:42 PM, Daniel F. Savarese wrote: > > > > In message , > 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). > > > > > > 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 c...@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 > > d...@jakarta.apache.org (also like commons). > > > > > > 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-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
Re: [PROPOSAL] One development list
On Fri, Oct 9, 2009 at 8:42 PM, Daniel F. Savarese wrote: > > In message , > 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). > 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 c...@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 > d...@jakarta.apache.org (also like commons). > 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-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [PROPOSAL] One development list
In message , 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). >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 c...@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 d...@jakarta.apache.org (also like commons). daniel - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
[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. 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
