I'm a few hours beind in this thread but... I like the idea of a Jakarta sandbox. Maybe we could put a page on the Jakarta web site with a few paragraphs explaining purpose and criteria. My impression is that this is an informal way to start exploring a new project or codebase - is that right? (and I'm assuming with looser standards regarding release and version numbering). It makes sense to make this Jakarta level - why force someone to be part of the commons community when doing this?
This could be a good first step in equalizing Jakarta and commons. WILL On 3/6/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > Over on Commons-Dev, Stephen has suggested that we split some of the > components out to form a Jakarta Language Components group. Consensus > is in favour of the idea, so I'm sure we'll see a vote on that and some > movement soon. > > Commons ID (and Commons CSV perhaps) are two elements in the Commons > Sandbox which would potentially go to JLC, but there are (wisely) no plans > for a separare JLC Sandbox. > > Additionally we have Jakarta Web Components, which will take on various > bits - including Jakarta Taglibs (can't recall if the Standard Taglib > would go in there or not). That has a Sandbox as well. > > Lastly we have Jakarta HTTP Components - formerly Commons HttpClient - > which technically lost access to its sandbox - though I suspect it's been > a long time since it used it. > > To that end, I'd like to propose that Commons Sandbox and Taglibs Sandbox > merge into Jakarta Sandbox - servicing all of Jakarta - though I imagine > it would mostly be the component groupings. > > Thoughts? > > Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- _______________________________________ Forio Business Simulations Will Glass-Husain phone (415) 440-7500 x89 mobile (415) 235-4293 [EMAIL PROTECTED] www.forio.com
