OpenTelemetry Graduation

[austinlparker]

This is the formal proposal for OpenTelemetry to move from Incubation to Graduation.

What is OpenTelemetry?

OpenTelemetry is one of the largest CNCF projects, aside from Kubernetes, and has maintained an impressive velocity over the past few years. Over the past five years, we have successfully fulfilled our original mission of defining a vendor-agnostic API, SDK, wire format, and tooling needed to enable observability in cloud-native systems.

Why graduate?

In 2023, we stabilized our specification for core signals and are rapidly moving towards stability in core repositories. In addition, we continue to work to add new signals, improve our SDKs, and integrate OpenTelemetry into other CNCF and open source projects. OpenTelemetry is in use at hundreds of organizations world-wide, with millions of downloads of our software a month. Graduation formalizes the readiness of our project as a foundational component of open source observability. Thank you for your consideration!

A huge thanks to our community!

We would not have achieved this milestone without the thousands of dedicated contributors and users who help make this project better every day. Take a bow -- this PR's for you!

(This was prepared under the old template, we just didn't get a chance to vote in governance until this week. I see that the form has changed... let me know if we need to re-do this)

[lukaszgryglicki]

Please ping me when OpenTelemetry moves to graduation so I'll update DevStats immediately then.

[jpkrohling]

I'm happy to see this!

[wu-sheng]

Good to see the project is moving toward graduation. Showing my support here.

[horovits]

OTel FTW! 🎉

[alolita]

Go OTEL! Thank you @austinlparker for getting this process underway!

[dilipbravo]

Awesume guys..! Great stuff

[lukaszgryglicki]

Hi, what is the exact graduation date?
I wanted to update DevStats.

[dims]

@lukaszgryglicki process has just started :) watch for [VOTE] and then [RESULT] on cncf-toc mailing list.

[lukaszgryglicki]

OK, thanks.

[XSAM]

Very happy to see this!

[austinlparker]

Question - will we need to re-do the application (per https://github.com/cncf/toc/blob/main/process/README.md#applications-to-move-levels-are-done-by-submitting-an-incubation-or-graduation-application-issue-on-the-toc-repo)? If so, I can go ahead and re-do it...

[austinlparker]

I've updated the application with the published results of our security audit.

[avocade]

Looking forward to it! Congrats.

[angellk]

Hi @austinlparker - In preparation for OpenTelemetry to be picked up by a TOC member after the KubeCon freeze period -- and prior to TOC member assignment -- please:

• review the definition of an adopter
• verify 5-7 project adopters that can and are willing to be interviewed by the TOC reviewer(s) and
  submit information for each adopter to the Adopter Interview Questionnaire form
• complete the required Security Self Assessment

[angellk]

@austinlparker

Question - will we need to re-do the application (per https://github.com/cncf/toc/blob/main/process/README.md#applications-to-move-levels-are-done-by-submitting-an-incubation-or-graduation-application-issue-on-the-toc-repo)? If so, I can go ahead and re-do it...

When the TOC member picks up your application for Graduation - they may request the project to use the new template at that time. If you would like to proactively move to the new template - it is entirely optional - however, your current place in the queue will be maintained. Keep in mind the Adopter contact information and security self assessment in the previous comment still apply.

[austinlparker]

Hi @austinlparker - In preparation for OpenTelemetry to be picked up by a TOC member after the KubeCon freeze period -- and prior to TOC member assignment -- please:

• review the definition of an adopter
• verify 5-7 project adopters that can and are willing to be interviewed by the TOC reviewer(s) and
  submit information for each adopter to the Adopter Interview Questionnaire form
• complete the required Security Self Assessment

Will do, thanks!

[timscharfenort8]

Good

[austinlparker]

Hi - apologies for the delay, but here's our security self-assessment. https://docs.google.com/document/d/18m7ssMjbFAaqMjjUObmHJkFqLvojLKB_f1_a7tK6-Fo/edit?tab=t.0#heading=h.azlmb3bnjxe4

[TheFoxAtWork]

@austinlparker i believe the self-assessment is to be filed as a PR with TAG Security so they can review it and provide recommendations. Looking over their repo, it looks like one is from last year: cncf/tag-security#1185 and both have similar but different content. I would suggest filing a PR with TAG Security to correct/update the self-assessment with the updated version.

I would also recommend the project to share updates on OTEL's security efforts, new features and functionality, with TAG Security.

[austinlparker]

@austinlparker i believe the self-assessment is to be filed as a PR with TAG Security so they can review it and provide recommendations. Looking over their repo, it looks like one is from last year: cncf/tag-security#1185 and both have similar but different content. I would suggest filing a PR with TAG Security to correct/update the self-assessment with the updated version.

I would also recommend the project to share updates on OTEL's security efforts, new features and functionality, with TAG Security.

Well, huh. This is the first time any of us have heard about/seen that existing assessment.

[TheFoxAtWork]

@austinlparker Oh what fun! then definitely recommend catching up with the TAG security folks!

[eddie-knight]

Hey @austinlparker — we had a boatload of student-led assessments early last year, and in some cases (like this) it seems like the contributors didn't manage to connect with projects how we'd expected.

Definitely became a lasting source of confusion.

Feel free to adjust or replace any content that's already in the STAG repo

[austinlparker]

@eddie-knight @TheFoxAtWork Yep, I've pulled the existing assessment in the TAG repository and will be reviewing/updating it. Please expect a PR within the next day or so. :) Thanks, sorry about the confusion.

[austinlparker]

@eddie-knight @TheFoxAtWork happy to report that I've submitted an updated PR that combines and expands the self-assessment. cncf/tag-security#1445

In addition, I'll be coming to TAG Security meeting on 2/12 to discuss the project.

[angellk]

Thank you @austinlparker for submitting the adopters and completing the Security Self Assessment. Moving to 'Ready for assignment'. When a TOC member becomes available for this domain area, they will self-assign and contact the project for next steps.