Is there anybody (at least one person) who is in the process of getting commit status (so sending in patches which are picked up by team members)?
Has the apache organisation any internal procedure to revive slow going projects? gr. Martin Taal On Monday 30 June 2003 13:09, you wrote: > ----- Original Message ----- > From: "James Higginbotham" <[EMAIL PROTECTED]> > To: "Slide Users Mailing List" <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Monday, June 30, 2003 5:31 PM > Subject: RE: Who is using slide in production environment? > > > Hi, > > Disclaimer: I'm not a commiter nor do I represent the Slide team, but > here are my findings as a user of the framework. > > There are mailing list archives that discuss the status, but basically > all of the team members are busy with other projects. The project needs > a dedicated lead with commit and version rollout status, but before you > can do that you have to submit patches to the project to fix bugs. Once > they see that all is well with you, you can get commit status and then > hopefully help stabilize the product and maybe get a 2.0 rollout done. > Slide is a great project with a lot of effort out into it that has been > neglected recently. I think with some dedicated help, it could become a > fantastic framework - time which most on this list (including myself) > just can't dedicate right now. > > I've found that it makes a great DAV/Delta-V server framework with nice > things like interceptors on the server side for hooking other processes > into the framework. If you don't need that, you can decide whether a > pre-canned solution will work better since this project gets little > attention code/bug wise. Also, the framework is really good for document > management via DAV, or dedicated content management without DAV with a > lot of work to make it do what you want. It has no good examples to > learn from, other than a non-thread-safe struts admin client that is > mostly-read-only. Most projects built off of slide are for internal > intranet or commercial products, so you will find mostly consumers > rather than producers to the framework (beyond basic bug fixes). The > framework was built to facilitate DAV, and later DeltaV, but was never > really architected for a true CMS application framework. Much of the > frameowk requires you to be in the same classloader (no cross-VM > invocation framework) and all of the versioning code is tied to HTTP and > the DAV servlet that handles incoming DAV/DeltaV requests. There is some > work around making this framework handle the upcoming JSRs (170 and 147 > *I think*) that define a CMS API. The webdav client API uses HTTP > commons client and is stable, but a little tough to figure out (the API > was built around the spec rather than a convienant API). I think Slide > is the most neglected project @ Jakarta, and I hope this changes soon. > > In the past I submitted a proposal for a revised architecture for Slide, > from the perspective of an architect who is trying to use Slide as a CMS > kernel in a webapp (webdav being nice but not a requirement for my > needs). Here is the MARC link: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg03616.html > > Followup discussions are shown at the bottom and clarify a few issues, > specifically: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg03618.html > > Hope this helps you determine if this framework will work for you. Take > a look, give it a spin, and see what it can do for you. If it does most > of what you want, you can contribute a little work and get it to do what > you want it to do without rebuilding from scratch. I hope to do that > soon when time allows, but for now I have to locate a precanned CMS > solution as I have not the time to dedicate. Slide will make a wonderful > doc mgmt framework (like MS SharePoint) and, with a little help, a CMS > framework. > > Regards, > James > > > -----Original Message----- > > From: Michael Oliver [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 30, 2003 10:12 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Who is using slide in production environment? > > > > > > Ditto on Martin's request with the added question, what is > > the state of the development of Slide, it seems to be stalled > > and no progress to speak of in the last 18 months or so. > > > > Michael Oliver > > CTO/Matrix Intermedia > > 7391 S. Bullrider Ave. > > Tucson, AZ 85747 > > Office (520)574-1150 > > Cell (518)378-6154 > > > > Martin Taal said: > > > Hi All, > > > We are considering to use slide as a content repository > > > > layer in our > > > > > application framework. Although I see some modest traffic on the > > > mailing list I am not sure if and how slide is used in practice. > > > > > > So my question is: is there a list of live > > > > products/projects in which > > > > > slide is being used? If not, I am just interested from > > > > others if and > > > > > how they are using slide in live products/projects. > > > > > > -- > > > > > > With Regards, Martin Taal > > > > > > Springsite > > > Barchman Wuytierslaan 72b > > > 3818 LK Amersfoort > > > tel: +31 (0)33 462 02 07 > > > fax: +31 (0)33 463 77 12 > > > Mobile: +31 (0)6 288 48 943 > > > email: [EMAIL PROTECTED] > > > web: www.springsite.com > > > > --------------------------------------------------------------------- > > > > > 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] -- With Regards, Martin Taal Springsite Barchman Wuytierslaan 72b 3818 LK Amersfoort tel: +31 (0)33 462 02 07 fax: +31 (0)33 463 77 12 Mobile: +31 (0)6 288 48 943 email: [EMAIL PROTECTED] web: www.springsite.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
