> Therefore, I am proposing that the jcrri code be moved out of > Slide and into the incubator as its own subproject, with explicit > encouragement of anyone who wants to work on JCR itself to join > that project as well.
I hear/share all your concerns and in general I welcome your proposal, but OTOH I do have some as well. 1. slide dependancy: I understand that the jcrri code has still quite a bit to do with slide, which is used as a backend (please correct me if I'm wrong). How would this affect the development process for all the stuff which doesn't clearly belong to slide or jcrri but affects both? 2. project scope. We all know that Tomcat is a RI as well, but its success has gone far beyond that. I would welcome jcrri as an Apache effort if the project scope is making a worthwile, performant and stable ASF-licensed implementation out of it, something that can be used in production: if, on the contrary, this impl is meant just as a barebone spec ri, it's still a very nice thing to have, but it could probably keep on living on slide as a more or less visible subproject. As a consequence, then, my first proposal would be rethink the name: jcr or jcrri aren't "product" names, and they smell bad of "just" RI (a quick "grep '.*j.*c.*r.*' /usr/share/dict/words" didn't blow my mind, the best alternative being "rejoicer". > Likewise, if you are already a Slide or other Apache project > committer, please let me know if you would like to be added > to the list of initial committers. Count me in, I'd be glad to help out in my Copious Free Time (urgh). Ciao, -- Gianugo Rabellino --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
