community

community copied to clipboard

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
• have a shadow
• what else?

this person should:

• have experience moderating at least one of the platforms for kubernetes, current or in the past
• put 1 hour a week into the role (we are large and have enough random tidbits that this is realistic)
• expect ~5 hours a month
• grow a shadow
• what else?

this issue will close when/if:

• we've drafted the role and its merged by one of the contribex leads https://hackmd.io/PectKpzeRfy0tkizWUUZjw
• we can't come to an agreement that the role should exist

/sig-contributor experience

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

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

lol dang that hyphen

/sig contributor-experience

/area community-management

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

In response to this:

/priority long-term

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/test-infra repository.

/priority important-longterm

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

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.

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.

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:

• we need to poll the existing moderation teams and get their collab on this. Otherwise it could be seen as "imposing management".
• 5 hours a month is unrealistically low; think 10-15. I spend 5 hours a month and I'm just a routine Slack mod.

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.

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

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

@jberkus yes, I see that as being critical

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

/remove-lifecycle stale

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

/remove-lifecycle stale

This is still ongoing but very close to the end.

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

I think this is complete @parispittman also cc @coderanger

/remove-lifecycle stale

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

This has been completed /close

@markyjackson-taulia: Closing this issue.

In response to this:

This has been completed /close

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/test-infra repository.