The GNU GPL Family
You'll learn how strong copyleft licenses ensure derivative software remains open source through the GPL v2 and GPL v3.
What Makes GPL Different
The GNU General Public License (GPL) family represents the strongest form of copyleft licensing. Unlike permissive licenses (MIT, BSD, Apache), GPL licenses require that any modified or derivative work must also be distributed under the GPL. This creates a "viral" or "infectious" quality—if you build on GPL code, your code becomes GPL too.
Think of it like a chain letter that can't be broken: everyone downstream must pass along the same freedoms they received.
GPL v2 (1991)
GPL v2 was the workhorse license for decades. Key requirements:
- Distribute source code with binaries (or offer it)
- Keep all GPL notices intact
- License derivative works under GPL v2
- Document your changes
Ambiguity: GPL v2 left questions about network services (SaaS loophole) and patent rights.
GPL v3 (2007)
GPL v3 modernized the license to address contemporary concerns:
- Patent protection: Contributors grant patent licenses to users
- Tivoization prevention: Hardware can't use technical restrictions to prevent users from running modified GPL software
- Network use clause: The AGPL v3 variant closes the SaaS loophole
- Better international compatibility
When to Use GPL
Choose GPL when you want to:
- Ensure all improvements remain open source
- Build a commons that corporations can't privatize
- Follow in the footsteps of Linux kernel, Git, WordPress
Avoid GPL if you want maximum adoption in commercial products—many companies prohibit GPL dependencies due to copyleft obligations.
Key Takeaway: The GPL family enforces software freedom through strong copyleft, requiring all derivative works to remain open source and granting explicit patent protections, making it the license of choice when you want to guarantee perpetual openness.