Should we replace each source file header lock, stock and two smoking barrels? If so, does any one have a script for this?
Gary > -----Original Message----- > From: Henri Yandell [mailto:[EMAIL PROTECTED] > Sent: Monday, February 02, 2004 12:02 > To: Jakarta Commons Developers List > Subject: Re: Relicensing to the Apache License 2.0 ? > > > The policy as far as I know is: > > All releases after March 1st must use Apache License 2.0. > > No agreement is needed as the only copyright holders to the ASF version of > the source is the ASF. While people retain copyright to their submissions, > they retain the copyright to their copy and not to the ASF copy. > > It might be different for say ASF-members who have not signed the CLA, but > I would expect committers who have not signed the CLA to be the same as a > contributor. > > IANAL etc. Just passing on what I've seen said, which could be wrong for > all I know. > > Hen > > On Mon, 2 Feb 2004, Emmanuel Bourg wrote: > > > Hi, the Apache License 2.0 has been released last month > > (http://www.apache.org/licenses/LICENSE-2.0) and it seems it will become > > mandatory for all Apache projects this year. > > > > I wonder what is the procedure for this migration, i guess all copyright > > holders, that's committers and external contributors, have to agree > > explicitely on the relicensing. This should be immediate for the > > committers since they signed the Contributor License Agreement allowing > > the ASF to license the code in any way. But the other contributors will > > have to be contacted to request permission for relicensing, correct? > > > > Emmanuel Bourg > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
