📖 Documentation improvements: suggestions for team leads

[Prajyot-Parab]

What this PR does / why we need it:
Part of #9216

• Doc improvement (add a recommendation to leads tasks):Communicate and set clear expectations between the leads and the shadows about timeline and rotation.

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

[Prajyot-Parab]

/cc @furkatgofurov7
/area documentation

[killianmuldoon]

The wording looks good in general- but I think this sort of information might fit better in the release team doc - that's where we have the existing time commitment info.

It would be better IMO to keep this doc as a more focused task list.

[Prajyot-Parab]

The wording looks good in general- but I think this sort of information might fit better in the release team doc - that's where we have the existing time commitment info.

It would be better IMO to keep this doc as a more focused task list.

Noted will move over the text there.

[furkatgofurov7]

Thanks for the PR, few suggestions inline:

[sbueringer]

/approve

Thank you very much for improving the docs.

Leaving lgtm to folks from the release team to merge it

[sbueringer]

@furkatgofurov7 Sort of related. We have to discuss it but I would be in favor of giving "cluster-api-release-team" reviewers and "cluster-api-relase-lead" approver rights on the docs/release folder (basically same as CHANGELOG)

[killianmuldoon]

@furkatgofurov7 Sort of related. We have to discuss it but I would be in favor of giving "cluster-api-release-team" reviewers and "cluster-api-relase-lead" approver rights on the docs/release folder (basically same as CHANGELOG)

sounds like a very good idea to me

[furkatgofurov7]

@furkatgofurov7 Sort of related. We have to discuss it but I would be in favor of giving "cluster-api-release-team" reviewers and "cluster-api-relase-lead" approver rights on the docs/release folder (basically same as CHANGELOG)

@sbueringer sounds like a good idea to me as well

[furkatgofurov7]

I think we need to propose it in the next office hours, perhaps (as we always do)?

[sbueringer]

I think we need to propose it in the next office hours, perhaps (as we always do)?

I think it doesn't hurt and we're not in a rush. But feel free to open a PR already and cc maintainers

[furkatgofurov7]

Thanks for working on this @Prajyot-Parab!

/lgtm
/hold

in case @killianmuldoon has further comments, feel free to unhold

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: af95458b938ba9383c31e5cd6159fbbe280af16a

[killianmuldoon]

All good from my side!

/lgtm
/approve

/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: killianmuldoon, sbueringer

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:

• docs/OWNERS [killianmuldoon,sbueringer]

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

[furkatgofurov7]

I think we need to propose it in the next office hours, perhaps (as we always do)?

I think it doesn't hurt and we're not in a rush. But feel free to open a PR already and cc maintainers

hey, here it is: #9294