Hello Leo. The proposal is not very different from some of the options which have been discussed. Of course, the devil is in the details.
Some requirements and questions which I can think of off the top of my head: 1. The code should remain licensed under the ASL 2.0. If you are planning on relicensing the code, then copies of the current releases would need to remain available from Avalon under the ASL. 2. At best, branding would would be limited to Fortress, ECM and Excalibur and not included general use of Avalon and Apache. Under your proposal, the project would not be under the ASF umbrella and thus could not use the ASF marks. However, there is the possibility of listing this project as a 'sister' project to Avalon, similar to the PHP Group's relationship with the ASF. 3. Are you proposing transfering the copyright ownership? 4. Do you have the infrastructure in place to support this development? If so, what and where should be noted. Also, be aware that we still have a few developers who never filed CLA's. From the best that I can tell, this affects the old Phoenix codebase more than Fortress or Excalibur; however, if a copyright transfer were to take place we would need to ensure that the ASF has all the appropriate legal rights to do so. While I would have rather seen development remain in Avalon, I am not opposed to this option. However, I want to hear the voice of the PMC and the community on the matter, see a much more detailed proposal, and then I would also need to take the issue before the ASF board. --- jaaron <http://jadetower.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
