Gianugo Rabellino schrieb:
As Slide 3.0 will introduce some major changes that will lead to Slide
level api incompatibilites, I'd vote for setting up a new CVS module for
Slide 3.0 as tomcat is doing the same for major versions. This would
give us the chance to set up a clean directory structure that reflects
our increased wisdom.
As the Slide subprojects are big ones (server,clientlib,
commandlineclient, testsuite, projector,...) it might also be a choice
to split them into different cvs modules. What do you think about this?
This would lead to the question if we should try to shift Slide to
apache top level (webdav.apache.org) to give the users a better
understanding what Slide is all about and to simplify the access to the
different subprojects.
I know I don't quite belong here, but just wanted to throw my .2 cents
with a couple of thoughts:
1. I'd be glad to see Slide grow as a TLP, but wouldn't webdav.apache.org
be somehow limiting, given that Slide isn't just a webdav server (JCRRI
being the first and foremost feature beyond webdav)? Also, it might clash
with mod_dav somehow...
Slide is more than just the server, it contains different subprojects
dedicated to WebDAV. So I'd still the idea of having a TLP called webdav...
2. Isn't it a good time for webdav folks to move to Subversion? :-) You
have no idea on how it made my life easier: apart from being generally
better, faster and nicer, as a roadwarrior, I have to painfully grab CVS
snapshot whenever I get to an open Internet access. When I'm behind a
nasty firewall, and it happens quite frequently, I'm relieved to know that
I can always access the latest versions of the sources via plain HTTP.
Yes, good idea as subversion is also using WebDAV/DeltaV as it's
protocol :-)
Ciao,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
