PublicRelationsDocumentation

Contents

    1. PR Strategy
    2. Public Relations Team
    3. Writing Posts
      1. How to Post
      2. What to Post
    4. Making Videos and Podcasts
    5. List of Communication Channels
        1. Ubuntu Studio Web Site
        2. Mail Lists
        3. Forums
        4. Social Channels (linked to from the website)
        5. Other Social Channels
        6. Podcasts
        7. News Sites
  2. Sharing Passwords Between Team Members
    1. Make sure the recipient has a published gpg key at launchpad
    2. Import the published gpg key
    3. Encrypt the File
    4. Decrypting the file
        1. Old PR page archived

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

May be used for any announcements:

Use these?

Social Channels (linked to from the website)

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

Other Social Channels

  • Youtube (separate Ubuntu Studio account)
  • reddit

Podcasts

  • Bad Voltage?

News Sites

Sharing Passwords Between Team Members

In order to keep passwords secure, the best way to share them between team members is to use encryption. There are easy ways, like using protonmail. One can set up gpg encryption manually using an email client that supports it - like evolution.

Here is described how to encrypt a file using gpg so that only the recipient may open it. The file may be sent by email, or any other means. Only the recipient will be able to decrypt it.

Make sure the recipient has a published gpg key at launchpad

The file needs to be encrypted so only the recipient can decrypt it. This means the recipient needs to have a published gpg key. So, the recipient needs to go through this part, which describes how to create a gpg key and publish it.

Import the published gpg key

In order for you to encrypt a file using the recipients public key, you will need to import it first. First, to see which keys you already have locally: 

gpg --list-keys

The result may look something like this for each key you have imported: 

pub   2048R/D96A398A 2012-11-14
uid                  Kaj Ailomaa <zequence@mousike.me>
uid                  [jpeg image of size 3737]
sub   2048R/8EEEA58B 2012-11-14

The command to import a new key from the Ubuntu key server, is: 

gpg --keyserver keyserver.ubuntu.com --recv <publickeyID>

Obviously, you will need to replace <publickeyID> with the actual "ID". You can find one listed on the team members frontpage at launchpad, under "OpenPGP keys". It consists of eight characters.

Once you imported the key, make sure you got it by again doing: 

gpg --list-keys

Encrypt the File

When encrypting the file, you will be using the recipients email address. You can find the correct email address when listing keys, so do that again, if you don't see the list of keys: 

gpg --list-keys

In the case when the result looks like this: 

pub   2048R/D96A398A 2012-11-14
uid                  Kaj Ailomaa <zequence@mousike.me>
uid                  [jpeg image of size 3737]
sub   2048R/8EEEA58B 2012-11-14

The email adress in this case is zequence@mousike.me. So, let's use that in this example. To encrypt the file, do (replace <filename> with the path to the text file you want to encrypt): 

gpg --encrypt --recipient zequence@mousike.me <filename>

You will get a warning that there is no way to determine if the key actually belongs to the right person. This is because you have not signed the key. Debian and Ubuntu developers do not sign each others keys, unless meeting in person and exchanging keys physically. No need to sign the key, just ignore the warning.

The produced result will be a file name ending with ".gpg". That is the file you send to the recipient, and you can do this by email. No one but the recipient will be able to decrypt the file.

Decrypting the file

Once the recipient gets the file, it can be decrypted with the below command (replace <filename.gpg> with the path to the actual file): 

gpg --decrypt <filename.gpg>

Old PR page archived

UbuntuStudio/PublicRelationsDocumentationArchive

CategoryUbuntuStudioPublicRelations

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