I'd like to take this opportunity to point something out. I just re-changed a couple of license headers in the client dir that had been changed to Copyright Drizzle Open Source Development Team. We can't actually do that, since Sun/MySQL is the party that actually owns the original copyright. We can _add_ our name/names to the list if we make significant changes, but the GPL license does not allow us to all of a sudden own the code.
Also, I think if we do add copyright ownership, it needs to be either adding individuals to the list, or an established legal entity. The "Drizzle Open Source Development Team" is not a body that can actual own anything, so if we did try to apply that copyright to a new file, for instance, we would be in effect putting that file in the public domain, since there would be no way to enforce the GPL if someone violated it. (A copyright holder has to be a party to a violation lawsuit, and in this case there would be no legally recognized entity to bring suit.) So, in short - don't change the copyright headers away from Sun/MySQL, and if you add someone, add someone who legally exists. Monty Brian Aker wrote: > Hi! > > On Sep 7, 2008, at 9:17 AM, Jay Pipes wrote: > >> OK, crap. Would be nice to have all this crap standardized. Source >> files have various versions of license text on them. > > > I sort of expect this to be the case. > > What is the real source for information though? "bzr", it is what > contains all information on licensing. It is one of the big reasons I > want people to put up trees on launchpad, and have us pull (and if > anyone takes a patch from email, it should be documented as to > where/whom it came from). _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
