Hi everyone – if you are a “member of standing” (TL;DR “a member of the OpenTelemetry GitHub organization), please endorse candidates for the governance committee election that’s taking place this month:
The form: https://forms.gle/3nrPt9HTsNBFdeku7
Trace. A colleague and I are working on getting an subscriber (an exporter, in
tracing's terminology) from
tracingto OpenTelemetry once we've fuzzed a lock free-free hashmap sufficiently. i'd love to share the end product once it's in a decent state!
Going forwards, I would like make sure that we are not leaving unanswered questions until the end. Over the next week, I will assist in rounding up working groups to pay active attention to the spec – possibly by spiking on implementations early while we are discussing RFCs and Spec PRs – to make sure that we aren't leaving implementation concerns unaddressed until after the work is merged. If people are interested in this, please let me know. We want to have the current set of v0.3 issues finished by kubecon.
Personally, I'm excited for the final bits of spec work, like separating out context propagation from observability. But I am also concerned that some changes may be too much, or are going to slow us down significantly. If that's the case, I'm going to suggest that better is the enemy of good enough, and move to cut scope so that we can reach our original goal of merging OT/OC and quickly achieving parity.
So, again, I'd like to see a big push to finish the last round of spec work in the next four weeks. I don't think we can do that without active and early participation from SIG members!