(we've done some talking on the pmc list and turbineers have discussed this in the past but since it's not really confidential i'm starting this thread to give everyone a chance to participate.)
some information about Turbine-JCS:
* JCS has no release * other apache products depend on JCS * JCS is not really directly related to turbine
concerns:
* JCS is a sub-sub-project with it's own mailing list (this kind of structure has proved difficult to properly supervise)
* JCS's health
* want to find the 'right' place for JCS
------------------------------------------>8
Andy: There most definitely are Turbine people (count me in) - but as Robert suggests above, with it's own mailing list many of us are unaware of JCS.
The connection between Turbine and JCS is Torque, which was spun out into db.apache.org some time ago. JCS could well receive more attention if it was located somewhere more appropriate - more attention leads to more users and developers.
Without knowing too much, should perhaps "JCS to db top level" and "JCS to db commons" also be considered options?
Of the available options below I have selected jakarta commons more by excluding the other options than because of some perceived positive fit in jakarta commons (though commons is a good place to be no doubt).
------------------------------------------>8
[ ] leave JCS within turbine [ ] JCS to apache commons [x] JCS to jakarta commons [ ] JCS to jakarta top level [ ] JCS to incubator [ ] something else (please specify)...
--------------------------------------------
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
