having read the thread so far, here's my feelings:
1. i feel strongly that JCS should not continue as a turbine sub-project.
2. i think that JCS could reasonably aspire to be a sub-project of either db or jakarta.
3. i think that the route for JCS to become a jakarta sub-project should be through the commons (in order to develop the strength required for a separate sub-project).
(i'm a little inclined towards db but) i'd support a proposal from the JCS team for a future in either db or jakarta (along the lines outlined above). guys - have you come to any opinions about what's the best option yet?
- robert
On 4 Dec 2003, at 17:45, Henning Schmiedehausen wrote:
On Thu, 2003-12-04 at 09:17, Daniel Rall wrote:
Jakarta Commons or the Incubator have been my preference for some time now. The
Incubator seems like a more appropriate place, as JCS could use some life
I was thinking about the incubator, too. But as projects failing to leave the incubator might drop off-ASF completely, we would put JCS (which is already ASF code) to the risk of being dropped out of ASF. That's why I suggested jakarta-commons.
(First rule of software acquisition: Once you have the code, never give it back. ;-) )
Regards Henning
-- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
--------------------------------------------------------------------- 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]
