community

community copied to clipboard

Currently there isn't a clear definition of what should/shouldn't be considered an event that can be promoted. To ensure a neutral stance, the guidelines should be updated to state that only Kubernetes community or CNCF hosted events can quality for promotion.

Both the social media guidelines and issue template should be updated.

/sig contributor-experience /area contributor-comms

feel free to take a variation of this: https://github.com/cncf/foundation/blob/master/social-guidelines.md

On Sun, Feb 7, 2021 at 11:33 AM Bob Killen [email protected] wrote:

Currently there isn't a clear definition of what should/shouldn't be considered an event that can be promoted. To ensure a neutral stance, the guidelines should be updated to state that only Kubernetes community or CNCF hosted events can quality for promotion.

Both the social media guidelines and issue template should be updated.

/sig contributor-experience /area contributor-comms

— 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/5478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSIKTF2GM756FULXSPLLS53FGXANCNFSM4XHVKCBQ .

-- Cheers,

Chris Aniszczyk http://aniszczyk.org

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

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

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:

• Mark this issue or PR as fresh with /remove-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 rotten

We still get requests about this from time to time so formal guidelines, even if they are very simple, would be good.

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

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

/close

@k8s-triage-robot: Closing this issue.

In response to this:

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

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

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

/reopen /lifecycle frozen

@mrbobbytables: Reopened this issue.

In response to this:

/reopen /lifecycle frozen

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.

I like the idea of having a place to drop tweets for amplification. I feel like that's the sig-contribex Slack channel right now though. Maybe there's a better place.

The strategy we can pull from our charter as it lines up nicely: https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md

As far as themes and topics its Kubernetes Contributor content. If it's relevant to a contributor or highlighting their work we share it. We stay in the Kubernetes and its subprojects for topic areas. We need to flesh out some specifics. Also, some example tweets would be helpful.

Writing this now before I forget. I think we'll need to get a draft going at the next meeting.