Four Years in Open Source: Insights and Reflections

During my four-year journey as the Editorial Director for The Linux Foundation, I've gleaned significant insights and experiences open source. My role as the head of external and strategic communications involved producing blogs and whitepapers for virtually every open source project we oversaw, alongside extensive monthly and quarterly newsletters, and the organization’s annual report—2023's edition was a massive 160 pages.

After a month of reflection on my 30-year technology career, I've synthesized my insights about open source and its driving communities. My time at The Linux Foundation, especially under Mike Dolan, SVP of projects, stands out as a profoundly fulfilling chapter. In early 2020, Mike crafted a bespoke role for me, positioning me as LF’s chief storyteller for software and standardization projects. This allowed me to spotlight their vital contributions to the open source community and the broader tech industry. I am immensely thankful for his mentorship and the opportunity to elevate the communities that needed it most.

I'm equally thankful for the opportunity to work alongside a highly talented research writer and editor like Hilary Carter, who cultivated my op-ed-style writing talents into an academic format I had not had the chance to demonstrate previously. I assisted her in building the Linux Foundation Research organization from scratch and contributed as a research editor and author for reports like the annual State of Tech Talent Report and Mentorship in Open Source, among others.

As I transitioned out of the organization, I carried with me pride in my achievements and the contributions of others I helped elevate, both on social media and within the broader tech industry. Here are some pivotal lessons and observations from my journey:

Open source projects are in dire need of support. While well-funded and organized entities like CNCF, Hyperledger, and LF Networking thrive, hundreds of other initiatives urgently require diverse contributors, including maintainers, documentation experts, and financial and technical contributions from large organizations. However, these organizations often consume open source innovations without reciprocating, creating substantial risk and potentially affecting the operations and security of these projects and their users. Many smaller projects of vital importance to the tech industry need your help, such as Zephyr, Open Mainframe Project, and ELISA, to name a few. New projects like Open Wallet Foundation and even veteran ones like the Linux Kernel and RealTime Linux (PREEMPT_RT) need maintainers and contributors, and yes, financial assistance.

The role and importance of Open Source Program Offices (OSPOs) in both large and small organizations are dramatically understated. While a well-organized and funded OSPO is crucial for the success of open-source communities, many industries, particularly those heavily regulated like financial services, consume copious amounts of open source software but rarely contribute back due to various concerns. A well-run OSPO can bridge this gap, interfacing with stakeholders to alleviate fears, address issues, and cultivate best practices.

Neutral homes for open source projects, like the LF, are often overlooked. Many companies opt to maintain control over their projects, inhibiting adoption and contributions. This insular approach can chill the potential impact of these projects and often stems from a desire to avoid the complexities of neutral governance. However, this can be a short-sighted and self-centered strategy.

Politics and interpersonal relationships play a significant role in the success or failure of open source projects. A single toxic individual can cause significant disruptions, leading to contributors leaving or organizations withdrawing support. Conversely, a diverse and inclusive environment can foster a more robust and innovative community. While some view Diversity, Equity, and Inclusion (DEI) as contentious, diverse contributions are essential for innovation and health. Projects with a mix of genders, orientations, cultures, and abilities avoid becoming stagnant monocultures. When underrepresented individuals feel marginalized, the project's future is at risk. A thriving open source community requires evolving, diverse perspectives to foster growth and adaptation.

Finally, many brilliant minds behind open source projects aren't natural communicators. They often lack the time or skills to share their stories and impact effectively. If storytelling and communication are your strengths, consider lending your voice to these projects. Your support can make a substantial difference whether you're a coder, a business professional, or an end-user.

As we look ahead, the potential within the open source community is immense. Collaboration, innovation, and diversity are the cornerstones of this realm. Yet, realizing this potential requires active participation and thoughtful engagement from each of us. Here are some calls to action:

Join a Project: Identify an open source project that resonates with you and contribute in any way you can. Your skills can significantly impact smaller, under-resourced projects.

Advocate for Effective OSPOs: If you're in a position of influence, ensure your organization's OSPO is empowered and aligned with the broader goals of open source contribution.

Embrace and Advocate for Diversity: Whether through mentorship, supporting DEI initiatives, or simply amplifying underrepresented voices, your actions matter. If you're a communicator, lend your voice to projects in need. Your words can elevate the unseen work of brilliant minds.

Let's collaborate to build a more open, inclusive, and innovative world.