Curating Community Meeting Topics

[nimbinatus]

Following up from #5462, one of the concerns is trying to gather topics ahead of time on a continuous basis. As hosts have traditionally been new to the project as a way to get involved, asking hosts to find topics to discuss is unsustainable, and we've been relying on various members to find topics.

At the moment, we have a few ways that folks can raise a topic:

• Add it to the agenda (in the past, we did try adding to a sheet, but it got very messy very quickly as there was no way to prevent overwriting of cells)
• Use a Google form
• Ping on Slack/email

We also have talked about ideas like these:

• Labels in GitHub to add to issues or PRs to raise it to the list of topics
• Emojis or a Slack handle in Slack to flag discussions for the community meeting

As we're still getting the regular cadence, we want to be careful of "flailing," or changing course too fast by dropping ways and adding more. We're interested in the community's ideas on curating topics to add to our existing methods.

/assign @nimbinatus
/sig contributor-experience

[parispittman]

im a fan of having the same person do it for a 6 month or 1 year period with a shadow and then the curation will come naturally once you have been around for a bit. if folks really like it that a new person hosts, maybe the host is the one that is new and just reads the script while the 6mo-1yr role does the curation.

[panzerox123]

Hey everybody! @utkarsh348 and I are working on a slack bot that should be able to store data from messages sent on a slack group when there's a specific reaction added to them. We have a proof of concept ready here, if you would like to check it out.

[utkarsh348]

The POC can track the specific events for the reaction added to a message. This is just a barebones implementation and from here we can proceed by understanding what features and permission settings we'll need to add(naturally this bot's features will need to have some restricted access), along with where to post the messages or agendas. We realize this will need some deliberation and we'd like to be a part of that to understand the requirements if this slack bot seems like a feasible solution :)

[k8s-triage-robot]

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

[nimbinatus]

/remove-lifecycle stale

[k8s-triage-robot]

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

[k8s-triage-robot]

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

[nimbinatus]

/remove-lifecycle rotten

[nimbinatus]

ref: #7068

/close

[k8s-ci-robot]

@nimbinatus: Closing this issue.

In response to this:

ref: #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.