Commit 4bef95f4 authored by intrigeri's avatar intrigeri
Browse files

Clarify who does what for monthly reports.

See discussion on tails-project@, that clarified that the editor/coordinator
does not *have to* do all this work themselves (and de facto it's not been
consistently done since we resumed these reports).
parent 1633bc93
......@@ -97,20 +97,25 @@ Template
Code
====
XXX: List important code work that is not covered already by the Release
section (for example, the changes being worked on for the next version).
XXX: If you feel like it and developers don't do it themselves,
list important code work that is not covered already by the
Release section (for example, the changes being worked on for
the next version).
Documentation and website
=========================
XXX: Explore the Git history:
XXX: If you feel like it and technical writers don't do it
themselves, explore the Git history:
git log --patch --since='1 October' --until='1 November' origin/master -- "*.*m*"
User experience
===============
XXX: Check the archives of tails-ux: https://mailman.boum.org/pipermail/tails-ux/
XXX: If you feel like it and the UX team does not do it
themselves, check the archives of tails-ux:
<https://mailman.boum.org/pipermail/tails-ux/>
Infrastructure
==============
......@@ -173,4 +178,4 @@ Template
[[How do we know this?|support/faq#boot_statistics]]
XXX: Ask tails@boum.org for these numbers.
XXX: Ask <tails@boum.org> for these numbers.
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