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.

[[!toc]]

<a id="coordinators"></a>

Coordinators for the next reports
=================================

The month in the list corresponds to the month to be reported about. For
example, the report about April in the list will be written at the
beginning of May.

  - January 2017: u
  - February 2017:emmapeel
  - March 2017: intrigeri
  - April 2017: spriver
  - May 2017: u
  - June 2017: intrigeri
  - July 2017: sajolida
  - August 2017: spriver
  - September 2017: emmapeel
  - October 2017:
  - November 2017: 
  - December 2017: muri
  - January 2018: sajolida
  - February 2018: u
  - March 2018: intrigeri
  - April 2018:
  - May 2018:
  - June 2018:
  - July 2018:
  - August 2018:
  - September 2018:
  - October 2018:
  - November 2018:
  - December 2018:

Checklist
=========

If you feel like it:

- Check [[reports written for sponsors|contribute/reports]]
- Redmine view of closed issues:
  - <https://labs.riseup.net/code/projects/tails/issues?query_id=212>

Publishing
==========

- 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:

  - 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 your text
         for the tweet along with your merge request for the report.
  - Email the link to the report:

          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
========

    \[[!meta title="Tails report for MONTH, YEAR"]]
    \[[!meta date="DATE (eg. Tue Aug 8 12:34:56 2018)"]]

    \[[!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: 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: 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: 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/>

    Hot topics on our help desk
    ===========================

    XXX: Ask tails-bugs@boum.org to list hot topics for the last month.

    1.

    1.

    1.

    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.

    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
         This page is continuously updated by tails-press@boum.org, so if
         it's empty there might be nothing special to report.

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

    XXX: Add the output of `contribute/l10n_tricks/language_statistics.sh`
    XXX: Add the output of (adjust month!):

        git checkout $(git rev-list -n 1 --before="September 1" origin/master) && \
        git submodule update --init && \
        ./wiki/src/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.

    \[[How do we know this?|support/faq#boot_statistics]]

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