Subject | idpl/ipl/mpl license |
---|---|
Author | marius popa |
Post date | 2006-05-10T10:35:16Z |
New parts of firebird could be released with an better open source license
in the future :
like mozilla finished their relicensing task
http://www.mozilla.org/MPL/relicensing-faq.html
like jaybird is released under LGPL
http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=info:licensing
The MPL avoids the three problems associated with the "viral" nature of GPL
in that it:
allows for the combination of MPL code with other code in a larger work
without requiring that all code in the entire work be distributed under the
same license;
in turn allows for innovation in Open Source licensing evolution, in that,
if an Open Source license that is more free and open than MPL comes along,
the Open Source movement can adopt it without having to abandon a
potentially large body of MPL work, as would be required with the GPL; and
gives developers employed by commercial organizations the opportunity to
contribute to the Open Source movement and the body of public knowledge
since the MPL only requires that just the derivative works be released as
MPL, not the entire larger work which the employing commercial entity may
have a proprietary interest
http://www.croftsoft.com/library/tutorials/gplmpl/
--
developer flamerobin.org
[Non-text portions of this message have been removed]
in the future :
like mozilla finished their relicensing task
http://www.mozilla.org/MPL/relicensing-faq.html
like jaybird is released under LGPL
http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=info:licensing
The MPL avoids the three problems associated with the "viral" nature of GPL
in that it:
allows for the combination of MPL code with other code in a larger work
without requiring that all code in the entire work be distributed under the
same license;
in turn allows for innovation in Open Source licensing evolution, in that,
if an Open Source license that is more free and open than MPL comes along,
the Open Source movement can adopt it without having to abandon a
potentially large body of MPL work, as would be required with the GPL; and
gives developers employed by commercial organizations the opportunity to
contribute to the Open Source movement and the body of public knowledge
since the MPL only requires that just the derivative works be released as
MPL, not the entire larger work which the employing commercial entity may
have a proprietary interest
http://www.croftsoft.com/library/tutorials/gplmpl/
--
developer flamerobin.org
[Non-text portions of this message have been removed]