On 2/23/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > We shouldn't be leaping in to make all the source ASF-based while > there are still questions over the resolution of the LGPL > dependencies.
What I would suggest is that we * place a single COPYRIGHT.txt file in the root of the project with whatever copyright assertions we want to make now, * remove *all* the copyright notices and other cruft from the top of the files that are asserted by the ASF Committers, and * note any other copyright assertions (e.g. Sun) in the COPYRIGHT.txt file. It hasn't been made altogether official yet, but it looks like leaving all copyright notices out of the files and putting them in a single COPYRIGHT file is probably to be an acceptable alternative to the ASF. Even if it isn't, it would be much easier to have a script update all the source files if the heads were already clean. Even if the committers trudged back to java.net, using a single COPYRIGHT.txt instead of individual statements scattered in some of the files seems like a better approach for everyone. Given a volunteer to do the work (me! me!), it's win-win either way. Of course, even if all the files were marked with the usual ASF statement, the team would still be able to trudge back to java.net and setup shop. The ASF statement is non-exclusive and doesn't prevent anyone from continuing work elsewhere. If Roller fails incubator, no one is going to assert that the "Roller" name is still under the ASF copyright. We really are all friend here :) But, I'm not suggesting that we insert the ASF statement at this time, just that we remove *all* the statements, and use a single COPYRIGHT.txt file instead. > that it makes it harder for the Roller committers to make releases at > rollerweblogger.org. Currently it does as much as possible to not look > like an Apache release. Under the Apache License, anyone can roll a release of any of our codebases and distribute it wherever they like. The only stipulation is that no one else can call it an Apache or ASF release. > Hibernate is the easy one to focus on, but we have other licensing > issues to deal with too. There are other LGPL components, and we need > to do an audit of our Javascript; I want to make sure that we're good > there license-wise. Is that it, then? Hibernate and the Javascript? If another alternative is not forthcoming, I'll do whatever it takes to replace Hibernate with iBATIS or Cayenne. * http://www.objectstyle.org/cayenne/ The Cayenne team is considering an Incubator proposal of their own. * http://www.mail-archive.com/tapestry-dev@jakarta.apache.org/msg04867.html Aside from my own commitment, I'm sure some of the Cayenne team would be very keen on helping us move Roller to Cayenne. -Ted.
