Open Knowledge Foundation Germany has just released a new report titled: “From Software to Society: Openness in a Changing World” by Dr. Henriette Litta and Peter Bihr (I was also interviewed for it). The report talks about what openness means in our digital ages, both from the history of openness and evaluates current challenges.
One of the report’s key insights is that “Openness is not neutral”—a point that resonates deeply with me. I often find myself frustrated with limited imaginations of what free and open source software is and should look like and what it should accomplish.
The recent “open source AI” definition debacle has made this painfully clear. Watching the Open Source Initiative contort themselves to legitimize technologies that rely on extractive labor and environmental gluttony at a desperate bid for relevancy shows how hollow these older definitions have become, that even the organisation that claims to defend the open source definition just ignores a key tenet because it’s not “practical” (read: profitable).
Which is why we need a better definition for what makes a technology truly open beyond the issue of licencing or making source code available. Making source code available doesn’t automatically create ethical practices or sustainable communities. A permissive license doesn’t prevent maintainer burnout, toxic communities, or corporate capture of standards.
I’m not proposing we throw it away, I still believe firmly in the four freedoms. But we need a more holistic definition. And there is still potentially some room for improvement in the licencing realm. The OKFN report for example refers to the need for “protective mechanisms such as fair licences and share-back models”.
That said, I have some more thoughts to share on how to evaluate and improve the openness of the FOSS ecosystem more holistically. I’m not about to propose a full definition here, but here are some aspects I think should be considered:
- Open standards and interoperability. True openness requires genuinely open standards and meaningful interoperability, not just open source licenses. We’ve seen how open protocols and formats can enable entire ecosystems to flourish, especially looking at internet technologies. Market concentration undermines even the most open standards when monopolies can embrace, extend, and extinguish at will.
To reference this recent research by Clement Perarnaud and Francesca Musiani on QUIC’s standardization, even “open” standards processes can become vehicles for corporate control when dominant players leverage their resources to reshape fundamental Internet architecture. Google’s QUIC development demonstrates how a company can mobilize superior “human resources, technical means, and strategic vision” to effectively capture standards bodies while maintaining the appearance of openness.
- Fair work practices, not free labor. The maintainer crisis won’t be solved by better licenses but by sustainable funding models, reasonable expectations, and treating the labor that builds our digital commons with dignity. The report emphasizes, we need “targeted investment in innovation for the common good”—which must include investing in the people who maintain our infrastructure.
- Democratic governance structures. Our critical infrastructure shouldn’t depend on benevolent dictators or corporate whims. We need transparent, accountable governance that serves communities, not shareholders.
- Worker organization. We’re stronger together than as atomized individual contributors. Other industries have learned this, FOSS developers can too.
- Inclusive communities. Codes of conduct aren’t just theater; they’re about creating spaces where everyone can contribute without fear or harassment. There is a loud section of developers in FOSS communities that seem to believe that diversity is a zero sum game, but it isn’t. We need more contributors and maintainers, and the only way to grow is to remove the barriers that have historically marginalised diverse communities from participating.
Ultimately, I think we need to build new structures and institutions, ones that understand openness as a holistic practice, not just a licensing strategy or a vehicle to stay up to date with hype technologies. Organizations that speak for workers, not just code, or capital.
This blogpost won’t resonate with everyone, but I’m not writing this to provoke a reaction or argue, so if you find yourself at odds with what I wrote, here is my permission for you to let go and live your day. If it did resonate with you however, I would love to talk more about how we can better build these structures and institutions that can make FOSS more holistically open, through the communities we build, the standards we protect, the labor we organize, and how we treat each other.