Re: xmlbeans project
Ted, Ok, Is the issue here being @xml vs being @incubator? If they need to be @incubator that's totally fine with me. Or is there something that I'm missing? IIUC it's all there is to it. If you look at this message in the [EMAIL PROTECTED] mailing list it seems clear that they went into the incubator @jakarta http://archives.apache.org/eyebrowse/ReadMsg?listId=129&msgNo=2 So incubator folks, what is the correct policy here? Both Tapesptry and Lenya were special cases. We've set policy since then. All new projects come through Incubator (mail lists, sites, CVS). Best to just go with the flow. One would also hope that future projects coming in take a while to incubate, and don't declare "success" and exit a mere couple of months after arriving. There is no allegation there of course :-) - Paul (Incubator PMC member). -- http://www.thoughtworks.com -> The art of heavy lifting. Home for many Agile practicing, Open Source activists... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlbeans project
Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: > >> I do not see much sense in moving mailing lists arround. Please > >> avoid such needless work. > > Then incubating would be needless work anyhow, we would make the project > go live as final right away 8-> I do not hope that the main sense of the incubator is to have separate mailing lists... > The problem is that by creating the CVS and ML space in the final > destination, the project actually behaves itself as it was already fully > accepted by ASF, which is *not* the case. I agree that there is a problem but I do not like the solution. What about a one-line automatic signature added to mails which are sent to these mailing lists? > Renaming a ML or a CVS module is a trivial thing to do. While it is not a big change "trivial" is not precisely true. Subscribers have to update their mail filters/sorting mechanisms, mail archives have to be merged somehow (or old contributions effectively become unfindable) etc. And sometimes one of the mailing lists or Bugzilla-entries are simply forgotten in the process - which can lead to missed mails. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Policy for incubating project resources (was Re: xmlbeansproject )
Since IMHO this has been already discussed enough and different POVs remain, I ask for a vote on the following. What should we use as a policy in creating resources for incubating projects? [ ] project-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [ ] incubator-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Please vote. Here is mine: [X] incubator-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy for incubating project resources (was Re:xmlbeans project )
IMHO it depends on what the incubator PMC does. If they *do* create the lists and the such then maybe they should set policy (meaning telling other people what do do == policy). If they rely on the XML project and the XMLBeans folks to do things then they should allow the XML project and XMLBeans folks to set their own policy. -Andy On 7/24/03 9:48 AM, "Nicola Ken Barozzi" <[EMAIL PROTECTED]> wrote: > > Since IMHO this has been already discussed enough and different POVs > remain, I ask for a vote on the following. > > What should we use as a policy in creating resources for incubating > projects? > > [ ] project-subproject CVS >[EMAIL PROTECTED] >[EMAIL PROTECTED] >[EMAIL PROTECTED] > > [ ] incubator-subproject CVS >[EMAIL PROTECTED] >[EMAIL PROTECTED] >[EMAIL PROTECTED] > > Please vote. > > Here is mine: > > [X] incubator-subproject CVS >[EMAIL PROTECTED] >[EMAIL PROTECTED] >[EMAIL PROTECTED] > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy for incubating project resources (was Re: xmlbeans project )
On 24/07/2003, at 03:48, Nicola Ken Barozzi wrote: Since IMHO this has been already discussed enough and different POVs remain, I ask for a vote on the following. What should we use as a policy in creating resources for incubating projects? ... I'm not on the incubator pmc but I'd like to see the following policy: [X ] incubator-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Cheers, Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlbeans project
On 7/24/03 4:21 AM, "Paul Hammant" <[EMAIL PROTECTED]> wrote: > Ted, > Ok, Is the issue here being @xml vs being @incubator? If they need to be @incubator that's totally fine with me. Or is there something that I'm missing? >>> >>> >>> >>> IIUC it's all there is to it. >> >> >> If you look at this message in the [EMAIL PROTECTED] mailing list >> it seems clear that they went into the incubator @jakarta >> >> http://archives.apache.org/eyebrowse/ReadMsg?listId=129&msgNo=2 >> >> So incubator folks, what is the correct policy here? > > Both Tapesptry and Lenya were special cases. We've set policy since > then. All new projects come through Incubator (mail lists, sites, CVS). > Best to just go with the flow. One would also hope that future projects > coming in take a while to incubate, and don't declare "success" and exit > a mere couple of months after arriving. There is no allegation there of > course :-) Good thing its not an allegation because Tapestry took nearly a year. > > - Paul > (Incubator PMC member). -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy for incubating project resources (was Re: xmlbeansproject )
This is embarrassing. How can we have incubated several projects and not have this worked out? No wonder people are complaining about the incubator. Nicola Ken Barozzi wrote: Since IMHO this has been already discussed enough and different POVs remain, I ask for a vote on the following. What should we use as a policy in creating resources for incubating projects? [ ] project-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [ ] incubator-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Please vote. Here is mine: [X] incubator-subproject CVS [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy for incubating project resources (was Re: xmlbeans project )
On Thursday, July 24, 2003, at 07:23 AM, Andrew C. Oliver wrote: IMHO it depends on what the incubator PMC does. If they *do* create the lists and the such then maybe they should set policy (meaning telling other people what do do == policy). If they rely on the XML project and the XMLBeans folks to do things then they should allow the XML project and XMLBeans folks to set their own policy. I agree. If a new project already has a prospective home, and that PMC wants the mailing lists and CVS in their namespace, then go for it. If a project has no prospective home, or the hopeful home's PMC isn't totally on board yet, then they can always have @incubator. -aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy for incubating project resources (was Re: xmlbeans project )
On Thursday, July 24, 2003, at 11:20 AM, Ted Leung wrote: This is embarrassing. How can we have incubated several projects and not have this worked out? No wonder people are complaining about the incubator. It was never this big of an issue then (and I still don't think it's that big of an issue). -aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy for incubating project resources (was Re: xmlbeans project )
> This is embarrassing. How can we have incubated several projects and > not have this worked out? These problems are typical for self-incubating incubators ;-) Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
