Welcome to the Mozilla Public License Update Process.

On March 10th, 2010, Mozilla announced a public process to help create the next update of the Mozilla Public License. Here you can find information on the process, details, and learn how to get involved.

Beta 2!

On Mar. 28th, we published the second Beta draft of the new license! We hope you’ll join us to discuss and comment on it.

The Beta achieves the primary goals we set out in our initial scope, including modernizing and simplifying the license so that it is easier to understand and use, globalizing the license, and improving compatibility with other licenses. Despite the success we’ve had so far, feedback from current and future users of the license is still important and appreciated as we work to wind up the process and make the license as good as possible.

Get Involved

Since this process started, we’ve received formal and informal feedback and suggestions from a large number of people. If you’re interested in joining this community of contributors, there are a few ways to do it.

You can start by adding comments to the current version of the MPL using our commenting tool. We will use the same tool to allow commenting on drafts once they are published.

To discuss the process and get announcements about drafts and other important milestones, join the mpl-update mailing list.  Announcements will also be posted to our announcements page.

Process Background

We’ve been using version 1.1 of the Mozilla Public License for about a decade now. Its spirit has served us well, helping to communicate some of the values that underpin our large and growing community. However, some of its wording may be showing its age. Keeping both those things in mind, we’ve launched this process to update the license, hoping to modernize and simplify it while still keeping the things that have made the license and the Mozilla project such a success. We’ve also had the benefit of input from other groups that have gone through a similar process, so we’ve tried to learn from their experiences as well.

To find out more about the process, read our initial announcement, our FAQ, and our original process page.