How to make a living from WordPress development without violating the GPL
Much of what is written below has already been covered in interviews ad-nauseum with Matt Mullenweg. And if you’re already ‘pro at GPL’ then there probably isn’t much new you could learn here, unless you’re looking for a refresher course. If you want the TLDR version you can go straight to the video below, but for additional insight from a one-man-army developer, read on. You may just learn a thing or two.
A little background
When I first got into WordPress development I was admittedly a bit fuzzy on what my rights were when it came to the subject of selling my work online. I had a vague idea that anything I produced under the WordPress framework was ‘public’ or ‘open’ to some degree, but I didn’t know to what extent.
Not everyone who works with WordPress for a living necessarily knows exactly where they stand relative to the GPL, and depending on who you ask you may get varying degrees of opinions on the subject.
To cite an anecdotal example, I once had a developer email me a few years ago insisting that I “hand over a copy” of the Task Rocket website theme (the original theme I custom designed and built specifically to market the Task Rocket product) because, he said – and I’m paraphrasing here – “WordPress is open source and you have to give it to me whether you like it or not” – or some misguided reasoning to that effect. While he was completely misinformed, it still serves to illustrate that not everyone knows what rights the GPL actually affords those who work within the WordPress ecosystem.
I’m sure other developers have similar stories but in case you’re wondering, you absolutely do not have to hand over a copy of your custom theme or plugin – under certain conditions (more on this subject later).
WTF is the GPL?
The General Public License (which WordPress utilises) allows users the freedom to run, study, share, modify or even sell any software that is licensed under the GPL. In the context of WordPress this extends to any software that uses the WordPress framework and APIs in order to function and – this is the key distinction – only if you are distributing said software.
The key here is worth repeating: this only applies to GPL software you are distributing.
The basic principle is: the same rights that were afforded to you while developing your WordPress software should be inherited by the people using your WordPress software.
In other words, as you were happy to build your software on top of established GPL licensed WordPress APIs, functions, hooks etc, the same license applies to whatever you were able to derive from it. This is a condition of working with any software licensed under the GPL, not just WordPress.
Furthermore, if you were to distribute your custom WordPress theme or Plugins with a proprietary license, you would in fact be violating the terms of the GPL.
Does this mean I have to give my work away for free?
Absolutely not, but it’s easy to interpret it that way.
As mentioned the GPL affords many freedoms, including the right to sell (distribute) your software to paying customers. But it’s worth keeping in mind that the person who paid money for your software also inherits the right to do exactly the same with it, and neither party can dictate any conditions (aside from keeping a copy of the GPL license with the software).
At this point it’s very easy to form a picture in your head where one person buys a copy of your software and then distributes it to all his friends, and although that’s a legitimate concern and it might feel like piracy, it’s not even close.
Think of it this way: When you’re selling your WordPress software you should be selling the value in other areas, instead of just the code. For example, most theme and plugin developers put up a paywall to sell their products and make you enter a license key (which is legit and the GPL is totally cool with it), but in reality what they’re selling is the support, time and resources that are required to maintain the product for you.
This is something that most customers are willing to pay for because:
- it provides reassurance to know they can get support for the product
- the product they paid for will continue to work into the future with updates
- they typically don’t have the technical expertise or the budget to roll and maintain their own solution
This is also why it’s important to make sure your potential customers understand what they are getting for their money, such as ongoing software updates, fast support, access to community forums and documentation etc, and make this known when marketing the product. Most customers probably don’t care (or are even aware) that they can share, modify or sell the software they just purchased from you.
Is my original content forced to inherit the GPL?
That’s totally up to you. If you want to employ a different license for CSS, JS, Images, SVGs, documentation, branding or anything else that is your own original work, you are free to do so. Some developers will offer a separate ‘developer license’ (usually paid for) that will give the user the right to include all your original assets when they share your software.
A good real world example of this happened a few years ago, when Sean Lang forked the excellent commercial Migrate DB Pro plugin on Github, and stripped out the licensing code. It would be easy to think this was a dick move, but Lang was well within his rights (as is anyone) because Migrate DB Pro is licensed under the GPL. He did, however, have to remove all instances of copyrighted material owned by the plugin developer.
What about the website I built for myself or a customer?
If you’re contracted to build a website for a client on WordPress, in this instance the GPL does not apply. The GPL would only apply if you or your client plan on distributing the software, but this is typically not the case when a client has contracted you to build them something that will only be used in a single instance.
That said, if you handed over the software (website files) to your client and they decided to start distributing it, then the software would be bound by the GPL. This might be worth mentioning to your client if you’re in a situation where you need to hand over the theme or plugin you created to them.
Are collaborators on the software allowed to distribute it?
No. If you have other developers working on the software, say in a web development agency scenario or even remotely for example, this does not constitute distribution. The software developer (typically the company or agency producing it) with all its employees and contractors is considered to be a single entity and therefore retains copyright ownership of the code regardless of how many employees it has been distributed to for development purposes.
Ways to legitimately earn income from your WordPress software
As mentioned earlier many developers put up a paywall for their products. But you don’t have to do this for all your products. An excellent real-world example of this is WooCommerce, who give access to their core theme for free (a good strategy for encouraging mass adoption) and only charge for their extensions, premium store themes and support (all of which is optional). But that model doesn’t necessarily agree with everyone and if you’re not comfortable with it, there are other options.
Some developers offer a free ‘lite’ version of their theme or plugin but charge to upgrade to a pro version.
Another (perhaps financially riskier) scenario is to simply give all your software away for free but charge to help customers set it up, customise it, or solve other problems for them.
There are even WordPress developers who don’t produce specific products for sale as such, but instead market themselves as WordPress solutions experts who will build custom theme and plugins for your business needs.
It all depends on what model your comfortable with (and you can change anytime), but the point here is that there are options available that don’t violate the terms of the GPL.
How to decide if your WordPress software is bound by the GPL
Usually it always does. But if in doubt, ask yourself: Will my code function normally if I take WordPress out of the equation? If the answer is no, then your code is considered WordPress derivative and therefore the GPL applies.
Matt Mullenweg talks about the GPL
Where’s the Money in Free Software?
Stripe for Invoice Rocket has been updated to 1.2
The new update to the Stripe extension adds an improved user experience for your customers and also some nice workflow enhancements.Keep reading
Invoice Rocket goes dark
If you’re the type who likes to work in the dark, or you just prefer dark themes in general, then the new Dark Theme option should be a welcome addition.Keep reading
The Invoice Rocket sidebar UX has been improved
This new interface tweak solves that problem by breaking the invoice sidebar up into three sections: Invoice Details, Chart and Tools, allowing you to tab between them.Keep reading
Invoice Rocket 1.2.9 update
Thanks to a nudge in the right direction from a new user, Invoice Rocket now complies with European tax regulations.Keep reading
Another preview of the new Task Rocket 5 interface
Although it may not look like much has changed since the last preview, a lot of work has been happening under the hood to make it this seamless.Keep reading
An early preview of the Task Rocket 5 interface
It’s still got a long way to go, but I thought it would share a little progress with the Task Rocket 5 interface update.Keep reading
Task Rocket 5 is in development. Here’s what you need to know.
I think it’s well worth investing time and resources into a re-build of Task Rocket instead, which will eventually be Task Rocket 5.Keep reading
Why automation in WordPress is unreliable and how to fix it
How WordPress handles automation, why it took so long for any Rocket Apps product to get automation, and how you can easily fix automation on your own website.Keep reading