PublicRelationsDocumentation

Differences between revisions 47 and 48
Revision 47 as of 2015-08-28 15:00:07
Size: 5777
Editor: c-5eeaaa24-74736162
Comment:
Revision 48 as of 2015-08-28 15:05:31
Size: 5664
Editor: c-5eeaaa24-74736162
Comment:
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
(__update or remove? __)
Line 35: Line 36:
||<#FFCC99> Release News || Make an official post on a new release every 6 months || website & social channels, G+, mail lists, forums, || [[slavender]] ||
||<#CCFFCC> Milestone Testing || Announce testing, and ask for participants for Beta2 and R.C || website & social channels, G+, mail lists, forums || [[smartboyhw]] ||
||<#ADD8E6> Request Help From Community || Hunt for developers and contributors at least once after each new release is out|| website & social channels, G+, mail lists, forums || [[zequence]] ||
||<#FFFFCC> Non Formal Posting || Any news about Ubuntu Studio, reviews, interviews, UDS, meetings, release planning, etc || website & social Channels, G+ || [[Ttoine]], [[holstein]] ||
||<#FFCC99> Release News || Make an official post on a new release every 6 months || website & social channels, G+, mail lists, forums, || ||
||<#CCFFCC> Milestone Testing || Announce testing, and ask for participants for Beta2 and R.C || website & social channels, G+, mail lists, forums || ||
||<#ADD8E6> Request Help From Community || Hunt for developers and contributors at least once after each new release is out|| website & social channels, G+, mail lists, forums || [[zequence]], PR team? ||
||<#FFFFCC> Non Formal Posting || Any news about Ubuntu Studio, reviews, interviews, UDS, meetings, release planning, etc || website & social Channels, G+ || [[Ttoine]], [[holstein]], PR team? ||
Line 42: Line 43:
Use only text, when writing posts. Save the article as a textfile. Then post the same text to each channel, one at a time. Use the #ubuntustudio hashtag in footer. (!ubuntustudio on identi.ca). ''Use only text, when writing posts. Save the article as a textfile. Then post the same text to each channel, one at a time. Use the #ubuntustudio hashtag in footer.''
Line 84: Line 85:
 * Facebook
 * Identica
 * Facebook 
 * G+ (separate Ubuntu Studio account)
Line 89: Line 90:
 * G+ (separate Ubuntu Studio account)
Line 93: Line 93:
 * [[http://sixgun.org/linuxoutlaws|Linuxoutlaws]]
 * [[http://tllts.org/|the linuxlink tech show podcast]]
 * Bad Voltage?

The purpose of this wiki page is to define the public relations strategy for the Ubuntu Studio Public Relations team. This will include defining the team, the communications channels used, list of events to publicize, etc.

PR Strategy

The primary goals of Ubuntu Studio Public Relations are to:

  • spread the word of Ubuntu Studio to attract and grow the user base, community and development team.
  • communicate more often to users
  • encourage contributors and developers to join the Ubuntu Studio Development Team
  • calls for volunteers for testing

Public Relations Team

The Ubuntu Studio Public Relations Team will be primarily repsonsible for all public relations and external (i.e. not inter-team or to Ubuntu) communications for Ubuntu Studio.

(italics = to be discussed)

To become a member of the PR team, first one must volunteer either in #ubuntustudio-devel on Freenode IRC or on the ubuntustudio-devel mailing list and then be approved by one of the PR team's admins.

The team should have at least two admins to ensure responsiveness to volunteers and other matters for the team.

The Ubuntu Studio Public Relations Team will act as the Launchpad team for the PR team, providing a mechanism for controlling access to the website (i.e. authentication for website login has been assigned to the website team).

The PR team should remain small, perhaps no more than five active members. This should hopefully prevent major overlap of news coverage and hopefully such a small group can find an easy (and informal) consensus about what topic each member should cover.

Furthermore, it might be wise to assign one PR team member for some large, specific events (e.g. release) with a secondary as fail over.

Writing Posts

(update or remove? )

Event Posting

Event

Description

Channels

Assignee

Release News

Make an official post on a new release every 6 months

website & social channels, G+, mail lists, forums,

Milestone Testing

Announce testing, and ask for participants for Beta2 and R.C

website & social channels, G+, mail lists, forums

Request Help From Community

Hunt for developers and contributors at least once after each new release is out

website & social channels, G+, mail lists, forums

zequence, PR team?

Non Formal Posting

Any news about Ubuntu Studio, reviews, interviews, UDS, meetings, release planning, etc

website & social Channels, G+

Ttoine, holstein, PR team?

How to Post

Use only text, when writing posts. Save the article as a textfile. Then post the same text to each channel, one at a time. Use the #ubuntustudio hashtag in footer.

What to Post

  • Any significant news on Linux Multimedia that somehow may be interesting for Ubuntu Studio users (new software, changes in technology)
  • Interviews..
    • ..of Linux multimedia developers (we may conduct our own)
    • ..of multimedia producers (audio, video, graphics, etc)
  • Significant news on Ubuntu Studio development
    • Call for testing
    • New features or applications added

..add more here

Making Videos and Podcasts

At this time, there is no plan on how to do this.

List of Communication Channels

Ubuntu Studio Web Site

Mail Lists

Forums

Social Channels (linked to from the website)

  • Facebook
  • G+ (separate Ubuntu Studio account)
  • Twitter

Other Social Channels

  • Youtube (separate Ubuntu Studio account)

Podcasts

  • Bad Voltage?

==== Old PR page archived ====

UbuntuStudio/PublicRelationsDocumentationArchive


CategoryUbuntuStudioPublicRelations

UbuntuStudio/PublicRelationsDocumentation (last edited 2015-11-16 08:26:23 by 118)