View source for Drumbeat/website/SocialMedia/policy

==Policy & process==

Both Mozilla Drumbeat and each project should have the same basic social media presence.

=== Basic ===

* facebook
** fan page
** group (optional)
* twitter
* status.net
* flickr
* youtube (or its alternatives)

===WHO===

* Drumbeat chosen users
** those who have access to Drumbeat access spreadsheet
** all @Drumbeat general accounts
** all RSS 2 Socialsphere (or similar) configuration profiles
** choice on RSS sources to be  bounced on the socialsphere

* Drumbeat project initiators
** @Prj_Drumbeat account (@Drumbeat general accounts are going to follow each one of them)
** all RSS 2 Socialsphere configuration profiles for projects.
** choice on RSS sources to be bounced on the socialsphere

* Drumbeat editorial general users
** some of the @Drumbeat general accounts

* Drumbeat editorial project users
** @prj_drumbeat account

===WHAT AND HOW===

Our publishing policy implies the use of proprietary platform like Facebook, Twitter, Flickr and YouTube in the first phase as mirrors of the open alternatives to them.

Later on, we need to implement a tool to link them together.

We are going to distinguish between ACTIVE publishing and PASSIVE publishing.

=====active publishing=====

This kind of publishing is when a user or more than one are publishing actively on these platform, updating their statuses, or sharing some other experience.

=====passive publishing=====

This kind of publishing happens when the set up tools like RSS 2 Socialsphere take one rss item and publish it around the various platforms.

* RSS 2 Socialsphere
* aggregating rss sources from users
* tweeting on with #mozilla #drumbeat 
* posting facebook updates on fan page

====Identi.ca / Twitter====

* follow each projects' twitter account
* using #mozilla #drumbeat hashtag
* general tweets
** taxonomy terms from Drupal nodes tag
** RT valuable content from projects' account
** RT valuable content from projects' passive publishing
* project tweet
** @project_username
** taxonomy terms from Drupal nodes tag

====Facebook====

* status updates
** using effective keywords and mention (@Username on facebook)
** tagging users on pictures, videos and notes (facebook)
** reshare valuable contents from fan or group users

====Flickr====

* photosharing on general pictures
** posting events picture on Flickr "official" account
** tagging picture with at least "drumbeat" keyword (also on other accounts), and relevant keywords as well

* photosharing on project related pictures
** posting projects events picture on Flickr "official" account
** tagging picture with "drumbeat" and "project name" keywords (also on other accounts)

====Video====

* How do we co-ordinate w. video aggregator tools that Ben M. / Brett are creating?
    
* videosharing on general video/presentations
** posting videos on YouTube, Vimeo, etc. "official" channels, and in other channels
** marking as favourite videos on those platforms
** tag video with "drumbeat" keyword, and relevant keywords as well

* videosharing on project related video/presentations
** posting videos on YouTube, Vimeo, etc. "official" channels, and in other channels
** marking as favourite videos on those platforms
** tag video with "drumbeat", "project name" keyword, and relevant keywords as well


Each publishing policy until now, is referred to an in-platform policy. What an editorial user sees into the platform is going to be re-published, re-shared on the same platform.
This is going to be almost effortless, thanks to the built-in tools of the platforms themselves.

A bit more difficult could be to choose contents from one platform and consciuosly reshare it around.

A golden rule could be to choose relatively to source medium.

* picture -> photosharing
* video -> video sharing
* documents -> document sharing
* quick experience and thought -> microblog
* event -> event sharing
* trip -> trip sharing

===Drumbeat Social Media presence.===

==== profiles:====

* facebook
** group
** fan page
* twitter
** profile
** lists
* identi.ca
** profile
** groups

* Blogosphere: 
** blog drumbeat
** project blog

* RSS
** planet drumbeat
** users' sources

* Photosharing
** Flickr

* Video sharing
** vimeo
** youtube channel
** blip.tv 
** dailymotion.com

* Documents and presentation
** scribd
** slideshare
** issuu

* NetWorking
** linkedin group

* Container
** Friendfeed

* Social Bookmarking
** Delicious

* Location sharing
** foursquare
** tripwolf
** dopplr

* Newsletter
** general newsletter
** project newsletter

* Linking services
** Twitterfeed, Hootsuite etc. are RSS 2 Socialsphere tools

==Process roadmap==

We need to set all up in order to be ready to get engagement all around. So everything has to connected and autoshared as in the [presentation http://bit.ly/socdrm].

* Twitter
** RSS 2 Socialsphere
*** planet
*** project feeds
*** following some trendsetter about the web the  openweb and socialmedia stuff

* Fanpage
** update  drumbeat data
** link twitter @mozilladrumbeat
** static  FBML box as a default landing page
* engagement 
** a  Follow us on twitter/identi.ca button to engage users
** subscription  form for newsletter
** Preferred fan pages


===Social media plan AFTER beta. Once we're ready to make more noise about Drumbeat, how do we ramp up?===

Proposal: 

It could be great to have a contest to engage users.
Basically this could be distributed along all the Mozilla projects social presences. Like on Facebook fan page of Mozilla Firefox or Creative Collective, sort of a quiz or something.
In any case we need to create engagement and get people participating.


==== Drumbeat is a container, let's spotlight great content ====

In order to engage people both on Drumbeat and on its great content and projects, it could be great to gather every week some presentation, and update from each project in the platform.
In this way we can both achieve updated great content for Drumbeat, and updates on projects, promoting and spotlighting them periodically.