There’s a bunch of drama going on in the Wordpress community right now over the GPL.
I’ll be honest, I don’t understand the whole story–I only live at the fringe of the Wordpress world. But I follow a couple Wordpress rockstars on Twitter: GPL advocate Ian Stewart and GPL opposer Nathan Rice (honestly, Nathan’s position is substantially more complex than that–I’m simplifying for the sake of argument).
A few days ago, they had a battle royale on Twitter over the GPL, and later some brief discussion over this article’s claim that the GPL is bad for Wordpress.
Two interesting things strike me here:
- This whole debate hasn’t been picked up by Slashdot and the people opposing the GPL (because people could take their premium, pay-to-play, themes and redistribute them for free) mocked for not understanding the GPL in the first place.I’m not arguing that they should be mocked, just that’s its suprising it hasn’t happened.I will say, though, that I don’t understand what theme creators and sellers expected to happen as they move towards the GPL–the GPL has always been about giving the people with your code the freedom to do what they want with it (as long as they don’t lock it up).
- I’m suprised at how valuable the community is to these people. In fact, I can’t help but wonder if it’s not more important than the code itself.When I read the article I linked to above, my first gut response was “If you don’t like the way things are, just fork it–it’s GPL’ed!“But the more I thought about it, the more I realized that forking isn’t necessarily an option–the issue isn’t a dissatifaction with the code; it’s a dissatisfaction with the community around the code, and the way that community is being forced to use the GPL for everything.This slides pretty quickly into the classic BSD vs. GPL argument, ie. which is more free, a licesnse that preserves freedom indefinitely or a license that gives indefinite freedom (including the freedom to end freedom).
I have no desire to weigh in on that debate, nor do I think I have any authority to suggest which is more appropriate for Wordpress (I tend to think that a BSD-style would be better, but things get murky really fast when you’re talking about web applications, so I don’t really know).
In any case, I’ll give kudos to Ian Stewart and his Thematic project, which positions itself pretty clearly as theme built on the ideas behind the GPL. Thematic is a theme designed to built upon, as a sort of library that new themes can link in, something that will do a lot of the heavy (and boring) lifting freeing up the author of the new theme to work on the fun stuff.
In so doing, Ian has created not a new theme, but a new market with himself as the market-share holder: the custom Thematic theme creation and support market. It might not (yet) be as lucrative as simply selling themes for $50/pop, but he’s certainly the person I’d try to hire if I had the budget to build an important blog on Wordpress.
A few days ago, I read this blog entry by a software developer. He writes:
To be totally honest I don’t have a lot of sympathy for capitalists who say “you’re doing something that makes it hard for me to make money in the way that I’ve grown used to making money.” Capitalist’ lack of creativity is not a flaw in the Free Software movement.
This is the problem with using the GPL for Wordpress–it puts a big dent in a business model built around the project in the name of preserving innovation.
Ian understands this and is building his lively hood and reputation online around this idea–he’s making money in a new way, preserving his livelyhood and the culture of freedom and innovation that the GPL demands. That’s the kind of new business models we need.
2 Comments
Thanks for the very kind words! I’m humbled.
But note: Nathan Rice and I are sorta online pals—even though he’s always wrong. Except when he’s always right.
I don’t see any problem with the gipples.