The GNU General Public License (GPL) is a series of widely used free software licenses that guarantee users the freedom to run, study, share, and modify software. It uses a legal mechanism called copyleft to ensure that all derivative works remain free for everyone. For marketers and SEO practitioners, the GPL is the foundation of platforms like WordPress and Drupal, influencing how tools and plugins are developed and commercialized.
What is the GNU General Public License (GPL)?
The GPL is a copyleft license created by Richard Stallman for the GNU Project and the Free Software Foundation (FSF). Unlike permissive licenses that allow users to take code and make it proprietary, the GPL requires anyone who distributes the software to provide the source code and the same freedoms they received.
The license family is historically one of the most popular in the free and open-source software (FOSS) domain. Developers used the first version of the license, [v1, released on 25 February 1989] (GNU Project), to prevent software distributors from restricting human-readable code. Over time, it has evolved into a standard that protects community contributions from being exploited by companies that do not contribute back.
Why the GNU General Public License (GPL) matters
- Continuous Freedom: Copyleft ensures that software remains free in all future versions, preventing it from being turned into proprietary "black box" tools.
- Commercial Potential: You can charge for the service of distributing GPL software, but you cannot hide the source code from your customers.
- Safety from Patents: The license includes protections to prevent software patents from making a free program effectively proprietary.
- Community Growth: By requiring modifications to be shared, the GPL builds a large pool of compatible code that everyone can use to improve their own tools.
- Legal Protections: The GPL removes the liability for authors by stating clearly that there is no warranty for the free software.
How the GNU General Public License (GPL) works
The GPL operates on the principle of "reciprocity." If you use and distribute GPL-covered code, you must abide by these mechanisms:
- Copyright Assertion: Developers first assert copyright on the software and then offer the GPL to give others permission to use it.
- Propagation and Conveying: The license regulates "propagation" (copying or modifying) and "conveying" (transferring copies to others). Mere internal use does not trigger the requirement to share code.
- Source Code Access: If you convey software in a compiled (binary) form, you must also provide the "Corresponding Source" in a way that is easy for the recipient to access.
- License Continuity: Each recipient automatically receives a license from the original licensors to run and modify the work.
Versions of the GNU General Public License (GPL)
| Version | Release Date | Key Focus |
|---|---|---|
| GPLv1 | Feb 1989 | Prevented "binary-only" distribution and added protection against restrictive combinations. |
| GPLv2 | June 1991 | Introduced the "Liberty or Death" clause (Section 7), ensuring rights cannot be severed by legal disputes. |
| GPLv3 | June 2007 | Addressed "tivoization," software patents, and improved compatibility with other licenses. |
The transition to the latest version involved a massive public consultation where [2,636 comments were submitted] (Wikipedia). Following the [v3 launch on 29 June 2007] (GNU Project), adoption was swift in many areas: by [2009, 50% of GPL projects had moved to v3] (CNET News). However, usage has shifted recently: by [2018, the combined GPL family share of projects fell to 24%] (Black Duck Software).
Best practices
- Include a license copy: Always distribute a verbatim copy of the GPL license text along with your program.
- Mark modifications: Clearly state in your files that you have changed the software and provide a relevant date to avoid errors being attributed to previous authors.
- Use the "or later" clause: Licensing software as "GPLv2 or any later version" provides a "lifeboat" for future compatibility if the FSF updates the license.
- Provide source code simply: Use peer-to-peer transmission or network servers to give users access to the source code at no extra charge.
- Verify library licenses: If you are building a proprietary tool, use the LGPL (Lesser GPL) for subroutines to avoid the "viral" requirement of releasing your entire application's code.
Common mistakes
Mistake: Thinking GPL software cannot be used for commercial products. Fix: You can sell GPL software at any price, but you must grant the buyer the same freedoms you had.
Mistake: Providing source code in an "obfuscated" or unreadable format. Fix: Provide the "preferred form" of the work that is actually used for making modifications.
Mistake: Ignoring the "viral" nature when linking libraries. Fix: Understand that statically or dynamically linking a GPL library usually requires your entire program to be under the GPL.
Mistake: Using GPLv3 code in hardware that blocks user-modified software. Fix: Ensure your hardware (User Products) provides "Installation Information" so users can run their own versions of the code.
Examples
- Cisco Systems Settlement: In 2009, Cisco settled a lawsuit by agreeing to appoint a Free Software Director and make source code available for its Linksys division.
- Stockfish vs. ChessBase: Developers of the Stockfish chess engine sued ChessBase for selling modified versions without distributing them as free software. The [parties reached a settlement in 2022] (Stockfish Project) that restricted ChessBase from selling products containing the code.
- IBM and SCO Group: A long-running dispute over code in the Linux kernel ended when [IBM paid $14.25 million in a final settlement] (ZDNet).
- WordPress Ecosystem: Most WordPress themes and plugins are licensed under the GPL because they are considered derivative works of the WordPress core.
GPL vs LGPL
| Feature | GPL | LGPL |
|---|---|---|
| Primary Goal | Protect user freedom | Allow library use in proprietary apps |
| Derivative Requirement | Entire work must be GPL | Only the library must be LGPL |
| Common Use Case | Operating systems, CMS | Shared software libraries |
| Commercial Risk | High: Must share all code | Low: Only share library changes |
FAQ
Does using a GPL tool like GCC to compile my code make my code GPL? No. Using GPL-licensed tools (compilers, editors, or operating systems) to develop your software does not require you to license your finished product under the GPL. The license only applies to the code itself and any derivative works based on it.
If I modify GPL software for my company's internal use, do I have to share the code? Not specified in the sources as a requirement. Copyleft generally applies only when you "convey" or distribute the software to others. If the modified version is never shared outside your organization, you are not obligated to release the source code.
Can I use GPL code in a web service without releasing my own code? Yes. Under standard GPL, simple interaction with a user through a computer network (like a web portal) is not considered "conveying" a copy. However, the GNU Affero General Public License (AGPL) was created specifically to close this loophole for network-based applications.
What happens if I accidentally violate the GPL? Your rights terminate automatically, but they can be reinstated. If you cease all violations, your license is reinstated provisionally unless the copyright holder terminates it. If you cure the violation within 30 days of your first notice, your license is permanently reinstated.
Is the GPL an enforceable contract? Courts have ruled in favor of this interpretation. A [US federal court ruled in April 2017] (Quartz) that open-source licenses are enforceable contracts.
