Permissive vs Copyleft Licenses
You'll learn: The two major philosophies of open source licensing and how they affect what you and others can do with code.
The Core Distinction
When you release open source software, you must choose a license that defines how others can use, modify, and redistribute your code. These licenses fall into two fundamental categories that represent different philosophies about freedom and obligation.
Permissive licenses (like MIT, BSD, Apache 2.0) are minimalist. They say: "Use this code however you want—commercially, in closed-source products, wherever. Just keep the copyright notice." You can take MIT-licensed code, modify it, and sell it in a proprietary product without sharing your changes.
Copyleft licenses (like GPL, AGPL) enforce reciprocity. They say: "You can use and modify this code freely, but if you distribute your modified version, you must share those modifications under the same license." The GPL "infects" derivative works—it requires that software built on GPL code must also be open source under the GPL.
The Practical Implications
Think of permissive licenses like giving away a recipe with no strings attached. Someone can take it, add secret ingredients, and sell the result without telling anyone what they changed.
Copyleft licenses are like giving away a recipe that requires anyone who improves it to share their improvements back to the community. This ensures the software remains free and that improvements benefit everyone.
For businesses, permissive licenses are often preferred because they allow proprietary integration. Copyleft licenses can create "contamination" concerns—incorporating GPL code into a product may legally require open-sourcing the entire product.
Key Takeaway: Permissive licenses maximize freedom for users with minimal restrictions; copyleft licenses maximize freedom for the software itself by ensuring it and its derivatives remain open source forever.