Community: Create a bot to push announcements to multiple communications channels

[RobertKielty]

High Level Use Case

• As a designated user responsible for communications they should be able to create a message that can be automatically published to multiple specified communications channels.

The idea here is to make multi-channel communications easy: write once, then optionally publish to some or all of the comm channels such as rooms/accounts/groups on say Slack, Twitter, Discuss, Mailing list etc.

We may need to define :

• announcer roles

• an access and authorization mechanism for announcers

• the channels to which announcement content can be published

• community segments (may not be necessary if we rely on community members subscribing to channels)

_Might_ also want consider :

• Having a review process, (make it GitHub/PR based maybe) to ensure any message policy compliance, accuracy, spelling etc.
• Time targeting of message delivery based on Time Zone
• Message Targeting based on any definable community segmentation (again subscription to a channel may make this a non-requirement)

Other ideas welcome ...

[parispittman]

i will put an area/contributor-comms label on this once it is live :)

these are good ideas for sure and worth exploring with the marketing and slack teams.

[mbbroberg]

Relates to #4616 which is resolved by #4679

If you're interested in mapping from the strategy above into tooling, come hang out :dancing_women: :dancing_men:

[rajula96reddy]

/assign

[rajula96reddy]

@mbbroberg I have assigned this to myself as discussed. I will start with a basic proof of concept sort and see where it goes

[mbbroberg]

Meeting notes: cc @jonasrosland you'll end up helping @rajula96reddy move forward with automation.

[jonasrosland]

Sounds great!

[rajula96reddy]

Update:
Opened an issue on slack-infra regarding integrating the bot to infra
https://github.com/kubernetes-sigs/slack-infra/issues/32

[phumberdroz]

Currently we get a couple of requests in #slack-admins that involve around posting something in #announcements

for example:
https://kubernetes.slack.com/archives/C4M06S5HS/p1594223527225500

Would be nice if we can consider these kind of requests as well.

[mrbobbytables]

Just checking in on this, now that we have the slack integration - do you think should be closed? or are there other work items.

[fejta-bot]

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]

We have a Slack multi-channel sender and Twitter automation. A longer-term vision more akin to this diagram will take planning and scoping.

This issue doesn't need to remain open as we do so.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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.