Reposted (edited) from original commons proposal. Currently this proposal has general, though not unanimous, support. A vote thread may follow this thread if the mood remains positive.
I hereby propose the creation of a new Jakarta entity named 'Jakarta Language Components'.
This will be formed from the following codebases: [lang] [io] [collections] - expected to divide [primitives] [codec] [id] - on exit from sandbox [beanutils] - logging to be removed The following are invited to join if their communities desire: [oro] [regexp] [cli] Jakarta Language Components mission: 'Enhancing Java SE' Jakarta Language Components will: - develop multiple independent components - each component will have no dependencies - each component will have no configuration - each component provides an extension to the JavaSE - code judged by would it be out of place in the JavaSE - a component typically has a broad API (many callable methods) - each method typically does relatively little processing - have mailing lists (language-user/language-dev) - not have a sandbox - use [EMAIL PROTECTED] ML (new) for cross group issues Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
