search

kubernetes-sigs / slack-infra

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

Contrib-ex multichannel communication bot #32

Closed rajula96reddy closed 4 years ago

rajula96reddy commented 4 years ago

Hey there!

As a part of the contib-ex marketing team, we are working on a slack bot to improve slack communications. Upon discussion, we have planned for the following features

  1. Bot should be able to send messages to multiple k8s slack channels upon user input
  2. Bot should be able to make a tweet to the Community twitter account directly from the K8s slack itself
  3. Bot should be able to integrate k-dev posts to k8s slack
  4. Bot should be accessed only by a member of contributor-comms user group

Current status: As a POC, we built an app on a dummy slack instance. Take a look at the progress here. The app is very basic and is currently written in python using the slackeventsapi and slack modals

The bot requires a backend server running to handle requests and therefore we are planning to integrate the bot to the slack-infra repo. We would like to know the process for this. Further we want to know if we are required to rewrite the bot in golang similar to the ones present in slack-infra repo.

Please do let us know if you have any specific feedback or comments on this.

CC: @jonasrosland @mbbroberg @parispittman @mrbobbytables

Ref:

  1. https://github.com/kubernetes/community/issues/4446
  2. https://github.com/rajula96reddy/k8s-slack-contribex-marketing-bot
mbbroberg commented 4 years ago

cc @mrbobbytables to nudge this one.

jeefy commented 4 years ago

I think the process for this would be to submit a PR for us to review. I'd rewrite it in Golang to keep things consistent within this repo.

I do have mild concerns with a bot having this much power but this is also an internal/contribex project. Other thing of note, we'll have to add the Twitter creds as a secret.

fejta-bot commented 4 years ago

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-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

mbbroberg commented 4 years ago

This is done as of https://github.com/kubernetes-sigs/slack-infra/commit/55fbfb1994a84e57daa8e5aa0b25578dd9072b0b

/close

k8s-ci-robot commented 4 years ago

@mbbroberg: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/slack-infra/issues/32#issuecomment-700995120): >This is done as of https://github.com/kubernetes-sigs/slack-infra/commit/55fbfb1994a84e57daa8e5aa0b25578dd9072b0b > >/close 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.