Re: Changing licenses

Todd Runstein wrote:
> Do I just change the license.txt file, update the
> comments (which include the copyright and license
> info) and call it "good-to-go"? 

Dave Hansen wrote:
> If you wrote everything in there, than you can do with it whatever you
> want.  The owner of a work can always do with it what they please.
> However, if you've accepted contributions from other people, it gets to
> be a bit more complicated.

You should have no problem. Everything you mentioned is sufficient enough.
If you have accepted contributed code here's your life line:

The following is taken from the GNU LGPL 2.1:
> 3. You may opt to apply the terms of the ordinary GNU General Public License
> instead of this License to a given copy of the Library. To do this, you must alter
> all the notices that refer to this License, so that they refer to the ordinary GNU
> General Public License, version 2, instead of to this License. (If a newer version
> than version 2 of the ordinary GNU General Public License has appeared, then
> you can specify that version instead if you wish.) Do not make any other change
> in these notices.

Fedor Pikus wrote:
> ... you can't change it retroactively: the last LGPL'ed copy
out there will forever be LGPL'ed,

Well, not exactly, see above.

> someone can fork it at this point and continue developping LGPL version of
> your project.

This point is valid. If someone does decide that they preffer the
LGPL, then they can still
use the LGPL'd copy they have in their hands. The key is "can't change
it retroactivly". You can't revoke the LGPL licence from copies of
version n that people already have, you can only release version n+1
as GPL and hope for a no-fork.
_______________________________________________
PDXLUG mailing list
[email protected]
http://lists.pdxlug.org/mailman/listinfo/pdxlug
IRC: irc.freenode.net #pdxlug