Sustaining OpenTelemetry: What a 10-week contributor cohort actually looks like

In April 2026, the Cloud Native Computing Foundation (CNCF), the OpenTelemetry (OTel) project, and Bloomberg’s Open Source Program Office ran a joint effort on sustaining the project. The write-up is a follow-up to “Sustaining OpenTelemetry: Moving from Dependency Management to Stewardship” and centers on what a 10-week contributor cohort actually looked like in practice—not a high-level policy note, but a concrete run of people, time, and project work.

The program treated contribution as a managed pipeline rather than ad hoc pull requests. Over those 10 weeks, participants moved through onboarding, scoped tasks, review loops, and handoff so work stayed aligned with OpenTelemetry’s existing maintainers and governance. That is the operational side of stewardship: maintainers still own merge and design decisions, while the cohort supplies focused capacity on agreed workstreams instead of scattering effort across random issues.

For engineers who depend on OTel for traces, metrics, and logs, sustainability is not abstract. Collector components, language SDKs, and semantic conventions all need ongoing review and ownership. A cohort model shows one way large consumers can fund attention without forking or bolting on proprietary forks—by putting contributors into the same review culture the project already uses.

In the broader observability stack, OpenTelemetry sits as the common instrumentation layer many vendors and platforms build on. When stewardship stays with the CNCF project rather than any single product team, the competitive pressure is less about who owns the protocol and more about who ships reliable exporters, backends, and ops tooling on top. Bloomberg’s OSPO participation is a signal that large finance-scale operators treat OTel as shared infrastructure worth staffing, not only consuming.

If you run OTel in production, the practical watch is whether cohort-style programs become a repeatable path from “we use it” to “we help maintain it.” Track whether follow-on cohorts keep the same 10-week shape, how tasks map to high-churn surfaces (SDKs, Collector, conventions), and whether other OSPOs copy the model. The earlier stewardship framing and this cohort report together are the template: dependency management alone is not enough; structured contributor time is what keeps the shared stack from stalling.