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.
I like the package better than everything else in this area. As such I'd like to see it become a de facto standard. But I'm not really feeling like putting in a lot of work to make that happen; my interest is in other areas atm. I can help do releases 'n stuff and answer user questions though. That said, since you volunteered already and you're just asking for opinions, I'll vote anyway.
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 thing fits our bill, it works well, we have a need for it right now, so this is a good idea. If cvs access restrictions become an issue, that is a technical issue easily solved.
2. Leave it where it is and in its current state - we'll get back to it
later if we want.
-0. History shows this is a bad idea for us.
3. Move it to some other Apache project (please specify which).
+1. jakarta-commons or apache-commons. I think this baby should stay small, hence not to incubator imo. It would just migrate back here :D
4. Move it [elsewhere]
+0
5. Kill it.
-0. It is a good package already and has more potential.
6. Merge with some other project
+1. Maybe integrating into QDox or XDoclet is an option. Other projects seem a little orphaned and/or silent.
I'll do whatever work is required, but I want to know that my actions are in line with community consensus.
good call, but your call :D
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
