Tzeng, Nigel H.
Nigel.Tzeng at jhuapl.edu
Tue Jan 20 20:35:25 UTC 2009
Well, you can use a permissive license that the FSF deems GPL incompatible for the issue of BSD compatibility, including the old 4-clause BSD.
Of course, it's by definition not GPL-compatible...or at least according to the FSF.
You could dual license those change blocks as BSD like you can in MPL.
MPL might be the closest in what he wants.
You can use MPL code in your BSD project but that code remains under the MPL license. Neither MPL or BSD claims all your base are belong to us.
On 1/20/09 2:13 PM, "Ben Tilly" <btilly at gmail.com> wrote:
On Tue, Jan 20, 2009 at 7:00 AM, Steve Thomas
<steve.thomas.private at googlemail.com> wrote:
> Does a license already exist that, for any such chain as in (2), would
> preclude step (4) whilst allowing (5) and (6) in the event that Mr
> Takesallsorts chooses to distribute his derivative work ? Is it
> possible for any such license to be GPL-compatible ?
Almost certainly this is impossible.
Furthermore there is an interesting irony here. Suppose you came up
with a license that is permissive like the BSD but has a restriction
preventing its appropriation by GPL advocates. Suppose you have a
project under this license and wish to borrow some BSD code, which you
then make changes in. Guess what? If you license your changes under
your license, then the original BSD project can't accept them back
without being forced to change their license! No matter how great
your intentions, from the point of view of a BSD project, your
anti-GPL license is as bad as the GPL license itself!
It is in the nature of being permissive that you can't accept
restrictions on code. Any kind of restrictions.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the License-discuss