Mozilla To Be Dual Licensed - MPL/GPL
thegrommit writes "No doubt I'm one amongst many, but Mozilla is going to be
dual licensing their codebase" Actually, thegrommit was the first, but it's great news. Congratulations to all involved - I've been using Mozilla a huge amount over the last three months, and it's pretty amazing. You can check out the FAQ for more details.
Upon completion of the relicensing, I'll award the Mozilla folk an official Atta Boy. More await the release of a version usable by my father.
I must admit that I find myself browsing with Galeon more than I do with Mozilla these days. The simple and clean interface design out-weigh the 'Heavy' and feature full interface of Moz.
The biggest problem with Galeon is the steps involved in getting it to work. (They couldn't distribute the Mozilla compontents).
Using Galeon I get far fewer crashes (and Galeon is still in Alpha) than w/Mozilla or Netscape. It is MUCH faster than Mozilla and is close to being up to speed with Netscape with application zippiness. (GTK is fast!)
Give it a look, I believe that they are moving quicker than the Konquerer group because they are leveraging a rendering engine that WORKS.
Too bad that Opera never really happened. What a great little browser. Hehehee... long live open source.
--------------------
First, you can imagine that a dually-licensed source file is really two files: one that has the GPL at the top, and the other than has the MPL at the top. When you use the file -- distribute it, compile it into a binary and distribute that, combine it with other code -- you can choose which of those ``virtual files'' you're dealing with. So if you want to use nsMozFile.cpp with your GNOME app, you might choose to use it under the GPL. But when Netscape builds Netscape 6 from nsMozFile.cpp, they'll probably choose to mean the requirements of the MPL instead of the GPL.
I'll restate that, because it's traditionally the sticking point: a dually-licensed file lets you choose which license you will honour. You have to meet the requirements of one of the licenses, at least, so mixing and matching requirements is obviously out. (Obviously. I'm embarrassed to even mention it.) You do not have to meet all the requirements of both licenses, and in fact it's impossible to do that, because the GPL forbids additional restrictions, and the MPL has several requirements that would fall under that category.
So what about changes? Well, now you've got three choices: you can create a derivative that is GPL-only, or a derivative that is MPL-only, or -- perhaps better still -- a derivative that is also dually-licensed. mozilla.org would certainly prefer that people keep things dually-licensed, for the same reasons that we want to dually-license it in the first place: it serves a larger community of contributors and consumers. Now, we can't require that your derivative be dually-licensed; that would violate the terms of both licenses, I suspect, but certainly the GPL. So all mozilla.org can do is exert control over its infrastructure, and insist that contributions which go into the cvs.mozilla.org tree be dually-licensed. It's still well within anyone's legal rights to create a GPL-only derivative of Mozilla, and fork the world. I think that would suck, a lot, and even RMS has in the past discouraged people from doing that. If nothing else, it would discourage other organizations from going the dual licensing route.
I hope that helps some. I'm really psyched about this; it's been a dream of mine (and others') since before Mozilla was even released, and the success of dually-licensing the JavaScript, NSPR and NSS/PSM code whet my appetite for more. Please join us in the mozilla-license forum for more discussion.
I've used Mozilla now and again (M14 I think is the last one I touched), and it's stability leaves a great deal to be desired.
Yeah, I was trying out Windows 2.0 a little while back. Boy did it ever suck. Nobody would ever use that. Ack, and did you see that Linux 0.8 kernel? That'll never get anywhere either.
It's easy to envision there will be some individuals who are philosophically opposed to the GPL, and will refuse consent on that basis.
A bunch of volunteers working on an open source project with deep philosophical problems with GPL. Are you from Redmond?
This could potentially lead to a very messy code split
Kids, don't try taking logical leaps like this at home. Obviously this person is a professional and has taken the proper safety precautions to avoid falling into a mental abyss.
Other than that, good post.
The line must be drawn here. This far. No further.
The Galeon project will probably be one of the first to greatly benifit from the relicensing! Slashdot had a discussion about Galeon back in July.
Currently they cannot distribute the gtkembmoz.h file, due to licensing restrictions, which is needed for compiling the source code.
Through Galeon, this will also directally effect the GNOME project. Giving it a simple browser utilizing the Gecko rendering engine. We will, with evolution/nautilus(SP?) have seperate apps for browsing, e-mail, and file/system management! Along with the upcomming GPL of Star Office, GNOME is on the move to providing a complete productivity environment without the bloat!
If at first you don't succeed, skydiving is not for you.