Clarify publication process

wiki/src/blueprint/monthly_report.mdwn

@@ -38,19 +38,26 @@ Checklist
 Publishing
 ==========
 
-- Move report to `news/report_YEAR_MO.mdwn`.
-- 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`
-- 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]].
+- If you don't have the commit bit on our main repo, notify
+  tails-project@boum.org when you think that the report is ready for
+  publication.
+
+- If you have the commit bit on our main repo, you can do the
+  publication:
+
+  - Move report to `news/report_YEAR_MO.mdwn`.
+  - 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`
+  - 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]].
 
 Template
 ========