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.

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

### 2018

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

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:

  - Ensure the `meta date=` directive is set to today's date in RFC 2822 format
    (e.g. `date --rfc-2822`).
  - Move report to `news/report_YEAR_MO.mdwn`.
  - Commit.
  - Build the website locally and check that it builds fine and the
    report renders well (e.g. no broken links that worked earlier only
    because the report was under `blueprints/`).
  - 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 (and if you have time+energy, the
    full text after adjusting its formatting for email):

          To: tails-project@boum.org
          Cc: tor-project@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 --rfc-2822` eg. Thu, 08 Feb 2018 07:21:15 +0000"]]
    \[[!pagetemplate template="news.tmpl"]]

    \[[!toc]]

    Releases
    ========

    * \[[Tails VERSION was released on MONTH DAY|news/version_VERSION]] ([major|bugfix|emergency] 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, foundation team, and RMs 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 -- "doc**.*m*" "about**.*m*" "support**.*m*" "install**.*m*" "upgrade**.*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://lists.autistici.org/list/tails-XXX.html>

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

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

    1.

    1.

    1.

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

    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://lists.autistici.org/list/tails-XXX.html>.

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

    XXX: Copy content from press/media_appearances_2018.mdwn
         This page is continuously updated by tails-press@boum.org, so if
         it's empty there might be nothing special to report.

    Translations
    ============

    XXX: Add the output of (adjust month!):

        sudo apt-get install intltool
        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.

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

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