> > > Hmm... I'm not sure but would prefer the separation into its own
> > > CVS repo. But
> > > also how concerned should such tools be to Cocoon 2? I might put
> > > in other tools
> > > that we've developed in conjuction with C2 but are usable in any
> > > other context
> > > (I'm talking about our xml-java toolkit).
> > >
> > Sounds interesting!
> >
> > We could set up a new cvs with a more open name, like xml-tools
> > and make there a subtree cocoon2.
>
> Ehm... this touches other areas in the XML project. I don't
> know if it will be a
> good idea to go through the approval process for it, but it
> will make sense,
> sure. Would you commit yourself to such a project? Any other
> developers? This
> needs to be checked out because the PMC will not allow a new
> projects without a
> Apache member holding hands (that would probably be me) and
> some fund of
> developers pushing it forward.
I suppose sourceforge is as good as an option for a new project, if only to
find out whether it is able to gather a developer community around it.
http://httpd.apache.org/related_projects.html lists a lot of related
projects, most of them not hosted by the Apache Foundation - the same is
true for Comanche (http://www.covalent.net/projects/comanche/) which is
something like the smgui equivalent for the Apache httpd.
Perhaps the administrative burden of going through PMC approval would be too
much for something which is currently a one-mans-effort.
my .02 euros
</Steven>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
