Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Reverses "Absurd" Mozilla Code Ban

Posted by kdawson on from the standing-athwart-history-yelling-"eof" dept.

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.

5 of 201 comments (clear)

  1. Well, Google does have a point.. by jonnythan · · Score: 5, Insightful

    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.

  2. Re:Multi-license ! by houghi · · Score: 5, Insightful

    I believe this already exists: public domain.

    --
    Don't fight for your country, if your country does not fight for you.
  3. Re:Multi-license ! by FishWithAHammer · · Score: 5, Insightful

    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."
  4. Open source licenses come in 3 flavors. by jaaron · · Score: 5, Insightful

    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:

    • Gimme Credit: this includes the Apache, BSD and MIT licenses. Basically, you can do anything you want with the code, but you must give the original authors credit in some way.
    • Gimme Fixes: is used by the EPL, MPL, and LGPL. Basically, the original code will always be open source and any direct changes of the original code (patches, bug fixes, enhancements) must also be released as open source. However, you can combine this software with closed code to create a proprietary work. This license tends to be used by frameworks and libraries. Sometimes the original author gets special rights (like the NPL).
    • Gimme everything!: the GPL stands alone in it's requirement that the code itself and all derivative works be free software.

    Hope that helps.

    --
    Who said Freedom was Fair?
  5. Re:Proliferation of O/S software hosting services by SanityInAnarchy · · Score: 5, Insightful

    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!