Phillip Carter

Makes sense! I'll defer to maintainers here on how to best proceed. It's not strictly urgent (just a docs update), but if we get an indication that the time to...

I think (1) is the biggest one, with (2) probably also being a nice-to-have. The rest I could see not doing any work for.

Agreed @KathleenDollard, F# should be a part of the AOT story with no more caveats that C# (within reason!)

Another decision point would be if such a helper made the span the active span or not (and/or if there should be an equivalent `withActiveSpan` if not). Might be helpful...

Any concerns with implementing this? I'd be happy to contribute the sugared tracer design if that's preferred (it sounds like that would go in this repo and not the SDK...

@secustor I haven't started it no - was looking to see if anyone felt that was the right direction to go. But if you're keenly interested as well, I'd be...

Thinking about if we could just make `startActiveSpan` call `end()`. I guess that's a breaking change though: ```js let sp = tracer.startActiveSpan("ugh", span => { // something something something return...

This was discussed a bit at the maintainer's meeting last week. On the docs side, we have outlines that can be followed now! Getting started: https://github.com/open-telemetry/opentelemetry.io/issues/1746#issuecomment-1250157077 Manual instrumentation: https://github.com/open-telemetry/opentelemetry.io/issues/1746#issuecomment-1250157891 As...

Sounds good!

When you say "language-sdk", who is the intended audience? If it is otel developer docs (e.g., extenders of otel-js) then I think it's fine to keep and maintain here. But...