Extending and releasing open source software



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

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.

I have already read most of the FAQ on
http://www.gnu.org/licenses/gpl-faq.html. I have added a COPYING file to
the project with the GPLv3 license in it. I have also added a license
file with the "This file is part of XXX" text from
http://www.gnu.org/licenses/gpl-howto, and added a reference to the
original author and license he released with. Finally, I have added the
same text (without reference to the original author) to all my
(modified) source files.

Is this appropriate for releasing a project? I am not sure if I should
put the license text in all source files, even those that I didn't
modify. I am also not sure what to do with the original author's license.

Could someone shine some light on this?

Kind regards,

Nick Douma
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1+PnEACgkQkPq5zKsAFihf5gCfQsK0Lu4ImrwrX2nQnTTGMib7
GxEAni8ESAKAsg9Au3aGPzYl6rP7/NiB
=Miqp
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Archive: http://lists.debian.org/4D7E3E73.1010308@xxxxxxxxxxxxx