So, here's what was in my mind when I was suggesting categories. I'm sure there will be some disagreements, but its a start ;-0
Core/JavaCore (aka J2SE) ---------------------------- - Each has a mission to fill key gaps in the J2SE. - Minimal dependencies. [lang] - extensions to the Java lang API [collections] - extensions to the Java collections API [primitives] - extensions to cover primitive collections [io] - (sandbox) extensions to the Java io API [reflect] - (sandbox) extensions to the Java reflect API Objects and Navigation ------------------------- - Basic management of Objects and navigating around them [pool] - object pooling [beanutils] - introspection and navigation of JavaBeans [el] - navigation of JavaBeans in line with JSP spec [jexl] - navigation of JavaBeans [jxpath] - navigation of XML and JavaBean structures Networking ------------ - all things http/html/ftp/network [fileupload] - support for fileupload [net] - support for various networking protocols [httpclient] - an http client XML ------ - all things xml [betwixt] - JavaBean to XML conversion [digester] - high level XML parsing assistant Enterprise (aka J2EE) ---------------------- - strictly server side [daemon] - server daemon [modeler] - J2EE JMX spec helper [messenger] - (sandbox) J2EE JMS spec helper Database --------- - all things db [dbcp] - database pooling [sql] - (sandbox) unified sql Other ------ [cli] - command line handling [logging] - log wrapper [discovery] - handling Java's classpath [attributes] - (sandbox) C# attributes in Java [cache] - (sandbox) general object cache [chain] - (sandbox) chain of responsiblity pattern [configuration] - (sandbox) helper for config [functor] - (sandbox) library encouraging small functors [resources] - (sandbox) helper for i18n config [threadpool] - (sandbox) pool for threads [vfs] - (sandbox) virtual filing system Standalone (New TLP) ----------------------- Should be, but has a community problem. [jelly] - XML scripting language Should be, but has licencing problems ATM. [hivemind] - application framework Maybe, although fairly new [math] - maths component --- (Note that the sandbox components are not all listed - I've excluded some without websites, and those that appear to be dead. Should really xref Henri's sandbox doc) These categories also reflect to some degree the personalities involved. To that end, potentially XML, DB and Enterprise could be merged to form a stronger group, with [discovery] and [logging] too. For oro/rexexp, there could potentially be a 'Text'/'String' group. Stephen From: "Justin Erenkrantz" <[EMAIL PROTECTED]> > So far, I've heard (from Stephen): > - XML > - HTTP/HTML/Networking > - Database > - Enterprise > - Pooling > > Here's my commentary on the above: > - XML: Should this be under xml.apache.org instead? > - HTTP/HTML/Networking: I'd split HTTP and HTML up as they aren't related. > (HTTP client and an HTML renderer should/would be separate codebases, I think) > - Database: Should this be under db.apache.org instead? > - Pooling: Can we be more specific? Memory pooling? Connection pooling? > > I've also heard 'Collections' and 'IO', but don't profess to know what that > means in context. > > As far as the ownership, I don't profess to know what the right thing is here. > What is the right thing for the XML and Database projects to own? Perhaps we > should create a dialogue with the appropriate PMCs? However, before doing > that, I'd like to know what the candidate projects are. What exactly are we > thinking of that would be 'database' and/or 'XML'? > > Thanks! -- justin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
