search

kubernetes / community

Kubernetes community content
Apache License 2.0
12k stars 5.17k forks source link

curate a lead moderator role #6088

Closed parispittman closed 1 year ago

parispittman commented 3 years ago

we have several platforms (mailing list, slack, etc) that are all moderated and/or administered in some way with a different set of moderators (some that overlap) for each. between sig-contribex chairs, myself, and other active leads on certain platforms, we all play a part in what could be a carved out role for a moderation lead.

this person would help with:

this person should:

this issue will close when/if:

/sig-contributor experience

k8s-ci-robot commented 3 years ago

@parispittman: The label(s) sig/experience cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/community/issues/6088): >we have several platforms (mailing list, slack, etc) that are all moderated and/or administered in some way with a different set of moderators (some that overlap) for each. between sig-contribex chairs, myself, and other active leads on certain platforms, we all play a part in what could be a carved out role for a moderation lead. > >this person would help with: >- training and onboarding all new members >- communicating changes to any of the flow (tech or non tech) >- helping to formulate incident management reporting >- check-ins with moderators >- recruiting new moderators >- updating documentation >- what else? > >this person should: >- have experience moderating at least one of the platforms for kubernetes, current or in the past >- what else? > >this issue will close when/if: >- we've drafted the role and its merged by one of the contribex leads >- we can't come to an agreement that the role should exist > > >/sig-contributor experience 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.
parispittman commented 3 years ago

lol dang that hyphen

/sig contributor-experience

Debanitrkl commented 3 years ago

/area community-management

k8s-ci-robot commented 3 years ago

@Debanitrkl: The label(s) priority/long-term cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/community/issues/6088#issuecomment-948054005): >/priority long-term 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.
Debanitrkl commented 3 years ago

/priority important-longterm

chris-short commented 3 years ago

Strong +1 here.

On Wed, Sep 29, 2021 at 19:09 Paris @.***> wrote:

we have several platforms (mailing list, slack, etc) that are all moderated and/or administered in some way with a different set of moderators (some that overlap) for each. between sig-contribex chairs, myself, and other active leads on certain platforms, we all play a part in what could be a carved out role for a moderation lead.

this person would help with:

  • training and onboarding all new members
  • communicating changes to any of the flow (tech or non tech)
  • helping to formulate incident management reporting
  • check-ins with moderators
  • recruiting new moderators
  • updating documentation
  • what else?

this person should:

  • have experience moderating at least one of the platforms for kubernetes, current or in the past
  • what else?

this issue will close when/if:

  • we've drafted the role and its merged by one of the contribex leads
  • we can't come to an agreement that the role should exist

/sig-contributor experience

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/6088, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKUD6J4S5JSFE43QLK5A7LUEOMDXANCNFSM5FA7TVJQ .

--

Chris Short https://linktr.ee/TheChrisShort He/Him/His TZ=America/Detroit

jdumars commented 2 years ago

Big +1 - and I would suggest a person + shadow(s) for this. It might also be good to have a calendar/schedule so there's continual coverage.

markjacksonfishing commented 2 years ago

I am interested in this role. Having served as Slack, email, and YouTube moderator, I have knowledge and am also looking to get back in to contributing.

jberkus commented 2 years ago

I was going to say: I don't see the point in having such a role unless we have a candidate for it. But: if Marky is available, I'll happily +1 him.

Couple of bits of feedback, neither of which should be considered blockers, just so that we get the role description right:

markjacksonfishing commented 2 years ago

I agree that this role would require more than 5 hours per week. 10 - 15 is more what I feel is needed, and I am up for that. As for gathering info from other moderators, this is an excellent idea. I do feel this could be done in parallel with the building of the role.

parispittman commented 2 years ago

folks: #6278 your reviews would be very appreciated. thank you!

jberkus commented 2 years ago

Also ... should this Lead be responsible for reporting to the CoCC?

markjacksonfishing commented 2 years ago

@jberkus yes, I see that as being critical

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

alisondy commented 2 years ago

/remove-lifecycle stale

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

markjacksonfishing commented 2 years ago

/remove-lifecycle stale

markjacksonfishing commented 2 years ago

This is still ongoing but very close to the end.

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

markjacksonfishing commented 2 years ago

I think this is complete @parispittman also cc @coderanger

/remove-lifecycle stale

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

markjacksonfishing commented 1 year ago

This has been completed /close

k8s-ci-robot commented 1 year ago

@markyjackson-taulia: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/6088#issuecomment-1344862775): >This has been completed >/close 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.