A Constitution, Not Just a License
When founder Dries Buytaert released Drupal in 2001, he bundled it with the GNU General Public License (GPL). In the freewheeling early days of open source, this was a monumental choice. The GPL is not a simple permission slip; it's a framework with a strong
philosophy. Often described as "copyleft," it grants anyone the freedom to use, study, change, and share the software. But it comes with a crucial condition: any derivative work you distribute must also be shared under the same GPL license. This prevents anyone from taking the open-source code, making proprietary improvements, and closing it off. Instead of just releasing code into the wild, the GPL created a reciprocal system—a constitution for a collaborative community.
Building a Community by Banning Forks
The GPL's primary effect was cultural. By ensuring that all improvements to Drupal would flow back into the main project, it created a powerful incentive for collaboration. If a developer built a new feature or fixed a bug, they couldn't just keep it for themselves and sell it. To benefit from the work of others, they had to contribute their own work back to the commons. This prevented the project from splintering into countless incompatible, private versions—a fate that has hobbled other open-source efforts. The license effectively forced everyone to invest in the same shared resource, turning a loose collection of developers into a unified community with a common goal: making Drupal better for everyone. This shared investment became a core part of the project's identity.
The Unlikely Engine of a Commercial Ecosystem
Here’s the paradox: a license that prevents you from selling the software outright ended up fostering a massive commercial ecosystem. Since no one could lock down and sell a superior, proprietary version of Drupal, companies had to find other ways to make money. They couldn't sell the car, so they started selling driving lessons, custom paint jobs, and high-performance engine tuning. An entire industry of digital agencies, hosting companies, and freelance developers emerged, offering services like customization, support, and maintenance. This model meant businesses were competing on the quality of their services, not on who owned the code. The GPL's "restrictions" inadvertently created a level playing field where expertise became the currency, allowing thousands of businesses to thrive by building on Drupal, not by owning it.
A Legacy of Trust and Predictability
Decades later, the wisdom of this choice is clear. The GPL provided a stable, predictable foundation that organizations could trust. Governments, universities, and large enterprises adopted Drupal precisely because the license guaranteed it would never be controlled or discontinued by a single corporate owner. The code was a public good, stewarded by a global community. While the code itself has been rewritten multiple times over successive major versions—from Drupal 7 to Drupal 11 and beyond—the license has remained the constant. It's the social contract that holds the entire project together, ensuring its longevity and independence. More than any single feature or elegant algorithm, the license is Drupal's most enduring and valuable asset, a testament to the idea that how we agree to work together is often more important than what we build.
