There was quite a stir last week when theme developer, Jake Caputo, posted on his blog that he was disallowed from speaking or volunteering at his local WordCamp because he sells his themes on ThemeForest. If you're interested in learning about the issue and the discussion, you can take a look at his post and the summary I wrote on my personal blog. This post isn't going to be about whether or not Jake should be able to present at WordCamps.
We wanted to take a few minutes to talk about the GPL and how it applies to Event Espresso. I tend to be the resident GPL evangelist, so I was asked to be the one to write this post on how the GPL plays into what we do at Event Espresso.
What is the GPL?
GPL stands for Gnu Public License, and it is the software license under which WordPress is distributed. Briefly, it is an agreement between the software developer and the user about how the software can be used and what the expectations of the software may be. There are a few key points that are important to remember when discussing the GPL:
1. The GPL affects distribution.
The GPL license only affects code that you distribute to other parties. Writing code for a web site or client, that never gets released for public consumption beyond that site, does not need to have the GPL license attached to it.
2. The GPL does not include any warranty or guarantee of support.
In fact, the GPL explicitly states that the code might not even work at all!
3. The GPL grants the user (anyone with a copy of the code) the freedom to take, modify and/or redistribute the code.
This means you can take any GPL code and re-release it as you see fit, though you need to put your name on anything you change, so someone can get in touch with you if there are problems.
4. All WordPress plugins and themes must be released under a GPL-compatible license.
This does not mean that WordPress plugins and themes must be released under the GPL exclusively, nor does it mean that everything in a WordPress plugin or theme must be licensed with the GPL. Internal usage within an organization is totally free and not subject to any conditions. There is no such thing as 'internal distribution' that would restrict the usage of your code by requiring it to be GPL'd. It does mean that if you are releasing a WordPress plugin or theme for distribution, that it needs to be -- in part or in whole -- released under a GPL or compatible license.
What's a "split-license"?
What does that mean for Event Espresso?
As a premium plugin developer, it's a difficult position to be in. The GPL makes it so anyone can get a copy of your plugin and resell it, or just provide a link to a full version of a piece of software that -- in our case -- has been the product of literally tens of thousands of hours of development. This is why, when you purchase Event Espresso, you are not buying the code. You are paying for support and updates for the length of the license -- the very things that the GPL implicitly does not provide. People are always finding ways to pirate software, and WordPress themes and plugins are no different. However, as I always like to say, good luck getting support. With Event Espresso, if you found a copy online (outside of our site) you would not be able to access the forums except for the free forums or the translator forums (where it would become obvious pretty quickly that you were not using the free version or had a question relating to the translations based on your version and your questions) and only limited access to our support documentation. And you would have no access to updates of any kind.
We are proud of our dedication to open source software. We are actively seeking new partnerships with other WordPress developers, and the API we're developing will expand Event Espresso events to sites that don't even run on WordPress. If you have questions about the GPL, take a look at the Frequently Asked Questions on Gnu.org or feel free to contact me on Twitter -- I love talking about the GPL helping people understand what it is and how it works!