Dear guys,

are you planning to share a daily link or tweet that would point to all the 
information that has been gathered about Day 1, Day 2...?

Such as videos, articles, photos, story-boarding from talks...?

Thanks,

Natalie Ardasevova 
[email protected] 
Marketing Communications Specialist 


----- Original Message -----
From: "Ryan Lerch" <[email protected]>
To: "Fedora Marketing team" <[email protected]>, 
[email protected], [email protected]
Sent: Friday, July 22, 2016 12:58:08 AM
Subject: [Marketing] Re: Social media for Flock



On Fri, Jul 22, 2016 at 7:59 AM, Paul W. Frields < [email protected] > wrote: 


A couple people noted in the Magazine meeting that last year's Flock 
was a little spammy in use of Twitter/social media. Would it make 
sense to use a different account for "this talk is now on" type 
things, and just have the @fedora account stay clear other than to 
point people to that account if interested? 

Yeah, i think we should definiently only have at most a couple of flock tweets 
in a row. The fedora social accounts aren't really high posting accounts, so 
jumping up from max 2-5 tweets a day, to many more is going to be seen as 
spammy IMO. 

The tweets we do post should have an impact to people following along at home 
-- unless we are streaming the keynotes, tweeting that the keynote is on is 
only really useful to the 200 people at flock, not the 70K on the social 
networks. 

--ryanlerch 



Other thoughts welcome. 

-- 
Paul W. Frields http://paul.frields.org/ 
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ 
The open source story continues to grow: http://opensource.com 
-- 
Fedora Marketing mailing list 
[email protected] 
https://lists.fedoraproject.org/admin/lists/[email protected] 


--
Fedora Marketing mailing list
[email protected]
https://lists.fedoraproject.org/admin/lists/[email protected]
--
Fedora Marketing mailing list
[email protected]
https://lists.fedoraproject.org/admin/lists/[email protected]

Reply via email to