search

kubernetes-sigs / slack-infra

Tooling for kubernetes.slack.com
Apache License 2.0
90 stars 36 forks source link

feature request: slackbot for group chairs/leads #55

Closed parispittman closed 2 years ago

parispittman commented 2 years ago

-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?

parispittman commented 2 years ago

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

mrbobbytables commented 2 years ago

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

parispittman commented 2 years ago

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.

mrbobbytables commented 2 years ago

so essentially the twitter bot but for slack?

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle stale

chases2 commented 2 years ago

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

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/slack-infra/issues/55#issuecomment-1217289686): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.