🌱 Add OWNERS file with labels to docs/book

[oscr]

What this PR does / why we need it:

Testing automatic area labels (discussed in #8263) on a limited area to try it out.

Big thanks to @ykakarap for investigating and finding this solution.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Partof #8263

cc @joekr

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from oscr. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• docs/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[killianmuldoon]

I think it's a good idea to try this out - but we don't currently have an area/docs label. We should add that first IMO.

Also - there's already and OWNERS file under /docs - could this just be added there? Or should that file be moved down a level?

[oscr]

I think it's a good idea to try this out - but we don't currently have an area/docs label. We should add that first IMO.

Great catch. I can add it to: https://github.com/kubernetes/test-infra/blob/7471678e74188b7bdd29ba378a13df5a4a47dbb8/label_sync/labels.yaml#L1676

Also - there's already and OWNERS file under /docs - could this just be added there? Or should that file be moved down a level?

That is a good question. I didn't want to put community, proposals and releases under docs. But I'm open to put it in the docs root.

[ykakarap]

How about trying with clusterctl? We have an area/clusterctl label already and also have an OWNERS file for clusterctl in the required subfolder.

[oscr]

Sure! I've created a pr for clusterctl: #8342

[sbueringer]

Hm we already have kind documentation. Should this be area/book?
But let's discuss this as part of the area label discussion

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[killianmuldoon]

/close

I think the current approach to area labels makes this unnecessary

[k8s-ci-robot]

@killianmuldoon: Closed this PR.

In response to this:

/close

I think the current approach to area labels makes this unnecessary

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.