Add WG leads to docs approvers

[pierDipi]

Every time there is a new page added, I cannot approve PRs (example #5916), so I'm adding WG leads to the top-level directory approvers

[netlify]

✅ Deploy Preview for knative ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	65354fe
🔍 Latest deploy log	https://app.netlify.com/sites/knative/deploys/6641e86d322c5c00087b64ed
😎 Deploy Preview	https://deploy-preview-5968--knative.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[pierDipi]

/cc @knative/technical-oversight-committee

[pierDipi]

/assign @knative/technical-oversight-committee

[Cali0707]

+1 from me!

/lgtm

[psschwei]

If the issue is approving page changes, would it make sense to add the working group leads as owners on the config directory rather than for all of docs? Though given that there's no docs team right now, perhaps it's better to have more folks able to approve for the whole repo?

[dprotaso]

If the issue is approving page changes, would it make sense to add the working group leads as owners on the config directory rather than for all of docs? Though given that there's no docs team right now, perhaps it's better to have more folks able to approve for the whole repo?

Yeah - let's subdivide the owners to the various sections

[dprotaso]

@pierDipi can you update the PR?

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Reopen with /reopen. Mark as fresh by adding the
comment /remove-lifecycle stale.

[Cali0707]

/remove-lifecycle stale

[skonto]

@pierDipi gentle ping

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Reopen with /reopen. Mark as fresh by adding the
comment /remove-lifecycle stale.

[pierDipi]

/reopen

I still think WG leads need access to the whole project to change nav, etc, since most of the time WG leads have also contributed to docs extensively to be able to be approver of the entire docs

[knative-prow]

@pierDipi: Reopened this PR.

In response to this:

/reopen

I still think WG leads need access to the whole project to change nav, etc, since most of the time WG leads have also contributed to docs extensively to be able to be approver of the entire docs

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-sigs/prow repository.

[pierDipi]

and obviously, WG leads will approve PRs in their area of expertise or expedite/review PRs they know are ok

[dprotaso]

and obviously, WG leads will approve PRs in their area of expertise or expedite/review PRs they know are ok

Yeah I agree - it's just the owner file right now will just tag doc approvers/reviewers first. So in addition to what you have we want to make sure we tag eventing approvers for eventing docs etc.

You can do that with separate owner files in nested directories

/lgtm
/approve

can you do the follow up in another PR?

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, pierDipi

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dprotaso]

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