search

kubernetes / steering

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

Community Annual Report Feedback #242

Closed parispittman closed 1 year ago

parispittman commented 2 years ago

https://www.cncf.io/reports/kubernetes-annual-report-2021/

steering public retro - Monday, June 6 @ 930am PT / 430pm UTC

Community Retro answer in comments

  1. What can we do better?

  2. Is the report valuable? How can we add more value?

  3. What did you like about it?

  4. additional comments/suggestions/ways you can help out?

Comment below!

parispittman commented 2 years ago

we buried the lede on areas that have single maintainer or really close; figure out how to get that to the top next time

parispittman commented 2 years ago

we're going to put a description together for an intern to help us with automation to cut down the time to prepare and to gather the summary information down to a few months from several. goal - 7 to 3.5 months

some of the scope is here but not the summary pieces: https://github.com/kubernetes/community/issues/6357

parispittman commented 2 years ago

feedback from chairs and tech leads meeting: Overall many sigs enjoyed a dedicated time to refine roadmap folks though template was good this year Covid may had an impact and the report helps with getting data and pulling people together to get measurements creating calls to actions are good Greater visibility on OWNERS helps start conversations with OWNERS and check

challenges about the process? Contributing.md - many SIGS don't have this up to date; hard to maintain and keep up to date some sigs spent a lot of time here (on contributing guide development) and was actually great Continue with template/swiss cheese holes with kep reporting

things we should do/ask for next time? Gap analysis stuff ‘where is your group now and where do you want to be’ Better refine questions so that the requests are useful Code owning sigs vs non code owning sig questions What is a package be more mindful of how we ask questions (‘if you own code, or is there some equiv metric’); help us understand goal of question use a chair/tech lead meeting as a working session

amcasari commented 2 years ago

If SIGs want focused help to improve their contributing docs, @glasnt and I have some frameworks that might help (and could schedule time in Q3-Q4).

parispittman commented 2 years ago

add specific questions for the following to the SIG template:

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

palnabarun commented 2 years ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 year 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

cpanato commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/steering/issues/242#issuecomment-1580575317): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues 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 with `/reopen` >- Mark this issue 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 not-planned > >[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.