Skip to content
OpenTelemetry community content
Branch: master
Clone or download
SergeyKanzhelev Update community-members.md (#128)
* Update community-members.md

#120

* Update community-members.md
Latest commit eec55a0 Jun 24, 2019

README.md

Community

OpenTelemetry community content.

Get Involved

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 wish to join one of the special interest groups, you can get in touch via this simple form. We are a friendly, collaborative group and look forward to working together.

Communication

Instant Messaging

We are on gitter.

Mailing Lists

Community

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.

Contributors

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.

TC (Technical Committee)

Used by the OpenTelemetry technical steering 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 steering committee with questions that cannot be discussed publicly on github, gitter, or the community or contributors mailing lists.

Governance Committee

Used by the OpenTelemetry steering committee for internal communication. Also can be used to contact the steering 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.

Public Communication Requests

Mailing list to notify and request reviews of upcoming announcements, or request a post on the OpenTelemetry Twitter account or other public channels.

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.

Community Meetings

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.

Special Interest Groups

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.

Cross-language specification

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: Gitter chat

Meeting will be help every Tuesday at 8 AM pacific time. Meeting notes are held in this google doc.

Join Microsoft Teams Meeting

+1(469)480-6275, 21468028# United States, Dallas (Toll)

+1(866)639-0588, 21468028# United States (Toll-free)

Conference ID: 634 117 56#

Local numbers | Learn more about Teams

Agent/Collector

The Service SIG meets every other week on Wednesday at 2 PM PT.

Meeting notes are held in this doc.

You can also join us on gitter.

.NET SDK

Regular sync up will be held initially weekly - every Tuesday at 9 AM PDT.

Meeting notes are held in this google doc.

Join Microsoft Teams Meeting

+1(469)480-6275, 21468028# United States, Dallas (Toll)

+1(866)639-0588, 21468028# United States (Toll-free)

Conference ID: 214 680 28#

Local numbers | Learn more about Teams

.NET Gitter Channel: Gitter chat

GoLang SDK

The Golang SIG meets weekly on Tuesday at 3 PM PDT. 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

Java SDK

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

Node.JS SDK

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.

Python SDK

The Python SIG meets weekly on Thursday 8 AM PDT. 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.

Ruby SIG

The Ruby SIG meets weekly on Wednesday alternating between 9 AM PDT and 4 PM PDT. 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.

Other

We also considering creating SIGs for byte code injection agents and other projects.

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

See Observability Working Group Proposal.

You can’t perform that action at this time.