OpenTelemetry community content
August 17, 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
Those who are brand new to OpenTelemetry and want to connect with other contributors, get guidance on contribution etiquette, or learn about development processes are encouraged to join the CNCF OpenTelemetry Slack channel #opentelemetry-new-contributors.
To follow project developments or chat about OpenTelemetry in general, feel free to join the #opentelemetry Slack channel.
If you are new to the CNCF Slack community, you can create an account.
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.
Note
All SIG meetings listed below are open to anyone. Whether you're a seasoned OpenTelemetry contributor, just starting your journey, or simply curious about the work we do, you are more than welcome to join.
Detailed SIG information, including meeting notes, repositories, sponsors, and liaisons, is available in sigs.md.
Specification SIGs
| Name | Meeting Time | Meeting Invites Group | Slack Channel | Details |
|---|---|---|---|---|
| Specification: General + OTel Maintainers Sync | Tuesday at 08:00 PT | calendar-spec-general | #otel-specification | Details |
| Specification: Sampling | Thursday at 08:00 PT | calendar-spec-sampling | #otel-sampling | Details |
| Specification: Logs | Tuesday at 10:00 PT | calendar-spec-logs | #otel-spec-logs | Details |
| Semantic Conventions: General | Monday at 08:00 PT | calendar-semconv | #otel-semantic-conventions | Details |
| Semantic Conventions: System Metrics | Thursday at 07:30 PT | calendar-semconv | #otel-system-metrics | Details |
| Semantic Conventions: K8s | Every other Tuesday at 07:30 PT | calendar-semconv | #otel-k8s-semconv-sig | Details |
| Semantic Conventions and Instrumentation: GenAI | General GenAI topics: every Tuesday 9:00 PT, every other Tuesday 9:00 UTC+8; agent-related topics: every Monday 9:00 PT | calendar-semconv | #otel-genai-instrumentation | Details |
| Semantic Conventions: CI/CD | Every Tuesday at 07:00 PT | calendar-semconv | #otel-cicd | Details |
| Semantic Conventions: RPC | Every other Thursday at 07:30 PT | calendar-semconv | #otel-semconv-rpc-stability | Details |
| Semantic Conventions: Service and Deployment | Alternating between Thursday at 08:00 PT and Thursday at 05:30 UTC | calendar-semconv | #otel-service-and-deployment-semconv-sig | Details |
| Specification: Entities | Every Monday at 09:30 PT | calendar-entities | #otel-entities | Details |
| OpAMP | Every other Tuesday at 09:00 PT | calendar-opamp | #otel-opamp | Details |
| Prometheus Interoperability | Every other Friday at 08:00 PT | calendar-prometheus | #otel-prometheus | Details |
| Functions as a Service (FAAS) | Every other Thursday at 8:00 PT | calendar-faas | #otel-faas | Details |
| Profiling | Every other Thursday at 08:00 PT | calendar-profiling | #otel-profiles | Details |
| OpenTelemetry on Mainframes | Wednesday at 10:00 PT | calendar-mainframe | #otel-mainframes | Details |
| Client Instrumentation | Every other Tuesday at 09:00 PT | calendar-client-side | #otel-client-side-telemetry | Details |
Implementation SIGs
| Name | Meeting Time | Meeting Invites Group | Slack Channel | Details |
|---|---|---|---|---|
| Android: SDK + Automatic Instrumentation | Thursday at 08:00 PT | calendar-android | #otel-android | Details |
| Arrow | Alternating between Tuesday at 16:00 PT and Thursday at 8:00 PT | calendar-arrow | #otel-arrow | Details |
| Browser | Thursday at 8:30 PT | calendar-browser | #otel-browser | Details |
| Collector | Alternating between Tuesday at 17:00 PT, Wednesday at 09:00 PT, and Wednesday at 05:00 PT | calendar-collector | #otel-collector | Details |
| C++: SDK | Alternating between Monday at 13:00 PT and Wednesday at 09:00 PT | calendar-cpp | #otel-cpp | Details |
| .NET: Automatic Instrumentation | Wednesday at 09:00 PT | calendar-dotnet | #otel-dotnet-auto-instr | Details |
| .NET: SDK | Tuesday at 11:00 PT | calendar-dotnet | #otel-dotnet | Details |
| Erlang/Elixir: SDK | Every other Thursday at 09:00 PT | calendar-erlang | #otel-erlang-elixir | Details |
| GoLang: SDK | Thursday alternating between 09:00 PT and 10:00 PT | calendar-go | #otel-go | Details |
| GoLang: Automatic Instrumentation | Every other Tuesday at 09:30 PT | calendar-go | #otel-go-instrumentation | Details |
| GoLang: Compile-Time Instrumentation | Every Thursday at 08:00 UTC | calendar-go | #otel-go-compile-instrumentation | Details |
| Injector | Thursday at 08:00 PT | calendar-injector | #otel-injector | Details |
| Java: SDK + Instrumentation | Thursday at 09:00 PT, and every other Thursday at 09:00 UTC+8 | calendar-java | #otel-java | Details |
| JavaScript: SDK | Wednesday at 09:00 PT | calendar-js | #otel-js | Details |
| Kotlin: SDK | Monday at 09:00 PT | calendar-kotlin | #otel-kotlin | Details |
| Packaging | Wednesday at 10:00 PT | calendar-packaging | #otel-packaging | Details |
| PHP: SDK | Wednesday at 08:00 EST | calendar-php | #otel-php | Details |
| Python: SDK | Thursday at 09:00 PT | calendar-python | #otel-python | Details |
| Ruby: SDK | Tuesday at 10:00 PT | calendar-ruby | #otel-ruby | Details |
| Rust: SDK | Alternating between Tuesday at 09:00 AM PT and Wednesday at 8:00 AM PT | calendar-rust | #otel-rust | Details |
| Swift: SDK | Thursday at 09:00 PT | calendar-swift | #otel-swift | Details |
| Network | Monday at 07:00 PT | calendar-network | #otel-network | Details |
| eBPF Instrumentation | Wednesday at 08:00 PT | calendar-ebpf-instrumentation | #otel-ebpf-instrumentation | Details |
| Kubernetes Operator | Thursday at 09:00 PT | calendar-k8s-operator | #otel-operator | Details |
| Kubernetes Helm Charts | Meets during OpenTelemetry Operator and OpenTelemetry Collector | calendar-k8s-operator | #otel-helm | Details |
| Community Demo Application | Wednesday at 08:00 PT | calendar-demo-app | #otel-community-demo | Details |
| Semantic Conventions: Tooling | Wednesday at 07:00 PT | calendar-semconv | #otel-weaver | Details |
Cross-Cutting SIGs
| Name | Meeting Time | Meeting Invites Group | Slack Channel | Details |
|---|---|---|---|---|
| Communications (Website, Documentation, etc.) | Every other Tuesday at 09:00 PT | calendar-comms | #otel-comms | Details |
| End-User SIG | Alternating between Monday at 09:00 PT (Blueprints) and Thursday at 10:00 PT (General) | calendar-sig-end-user | #otel-sig-end-user | Details |
| Security | Every other Monday at 09:00 PT | calendar-sig-security | #otel-sig-security | Details |
| Contributor Experience | Every other Monday at 10:00 PT | calendar-contributor-experience | #otel-contributor-experience | Details |
| Developer Experience | Wednesday 11:00 PT and 17:00 UTC+8 | calendar-developer-experience | #otel-devex | Details |
Localization Teams (part of SIG Communications)
| Name | Meeting Time | Meeting Invites Group | Slack Channel | Details |
|---|---|---|---|---|
| Bengali (bn) | #otel-localization-bn | Details | ||
| Chinese (zh-CN) | #otel-localization-zhcn | Details | ||
| French (fr-FR) | #otel-localization-fr | Details | ||
| Japanese (ja-JA) | Every third Wednesday at 01:00pm JST | calendar-localization-ja | #otel-localization-ja | Details |
| Polish (pl-PL) | #otel-localization-pl | Details | ||
| Portuguese (pt-BR) | #otel-localization-ptbr | Details | ||
| Romanian (ro-RO) | Monthly on a different day, at a different time (see Slack channel) | #otel-localization-ro | Details | |
| Spanish (es-ES) | Every second Friday at 8:30am UTC-3 | calendar-localization-es | #otel-localization-es | Details |
| Ukrainian (uk-UA) | #otel-localization-uk | Details |
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.