[OH Updates] OSHW Definition idea; compatibility clause

[G. Andrew Stone]

Hi all,

There has been some concern about forking licenses due to the problems with
license incompatibility discovered in the OSS world.  So I'm wondering if
the OSHW Definition should mandate (or at least strongly recommend) that
all licenses contain some sort of de-facto compatibility clause.  IANAL so
this is going to be a bad first try at it, but maybe something like:

Derived works may combine works (or parts of works) licensed under this
license and under any other OSI or OSHW certified license, even if these
licenses otherwise mandate incompatible requirements.  The derived works
should simply indicate (at the top of each file if file separation is
possible, in a separate license.txt file that somehow indicates which
section is which, or in inline comments at the derived work's author's
discretion) which sections fall under which license.  The requirements
stated by both licenses must still be followed as if the single derived
work was 2 separate projects.  In the case of "viral" licenses, additional
creative work must be dual-licensed under all source-work viral licenses
(and of course MAY be licensed any other way the copyright holder
chooses).  "Dual-licensed" means that the licensee of the additional work
can choose either license to apply to the additional work when creating
another derived work.

Cheers!
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhardwaresummit.org/pipermail/updates-openhardwaresummit.org/attachments/20111117/303618a3/attachment.htm>