A Fork in the Road
To understand Joomla, you have to start with Mambo. In the early 2000s, Mambo was a popular open-source content management system (CMS). But by August 2005, a conflict erupted between its core development team and Miro International Pvt. Ltd., the company
that held the Mambo trademark. The developers alleged that a newly formed foundation, meant to protect the project, was structured in a way that violated open-source values and prior agreements. Feeling that the principles of the project were at risk, the entire core development team walked away. They 'forked' the code, creating a new, independent project. Within a day, over a thousand supporters flocked to the new effort, signaling a major schism in the community. This new project was soon named Joomla, from the Swahili word 'jumla', meaning 'all together'.
The Principle of the Matter: Choosing the GPL
The newborn Joomla project had to make a foundational choice: its software license. The team unanimously committed to the GNU General Public License (GPL), the same license that powers projects like Linux and, notably, its future rival, WordPress. This wasn't just a legal technicality; it was a declaration of identity. The GPL is a 'copyleft' license, meaning it ensures four key freedoms: the freedom to run, study, share, and modify the software. Crucially, any derivative work must also be distributed under the GPL. This decision was a direct response to the conflict over control that led to the Mambo fork. By choosing the GPL, the Joomla founders ensured that their project could never be made proprietary. It was a promise to their community that the code would belong to everyone, forever.
An Ecosystem Built on Freedom
The GPL had a profound and immediate effect on Joomla's ecosystem. It cultivated a vibrant, collaborative community dedicated to the principles of free software. However, it also created a complex commercial landscape. The GPL requires that extensions which are derivative works of Joomla also be GPL-licensed. For a time, there was confusion and tolerance for non-GPL extensions as a way to attract commercial developers. But by 2009, the project fully committed, mandating that all extensions listed in the official Joomla Extensions Directory (JED) must be GPL-compliant. This fostered a culture of shared innovation but arguably made the commercial model more challenging than in the WordPress ecosystem. While the GPL allows for selling software, the requirement to distribute the source code made it harder to create the kind of proprietary, high-margin plugin and theme market that exploded around WordPress.
The Double-Edged Sword of Principle
In its early years, Joomla's popularity surged, at times even surpassing WordPress in search interest. Its more structured and powerful access control features made it a favorite for complex corporate and community sites. However, as the web evolved, Joomla's principled stance on licensing and its steeper learning curve became a competitive disadvantage against WordPress's relentless focus on user-friendliness and its sprawling, commercially supercharged ecosystem. While WordPress also uses the GPL, its community and commercial arms interpreted its application to themes and plugins more loosely, fostering a massive marketplace that lowered the barrier to entry for millions. Joomla’s market share, which was once a strong number two to WordPress, has since declined, finding its niche with developers and organizations that value its structured control over mass-market appeal.
