search

kubernetes / steering

The Kubernetes Steering Committee
Apache License 2.0
86 stars 61 forks source link

Docs audit #229

Closed justaugustus closed 2 years ago

justaugustus commented 2 years ago

Problem Statement

We have several documents in the Steering repo that, at the time of writing, have not been updated in multiple years.

Here are some examples:

Proposed Solution

Cost

If you are requesting funding please file requests issues here , otherwise please add any associated costs with your request if it is applicable.

Open Questions

Next Steps

Other Considerations, Notes, or References

/assign

justaugustus commented 2 years ago

From @tpepper w.r.t. inclusive training requirement:

The wording across the docs is slightly obtuse:

  • Issue 219:

    All new members must complete the Inclusive Leadership Training within 30 days from the date of their appointment.

  • Charter:

    Members are required to report completion of the course as part of on-boarding within 30 days from the date of their appointment.

…I’m assuming the intent is the course is to be taken within the first 30 days but the charter could use a tidier sentence to be clear to what part of the sentence 30 days refers.

justaugustus commented 2 years ago

@kubernetes/steering-committee -- For feedback on any particular areas you'd like to see covered.

parispittman commented 2 years ago

231

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/steering/issues/229#issuecomment-1120130640): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and 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 issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.