OpenTelemetry Monthly Update: October 2019

Welcome to the fourth monthly OpenTelemetry community update! If you’re new to the OpenTelemetry community, you should definitely join our community mailing list and subscribe to the shared community calendar (web, gCal, iCal). We also have a very popular official chatroom on Gitter.

This month’s meeting took place on Wednesday, October 9th at 4:00 PM PT. Full details on our discussions are in the notes and you can watch the meeting recording on YouTube.

Gitter!

As several people noticed on Wednesday, our community chat room disappeared overnight. We brought the issue up with GitLab (who own and operate Gitter) and they determined that the room was accidentally deleted by a member. Lesson learned: don’t delete the chatroom!

We’ve since restored the previous membership list and there’s a chance that Gitter will be able to restore the old chat history, though we don’t have an estimate for when this will occur.

Elections!

The other big item of note this week is our first governance elections! As discussed last month, Sergey Kanzhelev and Ben Sigelman have posted details about how to vote and how to run, and you can read the full procedural details and schedule on our elections page.

Candidate applications are now complete, and the committee has captured a list of eligible voters based on GitHub contributions. If you think that you have made significant project contributions that are not reflected in your GitHub work, you can still register to be added to the voters list.

Voting emails will be sent out to eligible voters on October 21st and they will have until October 23rd to cast their ballots. Results will be announced on October 28th.

GitHub Triage Role

Midori Kobie started a discussion about adding a triage role to our GitHub organization that would allow designated project managers to apply flags to issues and assist in project organization without requiring full approver access. Ted Young, sarahnovotny, Bogdan, and Midori will continue the conversation in a meeting and will report back with their decision.

KubeCon

As a reminder, we have two sessions accepted at Kubecon plus time during the keynote (on second glance there appear to be two additional sessions that I wasn’t aware of, awesome!).

Ted Young and others are also hosting the Observability Practitioners Summit, which will also feature OpenTelemetry.

SIG Status Updates

We have enough SIGs now that we’re not going to feature all of their status updates in the monthly blog post, instead we’ll highlight items of note while leaving the full details in the community meeting minutes.

• Lots of progress has been made on the metrics API and the first 60% is being merged now, however about 40% of the work still remains. This will be completed by the end of next week, however there are still 14 non-metrics related issues open against the specs repo. We need more people to look at these and make comments.
• The OpenTelemetry Service is now officially called the OpenTelemetry Collector. Version 0.2 was released last week.
• Java, Go, JavaScript, Python, and .Net have all mostly completed their 0.2 tracing work. 0.2 metrics features should be delivered in two weeks. There is concern that additional SDK features will take even longer.
• The PHP and C++ SIGs have just been formed. While they’ll be a few weeks / months behind the early language SIGs, we’re really excited to see progress being made on these languages!
• We’ve created a SIG for the website, which will be meeting weekly during the run up to Kubecon. Details are in the community calendar.