On Friday, November 09, 2012 01:32:53 PM Thomas Kluyver wrote: > On 9 November 2012 12:44, Maykel Moya <mm...@mmoya.org> wrote: > > Even in the case of the more restrictive license applying only to > > debian/* work? Could you/someone elaborate a little the implications of > > this (link to fine documentation is welcomed)? > > I'm not sure if there's a Debian rule about it, but I'd consider it good > etiquette, if you're adding something to a much larger work, to follow the > author's lead on licensing. > > For instance: say you patch the code to fix a bug you notice while you're > packaging. You don't forward the patch at the time, but the upstream author > later sees it and wants to include it. If debian/ is under the same > license, he's free to use your code and credit you. If debian/ is more > restricted, he has to try to contact you to get an appropriate license.
This isn't just a theoretical concern. I've had to do this when trying to upstream a patch that was provided to Debian with GPL licensing terms for a BSD licensed package. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6631952.Zg323h08oV@scott-latitude-e6320
