**Structured Contributor Pipelines: How Bloomberg and the OpenTelemetry Cohort Strengthened Open Source Sustainability**
In April 2026, the Cloud Native Computing Foundation (CNCF), the OpenTelemetry (OTel) project, and Bloomberg’s Open Source Program Office launched a 10-week mentorship cohort designed to test a new model for sustainable open source contribution. With 48 Bloomberg engineers participating—most of whom had never contributed to open source before—the initiative aimed to create a repeatable “structured contributor pipeline” that connects internal enthusiasm with upstream project needs. The results exceeded expectations.
### What Actually Happened
Over ten weeks, Bloomberg engineers delivered meaningful contributions to the OpenTelemetry project at a time when OTel achieved a major milestone: full graduation within the CNCF ecosystem, placing it alongside Kubernetes as one of the most trusted open source projects globally. The work was not symbolic; it was consequential maintenance and infrastructure work that project maintainers consistently lack bandwidth to address.
### What the Contributions Looked Like
– Florian Bourgey led a systematic renaming campaign in the OTel Demo repository, submitting 23 merged pull requests that standardized telemetry attributes across the project, making him the second-most prolific contributor.
– Thomas Baldwin, Mikiyas Bokan, and Larry Zebaze tackled static secret storage in the OTel Collector, designing a multi-cloud credential rotation extension for AWS, GCP, and Azure that remains under review but will outlive the cohort.
– Additional contributions spanned Python bug fixes, documentation improvements across opentelemetry.io, reference applications in JavaScript and Python (FastAPI), C++ code health, Go SDK enhancements, and tooling for multi-repo Python environments.
– Non-code contributions were equally valuable: triaging issues, reviewing pull requests, and reading specification documents helped the entire community.
### What Mentors Observed
The OpenTelemetry community brought extraordinary generosity, with seven global maintainers volunteering weekly to mentor, review, and unblock contributors. Key takeaways included:
– **Focus on real-world relevance:** Contributors who worked on problems tied to their day-to-day roles sustained engagement longer.
– **Maintenance work is satisfying:** Clear explanation of why “unglamorous” tasks matter drove enthusiastic participation.
– **Small, well-scoped PRs move faster:** Starting with focused contributions builds confidence and understanding.
– **All forms of contribution count:** Code, reviews, community participation, and standard-setting all advance project health.
Juraci Paixão Kröhling of the OpenTelemetry Governance Committee called it “one of the most successful mentorship programs I have seen at CNCF.”
### The Internal Team Behind the Success
Behind the scenes, a dedicated Bloomberg team designed the cohort structure, tracked participant progress, and maintained momentum:
– Devpriya Dave served as lead mentor and upstream contributor.
– Yoga Ramalingam and Stephen Black provided deep telemetry infrastructure expertise.
– Alyssa Wright designed the series model and managed partnership operations.
Together, they created an environment where 48 engineers could succeed—and where seven external maintainers felt supported enough to invest significant time.
### What We Learned
– **The bottleneck is issue discovery, not motivation.** Participants want to contribute but need clear, curated paths in.
– **Maintenance work is genuinely satisfying.** When contributors understand the “why,” they engage enthusiastically.
– **Cross-company collaboration compounds.** Engineers from different Bloomberg teams formed lasting working groups.
– **Confidence builds quickly.** 94% of respondents felt more confident contributing to open source after the cohort; 88% plan to continue contributing.
### What This Model Suggests for Others
This model succeeds because it is built on partnership—internal shepherds investing in people and project maintainers opening the door. For organizations, open source sustainability requires more than sponsorship or goodwill; it requires a practical, repeatable operating model that connects internal interest with upstream need. The Sustaining Open Source Series demonstrates that model in action.
Bloomberg has now run this series four times, with projects ranging from pandas to OpenTelemetry, proving a pattern that holds across languages, project types, and contributor profiles.
—
### FAQ
**Q: What is the “structured contributor pipeline” mentioned in the post?**
A: It is a 10-week mentorship cohort that pairs internal engineers with open source project maintainers to tackle real maintenance and development tasks, creating a repeatable path from first contribution to sustained upstream involvement.
**Q: Who was involved in this OpenTelemetry cohort?**
A: 48 Bloomberg engineers, seven OpenTelemetry maintainers, and internal Bloomberg staff including Devpriya Dave, Yoga Ramalingam, Stephen Black, and Alyssa Wright.
**Q: What kinds of contributions did participants make?**
A: Contributions included code fixes, documentation improvements, renaming campaigns, credential rotation extensions, CI improvements, and community tasks like issue triage and PR reviews.
**Q: Did participants need prior open source experience?**
A: No. Most participants had never contributed to open source before, but mentors provided guidance to help them start small and build confidence.
**Q: How did Bloomberg support this initiative internally?**
A: Through a dedicated organizing team, allocated volunteer time, collaboration between the Open Source Program Office and Corporate Philanthropy, and ongoing operational support.
**Q: What is the broader goal of the Sustaining Open Source Series?**
A: To create durable models that connect company engineering cultures with open source communities, making upstream contribution structured, supported, and repeatable.
—
### Conclusion
The Bloomberg–CNCF–OpenTelemetry mentorship cohort demonstrates that sustained open source stewardship is achievable through intentional partnership, clear structure, and meaningful work. By investing in internal shepherds and trusting project maintainers, organizations can transform individual enthusiasm into durable upstream impact. As open source becomes increasingly central to digital infrastructure, models like this one offer a practical, repeatable path to healthier, more resilient projects—and stronger ecosystems—for everyone who depends on them.
