Revert spam.

wiki/src/blueprint/GitLab.mdwn

@@ -12,7 +12,7 @@ See also the [GitLab doc on issues](https://docs.gitlab.com/ce/user/project/issu
 One can make an issue
 [confidential](https://docs.gitlab.com/ce/user/project/issues/confidential_issues.html)
 when creating it; confidentiality can later be toggled on/off at any
-time. A aonfidential issue is visible only by whoever created it and
+time. A confidential issue is visible only by whoever created it and
 by project members with at least
 [Reporter](https://docs.gitlab.com/ce/user/permissions.html#project-members-permissions) access.
 
@@ -78,6 +78,47 @@ issue, which allows one to find duplicates later on if needed.
 And to ensure we can list issues that have really been resolved,
 add a "Duplicate" label.
 
+## Status
+
+Each open issue must have one of these labels:
+
+ - "1. To do" (previously: "Confirmed")
+ - "2. Doing" ("In progress" was too vague: it could mean anything
+   between "someone did the first 2% of the work 5 years ago" to "this is
+   what I'm focused on today")
+ - "3. To review" (previously "Ready for QA")
+
+… except issues that were just created and need to be triaged by Help
+Desk (previously: "New").
+
+This lends itself to issue boards with 4 columns: "1. To do", "2.
+Doing", "3. To review", and "Closed".
+
+Closing an issue means one of:
+
+ - The fix or feature the issue is about was merged and will be in
+   a future release (previously: "Fix committed" for the next release,
+   "Resolved" for 4.0).
+
+   To list these issues: closed issues whose milestone is a version
+   was not released yet.
+
+ - The fix or feature the issue is about is already available to
+   our users (previously: "Resolved").
+
+   To list these issues: closed issues whose milestone is a version
+   that's been released already.
+
+ - We've rejected it or marked it as a duplicate (previously:
+   "Rejected" and "Duplicate")
+
+   To list these issues: closed issues with respectively the "Rejected"
+   or "Duplicate" label.
+
+Most closed issues will still have the "3. To review" label.
+That should not cause any problem in practice. Worst case this can be
+fixed automatically, either via a webhook or a scheduled batch job.
+
 ## Other issues metadata
 
 - Target version → Milestone
@@ -90,20 +131,6 @@ add a "Duplicate" label.
   - One can set multiple labels so we could perhaps merge "Category"
     and "Affected Tool". For example, a ticket about Thunderbird
     persistence could have the two "C: email" and "C: persistence" labels.
-- Status: use a set of labels, each with a numerical prefix, because
-  it's an ordered flow:
-   - "0. Needs triage" (ideally, have it set automatically on newly
-     created issues; probably requires a webhook; otherwise, can be
-     done in batch regularly on all issues that have no status label
-     set)
-   - "1. Backlog" ("Confirmed")
-   - "2. Working on it" (clearer than the too vague "In progress")
-   - "3. To review" (previously "Ready for QA")
-   - "4. To release" (i.e. closed issue but code not released yet,
-     to replace "Fix committed" which is too often misunderstood)
-- Status = Resolved → closed with neither "Rejected" nor "Duplicate" label
-- Status = Duplicate → closed with "Duplicate" laben
-- Status = Rejected → closed with "Rejected" label
 - Log time → Time tracking
 - Due date → Due date
 - Starter → dedicated label
@@ -154,6 +181,11 @@ For example:
  - I can click "Add todo" on an issue and it will appear on my list
    of Todos (regardless of whether I'm the assignee or not).
 
+## Core team (self-)management
+
+XXX: how to replace e.g.
+<https://redmine.tails.boum.org/code/projects/tails/issues?query_id=307>?
+
 ## Custom queries
 
 We use Redmine custom queries to have easy access to named searches

wiki/src/blueprint/UEFI_Secure_boot.mdwn

@@ -11,7 +11,13 @@ enabled, without the user having to do _anything_ special about it.
 Means: use the shim signed by Microsoft + GRUB2.
 
 We don't support booting on a custom built kernel, so that should be
-relatively easy.
+relatively easy. Except:
+
+* The kernel won't allow loading an unsigned `aufs` module so we need
+  to migrate to `overlayfs` ([[!tails_ticket 8415]]).
+* `overlayfs` does not allow stacking enough layers for our current
+  upgrade system, so we need to [[!tails_ticket 15281 desc="stack one
+  single SquashFS diff when upgrading"]].
 
 Resources
 =========

wiki/src/blueprint/mobile_messaging.mdwn

@@ -7,6 +7,33 @@ Corresponding ticket: [[!tails_ticket 14567]]
   currently being updated, the old version is still available
   [here](https://www.eff.org/node/82654)).
 
+## Use cases
+
+### Signal for attorneys
+
+People we met at the IFF 2019 started experimenting with using Signal as
+point of contact for attorneys and their clients or whistle-blowing
+sources.
+
+They have a script that makes it possible to validate a land-line phone
+at the attorney's office to create a Signal account attached to it. This
+Signal account can then be used from Signal on a desktop computer, or
+even better, on Tails.
+
+This setup has several advantages:
+
+- Giving your office telephone to a client doesn't look as dodgy as
+  sharing your personal mobile phone number.
+- Attorneys are obliged to have a land-line phone as their official
+  point of contact.
+- Attorneys can keep their work and personal contacts separate.
+- Attorneys can attend their work Signal even when outside of office and
+  keep secure communications with their clients even when traveling.
+
+An important limitation for this to work is that you can't change the
+name of contacts that were added, using a phone number, to Signal
+desktop. There is a feature request for this upstream.
+
 ## General requirements
 
 **MUST**

wiki/src/blueprint/monthly_report.mdwn

@@ -21,12 +21,12 @@ beginning of May.
   - February 2019: intrigeri
   - March 2019: sajolida
   - April 2019: TheNerdyAnarchist & emmapeel
-  - May 2019:
+  - May 2019: u
   - June 2019: 
-  - July 2019: u
+  - July 2019:
   - August 2019: intrigeri
   - September 2019:
-  - October 2019:
+  - October 2019: u
   - November 2019:
   - December 2019:
 
@@ -194,7 +194,6 @@ Template
 
     * 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]]
 

wiki/src/blueprint/monthly_report/report_2019_04.mdwn

@@ -28,6 +28,28 @@ XXX: If you feel like it and developers, foundation team, and RMs don't do it th
      Release section (for example, the changes being worked on for
      the next version).
 
+- The [[Foundations
+  Team|contribute/working_together/roles/foundations_team]] met for
+  a sprint focused on porting Tails to Debian 10 (Buster):
+  [report](https://lists.autistici.org/message/20190408.075929.1c2952c0.en.html),
+  [next
+  steps](https://lists.autistici.org/message/20190429.091241.82e34497.en.html).
+- We finalized our criteria for including dictionaries, fonts and language packs,
+  which will be reflected in Tails 3.14.
+- We prototyped a USB image with Secure Boot support and GRUB, in order
+  to better understand what implementation difficulties we should expect.
+- We
+  [submitted](https://ikiwiki.info/todo/_Add_ikiwiki_PO-Plugin_to_ignore_languages/)
+  to ikiwiki upstream a branch that makes it keep PO files up-to-date
+  for a set of languages that are not ready to be enabled and visible
+  on the live website yet. This will allow us to merge into our main
+  Git repository changes made via our upcoming Weblate-based
+  translation platform, which supports languages whose
+  work-in-progress translation is not ready for prime-time yet.
+- We
+  [uploaded](https://tracker.debian.org/news/1038188/accepted-gnome-shell-3302-6-source-into-unstable/)
+  to Debian a few fixes for regressions in the GNOME on-screen keyboard.
+
 Documentation and website
 =========================
 
@@ -57,6 +79,11 @@ XXX: Ask tails-bugs@boum.org to list hot topics for the last month.
 Infrastructure
 ==============
 
+- The Foundations Team started experimenting with GitLab for
+  [merge requests](https://salsa.debian.org/tails-team/tails/merge_requests/?scope=all&utf8=%E2%9C%93&state=merged).
+- We started looking into how GitLab could work for our issues
+  tracking and [[drafted a rough plan|blueprint/GitLab]].
+
 Funding
 =======
 
@@ -66,20 +93,50 @@ XXX: The fundraising team should look at the fundraising Git.
 
 XXX: The fundraising and accounting teams should look at the archives of <tails-fundraising@boum.org> and <tails-accounting@boum.org>.
 
+- We started working on a proposal for [Mozilla Open Source Support
+  Awards](https://www.mozilla.org/en-US/moss/).
+
 Outreach
 ========
 
 Past events
 -----------
 
+- sajolida, moire, and emmapeel were at the [Internet Freedom
+  Festival](https://internetfreedomfestival.org/) on April 1&ndash;5 in
+  Valencia, Spain.
+
+  sajolida presented there a workshop on [Creating
+  usable tools from day one with paper
+  prototyping](https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/custom/975).
+
+- [carlosm2](https://twitter.com/dospesosinc) held 2 workshops about Tails in Mexico:
+
+  - On [April 13](https://twitter.com/dospesosinc/status/1115675448753573888) at the Colima Hacklab
+  - On [April 25](https://flisol.acatlan.unam.mx/) at UNAM, Ciudad de Mexico
+
+- There was a [Tails workshop on April 27 in Vienna](https://abcfestvienna.noblogs.org/post/2019/04/11/tails-workshop-saturday-4-pm/) as part of the Anarchist Black Cross festival
+
 Upcoming events
 ---------------
 
+- Jesús Marín García will present 2 workshops about Tails in May in the
+  Comunidad Valenciana, Spain:
+
+  - On [May 4](https://hackandbeers.es/events/hack-beers-castellon-vol-2/) at Hack and Beers in Castellón de la Plana
+  - On [May 11](https://vlctechfest.org/) at VLCTechFest in Valencia
+
 On-going discussions
 ====================
 
 XXX: Link to the thread on <https://lists.autistici.org/list/tails-XXX.html>.
 
+- We [studied and narrowed down our
+  options](https://lists.autistici.org/message/20190429.094536.22d3598f.en.html)
+  regarding the future of Electrum in Tails. It seems there will be
+  a way forward, although it's unclear at this point how much effort
+  it will require from us.
+
 Press and testimonials
 ======================
 
@@ -102,7 +159,6 @@ 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 a Tails USB image or ISO from our website.
-* WHISPERBACK bug reports were received through WhisperBack.
 
 [[How do we know this?|support/faq#boot_statistics]]
 

wiki/src/blueprint/monthly_report/report_2019_05.mdwn

@@ -72,6 +72,12 @@ Outreach
 Past events
 -----------
 
+- Jesús Marín García presented 2 workshops about Tails in May in the
+  Comunidad Valenciana, Spain:
+
+  - On [May 4](https://hackandbeers.es/events/hack-beers-castellon-vol-2/) at Hack and Beers in Castellón de la Plana
+  - On [May 11](https://vlctechfest.org/) at VLCTechFest in Valencia
+
 Upcoming events
 ---------------
 
@@ -102,7 +108,6 @@ 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 a Tails USB image or ISO from our website.
-* WHISPERBACK bug reports were received through WhisperBack.
 
 [[How do we know this?|support/faq#boot_statistics]]
 

wiki/src/blueprint/monthly_report/report_2019_06.mdwn

@@ -102,7 +102,6 @@ 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 a Tails USB image or ISO from our website.
-* WHISPERBACK bug reports were received through WhisperBack.
 
 [[How do we know this?|support/faq#boot_statistics]]
 

wiki/src/blueprint/veracrypt/build-gnome-shell.mdwn

@@ -20,6 +20,7 @@
 * clone upstream git 
 
       git clone https://gitlab.gnome.org/GNOME/gnome-shell.git gnome-shell-git
+      git submodule update --init
 
 * disable upstream VCS tag checking