I suggest we go for whatever solution allows us to get development of tools
such as the sitemap editor moving quickly. One of the important factors that
will decide the success of Cocoon in the long run will be the availability
of tools.
So either include it in the Cocoon CVS or go for sourceforge. I think that
it would be best to go for Cocoon CVS as this would allow Cocoon to become a
"complete" package (building up tools as we go along) and also make sure the
tools stay in sync with Cocoon (which may be more difficult if they are on
SF).
Also - the developers would probably be the same as those currently working
on Cocoon (or come from the same groups) - At least they would in our case
:-)
Matthew
--
Open Source Group sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30 [[EMAIL PROTECTED] - http://www.sundn.de]
=================================================================
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 9. Juli 2001 10:25
An: [EMAIL PROTECTED]
Betreff: RE: AW: [C2] sitemap editor
> > > 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
