I don't have an oppinion on docs, but since there has been no maintenance I trust you guys that Anakia is a good solution. Anything is better than the current state, imo.
+1 for mailing list, and I believe it will also not hurt if everyone logs to sourceforge and subscribe to monitor the Open discussion forum (so we can get input from users of the tool that are not necessarily developers.) +1 for meritocracy Basically I am a big believer in not bugging other people with a very strict "policies" and just letting the developers that want to code submit patches and get these integrated in the head code asap. Code that does not work or break the tests will be flagged by the test cases, and naturally will be removed by one or more maintainers. More active CVS developement needs to be coupled with a better system to test the builds, but I can see that Jason and Kevin are already moving forward with this. The Apache project is recognized as a system that works and has produced excellent software. I believe it is wise for hsqldb to use the experience of apache/jakarta devs that want to contribute with this project, and hopefully get it going at full speed. Another option is to simply let the current development continue in SourceForge (with the current rules and process) and start a different branch based on the 1.43 sources as a subproject of Jakarta. I believe the license for 1.43 allows this, and the original developer has already stated that he has no interest in continuing hsql development. Regards, Mauricio Piacentini Tabuleiro _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
