feature request: slackbot for group chairs/leads

Question

feature request: slackbot for group chairs/leads

parispittman opened this issue 3 years ago · comments

-this is a draft/wip-

what
slackbot to remind community groups of important things in the community on a consistent, automated basis. only for #chairs-and-techleads channel.

why
why slack bot - taking out the human and the terrible calendaring.
why reminder - there is a lot and we forget because we are human

things?

have you uploaded videos this month?
have you scrubbed owners files this year? / run maintainers tooling?
who stands out in the last 3 months as someone to be promoted to member/reviewer/approver/chair/role?
annual report kick off / deadline approaching
kubecon maintainer track submissions are due / started
did your group shoutout anyone in the #shoutouts channel?

Paris · Answer 1 · Fri Feb 25 2022 01:38:32 GMT+0800 (China Standard Time)

this was an anonymous tip/suggestion and frankly, a great one. whoever you are out there, thank you. :p

Bob Killen · Answer 2 · Fri Feb 25 2022 02:29:21 GMT+0800 (China Standard Time)

Reminders are possible in slack already, we use them for the biweekly slack standup meetings in sig-contribex

Paris · Answer 3 · Fri Feb 25 2022 03:44:53 GMT+0800 (China Standard Time)

reminders could be ok for this as an interim solution but ultimately I think a bot would be best and the marketing team and other folks can contribute to it vs needing to remember if we set a reminder vs didn't, etc.

Bob Killen · Answer 4 · Fri Feb 25 2022 04:22:09 GMT+0800 (China Standard Time)

so essentially the twitter bot but for slack?

Kubernetes Triage Robot · Answer 5 · Thu May 26 2022 04:45:29 GMT+0800 (China Standard Time)

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

Sean-Logan Chase · Answer 6 · Sat Jun 18 2022 06:28:34 GMT+0800 (China Standard Time)

Would chairs and techleads configure which reminders they want, or is there some definite subset of reminders that every chair and techlead should get?

Kubernetes Triage Robot · Answer 7 · Mon Jul 18 2022 07:19:18 GMT+0800 (China Standard Time)

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

Kubernetes Triage Robot · Answer 8 · Wed Aug 17 2022 08:00:36 GMT+0800 (China Standard Time)

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

Kubernetes Prow Robot · Answer 9 · Wed Aug 17 2022 08:00:46 GMT+0800 (China Standard Time)

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