I never used https://github.com/gr2m/twitter-together previously, in the past I used Hootsuite to set up approval workflows, but I think that the idea of setting up a workflow through github PRs looks like a good idea. It would be able to leverage committer/pmc membership to merge the PRs and would allow anyone to contribute with social media content.
On Tue, Feb 1, 2022 at 12:43 AM QP Hou <q...@scribd.com.invalid> wrote: > I don't know how other projects manage this, but one solution we could > evaluate is using github PRs to manage the twitter account. For > example, here is a github action that does exactly this > https://github.com/gr2m/twitter-together. > > On Mon, Jan 31, 2022 at 3:14 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > > hi all, > > > > The project is approaching it's 6th birthday and we have come a long way! > > > > We have a relatively seldom-used Twitter handle > > twitter.com/ApacheArrow and only a handful of people in the community > > have access to it. I know that Jacques and I do, but I am not sure who > > else. > > > > I wanted to discuss a few things: > > > > * Giving more committers/PMC members access to the Twitter handle — I > > think clearly there should be more people with access (I tweet through > > TweetDeck, e.g. I just posted about a newly posted blog post) > > * Consider if there are any other social media channels where we might > > want to promote Arrow content > > * Discuss a social media policy more broadly for the project > > > > On the latter point, my feelings are: > > > > * Promote content and usage of Apache Arrow, but not companies or > > products (Apache projects are independent) > > * Provide a way for the community to submit ideas/materials for social > media > > > > Does anyone know if other ASF projects have policies/conventions about > > how they decide how to use their social media properties to best serve > > the community? > > > > Thanks, > > Wes >
