Bloomberg, CNCF, and OpenTelemetry Forge a New Path for Open Source Sustainability Through a Structured Contributor Pipeline
New York, NY – July 23, 2026 – A pioneering 10-week mentorship cohort, dubbed a "structured contributor pipeline," successfully concluded in June, demonstrating a powerful new model for open source sustainability through a collaborative effort between the Cloud Native Computing Foundation (CNCF), the OpenTelemetry (OTel) project, and Bloomberg’s Open Source Program Office. The initiative, which ran from April to June 2026, saw 48 Bloomberg engineers, many new to open source contributions, make significant and foundational contributions to the OpenTelemetry project, culminating in a robust framework for corporate engagement with critical digital infrastructure. This program followed an earlier strategic discussion outlined in the CNCF blog post, "Sustaining OpenTelemetry: Moving from Dependency Management to Stewardship," which laid the groundwork for a more proactive and integrated approach to open source support.
Program Genesis and Objectives: From Dependency to Stewardship
The concept of a "structured contributor pipeline" emerged from a recognized need to move beyond traditional dependency management – merely consuming open source software – towards active stewardship. Bloomberg, a firm deeply invested in open source technologies and operating as an "open source first company," has long understood that its reliance on projects like OpenTelemetry necessitates a reciprocal commitment. The previous blog post highlighted the challenges faced by widely adopted open source projects in maintaining velocity and health, often due to a scarcity of dedicated maintainer bandwidth for crucial but "unglamorous" tasks. The objective of this cohort was explicitly to address this gap: to systematically onboard corporate engineers into contributing roles, focusing on high-leverage maintenance work that directly benefits the project and its global user base. It aimed to provide a clear, guided pathway for engineers to transition from passive users to active contributors, fostering a deeper understanding of the project’s intricacies and contributing to its long-term health.
OpenTelemetry’s Ascendance and CNCF Graduation
The timing of this mentorship cohort coincided with a significant milestone for OpenTelemetry. In May 2026, the project achieved fully graduated status within the Cloud Native Computing Foundation, a prestigious designation that solidifies its position alongside industry titans like Kubernetes as one of the most trusted and mature open source projects globally. OpenTelemetry provides a collection of APIs, SDKs, and tools that are designed to instrument, generate, collect, and export telemetry data (metrics, logs, and traces) to help users understand the performance and behavior of their software. Its graduation signified a critical level of adoption, maturity, and community governance, establishing it as the de facto standard for observability in cloud-native environments. This achievement underscored the project’s vital role in modern software development and heightened the urgency and impact of sustained contributions. The success of the structured contributor pipeline not only injected valuable resources into the newly graduated project but also served as a testament to the community’s readiness to integrate new contributors into its core development processes.
The Cohort in Detail: Participation and Impactful Contributions
The initiative commenced in April 2026, bringing together 48 Bloomberg engineers from various teams. While some participants possessed prior, deep experience with OpenTelemetry, the vast majority were newcomers to open source contribution. Over the intensive 10-week period, these engineers channeled their efforts into a wide array of tasks, culminating in contributions that were both numerous and strategically significant. The project saw a substantial influx of development effort, with participants addressing critical maintenance tasks that often languish due to maintainer bandwidth constraints.
One exemplary contribution came from Florian Bourgey of Bloomberg’s Quant Research team within the Office of the CTO. Bourgey embarked on a systematic renaming campaign within the OTel Demo repository, an essential task for maintaining consistency and clarity across the project’s extensive codebase. His diligent work resulted in the submission of 23 pull requests, all of which were successfully merged, standardizing telemetry attribute naming across the entire demonstration project (see issue #3267 for context). By the cohort’s conclusion, Bourgey had become the second most prolific contributor to the OTel Demo, a remarkable achievement for someone relatively new to the project. This type of high-leverage, high-toil work, while perhaps not glamorous, is fundamental to a project’s long-term health and usability, and it perfectly exemplified the program’s focus on essential maintenance.
Another significant contribution emerged from Bloomberg’s Public Cloud Observability engineering team. Engineers Thomas Baldwin, Mikiyas Bokan, and Larry Zebaze tackled a real-world problem they encountered in their daily operations: the OpenTelemetry Collector’s static secret storage mechanism necessitated full restarts whenever credentials rotated, posing operational challenges in dynamic cloud environments. Recognizing an opportunity to solve this and contribute back to the community, they initiated a community issue (#48277) and subsequently developed a multi-cloud credential rotation extension for the Collector. Their work, encompassing solutions for AWS (pull request #48474), GCP (pull request #48477), and Azure (pull request #48484), is currently under review by project maintainers. Once merged, this contribution will provide lasting benefits to the wider OpenTelemetry user base, underscoring the program’s ability to translate corporate needs into valuable open source enhancements.
Beyond these standout examples, the cohort’s contributions spanned various facets of the OpenTelemetry ecosystem. Engineers delivered crucial bug fixes to Python instrumentation (pull request #4551), improved documentation across opentelemetry.io (pull request #9738), and developed reference applications in JavaScript (pull request #6770) and Python (FastAPI) (pull request #5244). Other vital work included C++ code health fixes (pull request #4041), enhancements to the Go SDK (pull request #8273), and the creation of tooling designed to assist future contributors working across multi-repository Python environments (pull request #4669). The sheer breadth and depth of these contributions highlight the effectiveness of a structured approach in channeling corporate talent towards specific project needs.
Beyond Code: Diverse Forms of Contribution
Crucially, the program emphasized that meaningful contributions extend far beyond writing code. Several participants dedicated their volunteer hours to reading complex specification documents, an essential activity for understanding and influencing the project’s architectural direction. Others engaged in issue triaging, helping to categorize, prioritize, and clarify reported bugs and feature requests, thereby reducing the burden on core maintainers. Active participation in reviewing pull requests authored by others also proved invaluable, providing critical feedback and accelerating the merging process. Furthermore, simply asking insightful questions in project forums and discussions contributed significantly by leading other contributors to the right answers or highlighting areas requiring further clarification. This holistic view of contribution reinforces the idea that an open source project’s health relies on a diverse range of activities, all of which were encouraged and supported within the Bloomberg cohort.
Mentorship at the Core: Voices from the OpenTelemetry Community
The success of the structured contributor pipeline was heavily reliant on the "extraordinary generosity" of the OpenTelemetry community. Seven dedicated maintainers from across the globe volunteered their personal time week after week, providing invaluable guidance, answering questions, reviewing code, and unblocking participants. Each weekly session featured a deep dive into different aspects of the OTel project, covering topics such as semantic conventions and Weaver, the OTel Demo, GenAI observability, the Collector architecture, and the pathway from contributor to maintainer.
Juraci Paixão Kröhling, a prominent member of the OpenTelemetry Governance Committee, lauded the initiative at its final session, stating, "This is one of the most successful mentorship programs I have seen at CNCF." This high praise from a seasoned open source leader underscores the effectiveness of the program’s design and execution.
Liudmila Molkova of Grafana Labs, who led a session on GenAI observability, offered practical advice that resonated with many participants: "Find something applicable to your actual work that also helps your main job – otherwise it’s not sustainable." She also provided a critical reframing of contribution impact, advising, "Reviews are more important than contributions. If you consistently provide comments, I’d be happy to promote you to Approver." This insight highlights the value of quality assurance and collaborative feedback in open source development.
Kemal Akkoyun, who guided contributors through the intricacies of the OTel Collector, provided a pragmatic framework for getting work accepted: "Signal intent before you write code – open an issue, describe the problem clearly, get alignment before spending time on a PR." For those just starting, he emphasized, "Start small. A focused, well-scoped PR with a clear problem description moves faster than a large one. Small PRs give you a ‘dopamine hit’ and help you understand the process." These actionable tips were crucial for demystifying the open source contribution workflow.
Martin Thwaites, participating in the semantic conventions session, reiterated the multifaceted nature of contribution: "Share your experience, not just opinions – practical feedback is the most valuable contribution to these standards. Lurking at meetings counts as contributing." This encouraged participants to engage in ways that leveraged their professional experience, even without directly writing code.
Pierre Tessier, a dedicated mentor, meticulously tracked every pull request from the cohort, celebrating individual journeys, particularly noting Florian Bourgey’s rapid ascent to become the second-largest human contributor to the OTel Demo in just a few weeks. Severin Neumann concluded the series with a poignant message: "Close what can be closed, merge what can be merged – and for everything else, keep the conversation going." These mentor insights collectively underscore the program’s success in fostering a supportive, educational, and productive environment for new contributors.
The Internal Engine: Bloomberg’s Enabling Team
Behind the seamless weekly rhythm of the cohort was a small, dedicated organizing team within Bloomberg. This internal team was instrumental in designing the program’s structure, tracking participant progress, and maintaining momentum throughout the 10 weeks. Engineer Devpriya Dave served as the team lead and a mentor, facilitating breakout rooms, coordinating with external maintainers, and even making her own upstream contributions to opentelemetry.io. Yoga Ramalingam and Stephen Black from Bloomberg’s Telemetry Infrastructure engineering team brought deep domain expertise, helping participants navigate complex development environments and connecting cohort learnings directly back to Bloomberg’s internal use of OpenTelemetry. Alyssa Wright, from Bloomberg’s Open Source Program Office, designed the series model, managed participant operations, and orchestrated the crucial partnership with the CNCF and the OpenTelemetry maintainer community.
Together, this internal team meticulously created the optimal conditions for the 48 engineers to succeed. Their support also ensured that the seven external maintainers felt sufficiently supported and valued to commit their valuable time to engage deeply with the cohort week after week. This internal infrastructure is deemed essential for the sustainability model, bridging a company’s engineering culture with the open source communities it relies upon.
A New Model for Open Source Stewardship
Bloomberg’s approach to open source sustainability extends beyond merely facilitating contributions. It integrates closely with the firm’s Corporate Philanthropy team, building upon existing systems for volunteering and charitable giving. This innovative partnership makes open source contributions easier to support, track, and recognize internally, positioning them as meaningful service rather than just an additional task. This integration transforms the "Sustaining Open Source Series" into more than just a contributor cohort; it connects the practical work of upstream contribution to a broader, more robust model for open source stewardship. This model encompasses foundation partnerships, dedicated maintainer mentorship, structured employee volunteering, and philanthropy programs that formally acknowledge open source contributions as valuable community service. For Bloomberg, an "open source first company," contributing upstream is not an exception but an integral part of its development philosophy. This structured approach simply provides more Bloomberg engineers with a supported and clear path to participate effectively.
Key Learnings and Unforeseen Insights
The program yielded several significant learnings, some of which were not fully anticipated at its inception:
- Issue Discovery, Not Motivation, Is the Bottleneck: Participants consistently expressed a strong desire to contribute but struggled with knowing where to begin. The most effective intervention proved to be maintaining a curated list of right-sized, readily available issues, with mentors actively helping participants scope and claim them in real-time. This highlights the importance of reducing friction for new contributors.
- Maintenance Work Is Genuinely Satisfying: Contrary to common assumptions, the contributors who logged the most hours and submitted the most pull requests were often engaged in less glamorous but highly meaningful tasks, such as renaming attributes, migrating feature gates, fixing CI workflows, and improving documentation. When participants understood the underlying "why" and the tangible impact of their work on project health, they engaged with these tasks enthusiastically. This suggests a re-evaluation of how "important" open source contributions are perceived.
- Cross-Company Collaboration Compounds: The cohort brought together engineers from different Bloomberg teams who had never collaborated before. Several participants naturally formed informal working groups that extended beyond the formal duration of the cohort. In one notable instance, a breakout room conversation evolved into a multi-month engineering project, demonstrating the organic innovation and collaborative spirit fostered by the program.
The tangible success of the program was further validated by post-cohort survey results: an impressive 94% of respondents reported feeling more confident contributing to open source after completing the program, compared to before they started. Furthermore, 88% expressed an intention to continue contributing to open source projects. These statistics clearly indicate that the impact of the structured contributor pipeline extends far beyond the cohort’s official end, cultivating a new generation of active and confident open source participants.
Replicable Success: Implications for the Broader Ecosystem
This highly successful model, built on a foundation of strong partnership between internal "shepherds" who invest in their people and open source project maintainers who welcome and guide them, carries significant implications for the broader open source ecosystem. The inherent trust between these two sides forms the bedrock of the program’s structure.
For companies, this model offers a compelling answer to the complex question of open source sustainability. It demonstrates that mere dependency management, financial sponsorship, or a generalized call for employees to "go contribute" is insufficient. What is needed is a practical, repeatable operating model that effectively connects genuine contributor interest with the specific, often urgent, needs of maintainers. This model ensures that contributions are not only visible and supported but also durable over time.
The "Sustaining Open Source Series" is a proven expression of this model. It provides employees with a clear, structured pathway into upstream contribution, offers maintainers concentrated support for critical work they often lack the bandwidth for, and furnishes companies with a repeatable mechanism to contribute meaningfully back to the vital digital infrastructure upon which their operations, and indeed the global economy, rely.
Bloomberg has refined and implemented this model four times to date. Its inaugural application was with pandas, the widely used Python data analysis library, in partnership with NumFOCUS and NVIDIA. Its most recent success with OpenTelemetry, in collaboration with the CNCF, further solidifies its versatility. The consistent pattern of success across different project types, programming languages, and diverse contributor profiles underscores the model’s robustness and adaptability.
Organizations seeking to move beyond theoretical discussions of open source stewardship to practical, impactful engagement are encouraged to explore this model. The outcomes are demonstrably real, the model is repeatable, and the open source projects that are critical to collective progress will undoubtedly be healthier for its wider adoption. Bloomberg’s Open Source Program Office welcomes conversations to compare notes or explore potential collaborations, with full outcomes and detailed learnings slated for presentation at Open Source Summit Europe in Prague this October. This initiative stands as a beacon for a more collaborative and sustainable future for open source.
