Dear all,
I suggest sharing access to Twitter with the contributors who might need to
do emergency announcements on behalf of the Jenkins community. In
particular, Jenkins Infrastructure and Security teams may want to make
announcements about outages, maintenance work, advisories and 0-day
security issues.
I suggest sharing access to jenkinsci Twitter with Daniel Beck, Olivier
Vernin, Wadeck Follonier and Damien Duportal. Although we do not have an
official "shadow officer" term yet, de-facto Wadeck and Olivier get a lot
of infra knowledge transfers and act as officers when Olivier or Daniel are
off. I believe it would be appropriate to share access with them right away.
There are two ways to share access:
1. Classic way: Grant access to TweetDeck to all contributors so that
they can manage posts manually
2. Suggested way (by me): Twitter as code
1. We create a new "Jenkins Announcements" GitHub repo and
configure Twitter
Together <https://github.com/gr2m/twitter-together> automation for
it. It will allow all contributors to manage announcements via pull
requests and, later, automate creating posts. Copy-editing could be done
via pull request reviews. Example:
https://github.com/jenkinsci/memkins
2. The repository is connected either to the main jenkinsci
account or to a new one. For the latter we may want to automate retweets
from jenkinsci, e.g. using IFFFT or a twitter bot. This step will require
assistance from Tyler as jenkinsci account owner who can setup a
Twitter app
3. Later: Keep evolving and consolidating Jenkins social media
- Why not "jenkins-twitter?" you may ask... Later we can use the
same repo to automatically put announcements in other channels like
Telegram Channels, Reddit or Hacker News
- Later I envision automating community.jenkins.io
announcements => social media, and it may go through the same
repo via pull
request automation
I would be interested in spending some time and implementing the second
option. IMO it is a good investment in the future and improving
communications with Jenkins end users. What do you think?
Best regards,
Oleg Nenashev
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCzO1xD8JZ7X0%2BMtWfr2Z64Ga6A-eAtRsP4j395MA3KCw%40mail.gmail.com.
