Skip to content

Changes

Page history
Adapt monthly report description to the new deal. authored by anonym's avatar anonym 
From now on Core Worker are responsible to write and publish the
monthly reports.

Ref: tails/summit#27
Hide whitespace changes
Inline Side-by-side
monthly_report.md
View page @ 3f36a37e
......@@ -14,7 +14,7 @@ Next reports
============
The month in the list corresponds to the month to be reported about,
and the coordinator for that report. For
and the curator for that report. For
example, the report about April in the list will be written at the
beginning of May.
......@@ -37,8 +37,9 @@ Preparing the Monthly report
Every month an automatic email reminder is sent to <tails-dev@boum.org>.
The curator has to answer to that email and remember to other teams to add their bits and set a date "2 days before" close the report and start publishing process.
So to be a curator you need to be subscribed to the dev-mailing list. Please [do it](https://tails.boum.org/about/contact) :)
The curator is solely responsible for the report, but contributors are
encouraged to answer this email and stating their intent to help, and
how.
You have 2 ways to work on the report:
......@@ -52,8 +53,8 @@ You can find the new page of the report in a list at the top of this page and cr
Publishing
==========
- If you have the commit bit on our main repo, you can do the
publication:
- All curators have the commit bit, so they can push the report to
make it public:
- Ensure the `meta date=` directive is set to today's date in RFC 2822 format
(e.g. `date --rfc-2822`).
......@@ -86,7 +87,7 @@ Publishing
to send emails in HTML format, you can probably do so from the
webmail application of your email provider.
- Make sure that we already have a volunteer for next month, or
- Make sure that we already have a curator for next month, or
otherwise raise the issue on <tails-dev@boum.org> and update the
[list of volunteers](monthly_report#coordinators).
......