Google makes Mozilla licence U-turn
'A bit more nuanced'
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Google has done a swift about-face and decided to allow code released under the Mozilla Public Licence (MPL) into its Google Code silo, just a month after it was judged redundant and banned.
In late July we reported from OSCON how Google caused a stir by booting MPL code. The firm's chief open source fancier Chris DiBona said Mozilla's licence wasn't widely used enough to justify its place on the Google Code site.
Software watchers said the true motivation for the MPL embargo was more likely concern by Google that its intellectual property might be legally imperilled by association with the licence's potentially wobbly terms. "Most open source licences have not a thing to say explicitly about patents or trade marks," DiBona said. "We [Google] will be unpopular for a while."
It seems Google simply couldn't handle the wrath of the open source crowd.
On Wednesday he wrote on the Google blog that a similar two-year Google Code ban on the Eclipse Public License, yet another open source licence, was being lifted "to show [Google's] solidarity with our friends at the Eclipse project".
"In that light," DiBona continued, "our removal of the MPL from the site seemed a little absurd. So, our bad.
"We're putting that option back up for new projects. The groups that want to use the MPL to enable their additions, extensions and more for Firefox and other Mozilla projects are legion and considering their recent summit, represent a very healthy global collection of developers."
However, he maintained Google's stance that too many very similar open source licences is damaging for the development community - "but how we think about licences is getting a bit more nuanced".
Dibona said the EPL now merits a spot on Google Code because although not many projects are licensed under it, the software has a large user base. Kicking out the MPL was "just a mistake", he admitted in response to a comment on his posting. ®
COMMENTS
Ice Weasel - Bon Echo
I don't know, Firefox needs to protect their brand sure, but they need to do it in a way that allows the distros to operate.
Firefox is really only installed by Windows, Mac and Gentoo peeps, the rest have to make do with Ali Quick Change, unless they download directly from Mozilla.
They need to tweak the license a bit, it was actually Mozilla that got a lot of opensource ire, it wouldn't surprise me if the person behind the original move to not host Mozilla license code was not in fact someone who was involved in opensource.
If Mozilla wants to count the downloads which I suspect is one of the motivations then a callback would probably be accepted.
If they want to ensure that things like the debian openssh debacle doesn't occur, well they could make that explicit as well, only source code from Mozilla is acceptable as being firefox, as it stands at the mo the only binary that is accpetable as being firefox is the one from Mozilla.
about:config
Thanks too AC - and I notice that the URL is also configurable, so you can point it to M$ Live Search if you want...!
I don't know about obscure functions
of FF3. I do know what most people do when they hear that Google was trying to dictate to projects which license they could use was a predictable "fook that I'll go to Sourceforge" it might be a while before that damage is undone.
IT infrastructure monitoring strategies
What you need to know about cloud backup
Enabling efficient data center monitoring
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
