When companies claim to be open-source but secretly maintain control and profit from their projects
The open source revolution was supposed to bring about a new era of transparency, collaboration, and innovation. Instead, we've seen a surge in corporate open-washing – a marketing spin that hijacks the goodwill and ideals of the open source community. It's a phenomenon that's both fascinating and disturbing, as companies exploit the terminology and aesthetics of open source to sell their products and services.
So, what exactly is open-washing? It's when a company claims to be open source, but in reality, it's just a marketing gimmick. They might release a partial codebase, but keep the essential parts proprietary. They might use open source software, but restrict its use or modify it in ways that undermine the original intent. The goal is to create a perception of openness, while maintaining control and profit.
"Open-washing is a form of greenwashing, where companies pretend to be environmentally friendly or, in this case, open source, without actually doing the work." - Heidi Hess von Kruedener, Director of the Open Source Initiative
A prime example is Redis Labs' decision to change its licensing terms, effectively limiting the use of its popular Redis database in open source projects. This move sparked outrage in the open source community, with many accusing Redis Labs of open-washing.
The rise of GitHub has made it easier for companies to claim open source credentials. A project can appear open source simply by hosting its code on GitHub, without necessarily adhering to open source principles. The sheer number of GitHub stars, forks, and contributors can create a perception of popularity and community engagement.
Consider the case of Microsoft's .NET Core, which was initially released as an open source project on GitHub. While it did attract a significant following, critics argued that Microsoft's control over the project and its restrictive licensing terms undermined its open source claims.
Some companies have mastered the art of open-washing, using it to create a marketing machine that generates buzz and drives sales. Take, for instance, VMware's Tanzu platform, which was marketed as an open source solution, but turned out to be a heavily customized and restricted version of Kubernetes.
"The most effective way to kill an open source project is to co-opt it, then starve it, or to fork it and fragment the community." - Eric Raymond, open source pioneer
Licensing is a critical aspect of open source projects. Companies engaging in open-washing often use permissive licenses or create their own custom licenses that seem open, but contain restrictive clauses. The Server Side Public License (SSPL), introduced by MongoDB, is a prime example. While it's touted as an open source license, it restricts the use of MongoDB's software in certain scenarios.
Corporate open-washing threatens the very fabric of the open source movement. As the community continues to evolve, it's essential to hold companies accountable for their claims. We need to look beyond marketing rhetoric and scrutinize licensing terms, code contributions, and community engagement.
The open source community must remain vigilant and ensure that the principles of openness, transparency, and collaboration are upheld. Only then can we prevent open-washing and foster a genuine culture of innovation and cooperation.