Hehe... Slide: The Resurrection - LOL.. Let me be clear here - I am not trying to usurp control of Slide. If there needs to be a leader with a vision to take Slide to the next level and no one steps up, I'll seriously consider it and step up. The plan I laid out I would hope will align with the Slide group and we could come up with a plan that could be led by whomever leads Slide, with some additional help by those that have volunteered on this list. If it doesn't fit with the Jakarta Slide vision, I believe then it could move to another project and become a focused vision to achieve the goals I outlined without usurping control from the Slide team.
As for whether docs or refactoring I have to ask - why are they mutex? It seems that we have some people that need docs. If those people are willing to contribute with someone designated as "editor" to outline and manage the pieces, each chunk could be farmed out and generated. I could see people that have pieces like Using the WebDAV client APIs, Extending the Slide Kernel, and even an example application that is threadsafe, uses other Jakarta projects like Struts, etc. While this is happening, a refactoring on a separate CVS branch could occur and the documentation updated to reflect the changes after an initial cut is produced. That way, people can go with the more stable codebase and utilize the newly created docs, while a new version and doc set is being generated. Basically, there are 2 *very generalized* views I take with an OSS project - do it fast or do it right. Do it fast if you are scratching an itch that is urgent and allow others to share/contribute to the solution by making is OSS; do it right in all other circumstances and prove that not only can an OSS project solve a problem, but it can solve it in a clean manner. JBoss is my inspiration for this, as they are professionals that produce a top notch product, which is released as LGPL. I figure it won't take long for someone like BEA to dump their internal codebase and build on top of JBoss to save time and support costs. My reasoning for this: its top quality, not a script kiddie OSS project. Let's get a clear vision, take Slide to the next step, and make it really shine as yet another quality Jakarta project. James > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 3:07 AM > To: Slide Users Mailing List > Subject: RE: newbie question about slide future > > > > I am working solely on the WebDav client-side, so I am happy > to extrapolate it out of the existing Slide project as > suggested by James and make it shinier, etc. > > Has anyone actually _ever_ had any response from a developer > on the project that they can get in touch with to let them > know our plans? > > I suggest James be the chief-coordinator of our new project > "Slide Resurrection" (call it whatever you like!) and Eelco > be deputy. I think some centralised co-ordination is essential. > > What do you think? > > Thanks, > Portia > > > > |---------+----------------------------------> > | | "James Higginbotham" | > | | <[EMAIL PROTECTED]| > | | arkets.com> | > | | | > | | 12/03/2003 21:13 | > | | Please respond to | > | | "Slide Users Mailing | > | | List" | > | | | > |---------+----------------------------------> > > >------------------------------------------------------------- > --------------------------------------------------| > | > | > | To: "Slide Users Mailing List" > <[EMAIL PROTECTED]> | > | cc: > | > | Subject: RE: newbie question about slide future > | > > >------------------------------------------------------------- > --------------------------------------------------| > > > > > I've experienced the same thing.. Actually, I want to put > together a proposed architecture change and either get commit > access or just branch and be a rebel ;) Here is what I'd like to see: > > 1) break the webdav client out into a separate project - it > should belong in commons, not in Slide > 2) break the current slide codebase into 2 areas: > a) Content server - a kernel that is capable of doing > versioned, workflow oriented content management and could be > the core of any CMS system > b) Content API - access to the content kernel via a number > of gateways, including (but not limited to): EJB, JMX, WebDAV/DeltaV > 3) Create a basic CMS system on top of the framework to prove that: > a) it can be done and > b) How to use the system > 4) Enhance the docs to provide better information from the perspective > of: > a) Extending the kernel (stores, interceptors, etc) > b) Writing to the framework using any of the gateways > c) Using/extending the example CMS system > > I originally started using Slide to build a CMS for my > church, and have found now that although nothing better > exists out there in the OSS world, this isn't as easy as I > thought it would be - mostly due to the lack of support and > poor code. For example, I want to lock a resource, but to do > that I have to copy/paste the logic from the LockMethod.java > that services webdav requests with 5 or 6 lock calls. Why not > have a LockCommand.java that is called from any gateway, > whether its from the webdav servlet (aka the LockMethod > class) or from my own Struts application (or for that matter, > even a JMX client within JBoss)? I've also seen some postings > of those trying to get the J2EE store to operate properly > within a UserTransaction and many failures resulting of that, > so some work on the stores themselves would be required. > > Now, I've actually considered backing off and just writing some > OJB->MySQL code to do what I need, but knowing that the > bazaar approach > is always "start from something that works and add to it", > I'd rather gain the knowledge of what the Slide authors > gained while writing it than stumbling over the same problems > again - even if I don't use the webdav gateway at all. > > Thoughts? > James > > > > -----Original Message----- > > From: Parker, Steve L. [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 12, 2003 11:16 AM > > To: 'Slide Users Mailing List' > > Subject: RE: newbie question about slide future > > > > > > I have experienced similar problems with getting any help or > > guidance.. I could get basically no response from anyone. > > > > The resulting effect on a potential user is that one becomes very > > unsure whether it is a safe bet to use this thing. One > simple (or not > > so simple) thing to do would be to have a more understandable and > > comprehensive documentation. There are several different ways of > > using Slide. For instance, use the WebDav Servlet, or just use the > > lower level API.. > > > > Are there any parties out there interested in > joining/helping out in > > Slide? > > > > Are the developers/committers out there?? How can we help out? > > > > Slide seems like solid code, but it is not at all presented > well.. We > > are using it on a pretty big project, and would definitely love to > > help out! > > > > Steve > > > > -----Original Message----- > > From: Jeremy Kuhnash [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 12, 2003 11:54 AM > > To: Slide Users Mailing List > > Subject: Re: newbie question about slide future > > > > > > Not only that but it would appear that the current > > maintainers/developers do not do much to support the > current questions > > on the list. > > > > This is probably the most neglected Apache Jakarta project and it > > should be released and replaced with some other Apache license > > compatible WebDav system, in my opinion. > > > > > > Nikos Vitalis wrote: > > > > >Hi, > > > > > >i am new to slide and noticed that the last stable version > > (1.0.16) was > > >released almost 1.5 years ago. Why did it took so long? Is > a further > > >release planned? > > > > > >Thanks in advance > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > ************************************************************** > ******************** > This email may contain confidential material. If you were not > an intended recipient, please notify the sender and delete > all copies. We may monitor email to and from our network. > > > --------------------------------------------------------------------- > 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]
