Comments on: Updating the Mozilla Public License http://blog.lizardwrangler.com/2010/03/10/updating-the-mozilla-public-license/ Sat, 11 Feb 2012 23:41:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Release Candidate for Updated Mozilla Public License; New Module Peers | Mitchell's Blog http://blog.lizardwrangler.com/2010/03/10/updating-the-mozilla-public-license/comment-page-1/#comment-18946 Release Candidate for Updated Mozilla Public License; New Module Peers | Mitchell's Blog Sun, 21 Aug 2011 00:30:51 +0000 http://blog.lizardwrangler.com/?p=2437#comment-18946 [...] for much of its code, including that of Firefox and Thunderbird.   In 2010 we started the work of updating the MPL (The current version was written in over a decade ago.)    The process incorporates a number [...] [...] for much of its code, including that of Firefox and Thunderbird.   In 2010 we started the work of updating the MPL (The current version was written in over a decade ago.)    The process incorporates a number [...]

]]> By: Revised Mozilla Public License — Beta 1 | Mitchell's Blog http://blog.lizardwrangler.com/2010/03/10/updating-the-mozilla-public-license/comment-page-1/#comment-17783 Revised Mozilla Public License — Beta 1 | Mitchell's Blog Wed, 22 Dec 2010 00:48:09 +0000 http://blog.lizardwrangler.com/?p=2437#comment-17783 [...] March of this year we kicked up a process to update the Mozilla Public License. We recently released the first beta of the MPL 2.0 and we believe that this beta is now feature [...] [...] March of this year we kicked up a process to update the Mozilla Public License. We recently released the first beta of the MPL 2.0 and we believe that this beta is now feature [...]

]]> By: Revised Mozilla Public License — Beta 1 | Mitchell's Blog http://blog.lizardwrangler.com/2010/03/10/updating-the-mozilla-public-license/comment-page-1/#comment-17784 Revised Mozilla Public License — Beta 1 | Mitchell's Blog Wed, 22 Dec 2010 00:48:09 +0000 http://blog.lizardwrangler.com/?p=2437#comment-17784 [...] March of this year we kicked up a process to update the Mozilla Public License. We recently released the first beta of the MPL 2.0 and we believe that this beta is now feature [...] [...] March of this year we kicked up a process to update the Mozilla Public License. We recently released the first beta of the MPL 2.0 and we believe that this beta is now feature [...]

]]> By: In Honor of Ada Lovelace: Top (Female) Innovators « Hypios – Thinking http://blog.lizardwrangler.com/2010/03/10/updating-the-mozilla-public-license/comment-page-1/#comment-16099 In Honor of Ada Lovelace: Top (Female) Innovators « Hypios – Thinking Tue, 30 Mar 2010 13:15:44 +0000 http://blog.lizardwrangler.com/?p=2437#comment-16099 [...] current plans for Mozilla include updating the Mozilla Public License to maintain open source standards. Baker also writes a blog, Lizard Wrangling, about Mozilla, the [...] [...] current plans for Mozilla include updating the Mozilla Public License to maintain open source standards. Baker also writes a blog, Lizard Wrangling, about Mozilla, the [...]

]]> By: mitchell http://blog.lizardwrangler.com/2010/03/10/updating-the-mozilla-public-license/comment-page-1/#comment-16075 mitchell Tue, 23 Mar 2010 23:14:49 +0000 http://blog.lizardwrangler.com/?p=2437#comment-16075 To those who asked why we don't just use the GPL; here's the relevant text from the FAQ (which is found at http://mpl.mozilla.org/faq/) Q: Why are you not planning to consider altering the scope? A: Changing the scope of the copyleft probably means choosing between a GPL-style strong copyleft and the Apache style “no-copyleft.” The Mozilla community includes some people who are strongly drawn to each of these options, and for whom living exclusively with the other option would be surprising and difficult. As a result, adopting either of these options exclusively is likely to be highly disruptive. The current file-level copyleft allows all of us to work together, which is a better outcome and a net positive for the Mozilla community. To those who asked why we don’t just use the GPL; here’s the relevant text from the FAQ (which is found at http://mpl.mozilla.org/faq/)

Q: Why are you not planning to consider altering the scope?

A: Changing the scope of the copyleft probably means choosing between a GPL-style strong copyleft and the Apache style “no-copyleft.” The Mozilla community includes some people who are strongly drawn to each of these options, and for whom living exclusively with the other option would be surprising and difficult. As a result, adopting either of these options exclusively is likely to be highly disruptive. The current file-level copyleft allows all of us to work together, which is a better outcome and a net positive for the Mozilla community.

]]>