OpenTelemetry community content.
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!
We are on Gitter chat.
The shared community calendar contains all public OpenTelemetry meetings, including weekly SIG meetings, the monthly community meetings, and others. You can access it on the web, in Google Calendar, and via iCalendar (syncs with Outlook).
You can also receive calendar updates by joining our calendar updates Google Group.
- List name: [email protected]
- Signup: https://lists.cncf.io/g/cncf-opentelemetry-community
- Membership: anyone
- Write Permissions: TC and Governance committee
- Read Permissions: anyone
The 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 a minimal moderation for a new users to reduce spam, new users are approved after one post.
- List name: [email protected]
- Signup: https://lists.cncf.io/g/cncf-opentelemetry-contributors
- Membership: anyone
- Write Permissions: anyone
- Read Permissions: anyone
The 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.
- List name: [email protected]
- Membership: TC
- Write Permissions: anyone
- Read Permissions: members
Used 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, Gitter, or the community or contributors mailing lists.
- List name: [email protected]
- Membership: Governance Committee
- Write Permissions: anyone
- Read Permissions: members
Used by the OpenTelemetry Governance Committee for internal communication. Also can be used to contact the Governance Committee for questions that cannot be discussed publicly on GitHub, Gitter, or other mailing lists. For instance, members could use this for issues related to improper applications of our community membership guidance.
- List name: [email protected]
- Membership: David Klein + Morgan McLean + Governance committee
- Write Permissions: anyone
- Read Permissions: members
Mailing 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.
The OpenTelemetry logos and brand guide can be found in the CNCF artwork repository.
We host monthly community video conferences, alternating between times that work for Europe and Asia. These meetings are open to all contributors!
Meeting invites can be accessed from our public Calendar (web, gCal, iCal), and we keep public notes in the agenda document available here.
We organize the community into Special Interest Groups (SIGs) in order to improve our workflow and more easily manage a community project.
Please do not hesitate to contact SIG owners if the proposed time of the meeting or tools used are unavailable for you. For instance, it will be 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 gitter channel.
This is a group for people interested in writing cross-language specifications and participate in high-level design discussions. SIG will be led by the members of a Technical Committee @open-telemetry/technical-committee. It is recommended for all members of @open-telemetry/specs-approvers and open for all.
Specifications gitter channel:
Meeting will be held every Tuesday at 8 AM pacific time. Meeting notes are held in this google doc.
Join Zoom Meeting https://zoom.us/j/6729396170
Meeting ID: 672 939 6170
One tap mobile +16465588656,,6729396170# US (New York) +16699006833,,6729396170# US (San Jose)
Dial by your location +1 646 558 8656 US (New York) +1 669 900 6833 US (San Jose) 855 880 1246 US Toll-free 877 369 0926 US Toll-free Meeting ID: 672 939 6170 Find your local number: https://zoom.us/u/abrmtXWOh8
The Logs sub-SIG of the specifiction SIG meets every other week on Wednesdays at alternating times via Zoom. Meeting notes are held in this doc.
You can also join us on gitter.
The Metrics sub-SIG of the specification SIG meets weekly on Thursday 11 AM PDT. This meeting is subject to change depending on contributors' availability, check the calendar for specific dates.
Meeting notes are held in this google doc.
Link to join the Zoom meeting.
You can also join us on gitter.
The Service SIG meets every Wednesday, alternating between 9 AM and 2 PM PT.
Meeting notes are held in this doc.
Link to join the meeting: https://zoom.us/j/8203130519.
You can also join us on gitter.
Regular sync up held weekly on Tuesdays at alternating time - 11 AM PT and 4PM PT. Check the public OpenTelemetry calendar (web, gCal, iCal) for potential meeting time updates or cancellations.
Meeting notes are held in this google doc.
Link to join the meeting: https://zoom.us/j/8287234601.
.NET Gitter Channel:
The C/C++ SIG meets weekly - every Monday at 3 PM PDT.
Meeting notes are held in this doc.
You can also join us on gitter.
The Golang SIG meets weekly on Thursdays, alternating between at 10 AM and 3 PM PDT. This meeting is subject to change depending on contributors' availability, look for the pinned message in the Gitter for specific dates (until a public calendar can be published).
Meeting notes are held in this doc.
You can also join us on gitter.
The Java SIG meets weekly on Friday at 8 AM PDT.
Meeting notes are held in this doc.
You can also join us on gitter.
Separate but related to the "Java SDK SIG", the "Java Instrumentation SIG" meets every Thursday at 9 AM Pacific Time.
The Java Instrumentation SIG covers both auto-instrumentation and (manual) instrumentation libraries.
Meeting notes are held in this doc.
You can also join us on gitter.
Regular sync up will be held initially weekly - every Wednesday at 9 AM PDT.
Meeting notes are held in this google doc.
You can also join us on gitter.
The Python SIG meets weekly on Thursday, alternating between 9AM and 4PM PT. This meeting is subject to change depending on contributors' availability, check the calendar for specific dates.
Meeting notes are held in this doc.
You can also join us on gitter.
The Ruby SIG meets weekly on Thursday at 9 AM PT. This meeting is subject to change depending on contributors' availability, check the community meeting calendar for specific dates.
Meeting notes are held in this doc.
You can also join us on gitter.
Weekly sync ups are on Thursdays alternating between 07:00 AM PT (16:00 PM GMT) followed by 15:00 PM PST (12:00 AM GMT). See the community Google calendar for all OpenTelemetry events and meetings.
Meeting notes are held in this Google doc.
Erlang/Elixir Gitter Channel:
The PHP SIG meets weekly on Wednesday 10:30 AM PT via Zoom. Follow this link to join the meeting.
Meeting notes are held in this doc.
You can also join us on gitter.
The Rust SIG meets bi-weekly on Tuesdays, 07:00 AM PT (16:00 PM GMT) followed by 15:00 PM PST (12:00 AM GMT). Check the Google calendar for the next meeting.
Meeting notes are held in this google doc.
Link to join the Zoom meeting.
Rust Gitter Channel:
Regular syncs take place every Thursday at 1:30 PM PT and are posted on the calendar. Meeting notes are updated every sync.
We also considering creating SIGs for byte code injection agents and other projects.
Join W3C Distributed Tracing Working Group to discuss standardization efforts in distributed tracing space.
The Erlang and Elixir API and SDK are maintained by members of the Erlang Ecosystem Foundation Observability Working Group. See the Observability Working Group page on the EEF website for details.