Published

The Word of the Day is “Derivative”

If WordPress were a country, our Bill of Rights would be the GPL because it protects our core freedoms. We’ve always done our best to keep WordPress.org clean and only promote things that are completely compatible and legal with WordPress’s license. There have been some questions in the community about whether the GPL applies to themes like we’ve always assumed. To help clarify this point, I reached out to the Software Freedom Law Center, the world’s preeminent experts on the GPL, which spent time with WordPress’s code, community, and provided us with an official legal opinion. One sentence summary: PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.

This has been a discussion in the WordPress community for a little while now, with the rise of both sponsored and commercial themes and the authors of many of those themes claiming full copyright or a subset of Creative Commons over them in order to protect them from redistribution or changes. I’m pleased to see that there’s an authoritative word on it now, and also pleased to know that the WordPress theme directory (and as of 2.8, in-admin theme browser) will only contain themes that are licensed by the GPL or are GPL-compatible (for WordPress, this also means making the CSS and Javascript GPL).

Some people might argue that it’s impossible to create a business structure based around something that is GPL-licensed, but if you take a good look around, there are many companies who now fully embrace open source (using the GPL, LGPL, GFDL, or even the OSL) as a way of life and a way of doing business who are doing quite well in offering consulting or expanded support, selling a base or preconfigured package, or offering other services that are built upon or extrude from their contribution to the open source community. Doing business this way earns you points, contributes to the Internet community as a whole, and gains you the support of dedicated volunteers to help make your product better. What’s not to like?

This also clearly illustrates Matt’s view that people can (and will be endorsed if they do with it with the GPL License) make money using WordPress.

Of course they can. Automattic makes money using WordPress. There’s a virtual army of consultants out there who make money using WordPress. I’ve made money using WordPress. And the endorsement area on WordPress.org is no small beans. I believe that listing page will prove to be lucrative for those theme houses who have chosen to go GPL.

UPDATE: Daniel Jalkut speaks to the GPL as an imposition on those who might want to make contributions to a project:

Speaking of GPL succeses, WordPress is itself an example of monumental success. All of its developers have something to be immensely proud of. But whenever I am reminded that WordPress is GPL, my passion for it takes a bit of a dive. I’m more comfortable with the true freedom of liberally-licensed products. If a liberally-licensed blog system of equal quality, ease of use, and popularity should appear, my loyalties to WordPress would not last long. It’s your party, and you’re entitled to write the guest list. But take a look around the room: not as many folks as you’d hoped for? Liberally-licensed projects are booming. Speaking for myself, a developer who has been to all the parties, I’m much more likely to pass through the door that doesn’t read “GPL Only.”

His objections and points are noteworthy. One of the things that popped into my mind, however, is that WordPress is—for good or ill—bound by the GPL to remain GPL-licensed, as WordPress itself is a derivative of b2/cafelog, which was licensed under the terms of the GPL. (I think that’s how it works; I’m far from a GPL expert.)

UPDATE TO THE UPDATE: Matt responds to Daniel’s feelings regarding the GPL and restrictiveness:

It’s user freedom that the GPL was created to protect, just like the Bill of Rights was created to protect the people, not the President. The GPL introduces checks and balances into an incredibly imbalanced power dynamic, that between a developer and his/her product’s users. The only thing the GPL says you can’t do is take away the rights of your users in your work or something derived from a GPL project, that the user rights are unalienable. You are free to do pretty much whatever you want as long as it does not infringe on the freedoms of others. (Sound familiar?)

That’s what software freedom means to me, and it’s something I believe in strongly enough to fight for and defend even when it’s not the easy or popular thing to do. (Especially this weekend as we celebrate the original “fork” of the US from from England.)

You’re correct in that the GPL isn’t limiting WordPress—at least, I don’t think so. Daniel’s argument is that more developers might be attracted to the project if it were released under a more “liberal” open source license, and he might be right, but WordPress (and Daniel points this out in his own argument) has been hugely successful in part due to the GPL.