Sorry, I was unclear. I mean subproject of Cocoon, not subproject of xml.apache.org.
I'm fine for this to be a subproject of/under Cocoon. Ted On Mon, 2002-08-12 at 13:50, Nicola Ken Barozzi wrote: > > Theodore W. Leung wrote: > > This sounds very much like a subproject to me. Can you explain why you > > think this isn't just a subproject? > > - It depends very strongly on Cocoon. > - The code it starts with will, have parts come out of Cocoon. > - We would want the Cocoon committers have automatic karma to it. > - Other subprojects already have a similar this arrangement, albeit on > the sister project Jakarta, like Lucene, Avalon, Turbine. > - It doesn't have a project goal, but is more a repository of Cocoon > apps, a sort of Cocoon-Commons. > > On the other hand it would seem to be another subproject, since there > would be a different community round it, but this has also happened with > the cocoon-docs mailing list without creating a Cocoon-docs subproject. > Besides we would probably still want to use the Cocoon-dev and > Cocoon-user lists for it, at least in the early stages. > > Basically we are thinking about a Cocoon subproject, versus the fact > that the norm is to have Xml.Apache Sub-Projects. > > Can it be arranged? > > > On Thu, 2002-08-08 at 07:09, Nicola Ken Barozzi wrote: > > > >>Carsten Ziegeler wrote: > >> > >>>Ok, can someone of the PMC clarify this. > >>> > >>>We should not use the cocoon cvs for cocoon-apps, so a > >>>separate cvs is the way to go. I don't want to give all > >>>'cocoon-apps' committers also access to cocoon itself. > >>>So it must be separated. > >> > >>Dear PMC, we need your assistance. > >> > >>Cocoon is gaining more "sample" applications every day, and more are > >>being proposed. > >> > >>We are in the process of cleaning the repository by separating the core, > >>the implementation and the components in different directories. > >>We also need to remove those apps that are not part of Cocoon itself but > >>that are important to us and to the community. > >>Therefore, a consensus is forming towards the creation of a new CVS > >>module for cocoon-apps. > >> > >>The reason why I contact you is that this would not be a completely > >>separate project itself, since we want the Cocoon committers to be able > >>to commit, while having the possibility of voting in committers that do > >>not commit to Cocoon. > >>A kind of young-sister project. > >> > >>Now, this is not a subproject, but not really still Cocoon. > >>What is it? How can it be arranged? > >>Lucene has a similar arrangement IIUC... > >> > >>Also, we had the proposal of a Forrest committer, Steven Noels, who is > >>driving the effort, and hasalready made available equipement. > >>He proposes to host this effort with his company's equipement. > >>Does Apache think it's possible to host Apache stuff on another server? > >> > >>Thank you in advance. > >> > >> > >>-- > >>Nicola Ken Barozzi [EMAIL PROTECTED] > >> - verba volant, scripta manent - > >> (discussions get forgotten, just code remains) > >>--------------------------------------------------------------------- > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
