I think that open source ideals are important and very much based on community, but it is easy to see by the trailing sentence (sum: 'if you wanna buy a decent version of the unreadable, insurmountable bees nest that we have created, please buy it from me') that the wrong folks are in charge here. Please correct me if I am wrong but I do not recall _ever_ seeing a post like that on the Tomcat/Struts/ORO/POI/Turbine/Jetspeed lists. And yes, I have given freely, both in time and code, to other Jakarta projects.
Considering that both Struts and Turbine live under the same roof, I would certainly say something is in order to either get Slide on a release schedule (if the CVS works well today why isnt this being released as a beta? why not create a branch and do bug fixes on the things that are implemented ?? these arguments make no sense.) or to branch it off and forget about the latent current fork. Besides many different projects have been branched in success when the goals were not unified - Samba/Samba-TNG, Emacs/Xemacs, etc etc.
Regards and wish it could have been a shorter mail :) , Jeremy Kuhnash
Pill, Juergen wrote:
Hello all,
I regret, if you are unhappy with the current Slide situation. Slide
consists of many pieces (e.g. WebDAV client API, server, cm API, GUI and
command line clients, etc). Some of those are actively worked on; some of
those are currently under lower development.
1) Release of next slide version There was a call last year to release slide version 2. At this point in time most responding people felt, that it would be too early to release. There were some areas still under heavy construction. We could issue this release call again.
2) WebDAV client API The WebDAV client API contains basic support of Delta-V, but higher level methods are not implemented. This is due to the fact, that JSR 147 is arising, which will be THE standard interface for a Delta-V enabled client. Currently this JSR 147 implementation is under construction. We will make it publicly available in Slide, when major parts can be used. Anyway pre-views could be found in Slide soon.
3) WebDAV command line client Currently this part is not completely Delta-V aware. I personally would suggest to use the JSR 147 API, when available.
4) CM API Remy just lately announced to support the JSR 170 support at the Slide CM API level. The JSR 170 will be the basis for further extensions. I have seen some JSR 170 related check-ins already.
5) Documentation This is a major (missing) point too. It was mentioned as a release blocking issue at last years next version call.
We will accept very happily any help, you did offer in your e-mails.
Especially documentation was mentioned more than once. We could make Slide
this good, that even newbies get an easy and comfortable jump to the very
powerful Slide functionality. You are part of the Slide community (if you
feel so) and with you together we make the open-source project working.
If you wish to get a ready-to-use product (integrated stores, installation, with guarantied support, and lots more) I would recommend following link: http://developer.softwareag.com/tamino/webdav/default.htm (Sorry, I could not resist)
Best regards,
Juergen
P.S. I know all committers are extremely busy and hard working (not only for Slide).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
