Add contacts to adopters

[svrnm]

Follow-Up to #3060

@flands @seanschade @nandita-cloudscaleinc @lizthegrey @avillela @MDrollette @arnoldberlin @sveiss @naseemkullah @dkatona @chris-smith-zocdoc,

tagging you all since you contributed to the list of OpenTelemetry adopters in the past (either directly or by approving a PR that added your company). We (Docs Team) are currently working towards improving the pages about OTel adopters, vendors & integrations.

One part of that is having someone who is a point of contact for each entry, such that we can reach out if we plan to do changes in the future as well. For this, please let me know, if you are the right person or if we need to update the point of contact to someone else (github handle, mail address, etc.)

Another part for adopters is that we want to have a reference (blog post, video, etc.) that gives details about the adoption. I understand that this is a much higher bar than before, but this will increase the value of this list significantly and it is also a great opportunity to shine some lights on you as publicly known adopters of OpenTelemetry.

cc @open-telemetry/docs-approvers @open-telemetry/end-user-wg

[sveiss]

I'm no longer with Shopify; @fbogsany or @robertlaurin might be the correct contacts (or know who should be these days)!

[nandita-cloudscaleinc]

@svrnm - some comments from our org perspective -

https://deploy-preview-3060--opentelemetry.netlify.app/ecosystem/adopters/ - Pls consider adding reference link to https://cloudscaleinc.com/cloud-scale-service-mesh/ (OpenTelemetry usage is called out explicitly under Deep Observability accordion)

[svrnm]

I'm no longer with Shopify; @fbogsany or @robertlaurin might be the correct contacts (or know who should be these days)!

thank you @sveiss! @fbogsany / @robertlaurin can you help us here?

@svrnm - some comments from our org perspective -

deploy-preview-3060--opentelemetry.netlify.app/ecosystem/adopters - Pls consider adding reference link to cloudscaleinc.com/cloud-scale-service-mesh (OpenTelemetry usage is called out explicitly under Deep Observability accordion)

@nandita-cloudscaleinc thanks for coming back on this. If I read the description on your website correctly, you provide a service to customers and this is not about your own company adopting opentelemetry for observability, right?

[nandita-cloudscaleinc]

@nandita-cloudscaleinc thanks for coming back on this. If I read the description on your website correctly, you provide a service to customers and this is not about your own company adopting opentelemetry for observability, right?

@svrnm it's both our organization has adopted opentelemetry as a standard for observability, and we also provide end customers with services that leverage opentelemetry.

[svrnm]

it's both our organization has adopted opentelemetry as a standard for observability, and we also provide end customers with services that leverage opentelemetry.

Thanks.

The adopters page is specifically for end-user organizations of OpenTelemetry, so if you have a link to some material (blog post, video, ...) how your organization leverages OpenTelemetry, this belongs here.

[nandita-cloudscaleinc]

it's both our organization has adopted opentelemetry as a standard for observability, and we also provide end customers with services that leverage opentelemetry.

Thanks.

The adopters page is specifically for end-user organizations of OpenTelemetry, so if you have a link to some material (blog post, video, ...) how your organization leverages OpenTelemetry, this belongs here.

@svrnm link to our top page in website - #3089 (comment) is calling out references of OpenTelemetry. The guidelines are unclear to me, such as if we must explicitly write a blog post or something else. Is a reference on the main website not sufficient?

[svrnm]

@svrnm link to our top page in website - #3089 (comment) is calling out references of OpenTelemetry. The guidelines are unclear to me, such as if we must explicitly write a blog post or something else. Is a reference on the main website not sufficient?

The list we want to have on https://opentelemetry.io/ecosystem/adopters/ consists of organizations that use OpenTelemetry internally and do not sell service offerings around OpenTelemetry. Historically it was a mix of those and others (especially also vendors), which is confusing for people visiting this page. That's why we are aiming for a change.

The page you linked states that your service includes an observability offering using OpenTelemetry, therefore it does not qualify to keep Cloud Scale as an adopter and that's why I ask for a reference on how you use OpenTelemetry internally.

But please, don't worry: we are not only overhauling the "Adopters" page but others as well. We will keep Cloud Scale where it is right now, but will move it over to the appropriate place eventually.

Thank you.