Table of Contents
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!
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 meetings are also recorded. If you want to check out the recordings, head to the meeting recordings.
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.
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.
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.
| List Name | Signup | Membership | Write Permissions | Read Permissions | Notes |
|---|---|---|---|---|---|
| cncf-opentelemetry-community@lists.cncf.io | Here | anyone | GC and TC | anyone | NotesThe community mailing list is for anybody who wants to monitor the latest news from the project. It is used to send updates on community meetings and announcements about new projects and SIGs. There is minimal moderation for a new user to reduce spam, and new users are approved after one post. |
| cncf-opentelemetry-contributors@lists.cncf.io | Here | anyone | anyone | anyone | NotesThe discussions mailing list is for anyone who is interested in contributing to OpenTelemetry or has questions (related to the contribution, technical issues,etc) they’d like to discuss. Will be used to announce updates related to how the project is being developed and ask general contribution questions related to the contribution processes. No approval is required to join. |
| 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. |
| cncf-opentelemetry-comms@lists.cncf.io | Here | GC and open for anyone | anyone | anyone | NotesMailing list to notify and request reviews of upcoming announcements, or request a post on the OpenTelemetry Twitter account or other public channels. |
For PR & Marketing inquiries, please contact pr@cncf.io.
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.
The OpenTelemetry logos and brand guide can be found in the CNCF artwork repository. In addition, a Google Slides template is also available.
- 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.
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 on Zoom cloud.
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.
| Name | Meeting Time | Meeting Notes | Slack Channel | Meeting Invites Group | Governance Committee Liaison |
|---|---|---|---|---|---|
| Android: SDK + Automatic Instrumentation | Tuesday at 08:00 PT | Google Doc | #otel-android | calendar-android | Trask Stalnaker |
| Collector | Alternating between Tuesday at 17:00 PT, Wednesday at 09:00 PT, and Wednesday at 05:00 PT | Google Doc | #otel-collector | calendar-collector | Pablo Baeyens |
| C++: SDK | Alternating between Monday at 13:00 PT and Wednesday at 09:00 PT PT | Google Doc | #otel-cpp | calendar-cpp | Severin Neumann |
| .NET: Automatic Instrumentation | Wednesday at 09:00 PT | Google Doc | #otel-dotnet-auto-instr | calendar-dotnet | Morgan McLean |
| .NET: SDK | Tuesday alternating between 09:00 PT and 16:00 PT | Google Doc | #otel-dotnet | calendar-dotnet | Morgan McLean |
| Erlang/Elixir: SDK | Every other Thursday at 09:00 PT | Google Doc | #otel-erlang-elixir | calendar-erlang | Austin Parker |
| GoLang: SDK | Thursday alternating between 09:00 PT and 10:00 PT | Google Doc | #otel-go | calendar-go | Ted Young |
| GoLang: Automatic Instrumentation | Every other Tuesday at 09:30 PT | Google Doc | #otel-go-instrumentation | calendar-go | Juraci Paixão Kröhling |
| Java: SDK + Instrumentation | Thursday at 09:00 PT, and every other Thursday at 09:00 UTC+8 | Google Doc | #otel-java | calendar-java | Trask Stalnaker |
| JavaScript: SDK | Wednesday at 09:00 PT | Google Doc | #otel-js and GitHub Discussions | calendar-js | Pablo Baeyens |
| PHP: SDK | Wednesday at 10:30 PT | Google Doc | #otel-php | calendar-php | Severin Neumann |
| Python: SDK | Thursday at 09:00 PT | Google Doc | #otel-python | calendar-python | Daniel Gomez Blanco |
| Ruby: SDK | Tuesday at 09:00 PT | Google Doc | #otel-ruby and GitHub Discussions | calendar-ruby | Ted Young |
| Rust: SDK | Tuesday at 09:00 PT | Google Doc | #otel-rust and Gitter | calendar-rust | Ted Young |
| Swift: SDK | Thursday at 09:00 PT | Google Doc | #otel-swift | calendar-swift | Alolita Sharma |
| eBPF | Tuesday at 09:00 PT | Google Doc | #otel-ebpf | calendar-ebpf | Ted Young |
| Kubernetes Operator | Thursday at 09:00 PT | Google Doc | #otel-operator | calendar-k8s-operator | Juraci Paixão Kröhling |
| Community Demo Application | Wednesday at 08:00 PT | Google Doc | #otel-community-demo | calendar-demo-app | Austin Parker |
| Semantic Conventions: Tooling | Wednesday at 07:00 PT | Google Doc | #otel-weaver | calendar-semconv | Trask Stalnaker |
| Name | Meeting Time | Meeting Notes | Slack Channel | Meeting Invites Group | Governance Committee Liaison |
|---|---|---|---|---|---|
| Maintainer Meeting | Monday at 09:00 PT | Google Doc | #otel-maintainers | calendar-maintainer-meeting | Morgan McLean |
| Communications (Website, Documentation, etc.) | Every other Monday at 10:00 PT | Google Doc | #otel-comms | calendar-comms | Severin Neumann |
| End-User SIG | Every other Thursday at 10:00 PT | Google Doc | #otel-sig-end-user | calendar-sig-end-user | Daniel Gomez Blanco |
| Security | Every other Wednesday at 07:00 PT | Google Doc | #otel-sig-security | calendar-sig-security | Juraci Paixão Kröhling |
| Project Infrastructure | Wednesday at 08:00 PT | Google Doc | #otel-project-infra | calendar-project-infra | Austin Parker |
| Contributor Experience | Monday alternating between 10:00 PT and 17:00 UTC+8 | Google Doc | #otel-contributor-experience | calendar-contributor-experience | Juraci Paixão Kröhling |
| Developer Experience | Wednesday 11:00 PT and 17:00 UTC+8 | Google Doc | #otel-devex | calendar-developer-experience | Austin Parker |
Join W3C Distributed Tracing Working Group to discuss standardization efforts in distributed tracing space.
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.
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.
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 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.
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.