Twitter github

Posts Tagged with “licensing”

Eclipse, Symbian and the Rise of the Weak Copyleft

In case you weren’t aware, the Symbian Foundation recently open-sourced their Symbian^3 platform under EPL. I’ve had a few people come to me and ask first, what is the Eclipse Public License and why would Symbian choose that license say over the GPL or APL.

So let me try to answer some of those questions (note: IANAL).

What is the Eclipse Public License?

The Eclipse Public License is an OSI approved license. It’s a weak copyleft license similar in spirit to the LGPL. Any changes and certain additions to EPL-licensed code need to be licensed on under the EPL.

This is unlike the GPL where it dictates that any work that is based on GPL-licensed code must itself be GPL-licensed. Some people like to call this licensing behavior viral.

If you want to learn more about the EPL, check out the EPL FAQ.

Why did Symbian favor the Eclipse Public License?

Well, according the Symbian FAQ, here is the reason…

“The Symbian Foundation has instead chosen the EPL because it wants to be absolutely clear about this: device manufacturers will be able to add new features and support new hardware without having to make all of that code open source, except where they are changing or making certain additions to EPL code supplied by the Symbian platform. We expect that device manufacturers will see the value of enriching the Symbian platform by contributing their innovations, but we don’t insist that everyone must contribute everything.”

On top of that, I postulate that Symbian recognized the importance of giving people a choice and protecting the investment in the Symbian platform code. This is where I argue a weak copyleft license like the EPL actually gives you more freedom than a strong copyleft license like the GPL. The GPL wants to devour your code and all of its friends. The EPL gives you a choice.

Why not LGPL? Well, there are some patent retaliation and reverse engineering clauses in the LGPL that make certain companies legal departments nervous. Other than that, I actually like the LGPL’s weak copyleft spirit.

The Rise of Weak Copyleft Licenses

One of my predictions is that in the near future, we will see a significant rise in the usage of weak copyleft licenses. If you’re looking to build an ecosystem full of commercial and individuals members, a weak copyleft license is the best choice in my humble opinion. Eclipse first blazed the weak copyleft builds ecosystems path with the CPL/EPL followed by Symbian. Microsoft is getting into the game with the MS-PL license (which is weak copyleft). Even Intuit’s Partner Platform is dancing with the EPL. I’m sure there are others in the wild.

Do other people have strong feelings on weak copy left licenses? Do you see a pattern too?

On a side note, if you have the time to burn on legal issues, I highly recommend taking a gander at Janet Campbell’s “Managing Open Source Legal Issues” video on EclipseLive.

Openfire switches to the Apache License 2.0

I was having my morning caffeine fix and saw a tweet go by…

OpenFire goes Apache 2.0

I quickly went to the front page and noticed it hasn’t been updated yet:

However, this is interesting news to say the least. When established open source projects backed by some company switch licenses, there’s usually a business model change afoot. Or was there pressure from Google to switch the license since Google Wave uses Openfire under the covers>?

Thankfully, Matt Tucker’s explanation hints at some of the reasons:

I’m happy to announce that Openfire will be moving to a more liberal open source license — Apache 2.0. Apache 2.0 provides significantly more flexiblity than the GPL in virtually every way, so it should be a big win for the community all around. We expect to get all the source code headers updated for the next release. There were several motivations for making this change:

  1. The GPL license was preventing some companies from using Openfire due to corporate policies
  2. There was no reason to keep using GPL and end-users generally seem to prefer Apache
  3. We’d like to encourage a broader range of commercial companies to contribute to the project and the Apache license is a good way to help make that happen

Would be happy to answer question or comments.

It was delightful to see the Openfire community be notified of the license change, with reasons why and a request for feedback. Scratch this one for the proper way of doing a license change in an open source community. In the open source world, we hold transparency sacred. Don’t be like switched from EPL to GPL and told no one until it was too late.

It’s important to be upfront and transparent.