Ben Sigelman
Ben Sigelman
The OTel GC recently met to discuss priorities for 2022, and one is to improve both the OTel contributor experience *and* the OTel maintainer experience. As part of this, we...
In #367 an OTel community member brought up the uncomfortable truth that the diversity of participants in OTel SIGs is – what's the word? – "minimal". (I.e., nearly or actually...
Related to #370, I'd like us to create a survey for all OTel contributors. I have been looking at some prior art in the k8s world (e.g., https://github.com/kubernetes/community/issues/3969 and https://github.com/kubernetes/community/blob/master/sig-contributor-experience/surveys/2019/contribex-survey-2019.md)...
This is a companion issue to https://github.com/open-telemetry/community/issues/370; from the "preface" there: >In #367 an OTel community member brought up the uncomfortable truth that the diversity of participants in OTel SIGs...
Per the discussion here: https://github.com/opentracing/opentracing-go/pull/135#discussion_r102151633 ... and the non-portable work here: https://github.com/uber/jaeger-client-go/pull/94 Should OpenTracing-Go provide an observer interface? basictracer-go has something like this, too. By baking it into OT proper,...
Now that #115 is in, we need to contend with the scenario where `ActiveSpanSource.activeSpan()` / `Tracer.activeSpan()` returns `null`. As I see it, there are three options. 1. Do nothing. Callers...
An application developer should care about OpenTracing because it saves them time and energy when connecting the dots between their software dependencies and their Tracer / tracing system. The new...
Per https://gitter.im/opentracing/public?at=58332e4c2db9526704625011
(Not just accessing them by a foreknown key) This has already been done in Go: opentracing/opentracing-go#85 We would need to make changes to opentracing.io/spec as well as the remainder of...
This "issue" started life as a github gist. I wanted to publish it somewhere that's friendly to collaboration and cross-referencing on github, and hence the "port" to the github issue...