Distro should include owners

[codeboten]

Component(s)

cmd/mdatagen

Describe the issue you're reporting

There's a list of distros available in mdatagen:

opentelemetry-collector-contrib/cmd/mdatagen/statusdata.go

Lines 14 to 24 in 5e285f0

	var distros = map[string]string{
	"core": "https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol",
	"contrib": "https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib",
	"aws": "https://github.com/aws-observability/aws-otel-collector",
	"grafana": "https://github.com/grafana/agent",
	"observiq": "https://github.com/observIQ/observiq-otel-collector",
	"redhat": "https://github.com/os-observability/redhat-opentelemetry-collector",
	"splunk": "https://github.com/signalfx/splunk-otel-collector",
	"sumo": "https://github.com/SumoLogic/sumologic-otel-collector",
	"liatrio": "https://github.com/liatrio/liatrio-otel-collector",
	}

However, this list doesn't include any owners. This makes it difficult to review PRs that include adding a component to any particular distro. I propose that owners should be listed, much like code owners for each of the listed distro.

[github-actions]

Pinging code owners:

• cmd/mdatagen: @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Sounds good to me.

To complete this we'll also need to add automation to ping the distribution owners when necessary.

Do we want labels for each distribution as well? We can use that as the event to ping the relevant owners. Maybe something of the form distro:core, distro:contrib, etc.

[dmitryax]

Do we want labels for each distribution as well? We can use that as the event to ping the relevant owners. Maybe something of the form distro:core, distro:contrib, etc.

Sounds like a good idea 👍

[codeboten]

I like the label idea... I don't know how often we would end up using it. The only changes I can think of that are distro specific are changes to readme files to include a component in a distro, which i don't know if it opens often enough to warrant automation.

[atoulme]

I propose the following: we will create a file describing the contents of a distro generated via mdatagen, and have a CODEOWNERS entry generated from the owners of the distribution so we can tag anyone managing a specific distribution and make sure to notify them of any changes to their distribution.