Deno pages & blog post

[svrnm]

This is a follow up to #5962 from @lucacasonato: I commented there that we need to think about, how we want to feature languages like Deno that have a first class implementation of OpenTelemetry, but do not have a SIG within the OpenTelemetry project. Here are a few ideas:

• First of all, I would like to have a blog post about it, just stating the fact that this exists, otel project is excited about it and maybe a short tutorial how you can make use of it. @lucacasonato: if you ore other Deno contributors are interested in collaborating to write such a blog post, let's chat!
• Uncontroversial, we should add it to the registry, so people can find it: https://opentelemetry.io/ecosystem/registry/?s=deno
• Then, I'd like to hear and discuss ideas how we can add Deno to our docs, to make people aware that they get first class support by the language developers (with a marker that it is experimental). The first solution that comes to mind is adding a Deno page to Language APIs&SDKs with a few words and then pointing out to the Deno documentation. However, we need to consider that other languages in the future will follow and how open we are to enlarge that list with more and more entries that point out to third parties. We also need to consider, if we want to give the language developers shared code ownership over those pages.

@open-telemetry/governance-committee @open-telemetry/technical-committee @open-telemetry/docs-approvers wdyt?

[mx-psi]

I support adding a link on the 'Language API & SDKs' for any (widely used) implementation of said language that has first-class support, including Deno.

In case of controversy of whether a particular implementation is "widely used" (to be clear, I think it's clear that Deno is widely used) we could defer to the language library SIG maintainers or develop some sort of criteria based on publicly available popularity metrics.

[lucacasonato]

This sounds great! And we would be super happy to collaborate on a blog post!

[svrnm]

I support adding a link on the 'Language API & SDKs' for any (widely used) implementation of said language that has first-class support, including Deno.

In case of controversy of whether a particular implementation is "widely used" (to be clear, I think it's clear that Deno is widely used) we could defer to the language library SIG maintainers or develop some sort of criteria based on publicly available popularity metrics.

We talked about this last Monday during the SIG call, but we ran out of time, so I would like to give it some more time to iterate on that. We have another PR around Quarkus open, which is for me related to the same question. At the end this is a "better registry" question once again, where we can put such projects and their docs more into the center of what we present end users.

This sounds great! And we would be super happy to collaborate on a blog post!

Awesome! Note that I am a little bit underwater right now, but I try to come up with a draft eventually, it just may take a little bit to get there! If you like to chat about it and throw around some ideas, you can DM me on CNCF slack, my handle is @severin (use https://slack.cncf.io/ to get invited to the slack)