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? >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. IANAL; TINLA IANADD; TINASOODP 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. >I am also not sure what to do with the original author's license. I would put it in the file COPYING.MIT, along with a note that this is the license of the original work by the original author and does not cover the derivative work that includes your additions. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.