Re: Extending and releasing open source software
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On 03/14/2011 06:15 PM, Boyd Stephen Smith Jr. wrote:
> On 2011-03-14 11:12:35 Nick Douma wrote:
>> I have a question about developing software and licenses. I have taken a
>> MIT-licensed library (https://github.com/peej/tonic), and modified and
>> extended it. The result is a REST library for PowerDNS, which I would
>> like to release under GPL. However, it is not clear to me how I should
>> do it.
>
> Why not keep the existing MIT license?
Because the GPL license is a better match for the project.
> Each file should contain a copyright notice for each entity that holds
> copyright on it. 'Copyright 2011 "Boyd Stephen Smith Jr."
> <bss@iguanasuicide.net>"' is a good example. New source files will just have
> your copyright, unmodified source files will just have the original authors
> copyright, modified source files will have both copyrights.
>
> For clarity, it is recommended you include at least a reference to the GPL in
> each file. The whole text of the GPL need not be reproduced in each file. If
> the only modifications you make to a file are the GPL reference and original
> author's copyright notice, you shouldn't add your copyright notice.
>
So basically I add two lines for source files that I modified, and the
original MIT license after that?
Kind regards,
Nick Douma
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1/WhgACgkQkPq5zKsAFijTygCffek9o3Zj09rVV0jXvne1jcmK
ePwAn1/f5/wcMznt/Da8kL7mJtWyvPNh
=7VtA
-----END PGP SIGNATURE-----
Reply to: