monthly_report.mdwn

[[!meta title="Monthly reports"]]

[[!map pages="blueprint/monthly_report/**" show="title"]]

This page could be a good place to gather HOWTO, tips, template, etc.
for the monthly reports.

Checklist
=========

- Check [[reports written for sponsors|contribute/reports]]
- Check the archives of:
  - <https://mailman.boum.org/pipermail/tails-dev/>
  - <https://mailman.boum.org/pipermail/tails-ux/>
  - <https://mailman.boum.org/pipermail/tails-project/>
- Explore the Git history:
  - `git log --patch --since="January 1" --until="February 1"`
  - XXX: Find a command to output the diff instead of the log here.
- Redmine view of closed issues:
  - <https://labs.riseup.net/code/projects/tails/issues?query_id=212>

Publishing
==========

XXX: Move report to news/report_YEAR_MO.mdwn
XXX: Tweet about the report: "Read about the activity of @Tails_live in MONTH YEAR: https://tails.boum.org/news/report_YEAR_MO."
XXX: 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

Template
========

<pre>
\[\[!meta title="Tails report for MONTH, YEAR"\]\]

\[\[!toc\]\]

Releases
========

* [[Tails VERSION was released on MONTH DAY|news/version_VERSION]] ([major|minor] release).

* Tails VERSION+1 is [[scheduled for MONTH DAY|contribute/calendar]].

The following changes were introduced in Tails VERSION:

XXX: Copy the "Changes" section of the release notes, and compact a bit:
       - Remove lines about software upgrade (that's not Tails itself).
       - Remove screenshots.
       - Remove "New features" and "Upgrades and changes" headlines.
       - Remove line about Changelog.

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).

Documentation and website
=========================

User experience
===============

Infrastructure
==============

XXX: Count the number of tests in /features at the beginning of next month

         git checkout `git rev-list -n 1 --before="June 1" origin/devel`
         git grep --extended-regexp '^\s*Scenario:' -- features/*.feature | wc -l

XXX: Report only if more scenarios have been written and add the diff from the previous month, for example:

       - Our test suite covers SCENARIOS scenarios, DIFF more that in May.

* XXX ISO images were automatically built and tested by our continuous integration infrastructure. XXX=ask tails-sysadmins@boum.org

Funding
=======

XXX: The fundraising team should look at the fundraising Git.

       git log --patch --since='1 December' --until='1 January' origin/master

XXX: The fundraising and accounting teams should look at the archives of <tails-fundraising@boum.org> and <tails-accounting@boum.org>.

Outreach
========

Past events
-----------

Upcoming events
---------------

On-going discussions
====================

XXX: Link to the thread on <https://mailman.boum.org/pipermail/tails-XXX/>.

Press and testimonials
======================

XXX: Copy content from press/media_appearances_2016.mdwn

Translation
===========

XXX: Add the output of `contribute/l10n_tricks/language_statistics.sh`

Metrics
=======

* Tails has been started more than BOOTS/MONTH times this month. This makes BOOTS/DAY boots a day on average.
* SIGS downloads of the OpenPGP signature of Tails ISO from our website.
* WHISPERBACK bug reports were received through WhisperBack.

XXX: Ask tails@boum.org for these numbers.