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

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 2018: sajolida
  • February 2018: u
  • March 2018: intrigeri
  • April 2018: emmapeel
  • May 2018: spriver
  • June 2018: sajolida
  • July 2018:
  • August 2018: intrigeri
  • September 2018:
  • October 2018: u
  • November 2018: sajolida
  • December 2018: spriver


  • 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: sajolida
  • November 2017:muri
  • December 2017: muri


If you feel like it:


  • If you don't have the commit bit on our main repo, notify 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 in RFC 2822 format (e.g. date --rfc-2822).
    • Move report to news/report_YEAR_MO.mdwn.
    • Commit and push.
    • Tweet about the report:
      • "In MONTH we worked on [...] and more:"
      • 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:

        Subject: Tails report for XXXXXXXX YYYY
    • Make sure that we already have a volunteer for next month, or otherwise raise the issue on and update the list of volunteers.


[[!meta  title="Tails report for MONTH, YEAR"]]
[[!meta  date="`date --rfc-2822` eg. Thu, 08 Feb 2018 07:21:15 +0000"]]

[[!toc ]]


* [[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.


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 -- "*.*m*"

User experience

XXX: If you feel like it and the UX team does not do it
     themselves, check the archives of tails-ux:

Hot topics on our help desk

XXX: Ask to list hot topics for the last month.






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


Past events

Upcoming events

On-going discussions

XXX: Link to the thread on <>.

Press and testimonials

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


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 && \


* 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 <> for these numbers.