RE: Wasting our Freedom


JFTR, I do *not* think that that assessment was questionable. Unless the
dual-licensing *explicitly* allows relicensing, relicensing is forbidden
by copyright law. The dual-licensing allows relicensing only if that's
*explicitly* stated, either in the statement offering the alternative, or
in one of the licenses.

Neither GPL nor BSD/ISC allow relicensing in their well-known wordings.

If you think that's questionable, you should at least provide arguments
(and be ready to have your interpretation of the law and the licenses
tested before court).

Nobody is relicensing anything, ever.

If the author licenses a work under the GPL only, then that is forever how
that work is licensed. If an author licenses a work under the BSD, then that
is forever how that work is licensed. Same for a dual license. This applies
until the copyright expires or the author offers the code under some other
license.

Nobody ever relicenses anything, ever.

If I give you a copy of a work covered by the GPL, the BSD, a dual-license,
or whatever, you get a license to every protectable element in that work
from the original author of that element.

Nobody ever relicenses anything, ever. Nobody ever modifies anybody else's
license, ever.

If you take work that's under a dual-license and remove one license notice
from it when you create a derivative work, every recipient of that
derivative work still receives a dual license from the original author to
every protectable element still in the distributed work.

The GPL is explicit about this in section 6. The BSD license is not, but
it's the only way such a license could work.

There are really only two ways you can screw up.

1) You can take GPL-only bits and put them in BSD or dual-licensed code.
(The GPL prohibits this.)

2) You can remove a BSD license notice from BSD-only code. (The BSD license
prohibits this.)

DS


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Wasting our Freedom
    ... dual-licensing *explicitly* allows relicensing, relicensing is forbidden ... The dual-licensing allows relicensing only if that's ... strictly up to the license of the original. ... So for code which is single-licensed under a BSD license, ...
    (Linux-Kernel)
  • Re: [Swsusp-devel] lzf license
    ... > So if Nigel takes the BSD license out and replaces it with GPL, ... I believe this was always possible, and should now be rather explicit ... But, again, relicensing is now explicitly allowed, I am aware of the ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • RE: Wasting our Freedom
    ... As far as the law goes, the GPL and BSD are not typical licenses. ... I would agree there's probably a legal issue if you modify license text so ... as to misrepresent to a person that they have rights they don't actually ... The whole relicensing thing is bogus. ...
    (Linux-Kernel)
  • Re: Wasting our Freedom
    ... dual-licensing *explicitly* allows relicensing, relicensing is forbidden ... Neither GPL nor BSD/ISC allow relicensing in their well-known wordings. ... strictly up to the license of the original. ... So for code which is single-licensed under a BSD license, ...
    (Linux-Kernel)
  • Re: Wasting our Freedom
    ... The most questionable legal advice in this thread was by Theo de Raadt ... dual-licensing *explicitly* allows relicensing, relicensing is forbidden ... The dual-licensing allows relicensing only if that's ... follow the GPL exclusively and I don't have to follow the BSD license at all. ...
    (Linux-Kernel)