Full Article Attached Relicensing Has Begun

Wednesday September 19th, 2001

Gervase Markham writes: "Today we are checking in the first set of license changes into the Mozilla source tree, in our effort to get all code licensed in a way which addresses concerns about potential incompatibilities between the MPL and the GPL and LGPL. Our ultimate goal is to relicense all the Mozilla code under an MPL/GPL/LGPL tri-license (except for a few contributed files which will remain under their current BSD-style licenses). For more information on this ongoing effort see the Mozilla Relicensing FAQ. Please read that before asking questions in the comments." Click the Full Article link to find out more about the relicensing.

#9 Re: when do we fork?

by asa <>

Wednesday September 19th, 2001 3:49 PM

You are replying to this message

This is just my opinion (and doesn't necessarily reflect reality or the opinions of bug as I understand it, lot's of forking has already happened. Active state forked a long time ago when they started working on Komodo. OEone's operating environment was a fork from one of our branches and they will probably return to fork the next one of our stable branches. I believe lot's of others, maybe Galeon, have done the same thing. Not everyone working on Mozilla based projects does it in The same thing happens with Bugzilla. RedHat's Bugzilla is a fork. They aren't participating in the mainline Bugzilla development as far as I know. I'm sure that scores of others have forked Bugzilla too. I don't see a lot of checkins to Bugzilla from NASA or the US Army or Apache. The license requires that people make their changes to MPL and NPL filed publically available. It says nothing about participating in hosted development. IANAL so my reading of the license may be way off base. I don't claim any expertise in this area but concern about forking seems silly to me.