Re: Re: Re: Opening up the PMC
The problem with moving Commons up is that when you look at where Jakarta needs to go, and when you look at where Commons generally is now; they are the same places - and it's hard to distinguish between the focuses. Hm... interesting... funnily I have never seen it like that before. Always had the impression jakarta is for products while commons is for libraries. Sometimes it's just not that clear where to draw the line though. Jakarta needs a way to blend community oversight with small numbers of active committers per component. That's pretty much Commons. For a start, I would merge BCEL, BSF, ECS, JCS, ORO and Regexp dev lists into either [EMAIL PROTECTED] or [EMAIL PROTECTED] Why that combination? ...feels quite unnatural to me - I am sure so it will for the users. Combining mailinglist would definitely get a -1 from me. I don't want the few BCEL subscribers left to unsubscribe because they get annoyed because they are receiving mails they are not interested in. We might get away with that at commons - but in general I think it's quite a bad idea. 1) BCEL, BSF, ECS, JCS, ORO and Regexp dev lists merging 2) Alexandria dies 3) POI to TLP 4) Consider merging user lists from 1) 5) Flatten HttpComponents, Velocity, Taglibs. Some mad ideas :) Sorry that I have to agree with the last sentence in some extend ;-) cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Opening up the PMC
On Thu, 17 Aug 2006, Torsten Curdt wrote: The problem with moving Commons up is that when you look at where Jakarta needs to go, and when you look at where Commons generally is now; they are the same places - and it's hard to distinguish between the focuses. Hm... interesting... funnily I have never seen it like that before. Always had the impression jakarta is for products while commons is for libraries. Sometimes it's just not that clear where to draw the line though. Yup. Compare Jelly to ECS or Regexp. Jakarta needs a way to blend community oversight with small numbers of active committers per component. That's pretty much Commons. For a start, I would merge BCEL, BSF, ECS, JCS, ORO and Regexp dev lists into either [EMAIL PROTECTED] or [EMAIL PROTECTED] Why that combination? ...feels quite unnatural to me - I am sure so it will for the users. It's our list of small largely inactive subprojects. We know that none of those are going to go TLP, and their dev lists are quiet by an order of magnitude compared to an inactive TLP potential project like Slide. Combining mailinglist would definitely get a -1 from me. I don't want the few BCEL subscribers left to unsubscribe because they get annoyed because they are receiving mails they are not interested in. We might get away with that at commons - but in general I think it's quite a bad idea. We've a bunch of relatively small codebases and subprojects that on their own are a stretch to maintain oversight over. It's a match for the Commons approach of having those communities share the same space and help each other on general issue topics, such as releases. The reason I don't suggest moving to commons-dev is that that would definitely be too much of a shock to those on the current dev lists, and even with those lists being combined traffic is still going to be low. I also don't suggest a merger of the user lists anytime soon. 1) BCEL, BSF, ECS, JCS, ORO and Regexp dev lists merging 2) Alexandria dies 3) POI to TLP 4) Consider merging user lists from 1) 5) Flatten HttpComponents, Velocity, Taglibs. Some mad ideas :) Sorry that I have to agree with the last sentence in some extend ;-) *grin* Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[intent] Retiring Alexandria
I think that the Incubator has the right concept/label in retiring projects, so I plan to create a link on the right hand side of the Jakarta site called Retired Projects and to create a retired page that contains links to the Alexandria site and the java.apache.org site. If anyone feels -1-like, then go for it else I'll do it on Friday evening. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [intent] Retiring Alexandria
+1 from me. On 8/17/06, Henri Yandell [EMAIL PROTECTED] wrote: I think that the Incubator has the right concept/label in retiring projects, so I plan to create a link on the right hand side of the Jakarta site called Retired Projects and to create a retired page that contains links to the Alexandria site and the java.apache.org site. If anyone feels -1-like, then go for it else I'll do it on Friday evening. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]