On Mon, Mar 28, 2016 at 10:22 AM, Joe Brockmeier <jzb(a)redhat.com> wrote:
On 03/26/2016 07:24 AM, Miro Hrončok wrote:
> Those might not be perfect, but it illustrates the idea. A Twitter
> account has to be managed by a real person, not just by a robot, in
> order to attract some followers.
Honestly, I don't think we should be using @fedoracommunity at all. It
dilutes the social media "presence" of Fedora and we're going to have an
uphill battle trying to attract followers.
We aren't so active with the @fedora account that we need to split the
effort, and we shouldn't silo off the contributor content because it may
not be of interest to some percentage of the audience.
This was an early bit of infrastructure that we stood up to test the
commblog->twitter pipeline, and yes, it's purpose is to be the jetpack
plugin's republisher of content from wordpress.
I'd suspect commops would be more than happy to have that jetpack
plugin auto-posting to the main @fedora account, but it'd be good to
get some consensus on whether folks think this is a good idea. It also
doesn't solve the "no human titles" issue that churchyard originally
raised. Perhaps if it is intermingled with the human content already
being posted, it would be 'more interesting' than just having it be a
rss->twitter pipe account?
Since it has been proposed, I'm going to cc some members of the Fedora
magazine editorial team, to see if they agree, and find out the
procedure for pointing jetpack to the main @fedora twitter account.
The only possible issue we're going to have though, is that we do
occasionally do cross-promotion between commblog and magazine
sometimes, so there may be some 'double' posting that happens when we
have big announcements. Not sure how to avoid this, besides manually
posting everything, which is not in the spirit of how commops
operates, and kinda defeats the purpose of the jetpack auto-posting
plugins. I think we're just going to have to accept a certain amount
Fedora Community Lead & Council