community

community copied to clipboard

Adding a roles doc as the community meeting is expanding some. Discussed in an async retro thread in the Contribex Slack channel.

Note: I'm not sure if this is the precise place to put the roles doc, so please let me know if it's the wrong spot.

Relates to #6544

/assign @nimbinatus

my advice for rolebook placement is in the folder where the action will occur so that you can go into the owners file there for the thing instead of contribex chairs managing the role as it would be in the placement right now.

/lgtm thanks a ton for your work here!

Ahh, got it. So it would live next to the community meeting doc. I'll move it!

New changes are detected. LGTM label has been removed.

Moved! @parispittman, was this where you were thinking of it belonging?

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nimbinatus To complete the pull request process, please ask for approval from parispittman after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• events/OWNERS

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

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

/unassign /assign @mrbobbytables

ref: https://github.com/kubernetes/community/pull/7068

/close

@nimbinatus: Closed this PR.

In response to this:

ref: https://github.com/kubernetes/community/pull/7068

/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.