[Weekly Report] Add section for components looking for new code owners

[crobert-1]

Component(s)

No response

Describe the issue you're reporting

Filing from #31115 (comment)

This request is to add a section to the weekly report that lists components that are looking for new code owners, in an effort to communicate with interested contributors where they can help out.

[LucaLanziani]

Duplicates? #32490

[crobert-1]

Duplicates? #32490

Not quite. This request is to include a list of components that have the following in their metadata.yaml:

status:
  ...
  codeowners:
    seeking_new: true

This is meant to let OpenTelemetry contributors know that this component welcomes help from anyone, and that contributors are welcome to become code owners.

#32490 is to list issues/PRs that have the label waiting-for-code-owners. This label is meant to notify code owners that there's something they need to take a look at.

[LucaLanziani]

Would something like this work?

Components Report

• deprecated: 1
  Components

  • instanaexporter: {"deprecated":["traces"]}
• unmaintained: 1
  Components

  • skywalkingexporter: {"unmaintained":["metrics","logs"]}
• looking for owners: 25
  Components

  • connector-grafanacloudconnector
  • connector-spanmetricsconnector
  • extension-filestorage
  • pkg-ottl
  • receiver-activedirectorydsreceiver
  • receiver-aerospikereceiver
  • receiver-awscloudwatchreceiver
  • receiver-azureeventhubreceiver
  • receiver-bigipreceiver
  • receiver-cloudflarereceiver
  • receiver-cloudfoundryreceiver
  • receiver-couchdbreceiver
  • receiver-elasticsearchreceiver
  • receiver-flinkmetricsreceiver
  • receiver-iisreceiver
  • receiver-memcachedreceiver
  • receiver-mongodbatlasreceiver
  • receiver-mongodbreceiver
  • receiver-rabbitmqreceiver
  • receiver-riakreceiver
  • receiver-sqlserverreceiver
  • receiver-syslogreceiver
  • receiver-vcenterreceiver
  • receiver-windowsperfcountersreceiver
  • receiver-zookeeperreceiver

[crobert-1]

Would something like this work?

I really like the component links! I'd prefer to remove the componenttype prefix (i.e. connector-) if possible. My preference would either be grafanacloudconnector or connector/grafanacloud. The second option would allow alphabetical order, and grouping by component type, but either one theoretically works.

[LucaLanziani]

Variation

• looking for owners: 25
  connector: 2

  • grafanacloudconnector
  • spanmetricsconnector
  extension: 1

  • filestorage
  pkg: 1

  • ottl
  receiver: 21

  • activedirectorydsreceiver
  • aerospikereceiver
  • awscloudwatchreceiver
  • azureeventhubreceiver
  • bigipreceiver
  • cloudflarereceiver
  • cloudfoundryreceiver
  • couchdbreceiver
  • elasticsearchreceiver
  • flinkmetricsreceiver
  • iisreceiver
  • memcachedreceiver
  • mongodbatlasreceiver
  • mongodbreceiver
  • rabbitmqreceiver
  • riakreceiver
  • sqlserverreceiver
  • syslogreceiver
  • vcenterreceiver
  • windowsperfcountersreceiver
  • zookeeperreceiver

[crobert-1]

Sure, that format works for me 👍

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[crobert-1]

Support for this was added in #33397, view the most recent weekly report to see the Seeking new code owners section.