Home Original page

[OT} How to un-GPL parts of a GPL'd module.

Jacob Hallen jacob at boris.cd.chalmers.se.cd.chalmers.se
Sat Oct 12 17:01:52 EDT 2002 
In article <anus7e$44r$1 at news.hccnet.nl>,
Anton Vredegoor <anton at vredegoor.doge.nl> wrote:
>On Tue, 8 Oct 2002 09:03:44 -0400, "Steve Holden"
><sholden at holdenweb.com> wrote:
>
>>"Anton Vredegoor" <anton at vredegoor.doge.nl> wrote in message
>>news:anujeq$qdk$1 at news.hccnet.nl...
>>
>>> I guess I could e-mail the author for permission but if I would have
>>> to wait for them to answer, it would slow my coding process down to a
>>> snail's pace, and there's always the possibility of the author being
>>> unwilling.
>>>
>>Indeed. Perhaps you should consider releasing your own code under the GPL
>>rather than some other license. That way there's no problem incorporating
>>GPL'd code.
>
>That would solve the problem at the cost of passing on the problem to
>the next coder. It's this kind of "chain letter like" property that I
>want to adress.

It is quite legal to copy small amounts of copyrighted material, with or
without attribution. For music, the legal amount is in most jurisdictions
considered to be 8 measures. In works of literature it is about a paragraph.
My guess is that with code it would be something like 10 lines.

Jacob Hallén

--
More information about the Python-list mailing list