As a side note I would want to remark that both "problems" are a bit exaggerated: not everything has found its way into Slide, but only stuff related to WebDAV and there has been a community right from the start of the Slide project :)
Cheers,
Oliver
Stefano Mazzocchi wrote:
Group,
I find the slide project problematic for two reasons:
1) the scope of the project has been so loosely defined that you can find almost everything and its granma in the slide CVS
2) the community has been non-existant until a few weeks ago [but things are getting much better now]
Since I believe that 1 and 2 are related (1 is the effect and 2 is the cause) and since 2 seems to be getting better, I would like to propose that we retarget the scope of the slide project a little.
These are the things that are currently found in the slide CVS:
- the Slide repository core - the WebDAV/DeltaV/DASL/ACL stack implementation on top of the Slide core - a few slide stores
- a WebDAV/DeltaV/DASL/ACL test tool
- a WebDAV client library (generic) [works, used in cocoon]
- a CLI frontend for the client library [didn't try]
- a Swing FileChooser-like frontend for the client library [didn't try]
- a GUI (DAVexplorer-like) frontend for the client librar [doesn't compile]
I propose to split the above stuff in three different CVS modules, respectively (with the grouping above)
- jakarta-slide - jakarta-slide-test - jakarta-slide-client
The reason for the separation of the tests from the slide core is that I believe that those tests could be extremely valuable for general WebDAV stacks and should have anything to do with Slide by itself. Moving it away from slide allows us to give commit access on different repositories, for example to new people coming in and willing to work only on the client side or the tests.
What do you think?
-- Stefano.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
