hi David — I just posted this tweet: https://twitter.com/ApacheArrow/status/1493965714646093824
I'll ping Jacques to ask him to give you TweetDeck access to the Twitter handle (and some other PMC members, too) On Wed, Feb 16, 2022 at 7:14 AM David Li <lidav...@apache.org> wrote: > > Following up here, how should we request access? I'd like to tweet out the > Flight SQL blog post that just landed. > > On Wed, Feb 9, 2022, at 17:22, Wes McKinney wrote: > >> In my opinion, any PMC member should be allowed to use the Twitter account > >> without any other checks, balances, or friction. > > > > I agree with this. Without objections, then, I would say we make sure > > as many PMC members have access to the account as have interest. I do > > not think I am empowered to grant access (Jacques may be the only one > > since he created the account initially) > > > > On Tue, Feb 1, 2022 at 4:44 PM Julian Hyde <jhyde.apa...@gmail.com> wrote: > >> > >> In my opinion, any PMC member should be allowed to use the Twitter account > >> without any other checks, balances, or friction. They know that they are > >> speaking for the project, and only for the project. They are PMC members > >> so we trust them to do the right thing. > >> > >> If committers and other non-PMC community members would like to suggest a > >> tweet then a GitHub PR is a reasonable process. But unlike a code change, > >> it needs to be approved by a PMC member. > >> > >> Quite frankly the easiest process for non-PMC members is just to tweet as > >> yourself (or your company, or project) and mention @ApacheArrow. A PMC > >> member will retweet or quote tweet if it deserves wider circulation. > >> > >> Julian > >> > >> > >> > >> > On Feb 1, 2022, at 11:00 AM, QP Hou <q...@scribd.com.INVALID> wrote: > >> > > >> > To be clear I haven't used that twitter-together action myself, was > >> > just using it as an example for how such a workflow could be set up. I > >> > imagine it won't be too much work for us to write our own action if > >> > needed. > >> > > >> > Thanks, > >> > QP Hou > >> > > >> > On Tue, Feb 1, 2022 at 5:31 AM Neal Richardson > >> > <neal.p.richard...@gmail.com> wrote: > >> >> > >> >> I like the idea too. If we were to use the github action to send > >> >> tweets, we > >> >> would need to get INFRA to add it to the allowlist since they restrict > >> >> which actions we can use. I don't think it's a blocker, just would add > >> >> some > >> >> extra time in the process of getting it set up. > >> >> > >> >> Neal > >> >> > >> >> > >> >> On Tue, Feb 1, 2022 at 5:25 AM Alessandro Molina < > >> >> alessan...@ursacomputing.com> wrote: > >> >> > >> >>> 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 > >> >>>> > >> >>> > >>
