Open-Source Tide and Bias

Open-Source Tide and Bias

Table of contents:-

A Rising Tide

Who Gets Left Behind?

The Bias Against Open Source Itself

Policy, Regulation, and the Road Ahead

Conclusion

---

There is a quiet but unmistakable revolution happening underneath the surface of global technology, and if you are running Linux, one of the BSD variants, a Unix derivative, or any independent distribution, you are already part of it. Open-source software is no longer a fringe pursuit for weekend enthusiasts or a cost-cutting compromise for budget-strapped startups. It has become the backbone of the modern digital world — powering clouds, data centres, artificial intelligence frameworks, financial systems, and government services from Reykjavik to Nairobi. Yet even as the tide rises with impressive force, currents of bias — both within open-source communities and directed at them from the outside — continue to shape who gets to participate, whose work gets recognised, and how the wider world perceives free and open-source software at large. This article sets out to explore both sides of that coin honestly and without fanfare.

---

A Rising Tide

The scale of open-source growth in the mid-2020s is genuinely staggering. According to market research published in early 2026, the global open-source software market was valued at approximately USD 45.8 billion in 2025 and is expected to reach USD 190 billion by 2034, growing at a compound annual growth rate of around 17%. What makes this figure meaningful rather than merely impressive is what lies beneath it: approximately 96% of commercial codebases in 2024 contained open-source components, with around 77% of internal code composition drawn from open-source libraries and frameworks. In other words, virtually every piece of enterprise software your organisation relies upon — whether or not the vendor admits it — is built, at least in part, on the work of open-source contributors.

The community driving this growth is vast and extraordinarily active. Over 1.1 billion open-source contributions were recorded in public repositories globally in 2024, with more than 395 million public projects active across various domains and over 518 million merged pull requests. That is not a hobbyist movement. That is a civilisation-scale engineering effort. And enterprises are taking note: nearly 95% of organisations increased or maintained their open-source use during 2023, with 33% reporting a significant increase in utilisation.

The sectoral breadth is equally striking. IT and telecommunications contributed around 26% of open-source service revenue in 2025, reflecting the deep penetration of Linux and Kubernetes across network infrastructure. Healthcare and life sciences is projected to grow at over 16% annually, driven by collaborative research and bioinformatics workloads, while 93% of manufacturing firms launched new AI projects during 2024, many built on open-source toolchains. Even the notoriously conservative financial sector has embraced the movement, with 52% of banks now operating formal Open Source Programme Offices.

The regulatory environment has begun to reflect this shift too. The EU Digital Markets Act designates six major technology gatekeepers, compelling enterprises to favour open standards in order to avoid ecosystem lock-in, while Germany's public sector has migrated to openDesk and Switzerland has introduced a legal requirement for government software transparency. Across Europe, the EuroStack Project has called for an "Open Source First" principle to be embedded into public procurement directives, arguing that open-source software should be the default choice for public-sector IT projects, with procurement of proprietary software requiring a demonstrably justified and publicly documented exception. This is a seismic cultural shift in how governments think about digital infrastructure.

For BSD users in particular — whether you are running FreeBSD, OpenBSD, NetBSD, or one of the many derivatives — it is worth noting that the permissive licensing model that BSD pioneered has quietly become the dominant approach to open-source distribution. Permissive licences now account for 78% of all open-source components as of 2024, up from 76% the previous year. The philosophy of sharing code freely, without the reciprocal obligations of copyleft licences, has won the argument in practice even if it rarely wins the headlines.

---

Who Gets Left Behind?

Here is where the picture becomes more complicated, and where honesty is essential. The open-source world has long celebrated meritocracy as one of its founding virtues: contribute good code, and your background should not matter. The evidence suggests that principle, noble as it is, has not yet been fully realised in practice.

The Linux Foundation's landmark 2021 Report on Diversity, Equity, and Inclusion in Open Source, based on a worldwide survey of over 7,000 initial respondents, provides the most comprehensive data we have on this subject. Whilst 82% of respondents reported feeling welcome in the open-source community, the 18% who did not were disproportionately from underrepresented groups — people with disabilities, transgender individuals, and racial and ethnic minorities in North America. Feeling unwelcome is not a minor inconvenience; it is a structural barrier to participation that drains the collective talent pool of the entire community.

The gender dimension is particularly well-documented. Data from the TODO Group, an open-source management programme backed by major technology firms, notes that women account for approximately 10 to 11% of open-source contributors, despite representing around 26% of the broader computing workforce. A widely cited 2017 study of over three million pull requests on GitHub found something revealing about the underlying dynamics: code written by women was accepted more often overall (78.6%) than code written by men (74.6%), but among developers who were not project insiders, women's code acceptance rates dropped by 12% when gender was identifiable from a username or profile picture — compared with only a 3.8% drop for men under the same conditions. The quality of the work was not the issue. The identity of the author was.

The Linux Foundation's report also found that women, non-binary people, LGBTQ+ individuals, and people with disabilities were twice as likely to have experienced threats of violence in the context of an open-source project, and that transgender respondents were three times as likely to face occasional or frequent threats of violence or stalking. These are not abstract statistics. They represent real people who have been driven away from communities that claim to value openness above all else.

Geographic and linguistic bias adds another layer. Only 66% of the open-source community agreed that people from different backgrounds have an opportunity to participate in open-source projects. Respondents from Africa and the Middle East, as well as Black and indigenous people, were more likely to cite race as a barrier, whilst Portuguese speakers — predominantly Brazilian — were more likely than average to say their background was a burden to participation. The tools, documentation, and community culture of many major projects remain overwhelmingly English-language and Western in their cultural assumptions, which creates a silent but effective filter on global participation.

The good news is that awareness of these issues is now firmly embedded in mainstream open-source governance. The Linux Foundation offers the Inclusive Open Source Community Orientation course, covering unconscious bias, racism, and sexism, and actively promotes mentoring programmes as a concrete mechanism for change. The Inclusive Naming Initiative, launched at KubeCon North America, works to standardise inclusive language across the industry. The Linux kernel itself adopted inclusive language in its 5.8 release. These are real steps, even if the distance yet to travel remains substantial.

---

The Bias Against Open Source Itself

Ironically, even as open-source software powers the planet's infrastructure, a persistent set of misconceptions and institutional biases continues to work against it — particularly in enterprise procurement decisions and in media coverage of the technology sector.

One of the most stubborn myths is that open-source software is inherently less secure than proprietary alternatives. The perception gap here is startling. When enterprise security professionals were asked about vulnerability trends in 2024, approximately 24% believed vulnerabilities had increased, 50% thought they remained stable, and 25% perceived a decrease. Meanwhile, the actual data showed approximately 25% more vulnerabilities across all software in 2024 compared to 2023, with Linux-specific vulnerabilities jumping from 290 to 3,559 — a figure largely attributable to kernel Common Vulnerabilities and Exposures authority developments rather than a genuine worsening of Linux security posture. The jump in reported figures largely reflects improved reporting and classification, not a sudden collapse in software quality. Yet the optics are damaging, and organisations making procurement decisions based on perception rather than evidence may draw entirely the wrong conclusions.

The bias against open-source AI models is similarly misplaced. A persistent and often misleading narrative paints open-source AI as an unregulated "wild west," implying that powerful models are released without regard for safety or potential misuse. In reality, open-source development allows for greater transparency, enabling researchers to detect and mitigate biases more effectively than in closed systems. The very openness that sceptics cite as a vulnerability is precisely the mechanism that makes open-source software auditable, correctable, and ultimately more trustworthy over time. Red Hat's work on projects such as InstructLab demonstrates that community-driven AI development can embed safety directly into the training process and make responsible AI accessible to organisations that cannot afford to build models from scratch.

There is also a commercial bias at play in how enterprise software is evaluated. Proprietary vendors have long benefited from a structural advantage: dedicated sales teams, polished marketing, and procurement processes designed around the assumption that "real" enterprise software comes with a commercial licence and a support contract. Independent Linux distributions, BSD variants, and community-led projects often lack the marketing budget to compete for visibility, even when their technical quality is equal or superior. The EuroStack Project's position paper on EU procurement noted that current procurement processes contain a direct bias against open-source software, arguing for mandating that all decisions to choose proprietary software over an open-source alternative be publicly documented and justified. This kind of structural transparency would be genuinely transformative if adopted widely.

Meanwhile, research bias in the academic study of open-source software has its own well-documented problem. As one peer-reviewed dataset paper noted, the open-source nature of accessible public repositories means that volunteer-driven projects are overrepresented, biasing research results — especially those related to software architecture or communication and organisation structures — away from enterprise-driven open-source development, which is far from a niche phenomenon. When the academic literature skews towards a particular type of project, the policy and procurement guidance that flows from that research skews with it.

---

Policy, Regulation, and the Road Ahead

The regulatory landscape of 2025 and 2026 is the most consequential in the history of open-source software, and the decisions being made now will shape the ecosystem for a generation. For users and developers across BSD, Linux, Unix, and independent distribution communities, understanding these policy currents is no longer optional.

The EU's Digital Markets Act has fundamentally reordered the competitive dynamics of the European technology market. By compelling major platform gatekeepers — Alphabet, Amazon, Apple, ByteDance, Meta, and Microsoft — to provide interoperability, data portability, and equal treatment, the Act aims to prevent large companies from abusing their market power and to allow new players to enter the market. For open-source projects, this creates genuine opportunity: when users can more easily switch between platforms and when APIs must be opened on fair terms, the advantage that proprietary ecosystems derive from lock-in begins to erode. The early evidence supports this optimism — in the first month after DMA provisions came into force in March 2024, independent browsers saw a spike in users across the EU, with several alternative browsers reporting user growth of hundreds of percent.

The EU AI Act, fully adopted by the European Parliament in March 2024, takes a risk-based approach to artificial intelligence governance and includes specific provisions relevant to the open-source community. Crucially, the Act provides limited exceptions for free and open-source AI models, acknowledging that the transparency and auditability of open-source development itself serves legitimate safety objectives. This is a meaningful regulatory endorsement of the open-source model's intrinsic value.

Outside Europe, the US Bureau of Labor Statistics projected employment in computer and information technology occupations to grow by 15% between 2021 and 2031, adding around 682,800 new jobs — growth that will inevitably drive demand for professionals with open-source skills. The US federal government, too, has increased its engagement with open-source infrastructure: a US Government Accountability Office report published in February 2024 found that federal agencies had increased their cloud adoption by 27% over the preceding two years, with open-source solutions playing a key role.

One area of genuine concern that the policy community is only beginning to address is the funding and sustainability of the volunteer-driven infrastructure that underpins so much of the digital economy. Supply-chain security incidents in 2024 and 2025 have exposed how much critical software relies on the unpaid labour of a handful of individual maintainers. The April 2025 withdrawal of US federal funding for the CVE vulnerability tracking system complicated vulnerability management across the global open-source ecosystem — a stark reminder that open-source infrastructure, for all its collaborative spirit, remains vulnerable to the withdrawal of institutional support.

The open-source community has every reason to engage actively with policymakers, not simply as advocates for permissive licensing, but as the architects of the digital infrastructure that modern society depends upon. The stronger the case made — with evidence, with professionalism, and with genuine diversity of voice — the more likely it is that regulation will reflect and protect the values of openness, transparency, and community-driven innovation.

---

Conclusion

The open-source tide is real, it is rising, and it is reshaping global technology in ways that were unimaginable even a decade ago. From the Linux kernel that powers most of the world's cloud infrastructure, to the BSD networking code embedded in devices billions of people carry in their pockets, to the independent distributions that give users genuine sovereignty over their computing environments, open-source software has already won many of the arguments that once seemed contested. But winning the technical argument is not the same as winning the cultural one.

Bias — in recruitment, in code review, in enterprise procurement, in media coverage, and in academic research — continues to limit who benefits from the open-source revolution and who gets to shape it. Addressing that bias is not a distraction from the technical work of building great software. It is part of that work. Communities that are genuinely diverse in gender, geography, language, and background produce better, more robust, more widely applicable software. The evidence for this is not ideological; it is empirical.

For every developer reading this on a BSD workstation, a Linux desktop, or a Unix terminal anywhere in the world: your platform represents something genuinely important — the idea that technology built in the open, by everyone, for everyone, is better for the world than technology built behind closed doors for the benefit of the few. Keep building. Keep contributing. And keep pushing back, respectfully but firmly, against every form of bias that would narrow the door.

---

Disclaimer: All trade names, trademarks, and registered marks referenced in this article — including but not limited to Linux, BSD, FreeBSD, OpenBSD, NetBSD, Unix, Red Hat, Ubuntu, Canonical, Kubernetes, GitHub, GitLab, and any other product or service names mentioned — remain the property of their respective owners. The Distrowrite Project makes no claim of association, affiliation, or endorsement by any of these entities. Every reasonable effort has been made to ensure the accuracy, currency, and factual integrity of the information presented, drawing from publicly available and officially sourced material. However, the open-source landscape evolves rapidly, and readers are encouraged to consult primary sources for the most current data. Nothing in this article should be construed as legal, financial, or procurement advice. The Distrowrite Project does not endorse, promote, or facilitate any activities involving malware, viruses, exploits, or harmful software of any kind, and firmly opposes any conduct that may compromise the integrity, security, or availability of networks, devices, or digital infrastructure.

---

References:-

1. Linux Foundation – Diversity, Equity, and Inclusion in Open Source (2021 Report): https://www.linuxfoundation.org/research/the-2021-linux-foundation-report-on-diversity-equity-and-inclusion-in-open-source

2. Linux Foundation – Addressing DEI in 2021 and Beyond: https://www.linuxfoundation.org/blog/blog/addressing-diversity-equity-and-inclusion-in-2021-and-beyond

3. Linux Foundation – Inclusive Open Source Community Orientation (LFC102): https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/

4. TODO Group – Building an Inclusive Open Source Community: https://todogroup.org/resources/guides/building-an-inclusive-open-source-community/

5. The New Stack – Look Past the Bros, and Concerns About Open Source Inclusion Remain: https://thenewstack.io/look-past-the-bros-and-concerns-about-open-source-inclusion-remain/

6. The New Stack – How Implicit Bias Impacts Open Source Diversity and Inclusion: https://thenewstack.io/how-implicit-bias-impacts-open-source-diversity-and-inclusion/

7. Wikipedia – Diversity in Open-Source Software: https://en.wikipedia.org/wiki/Diversity_in_open-source_software

8. Open Source Diversity (opensourcediversity.org): https://opensourcediversity.org/

9. Canonical – State of Global Open Source 2025: https://canonical.com/blog/state-of-global-open-source-2025

10. OpenLogic – State of Enterprise Linux Distributions After CentOS EOL: https://www.openlogic.com/blog/top-enterprise-linux-distributions

11. Red Hat – Reducing Bias in AI Models Through Open Source: https://www.redhat.com/en/blog/reducing-bias-ai-models-through-open-source

12. TuxCare – Enterprise Linux & Open Source Security: A Reality Check for 2025: https://tuxcare.com/blog/enterprise-linux-open-source-security-a-reality-check-for-2025/

13. Grand View Research – Open Source Services Market Report: https://www.grandviewresearch.com/industry-analysis/open-source-services-market-report

14. Market Reports World – Open Source Software Market 2025–2034: https://www.marketreportsworld.com/market-reports/open-source-software-market-14722346

15. Mordor Intelligence – Open Source Service Market: https://www.mordorintelligence.com/industry-reports/open-source-service-market

16. European Commission – Digital Markets Act: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/digital-markets-act-ensuring-fair-and-open-digital-markets_en

17. Wikipedia – Digital Markets Act: https://en.wikipedia.org/wiki/Digital_Markets_Act

18. EuroStack Project – Position Paper on EU Procurement for Open Source Digital Sovereignty (March 2025): https://euro-stack.com/blog/2025/3/eu-procurement-for-open-source-digital-sovereignty-final

19. MDPI – Is Open Source the Future of AI? A Data-Driven Approach (March 2025): https://www.mdpi.com/2076-3417/15/5/2790

20. commandlinux.com – Open Source Licence Usage in Linux Projects Statistics 2026: https://commandlinux.com/statistics/open-source-license-usage-in-linux-projects

---

🌊

Back to top