Commit d1c40b38 authored by intrigeri's avatar intrigeri
Browse files

Improve monthly report publication doc.

 * Add missing steps.
 * Avoid duplicating info.
 * Add the option to send the full text of the report instead of a mere link:
   I've been told by several people that they stopped reading our report
   since we've stopped doing so (email is asynchronous and can be read offline;
   a HTTP link needs Internet connectivity and adds one more step that some
   people won't go through).
parent 11628b70
......@@ -43,16 +43,21 @@ Publishing
- If you have the commit bit on our main repo, you can do the
publication:
- Set the `meta date=` directive to today's date.
- Move report to `news/report_YEAR_MO.mdwn`.
- Commit and push.
- Tweet about the report:
- "In MONTH we worked on [...] and more: https://tails.boum.org/news/report_YEAR_MO."
- If you don't have access to our Twitter account send you text
for the tweet along with your merge request for the report.
- Send link to tor-reports@lists.torproject.org and tails-project@boum.org
- `To: tails-project@boum.org`
- `Cc: tor-reports@lists.torproject.org`
- `Subject: Tails report for XXXXXXXX YYYY`
- `Reply-to: tails-project@boum.org`
- Email the link to the report (and if you have time+energy, the
full text after adjusting its formatting for email):
To: tails-project@boum.org
Cc: tor-reports@lists.torproject.org
Subject: Tails report for XXXXXXXX YYYY
Reply-to: tails-project@boum.org
- Make sure that we already have a volunteer for next month, or
otherwise raise the issue on tails-project@boum.org and update the
[[list of volunteers|monthly_report#coordinators]].
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment