+1 from me as well. Thanks for doing it On Mon, May 10, 2021 at 5:20 AM Tim Jacomb <[email protected]> wrote:
> +1 > > On Mon, 10 May 2021 at 11:57, Oleg Nenashev <[email protected]> > wrote: > >> Dear all, >> >> Last week I created the new Jenkins-related Twitter account: >> https://twitter.com/memkins. The goal of this channel is to repost funny >> memes and comics about Jenkins, while delivering best practices to end >> users. Although this channel will include more sarcasm and self-criticism >> than the official channel, the plan is to keep it overall positive w.r.t >> Jenkins. It will also remain within the Jenkins Code of Conduct boundaries. >> >> In the Jenkins Advocacy and Outreach SIG we had many discussions about >> adopting a social media as code approach so that we could simplify content >> contributions and to simplify reviews. Currently we do it manually via >> Tweetdeck and Gitter based content reviews, and the process is not that >> productive. In the case of Twitter, there is a GitHub action for that: >> https://github.com/gr2m/twitter-together . I briefly evaluated it for >> personal use, but the value would be rather evaluating it in a shared >> account. And it looks much more convenient to test it on Memkins instead of >> the official Jenkins accounts. >> >> With permission of the community, I would like to do the following: >> >> - Create a jenkinsci/memkins GitHub repository >> - Create a GitHub action which would post Tweets to @memkins. >> Effectively it means that, in addition to the current moderators, all >> GitHub Org Admins will get access to the account >> - Evaluate and document the flow >> >> If the experiment goes well, we can later update the IRC bot (or use >> another automation), to automate pull requests to the repository via a chat >> command or a GitHUb App form. Then we will be able to apply the same to the >> main @jenkinsci or other accounts if all goes well. >> >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Advocacy and Outreach SIG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAH-3BicYwOQeftNxTvRHaFHCbqNd3mQY9oKNowq_UBCyu74vmA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAH-3BicYwOQeftNxTvRHaFHCbqNd3mQY9oKNowq_UBCyu74vmA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEuARo13OQ6%3DLG%2BA_QHraAfy0GF0OVu0wtUJdgbPTVPhw%40mail.gmail.com.
