BSD & MIT licenses compatible?

View: New views
2 Messages — Rating Filter:   Alert me  

BSD & MIT licenses compatible?

by Suraj N. Kurapati :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

Please consider the following scenarios to help me better understand
whether BSD* and MIT code are "compatible".

*I am referring to the 3-clause BSD license:

  http://opensource.org/osi3.0/licenses/bsd-license.php


Scenario
========

Suppose that (1) I have two C source files (mit.c and bsd.c) and
that (2) each file is correctly placed under its respective license.


Simple case
-----------

I put mit.c and bsd.c into a tarball and send it to you.

What happens now?

Here is what I think:

  * mit.c remains under the MIT license

  * bsd.c remains under the BSD license


Complex case
------------

Suppose I append bsd.c to the end of mit.c while making sure to
clearly differentiate the two sources. For example:

  echo '/* begin BSD licensed code */' >> mit.c
  cat bsd.c                            >> mit.c
  echo '/* end BSD licensed code */'   >> mit.c

Next I put mit.c and bsd.c into a tarball and send it to you.

What happens now?

Here is what I think:

  * The portions of mit.c that were not copied
    from bsd.c remain under the MIT license.

  * The portions of mit.c that were indeed copied
    from bsd.c remain under the BSD license.

  * bsd.c remains under the BSD license


Remarks
=======

The BSD is not compatible with the MIT license because it has an
additional condition (i.e. you cannot use copyright holder's names
to promote the product) that the MIT license lacks.

Nevertheless, I was able to distribute the tarball in both cases
because I satisfied the distribution conditions of both licenses.


Thanks for your consideration.

Re: BSD & MIT licenses compatible?

by John Cowan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Suraj N. Kurapati scripsit:

> Please consider the following scenarios to help me better understand
> whether BSD* and MIT code are "compatible".

Your scenarios are correct as far as they go.

> The BSD is not compatible with the MIT license because it has an
> additional condition (i.e. you cannot use copyright holder's names
> to promote the product) that the MIT license lacks.

That just means they are not *identical*; they are still *compatible*.
You can take code under the MIT license and code under the BSD license
and license the result under (almost) any license you like.  The
BSD and MIT terms do not *contradict* one another.

--
Why are well-meaning Westerners so concerned that   John Cowan
the opening of a Colonel Sanders in Beijing means   cowan@...
the end of Chinese culture? [...]  We have had      http://www.ccil.org/~cowan
Chinese restaurants in America for over a century,
and it hasn't made us Chinese.  On the contrary,
we obliged the Chinese to invent chop suey.            --Marshall Sahlins