Surveying language SIGs

open-telemetry / sig-developer-experience

Apache License 2.0

2 stars 1 forks source link

Surveying language SIGs #3

Open tsloughter opened 2 months ago

tsloughter commented 2 months ago

This will act as the "top level" issue for tracking the collection of existing API additions that some implementations already have.

I believe each language should have its own separate issue which will then track the progress of collecting that information before posting back here.

lmolkova commented 2 months ago

template:

title: {language} Developer Experience Survey
body:
- differences from upstream spec:
  - discrepancies - why?
  - extra convenience
- most requested features
  - API
  - SDK
  - Instrumentations/semantic conventions
- things to consider from other telemetry projects

Languages/ repos:

[ ] Java - @lmolkova
[ ] .NET - @samsp-msft
[ ] Python - @lmolkova
[ ] JS - @tedsuo
[ ] Erlang/Elixir - @tsloughter
[ ] Ruby - @dmathieu
[ ] C++ - @tedsuo
[ ] PHP - @julianocosta89
[ ] Go - @dmathieu
[ ] Rust - @julianocosta89
[ ] Android - @austinlparker
[ ] Swift - @austinlparker

tsloughter commented 2 months ago

@lmolkova, can you put these names next to each language in your comment: @dmathieu has volunteered for Go and Ruby and @julianocosta89 volunteered for Rust and PHP. I'll take Erlang/Elixir and I figured I'd also take any that are leftover after today.

austinlparker commented 2 months ago

I'll take Android/Swift

julianocosta89 commented 1 month ago

Hello all 👋🏽

Just wondering, how are you handling the survey? Are you interviewing the maintainers, sending them a form, asking questions on the SIG meetings or what?

I was thinking of opening an issue per language and inviting the maintainers and approvers to it, so we could have a async discussion. By the end of it, the responsible for that language (from DevEx side) would compile the insights and open a PR or something to this repo.

WDYT?