|
[openbeos]
||
[Date Prev]
[07-2007 Date Index]
[Date Next]
||
[Thread Prev]
[07-2007 Thread Index]
[Thread Next]
[openbeos] Re: license question
- From: "André Braga" <meianoite@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 11 Jul 2007 19:28:37 -0300
On 7/11/07, Salvatore Benedetto <emitrax@xxxxxxxxx> wrote:
Hi,
when *porting* GPL code, can I distribute the new code under a different
license?
MIT for example?
Use GPLd code *only* for reference (i.e., device driver magic numbers
and such). Don't make verbatim copies of *any* excerpt, ever. Don't
rip code simply changing the names of functions and variables. Don't
try to mask code ripping by displacing parts of the code or changing
the ordering of variables/functions.
Doing so forces you to release your code in the GPL as well.
As I said, only for reference. Ideally, ask someone else to break out
the magic numbers for you and only look at the notes said person
produces. I.e., the reverse engineering approach.
In a nutshell: if you stay clear of what copyright law characterises
as "derivative work", minding the considerations regarding fair use,
you can't be bound by the GPL.
Cheers,
A.
|
|
