I want to preface this with the understanding that I am not out to alienate anyone or throw away good work, but the idea of a new project has entered my mind more than once. Since Micheal has yet to comment (that I have seen), the status of this most recent effort could be all for naught. I, for one, have very real and pressing issues for wanting to get on with this, so I am curious what the response of this community would be toward starting a new project. Mark has mentioned it here, and Mauricio had also mentioned it in a previous post which I quote below. Could the two groups could work together, sharing code and ideas, but under different processes? Would people here be willing to consider this as a real option?
curiously jim [EMAIL PROTECTED] wrote >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. [EMAIL PROTECTED] wrote: > >>-----Original Message----- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >> > > < - snip - > > >>>Michael is currently overseas, with limited access to >>> >>email, so we may not >> >>>hear from him on this subject. >>> >>> > > Combining responses here. One of the reasons I pointed this out was that > Michael is the official project manager, and is the principle of the HSQLdb > Development Group, Inc., as well as the holder of hsqldb.org. Without his > cooperation, you may be forced to start another project. _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
