But the project is a one-man codebase. It has no users (yet at least). It's not supported by the community. So I would like to get a community decision on what to do with it. Place your votes (anyway you like - vote multiple +1s if you feel like it):
1. Turn it into a full-blown project with manual, nicer code etc. In short - get out of the proof-of-concept stage. This means that the project must have community support - I can't be the only one supporting it.
+1--This could be merged with/supercede the Jakarta Commons Attributes sandbox.
2. Leave it where it is and in its current state - we'll get back to it later if we want.
+1
3. Move it to some other Apache project (please specify which).
Jakarta-Commons (merge with that project)
4. Move it to SourceForge or some other OS project place.
:/ If necessary we can host it at D-Haven.org but I would rather pursue an Apache owned place.
5. Kill it. Well just wait for Java 1.5 which is due Christmas and switch to it then. (Note that the attributes project gives us backwards compatibility for attributes, JDK1.5 doesn't.)
I think you did some good work, and it builds the foundation for a simpler container in the future. It can also be easily incorporated with the avalon-meta package in sandbox to read and build the meta model without too much trouble.
6. Merge with some other project (Attrib4J?, Commons-Attributes?). Please
make sure that the prject in question is still alive.
I would prefer Commons-Attributes if we do this. Kind of an eat your own dogfood type of thing.
I'll do whatever work is required, but I want to know that my actions are in line with community consensus.
:) Kool.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
