Sorry, I meant GPL-only code. This is because it cannot be used by the whole community - i.e. those who are using the code under the MPL or LGPL may not be able to use it.
>> Things like NSPR and XPCOM are extremely cool technlogies which >> would be of great use to other free software projects, who would >> not have to re-implement the portable-runtime and >> cross-platform component model wheels. > > Licencing under the GPL isn't necessary to achieve this, both NSPR > and XCOM can be used as LGPL targets, and without relicencing under > LGPL. If the application which wishes to use them is licensed under the GPL, then they need to be also licensed under the GPL. >>The only time anyone would ever need to identify the license they used >>would be if they are taken to court by one of the copyright holders. At >>that point, they would have to be able to say "I am using it under the >>XPL and have fulfilled all conditions of the XPL." Until that point, >>they would not need to make a determination. > > That is dangerously ignorant I'm afraid. Simon, if you continue to abuse me in this manner I will stop this discourse. > The whole point of the licence is to identify exactly what is to > happen in the case of dispute. Not caring about it at the time of > licencing is just irresponsible. That is not what I said. I'm sure you care very much at the time you pull Mozilla which terms you intend to use it under, and are very careful to abide by them. My point is that this information is completely irrelevant until the exact moment someone sues you. > And the licences give third parties the right to sue as well as the > original copyright holders, News to me. Where do they say that? >>>Originally, and some might remember this differently, the NPL >>>licence was meant to be a limited to I think three years. >>> >>There is no wording like that in the NPL. > > Yes lets forget about intent shall we. Essentially this is a fraud on > contributors since the original release. You assert this intent yet have no evidence. No emails, no newsgroup posts. >>As the FAQ clearly states, mozilla.org would like all code in the tree >>to be available under MPL, but has not yet secured the necessary >>permissions. This is not for want of trying. > > And will not now happen, there is no need, the tree will degrade > quickly into a GPL project As mozilla.org will refuse to admit any code into the tree which is not tri-licensed I fail to see how this could happen. > with AOL maintaining the fork they already have for the production > code. Its no more work than already has to happen. You might say but > you have to licence using MPL as well to get into the tree, and yes > that's so, but if all these marvellous things are happening in GPLand > and they aren;t contributed back (I promise you they won't be), That's very pessimistic. And, even if none contributed back (which I consider to be extremely unlikely - for a start, the Galeon developers have been very happy to work with us), what skin is it off our nose? It's a disappointment, certainly, but we'll have assisted in the creation of some excellent bits of free software. > then in 6 months time what is the point? Oh yes here is the point, > AOL will still get use of the codebase protected by the buffer and the > original copyright. AOL has exactly the same rights (effectively) to the codebase that you do. > I've no idea at the moment what I've contributed to, often patches rot. I do remember cleaning all of the classic style sheets at one point but that work was redone, and poorly at that. > Personally, if I contribute under a particular set of conditions then > that is the spirit under which they should be used. I doubt anything > of mine is in the way of anything though. I'm glad you feel that way, and will support the relicensing, which (as we argue in the FAQ) is definitely in the spirit of the original licensing. Gerv
