On 2/24/06, Ted Husted <[EMAIL PROTECTED]> wrote: > 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.
Bit wary of diving in and redoing the copyright to how we think it will be. It may get bogged down in legal realities in the same way the licensing issue has. I'd definitely like to get our copyright questions resolved (see below); and then probably go ahead and move to the standard ASL copyright at the top of each file method unless we've heard otherwise. I'd like to check with the Incubator PMC that changing the copyrights to the ASF wouldn't have much effect on the ability to release at rollerweblogger. > 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. +1 to starting the work to solve the copyright. ie) finding out how much code is affected by the two committers who are not ASF committers, getting their permission if need be, being happy about the Sun copyright statements from David and being able to zap them all. Then regroup before actually making the changes to see what our situation is. > > 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. Right. So grab the source; remove any reference to Apache Xxxx on the products published interface; add one that points to Apache as the owners of the code this is rereleased from; ideally change all package names from org.apache. It also changes the community sell of it. We're not forking the Apache version, we're squatting in the Apache infrastructure and releasing a version from the Roller community. > > 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. There are some other LGPL components; I think they mostly come down to one of the editors that we've talked about dropping (2.1? 2.2? not sure when it's going). There are also other licenses that the new policy is going to affect. And the LGPL issue is going to be lessened. Give me just a little more time to continue being a pain in the arse to Cliff before using up too much energy on the license fixing? :) > Aside from my own commitment, I'm sure some of the Cayenne team would > be very keen on helping us move Roller to Cayenne. Craig's doing a JPOX one isn't he? Sorry if the above is disjoint; Generally we need to: * Fix copyright * Fix distribution for licensing * Get a zone setup for the Roller website to be migrated over - involves a db migration from mysql (I think) to Derby. * Migrate Roller wiki (JSPWiki to moinmoin?) * Jira is another in a holding pattern - flat out not possible to migrate projects from one Jira into another Jira. Hen
