OpenTelemetry community content
April 30, 2026 · View on GitHub
Table of Contents
Get Involved
There is a lot to do! If you are interested in getting involved, here's how you can start:
- Check out our contributor guide to learn about our contribution process.
- Join our Slack and attend our community meetings.
- If you're interested in contributing to a specific part of the project, join the appropriate Special Interest Group (SIG).
Details for all of these items are below. We are a friendly, collaborative group and look forward to working together!
Governing Bodies
Both committees meet regularly, and the respective meeting notes are publicly available in the GC meeting notes and the TC meeting notes Google Docs. The Governance Committee and Technical Committee meetings are also recorded (although occasionally the meetings are not recorded due to the discussion of sensitive topics). If you want to check out the recordings, head to the meeting recordings.
Areas of Interest
Technical committee members, maintainers, and approvers are encouraged to list their areas of interest in this document to help community members find interested parties and form new special interest groups.
Communication
Slack
For those who are brand new to OpenTelemetry and want to chat or get redirected to the appropriate place for a specific question, feel free to join the CNCF OpenTelemetry Slack channel. If you are new, you can create a CNCF Slack account here.
Calendar
The shared community calendar contains all public OpenTelemetry meetings, including weekly SIG meetings, monthly community meetings, etc. You can access it via:
The best way to subscribe to specific OpenTelemetry meeting series is to join the associated calendar-...@opentelemetry.io meeting invite groups below. This will invite you to the specific OpenTelemetry meetings, correctly block time for accepted meetings, and keep your calendar in sync with new and updated events.
Alternatively, if you wish to subscribe to all OpenTelemetry meeting series you can subscribe to calendar-all@opentelemetry.io.
Mailing Lists
| List Name | Signup | Membership | Write Permissions | Read Permissions | Notes |
|---|---|---|---|---|---|
| cncf-opentelemetry-announce@lists.cncf.io | Here | anyone | GC | anyone | NotesUsed for announcements. |
| cncf-opentelemetry-tc@lists.cncf.io | N/A | TC | anyone | members | NotesUsed by the OpenTelemetry Technical Committee for internal communication. This mailing list should be used sparingly as we strive to keep all communication public. It only should be used to contact the Technical Committee with questions that cannot be discussed publicly on GitHub, GitHub discussions, or the community or contributors' mailing lists. |
| cncf-opentelemetry-governance@lists.cncf.io | N/A | GC | anyone | members | NotesUsed by the OpenTelemetry GC for internal communication. Additionally, contact the GC for questions that cannot be discussed publicly on GitHub, GitHub discussions, or other mailing lists. For instance, members could use this for issues related to improper applications of our community membership guidance. |
Media
For PR & Marketing inquiries, please contact pr@cncf.io.
License
All OpenTelemetry projects are shipped under the permissive Apache 2.0 license as CNCF IP Policy dictates. This blog post explains the reasoning behind choosing this license.
Logos and Brand Guide
The OpenTelemetry logos and brand guide can be found in the CNCF artwork repository. In addition, a Google Slides template is also available.
How to
- Get access and manage meetings.
- Request GitHub extension or create a bit.
- Configure new repository: listing settings TC members set when creating the new repository.
Special Interest Groups
We organize the community into Special Interest Groups (SIGs) to improve our workflow and more efficiently manage a community project. While meetings are expected to happen regularly, they are subject to contributors' availability and may be rescheduled or changed at time. Check our public calendar and SIG-specific GitHub discussions for meeting changes and cancellations. All meetings happen over Zoom, have a meeting notes document, and are recorded and available in the meeting recordings spreadsheet.
Please do not hesitate to contact SIG owners if the proposed time of the meeting or tools used is unavailable for you. For instance, it is a good practice to alternate morning/evening meetings once SIG has representatives from 3 largely distinct timezones. The best way to report it and suggest an alternative is to file an issue on this repository or discuss it in SIG-specific GitHub discussions.
Note
The meeting times in the tables below are given in 24-hour notation. Meetings are either in Pacific Time (PT), with Daylight Saving Time, or UTC+8, without Daylight Saving Time.
Specification SIGs
Implementation SIGs
Cross-Cutting SIGs
| Name | Meeting Time | Meeting Notes | Slack Channel | Meeting Invites Group | Governance Committee Liaison |
|---|---|---|---|---|---|
| Communications (Website, Documentation, etc.) 🔗 | Every other Tuesday at 09:00 PT | Google Doc | #otel-comms | calendar-comms | Severin Neumann |
| End-User SIG 🔗 | Alternating between Monday at 08:00 PT (Blueprints) and Thursday at 10:00 PT (General) | Google Doc | #otel-sig-end-user | calendar-sig-end-user | Marylia Gutierrez |
| Security 🔗 | Every other Monday at 09:00 PT | Google Doc | #otel-sig-security | calendar-sig-security | Trask Stalnaker |
| Project Infrastructure 🔗 | Thursday at 11:00 PT | Google Doc | #otel-project-infra | calendar-project-infra | Austin Parker |
| Contributor Experience 🔗 | Every other Monday at 10:00 PT | Google Doc | #otel-contributor-experience | calendar-contributor-experience | Marylia Gutierrez |
| Developer Experience 🔗 | Wednesday 11:00 PT and 17:00 UTC+8 | Google Doc | #otel-devex | calendar-developer-experience | Austin Parker |
Localization Teams (part of SIG Communications)
| Name | Meeting Time | Meeting Notes | Slack Channel | Meeting Invites Group | Governance Committee Liaison |
|---|---|---|---|---|---|
| Bengali (bn) 🔗 | #otel-localization-bn | Severin Neumann | |||
| Chinese (zh-CN) 🔗 | #otel-localization-zhcn | Severin Neumann | |||
| French (fr-FR) 🔗 | #otel-localization-fr | Severin Neumann | |||
| Japanese (ja-JA) 🔗 | Every third Wednesday at 01:00pm JST | Google Doc | #otel-localization-ja | calendar-localization-ja | Severin Neumann |
| Polish (pl-PL) 🔗 | #otel-localization-pl | Severin Neumann | |||
| Portuguese (pt-BR) 🔗 | Every second Wednesday at 7:15pm BST | Google Doc | #otel-localization-ptbr | calendar-localization-ptbr | Severin Neumann |
| Romanian (ro-RO) 🔗 | Monthly on a different day, at a different time (see Slack channel) | Google Doc | #otel-localization-ro | Severin Neumann | |
| Spanish (es-ES) 🔗 | Every second Friday at 8:30am UTC-3 | Google Doc | #otel-localization-es | calendar-localization-es | Severin Neumann |
| Ukrainian (uk-UA) 🔗 | #otel-localization-uk | Severin Neumann |
Related groups
W3C - Distributed Tracing Working Group
Join W3C Distributed Tracing Working Group to discuss standardization efforts in distributed tracing space.
Erlang Ecosystem Foundation – Observability Working Group
The Erlang and Elixir API and SDK are maintained by the Erlang Ecosystem Foundation Observability Working Group members. See the Observability Working Group page on the EEF website for details.
CNCF TAG Observability - Technical Advisory Group
The CNCF TAG Observability is a technical advisory group for observability that focuses on topics pertaining to the observation of cloud native workloads. Check out the CNCF TAG Observability page for details.
K8s SIG - Instrumentation Special Interest Group
The K8s SIG Instrumentation special interest group coordinates metric requirements of different SIGs for other components through finding common APIs. This group also covers best practices for cluster observability through metrics, logging, and events across all Kubernetes components. See the Instrumentation Special Interest Group for details on joining this group.
OpenMetrics
OpenMetrics is an effort to create an open standard for transmitting metrics at scale, supporting text representation and Protocol Buffers. See the OpenMetrics page for details.
eBPF Foundation
The eBPF foundation aims to facilitate collaboration between eBPF projects, and to ensure good maintenance and clear roadmap for eBPF core. See the eBPF Foundation page for more details.