Table of Contents
There is a lot to do! If you are interested in getting involved, please join the mailing lists and attend the community meetings. If you're interested in contributing to a specific part of the project, please 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. If you want to check out the recordings, head to the Governance Committee YouTube playlist.
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.
We use GitHub discussions for most communications. Please join us there!
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:
- Web
- Google Calendar
- iCalendar (syncs with Outlook)
The best way to subscribe to OpenTelemetry events is to join the calendar updates Google Group. This will invite you to every OpenTelemetry call and correctly block time for accepted events, and it will keep your calendar in sync with new and updated events.
| List Name | Signup | Membership | Write Permissions | Read Permissions | Notes |
|---|---|---|---|---|---|
| [email protected] | 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. |
| [email protected] | 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. |
| [email protected] | 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. |
| [email protected] | 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. |
| [email protected] | 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. |
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. Refer to CONTRIBUTING.md for details on code attribution.
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, are recorded, and available on YouTube, and have a meeting notes document.
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.
| Name | Meeting Time | Meeting Notes | Discussions |
|---|---|---|---|
| Maintainers weekly meeting | Every Monday at 09:00PT | Google Doc | Slack |
| Collector | Every Wednesday at 09:00 PT | Google Doc | Slack |
| C/C++: SDK | Every week alternating between Monday at 15:00 PT and Wednesday at 10:00 PT | Google Doc | Slack |
| DotNET: Instrumentation | Every Wednesday at 10:30 PT | Google Doc | Slack |
| DotNET: SDK | Every Tuesday alternating between 11:00 and 16:00 PT | Google Doc | Slack |
| Erlang/Elixir: SDK | Every Thursday alternating between 07:00 and 15:00 PT | Google Doc | Slack |
| GoLang: SDK | Every Thursday alternating between 10:00 and 15:00 PDT | Google Doc | Slack |
| Instrumentation: General | Every Tuesday at 16:00 PT | Google Doc | Slack |
| Instrumentation: Messaging | Every Thursday at 8:00 PT | Google Doc | Slack |
| Java: SDK + Instrumentation | Every Thursday at 09:00 PT | Google Doc | SDK and Instrumentation Slack channels |
| Java: JVM Metrics | Alternating: Monday at 10:00 PT, Wednesday at 10:00 CET | Google Doc | SDK and Instrumentation Slack channels |
| JavaScript: SDK | Every Wednesday at 09:00 PT | Google Doc | GitHub Discussions |
| PHP: SDK | Every Wednesday at 10:30 PT | Google Doc | Slack |
| Python: SDK | Every Thursday at 09:00 PT | Google Doc | Slack |
| Ruby: SIG | Every Tuesday at 09:00 PT | Google Doc | GitHub Discussions |
| Rust: SDK | Every other week on Tuesday alternating between 07:00 and 15:00 PT | Google Doc | Gitter |
| Specification: General | Every Tuesday at 08:00 PT | Google Doc | Slack |
| Specification: Logs | Every week on Wednesday at 10:00 PT | Google Doc | Slack |
| Specification: Sampling | Every Thursday at 08:00 PT | Google Doc | |
| Swift: SDK | Every Thursday at 09:00 PT | Google Doc | Slack |
| Communications (Website, etc.) | Every other week on Thursday at 13:30 ET | Google Doc | Slack |
| eBPF | Every week on Thursday at 10:30 PT | Google Doc | Slack |
| Agent Management WG | Every other week on Tuesday at 11:00 PT | Google Doc | Slack |
| Client Instrumentation | Every Wednesday at 8:30 AM PT | Google Doc | Slack |
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 SIG Observability is a special interest group for observability that focuses on topics pertaining to the observation of cloud native workloads. Check out the CNCF SIG 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 maintainance and clear roadmap for eBPF core. See the eBPF Foundation page for more details.