Slashdot Mirror
Google Reverses "Absurd" Mozilla Code Ban
Barence writes "Google has reversed its decision to ban projects created under the Mozilla Public License from being hosted on its Google Code site. Google banned the license in August, claiming it wanted to 'make a statement against open-source license proliferation' which it blamed for hindering the cross-pollination of code from one project to another. Chris DiBona, of Google's open source team, described its decision to ban the MPL as 'absurd,' citing the community's huge popularity." Jamie mentions that the issue was raised from the floor at OSCON at the Google Open Source Update panel, with DiBona on stage.
If there's a million "open source" licenses (which there are), it can become virtually impossible for code to move between projects with different licensing.
I believe this already exists: public domain.
Don't fight for your country, if your country does not fight for you.
I don't use adblocker because I don't object to ads. I object to stupid abusive techniques whether they're used for ads or knock-knock jokes.
No, the public domain does not mandate the openness of derivative products. That is what open source is about.
The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
Since when? Whether or not the source is encumbered by copyleft restrictions, it's still opensource.
I'm sick of GPL zealots, honestly. I choose to release my code completely free. That's permission to do ANYTHING (including making it GPL). But please don't try tell me it's not in the spirit of being open..
Is it only me who thinks that while the ethos of OSS is "open and free for everyone", these licences are just a way of developers saying "I want my slice of the pie also" ?
Truly free code comes with no restrictions whatsoever, be it over publishing licence text, making source available, having to pay the author for commercial use or whatever.
Free means free. Anything else is so much BS on the part of the developer.
It's like this: You're all free to eat at my farm. You're all free to plant things at my farm. You're not free to put a fence around my farm. The fact that you may have planted things at my farm still doesn't give you the right to put a fence around my farm.
If you consider the "no fences" stipulation too onerous for your liking, you can fuck off and don't come back. Keep your complaints to yourself, and don't let the door hit you in the ass on the way out.
-1 Uncomfortable Truth
Maybe you should try using AdBlock to only block those advertisers that engage in such practises then? It's not an all-or-nothing affair.
[insert witty comment here]
I would call it free, period. It's not free, subject to restrictions. It's free, and protected against future restrictive subversions, as opposed to free and abandoned to the machinations of selfish and evil men. It's the best kind of free, the kind you can rely on continuing to be free and relevant.
-1 Uncomfortable Truth
That's exactly why the GPL makes my eye twitch. Some of us don't care if our code is used commercially, and if you do, that's fine. Trying to say that you're "more free" and "more open" because you ban that is prima facie stupidity.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
In the U.S., public domain doesn't quite exist for code written by anyone who isn't the Federal government. What people call releasing code under public domain is essentially disclaiming liability and repudiating copyright.
Nerd rage is the funniest rage.
The MPL and the GPL are very different. The MPL is closer to the LGPL and the EPL than it is to the GPL
One of the easiest ways to think of it was give by Dave Johnson back in 2006. You can place most open source licenses into one of three categories:
Hope that helps.
Who said Freedom was Fair?
Frankly, given Google's record, I refuse to host any of my projects on Google Code, or to participate in the development of any projects hosted there.
...Why? What part of Google's record?
Most of the bad things I hear about Google are privacy-related... what part of your open source project needs to be private?
Don't thank God, thank a doctor!