Skip to content

Commit

Permalink
Merge pull request #312 from autocrypt/press-practise
Browse files Browse the repository at this point in the history
Press-team doc
  • Loading branch information
hpk42 committed Jan 4, 2018
2 parents 9d4e5f3 + 5d8e0c6 commit 046429c
Show file tree
Hide file tree
Showing 3 changed files with 71 additions and 1 deletion.
4 changes: 3 additions & 1 deletion doc/contact.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,9 @@ Channels

If you want to talk with us you may:

- join the `Autocrypt mailing list`_
- join the `Autocrypt mailing list`_ for community discussions

- for press-related inquiries contact the :doc:`Autocrypt press team <press-team>`

- collaborate through our `github Autocrypt repo`_

Expand Down
1 change: 1 addition & 0 deletions doc/contents.rst
Original file line number Diff line number Diff line change
Expand Up @@ -64,3 +64,4 @@ and contributors, MUA developers and privacy enthusiasts.
install-autocrypt-enigmail
news
bot
press-team
67 changes: 67 additions & 0 deletions doc/press-team.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
Autocrypt press team
====================

If you have any press-related inquiries please send e-mail to
the `press-team <mailto:press-team@autocrypt.org>`_, The press team
strives to answer within two workdays on press-related inquiries,
and often will get back faster (we have a knack for e-mail).

This document describes our practises how we handle and account for
press communications.

Current team members
--------------------

- compl4xx

- dkg

- Holger Krekel / hpk42

- r10s

- Vincent Breitmoser / valodim


Community interactions and responsibility
-----------------------------------------

If the press-team becomes aware of reporting, it will usually send
a link of press articles to the community mailing list. Anyone
can ask how media reporting came about and how and who, if anyone, was
involved from the press-team. Note that often journalists do not ask
back before they publish articles, or do not even contact a project
before reporting.

Press-team members remind each other when press-team internal
discussions touch community matters that are better discussed
through issues or the mailing list.


If you want to be on the team
-----------------------------

If you want to help, ask the existing press team. Anyone on the
existing press team may add you if you're an active member of the
project. Press team members don't need to formally publish their nicks
or names (though they can), but they are not considered a secret.
Providing legal names is not required. Nicks are sufficient.

Communication and reply practises
----------------------------------

When replying to an e-mail that was sent to the press-team, members
of the press team reply from their personal e-mail address, so everyone can
tell who is replying to and having the conversation. They will typically
Cc the press-team at least on the initial reply so that the others know the
communication is handled. If a conversation moved off to phone-calls,
interviews, or private e-mail, then press members typically send a brief
summary note to the other team members. Note that the press-team alias
e-mail address is only used for inbound contacts, and shouldn't be used to
send new messages that aren't a reply.

Changing practises
------------------

If you feel this press team document needs updates,
please send Pull Requests.

0 comments on commit 046429c

Please sign in to comment.