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!

• Governance Committee (GC): Charter, Members
• Technical Committee (TC): Charter, Members

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.

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.

(Internal Note: When creating or updating a calendar event in the OpenTelemetry Public Calendar, please ensure that [email protected] is added as an attendee to the meeting invite. This is what allows updates to the calendar to be synchronized to other attendees.)

For PR & Marketing inquiries, please contact [email protected].

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, 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.

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 maintainance and clear roadmap for eBPF core. See the eBPF Foundation page for more details.