summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint
diff options
context:
space:
mode:
authorbertagaz <bertagaz@ptitcanardnoir.org>2017-10-24 14:27:29 +0200
committerbertagaz <bertagaz@ptitcanardnoir.org>2017-10-24 14:27:29 +0200
commit15eb5d7ad7627916f1de3683071a79bb4b45f640 (patch)
tree766be2f5706de4d3d10e77b1efbbade9f9ae95b4 /wiki/src/blueprint
parent283014a4879a53f8786c73617803d4eeb7f84d97 (diff)
parent6ead712ff789c9e7f783f6f817bbd6f3d41614fe (diff)
Merge remote-tracking branch 'origin/stable' into bugfix/10494-retry-curl-in-htpdate
Diffstat (limited to 'wiki/src/blueprint')
-rw-r--r--wiki/src/blueprint/ARM_platforms/Acer_Chromebook_R_13_CB5-312T.mdwn90
-rw-r--r--wiki/src/blueprint/DAVE_2.mdwn83
-rw-r--r--wiki/src/blueprint/DAVE_2/OpenPGP.screen38
-rw-r--r--wiki/src/blueprint/DAVE_2/OpenPGP_advanced_1.screen15
-rw-r--r--wiki/src/blueprint/DAVE_2/OpenPGP_advanced_2.screen18
-rw-r--r--wiki/src/blueprint/DAVE_2/OpenPGP_basic_1.screen24
-rw-r--r--wiki/src/blueprint/DAVE_2/OpenPGP_basic_2.screen23
-rw-r--r--wiki/src/blueprint/DAVE_2/OpenPGP_basic_3.screen24
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/1.pngbin0 -> 3316 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/2.pngbin0 -> 1625 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/3.pngbin0 -> 6914 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/4.pngbin0 -> 2358 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/allow.pngbin0 -> 2317 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/check.pngbin0 -> 1109 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/download.pngbin0 -> 2690 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/failed.pngbin0 -> 382 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/install.pngbin0 -> 1971 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/notification_in_tails.pngbin0 -> 6111 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/verifying_in_tails.pngbin0 -> 6339 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/assets/warning.pngbin0 -> 1451 bytes
-rw-r--r--wiki/src/blueprint/DAVE_2/moving_parts_1.screen66
-rw-r--r--wiki/src/blueprint/DAVE_2/moving_parts_2.screen53
-rw-r--r--wiki/src/blueprint/DAVE_2/moving_parts_3.screen86
-rw-r--r--wiki/src/blueprint/DAVE_2/moving_parts_4.screen76
-rw-r--r--wiki/src/blueprint/DAVE_2/moving_parts_5.screen49
-rw-r--r--wiki/src/blueprint/DAVE_2/moving_parts_6.screen47
-rw-r--r--wiki/src/blueprint/DAVE_2/no_JS.screen64
-rw-r--r--wiki/src/blueprint/DAVE_2/outdated_browser.screen58
-rw-r--r--wiki/src/blueprint/DAVE_2/supported_browser.screen79
-rw-r--r--wiki/src/blueprint/DAVE_2/unsupported_browser.screen67
-rw-r--r--wiki/src/blueprint/Debian_Stretch.mdwn27
-rw-r--r--wiki/src/blueprint/Debian_testing.mdwn122
-rw-r--r--wiki/src/blueprint/RT_for_help_desk.mdwn9
-rw-r--r--wiki/src/blueprint/TailsGreeter.mdwn2
-rw-r--r--wiki/src/blueprint/additional_software_packages.mdwn13
-rw-r--r--wiki/src/blueprint/automated_builds_and_tests/testing.mdwn6
-rw-r--r--wiki/src/blueprint/better_metrics.mdwn84
-rw-r--r--wiki/src/blueprint/better_task_manager.mdwn2
-rw-r--r--wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn5
-rw-r--r--wiki/src/blueprint/l10n_Italian.mdwn6
-rw-r--r--wiki/src/blueprint/lizard_failover.mdwn14
-rw-r--r--wiki/src/blueprint/monthly_meeting.mdwn6
-rw-r--r--wiki/src/blueprint/monthly_report.mdwn54
-rw-r--r--wiki/src/blueprint/monthly_report/report_2017_09.mdwn15
-rw-r--r--wiki/src/blueprint/monthly_report/report_2017_10.mdwn11
-rw-r--r--wiki/src/blueprint/monthly_report/report_2017_11.mdwn11
-rw-r--r--wiki/src/blueprint/monthly_report/report_2017_12.mdwn11
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_01.mdwn (renamed from wiki/src/blueprint/monthly_report/report_2017_07.mdwn)55
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_02.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_03.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_04.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_05.mdwn (renamed from wiki/src/blueprint/monthly_report/report_2017_08.mdwn)36
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_06.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_07.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_08.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_09.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_10.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_11.mdwn117
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_12.mdwn117
-rw-r--r--wiki/src/blueprint/network_connection.mdwn5
-rw-r--r--wiki/src/blueprint/personas.mdwn393
-rw-r--r--wiki/src/blueprint/randomness_seeding.mdwn119
-rw-r--r--wiki/src/blueprint/remember_installed_packages.mdwn5
-rw-r--r--wiki/src/blueprint/replace_Pidgin.mdwn14
-rw-r--r--wiki/src/blueprint/survey_platform.mdwn91
65 files changed, 3047 insertions, 199 deletions
diff --git a/wiki/src/blueprint/ARM_platforms/Acer_Chromebook_R_13_CB5-312T.mdwn b/wiki/src/blueprint/ARM_platforms/Acer_Chromebook_R_13_CB5-312T.mdwn
index cfe8b30..41f6501 100644
--- a/wiki/src/blueprint/ARM_platforms/Acer_Chromebook_R_13_CB5-312T.mdwn
+++ b/wiki/src/blueprint/ARM_platforms/Acer_Chromebook_R_13_CB5-312T.mdwn
@@ -20,7 +20,7 @@ with a CB5-312T K2L7.
# Current status
-**Update**: see "Kernel approach 4: Arch Linux' ChromeOS-based kernel" for the most
+**Update**: see [[Kernel approach 4: Arch Linux' ChromeOS-based kernel|Acer_Chromebook_R_13_CB5-312T#arch-chromeos-based-kernel]] for the most
promising status update so far.
Both with the Chrome OS kernel and the Debian kernel approaches I end
@@ -66,39 +66,44 @@ See "Kernel approach 5: custom Debian kernel" below for a try at it.
Set some variables:
- DEV=/dev/sdb
MNT=/mnt/debian
- DATA_PART_SIZE=15292383
sudo mkdir -p ${MNT}
+ DEBIAN_CODENAME=stretch
-If using a USB drive:
+If using a 8 GiB USB drive:
+ DEV=$(readlink -f /dev/disk/by-id/usb-XXX)
+ KERNEL_PART=${DEV}1
ROOT_PART=${DEV}2
+ DATA_PART_SIZE=15292383
-Else, if using a micro-SD card:
+Else, if using a 64 GiB micro-SD card:
+ DEV=$(readlink -f /dev/disk/by-id/mmc-XXX)
+ KERNEL_PART=${DEV}p1
ROOT_PART=${DEV}p2
+ DATA_PART_SIZE=XXX
Partitioning the device:
sudo parted --script ${DEV} mklabel gpt
sudo cgpt create ${DEV}
-Below is for a 8 GiB device, adjust if needed.
-
XXX: the kernel partition is (still) too small for a Stretch kernel +
the gzip-compressed initrd generated from a running Debian desktop
system. Compressing it with xz (as instructed below) fixes that, but it
would be nice to be a bit more generous during the partitioning stage :)
- sudo cgpt add -t kernel -l kernel -b 34 -s 65536 ${DEV}
- sudo cgpt add -t data -l / -b 65570 -s ${DATA_PART_SIZE} ${DEV}
+ sudo cgpt add -i 1 -S 1 -T 5 -P 12 -t kernel -l kernel -b 8192 -s 262144 ${DEV}
+ sudo cgpt add -t data -l / -b 270336 -s ${DATA_PART_SIZE} ${DEV}
sudo blockdev --rereadpt ${DEV}
sudo mkfs.ext4 ${ROOT_PART}
sudo mount ${ROOT_PART} ${MNT}
- sudo debootstrap --arch=arm64 --foreign stretch ${MNT} http://ftp.de.debian.org/debian
+ sudo debootstrap --arch=arm64 --foreign "${DEBIAN_CODENAME:?}" \
+ "${MNT:?}" \
+ http://ftp.de.debian.org/debian
-Unmount the filesystems
+Unmount the root filesystem:
sudo umount ${MNT}
@@ -115,7 +120,7 @@ Enable booting a self-signed kernel from USB/micro-SD:
enable_dev_usb_boot
-Set some variables:
+Set some variables (adjust as above if using a micro-SD card):
DEV=/dev/sda
ROOT_PART=${DEV}2
@@ -136,7 +141,8 @@ Complete the bootstrap:
chroot ${MNT} /debootstrap/debootstrap --second-stage
-Configure the system:
+Configure the system and install what you'll need to make Wi-Fi
+and hardware work once you reboot on Debian:
cat > ${MNT}/etc/fstab <<EOF
${ROOT_PART} / ext4 errors=remount-ro 0 1
@@ -144,8 +150,13 @@ Configure the system:
echo "chromian" > ${MNT}/etc/hostname
cp /etc/resolv.conf ${MNT}/etc/resolv.conf
chroot ${MNT} apt-get update
- chroot ${MNT} apt-get install -y cgpt vboot-utils \
- vboot-kernel-utils
+ chroot ${MNT} apt-get install -y \
+ alsa-utils \
+ cgpt \
+ network-manager \
+ vboot-utils \
+ vboot-kernel-utils \
+ wireless-tools
chroot ${MNT} passwd -d root
@@ -202,11 +213,6 @@ Umount the filesystems:
umount ${MNT}
-Mark the newly written kernel partition as good and set the
-priority:
-
- cgpt add -i 1 -S 1 -T 5 -P 12 ${DEV}
-
### Debugging
I (intrigeri) have also tried:
@@ -249,6 +255,8 @@ a Debian userspace needs.
## Kernel approach 2 - Debian's kernel
+XXX: retry with a more recent Debian kernel.
+
From inside ChromeOS:
chroot "${MNT:?}" apt install initramfs-tools
@@ -548,8 +556,14 @@ Whatever: if we're ready to build a kernel based on the ChromeOS one,
we'd better start from the Arch Linux kernel config + included firmware
(see below).
+<a id="arch-chromeos-based-kernel"></a>
+
## Kernel approach 4: Arch Linux' ChromeOS-based kernel
+The results below are about `ArchLinuxARM-2017.09-oak-rootfs.tar.gz`,
+that's available at the time of writing in
+<http://os.archlinuxarm.org/os/mediatek/>.
+
I've followed
<https://archlinuxarm.org/platforms/armv8/mediatek/acer-chromebook-r13>
to install Arch Linux on a USB stick, and it booted flawlessly.
@@ -574,7 +588,7 @@ the partitioning and debootstrap steps have been done already.
-exec gunzip '{}' \;
sudo dd bs=1M if="${MNT:?}/boot/vmlinux.kpart" of="${KERNEL_PART:?}"
sync
- sudo depmod --basedir "${MNT:?}" 3.18.0-6-ARCH
+ sudo depmod --basedir "${MNT:?}" 3.18.0-9-ARCH
sudo umount "${MNT:?}"
### Status
@@ -587,14 +601,37 @@ the partitioning and debootstrap steps have been done already.
* Wi-Fi works.
* Display backlight brightness can be adjusted with the GNOME Shell
UI (in the top-right menu).
- * The GNOME sound preferences show no sound device, and I see error
- messages in the Journal about `mtk-rt5650 sound`.
+ * Sound works after unmuting a bunch of channels with `alsamixer` as
+ documented on the *Wiki* tab of
+ <https://archlinuxarm.org/platforms/armv8/mediatek/acer-chromebook-r13>
* The GNOME UI doesn't notice when AC power is disconnected.
- * Accelerometer and automatic screen rotation: mostly works, not as
- clever as I hoped.
+ * Accelerometer and automatic screen rotation: kind of works, but not
+ in a smooth/reliable way enough to be useful.
+ * Keyboard is automatically disabled when the screen is flipped to
+ tablet mode.
* Touchscreen: basically works, but I didn't try to exercise it much.
It seems that some parts of the GNOME UI don't work with touch but
_only_ when the display is rotated (e.g. flipped to tablet mode).
+ Some tweaks are needed to make it work really well, e.g.
+ `MOZ_USE_XINPUT2=1` for touch scrolling in Firefox 55.0.3-1
+ and setting `browser.gesture.pinch.in` to `cmd_fullZoomReduce` +
+ `browser.gesture.pinch.out` to `cmd_fullZoomEnlarge` for pinch
+ to zoom.
+ * Video playback:
+ - GNOME Shell does not get any hardware acceleration (glamor, dri3,
+ EGL) so it's "falling back to sw". And then both with Wayland and
+ X.Org, full-screen video playback eats tons of CPU to the point it
+ is totally unusable with Totem and VLC, and pretty bad even with
+ mpv. That's probably due to the lack of a `mediatek_dri.so` DRI
+ module for Mesa or VA-API support (the latter because
+ [[!debpts gstreamer1.0-vaapi]] is not installable on sid today);
+ I'll retry when the latter is fixed, that might help.
+ - GNOME Flashback (Metacity): even though the window manager does
+ not use tons of CPU, the end-result is only perceptibly better
+ with mpv (and even there it's not perfect). Touchscreen support
+ is far behind the GNOME Shell experience (no gesture to interact
+ with the desktop, poorly integrated screen keyboard, no automatic
+ rotation of the display).
## Kernel approach 5: custom Debian kernel
@@ -1074,6 +1111,9 @@ Same result as with the Debian kernels, which tends to confirm there's
something wrong either in the vmlinuz/initrd format, or in the way we
embed them in the FIT image.
+XXX: when running `mkimage`, try dropping `-p 2048`, adding `-A
+arm64`, using `-f auto` (with `-A`, `-O`, `-T` and `-C`).
+
Another idea would be to have the Chromebook's bootloader
[load our own GRUB](https://wiki.linaro.org/LEG/Engineering/Kernel/GRUBonUBOOT),
that will itself be able to deal with whatever we give it (without
diff --git a/wiki/src/blueprint/DAVE_2.mdwn b/wiki/src/blueprint/DAVE_2.mdwn
new file mode 100644
index 0000000..ce0ca7a
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2.mdwn
@@ -0,0 +1,83 @@
+[[!meta title="DAVE 2"]]
+
+Parent ticket: [[!tails_ticket 12328 desc="DAVE 2: Migrate to Web Extensions and support Chrome"]]
+
+[[!toc]]
+
+Scope
+=====
+
+With the port to Web Extension, we are:
+
+- Moving the download outside of DAVE
+- Adding a Chrome extension
+
+Relevant threads:
+
+- [Initial discussion on tails-ux](https://mailman.boum.org/pipermail/tails-ux/2017-May/thread.html)
+- [Decision on moving the download outside of DAVE](https://mailman.boum.org/pipermail/tails-ux/2017-June/003394.html)
+
+Goals:
+
+- Prevent people from using unverified ISO images.
+ - Proposed solution: Split the download in a different step and adjust
+ the "Next" link to what the user is doing on the page to discourage
+ (but still make it possible) skipping the verification.
+- Encourage BitTorrent download when DAVE is not supported.
+ - Proposed solution: Explain better the benefits of BitTorrent and how
+ to use it.
+- Make it easier to do a direct download for power users who do OpenPGP.
+ - Proposed solution: Have a "Direct download" button and embed the
+ OpenPGP instructions on the same page.
+
+Variations
+==========
+
+- 2 download techniques:
+ - Direct download
+ - BitTorrent download
+
+- 3 verification techniques:
+ - Browser add-on (Firefox, Chrome, or Tor Browser)
+ - BitTorrent
+ - OpenPGP (either on top of instead of the two others)
+
+- 6 variations of the same screen depending on the browser:
+ - Supported browser but no DAVE
+ - Supported browser and DAVE already
+ - Supported browser but outdated DAVE
+ - Supported but outdated browser (eg. Firefox < 38)
+ - Unsupported browser (eg. Internet Explorer)
+ - Browser without JavaScript
+
+External resources
+==================
+
+- Market shares of browsers:
+ - [Kleiner Perkins: 2017 Internet trends](http://www.kpcb.com/internet-trends)
+- Browser detection code by Firefox (support.mozilla.org)
+
+Wireframes
+==========
+
+Made with [*WireframeSketcher*](http://wireframesketcher.com/) which is
+proprietary but has a Debian package that works on Tails :)
+
+### Screens
+
+- [[supported_browser.screen]]: Supported browser but no DAVE
+- [[unsupported_browser.screen]]: Unsupported browser (eg. Internet Explorer)
+- [[outdated_browser.screen]]: Supported but outdated browser (eg. Firefox < 38)
+- [[no_JS.screen]]: Browser without JavaScript
+- Moving parts (to be used to simulate interactivity during paper prototyping):
+ - [[moving_parts_1.screen]]
+ - [[moving_parts_2.screen]]
+- OpenPGP instructions (to be displayed on all screens when scrolling):
+ - [[OpenPGP_1.screen]]
+ - [[OpenPGP_2.screen]]
+ - [[OpenPGP_3.screen]]
+ - [[OpenPGP_4.screen]]
+
+### Assets
+
+[[!map pages="blueprint/DAVE_2/assets/*"]]
diff --git a/wiki/src/blueprint/DAVE_2/OpenPGP.screen b/wiki/src/blueprint/DAVE_2/OpenPGP.screen
new file mode 100644
index 0000000..01cf1d4
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/OpenPGP.screen
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="99" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Text" id="100" x="42" y="152" width="605" height="105" text="If you know OpenPGP, you can also use it to verify your download instead, or in addition to, verifying using Firefox or BitTorrent.&#xA;&#xA;1. Download the [Tails signing key] (last updated on 2017-08-30).&#xA;&#xA;2. Download the [Tails 3.1 OpenPGP signature] and save it to the same folder where you saved the ISO image." measuredWidth="605" measuredHeight="105">
+ <font/>
+ <items x="89" y="48" width="87" height="16" text="Tails signing key"/>
+ <items x="89" y="80" width="149" height="16" text="Tails 3.1 OpenPGP signature"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="101" x="40" y="292" text="Basic OpenPGP verification" measuredWidth="289" measuredHeight="40">
+ <font size="24px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="102" x="40" y="466" text="Authenticate the signing key through the OpenPGP Web of Trust" measuredWidth="688" measuredHeight="40">
+ <font size="24px"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="103" x="42" y="514" width="589" height="61" text="Authenticating our signing key through the OpenPGP Web of Trust is the only verification technique that can protect you in case our website is compromised. It is also the most complicated technique and might not be possible for everyone to perform because it relies on trust relationships between individuals." measuredWidth="589" measuredHeight="61">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="104" x="42" y="340" width="605" height="59" text="Verifying using OpenPGP but without authenticating our signing key through the OpenPGP Web of Trust is equivalent in terms of security to verifying using Firefox or BitTorrent because it relies on downloading a genuine signing key from our website." measuredWidth="605" measuredHeight="59">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="105" x="42" y="571" text="Read more about authenticating the signing key through the OpenPGP Web of Trust." measuredWidth="439" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="106" x="40" y="100" text="Verify using OpenPGP (optional)" measuredWidth="401" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="107" x="41" y="398" text="See instructions for basic OpenPGP verification." measuredWidth="252" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="108" x="12" y="7" width="800" height="32" text="This screen appears below the fold." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/OpenPGP_advanced_1.screen b/wiki/src/blueprint/DAVE_2/OpenPGP_advanced_1.screen
new file mode 100644
index 0000000..2cc8034
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/OpenPGP_advanced_1.screen
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="131" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Text" id="116" x="42" y="102" width="657" height="535" text="The verification techniques presented until now (Firefox extension, BitTorrent, or OpenPGP verification) all rely on some information being securely downloaded using HTTPS from our website:&#xA;&#xA;- The checksum for the Firefox extension&#xA;- The Torrent file for BitTorrent&#xA;- The Tails signing key for the OpenPGP verification&#xA;&#xA;But, while doing so, you could download malicious information if our website is compromised or if you are victim of a man-in-the-middle attack.&#xA;&#xA;The OpenPGP verification is the only technique that allows you to verify the ISO image even better by also authenticating the Tails signing key through the OpenPGP Web of Trust. Relying on the OpenPGP Web of Trust is the only way to completely protect you from malicious downloads.&#xA;&#xA;If you are verifying an ISO image from inside Tails already, for example to do a manual upgrade, then the Tails signing key is already included in Tails. You can trust this signing key as much as you are trusting your Tails installation already because you are not downloading it.&#xA;&#xA;One of the inherent problems of standard HTTPS is that the trust we usually put in a website is defined by certificate authorities: a hierarchical and closed set of companies and governmental institutions approved by your web browser vendor. This model of trust has long been criticized and proved several times to be vulnerable to attacks as explained on our warning page." measuredWidth="657" measuredHeight="535">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="132" x="12" y="7" width="800" height="32" text="These instructions appears when the user clicks on &quot;Read more about authenticating...&quot;." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/OpenPGP_advanced_2.screen b/wiki/src/blueprint/DAVE_2/OpenPGP_advanced_2.screen
new file mode 100644
index 0000000..74f97a4
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/OpenPGP_advanced_2.screen
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="131" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Text" id="116" x="42" y="102" width="657" height="529" text="We believe that, instead, users should be given the final say when trusting a website, and that designation of trust should be done on the basis of human interactions.&#xA;&#xA;The OpenPGP Web of Trust is a decentralized trust model based on OpenPGP keys that can help solving this problem. Let's see this with an example:&#xA;&#xA;1. You are friend with Alice and really trust her way of managing OpenPGP keys. So you are trusting Alice's key.&#xA;&#xA;2. Furthermore, Alice met Bob, a Tails developer, in a conference and certified Bob's key. So Alice is trusting Bob's key.&#xA;&#xA;3. Bob is a Tails developer who directly owns the Tails signing key. So Bob fully trusts the Tails signing key.&#xA;&#xA;In this scenario, Alice found a path to trust the Tails signing key without the need to rely on certificate authorities.&#xA;&#xA;If you are on Debian, Ubuntu, or Linux Mint, you can install the debian-keyring package which contains the OpenPGP keys of all Debian developers. Some Debian developers have certified the Tails signing key and you can use these certifications to build a trust path. This technique is explained in detail in our instructions on [installing Tails from Debian, Ubuntu, or Linux Mint using the command line].&#xA;&#xA;Relying on the Web of Trust requires both caution and intelligent supervision by the users. The technical details are outside of the scope of this document.&#xA;&#xA;Since the Web of Trust is actually based on human relationships and real-life interactions, the best is to get in touch with people knowledgeable about OpenPGP and build trust relationships in order to find your own trust path to the Tails signing key.&#xA;&#xA;For example, you can start by contacting a local [Linux User Group], [an organization offering Tails training], or other Tails enthusiasts near you and exchange about their OpenPGP practices.&#xA;&#xA;After you built a trust path, you can certify the Tails signing key by signing it with your own key to get rid of some warnings during the verification process." measuredWidth="657" measuredHeight="529">
+ <font size="12px" bold="false"/>
+ <items x="0" y="256" width="652" height="32" text="installing Tails from Debian, Ubuntu, or Linux Mint using the command line"/>
+ <items x="251" y="416" width="89" height="16" text="Linux User Group"/>
+ <items x="346" y="416" width="194" height="16" text="an organization offering Tails training"/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="132" x="12" y="7" width="800" height="32" text="These instructions appears when the user clicks on &quot;Read more about authenticating...&quot;." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/OpenPGP_basic_1.screen b/wiki/src/blueprint/DAVE_2/OpenPGP_basic_1.screen
new file mode 100644
index 0000000..27c8d50
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/OpenPGP_basic_1.screen
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="99" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Text" id="70" x="44" y="79" width="657" height="266" text="This section provides simplified instructions:&#xA;&#xA;- [In Windows with Gpg4win]&#xA;- [In macOS with GPGTools]&#xA;- [In Tails]&#xA;- [Using the command line]&#xA;&#xA;This basic OpenPGP verification provides a level of verification equivalent to HTTPS, like the Firefox and Chrome extension or BitTorrent, unless you also authenticate the signing key through the OpenPGP Web of Trust.&#xA;&#xA;IN WINDOWS WITH GPG4WIN&#xA;&#xA;See the [Gpg4win documentation on verifying signatures].&#xA;&#xA;Verify the date of the signature to make sure that you downloaded the latest version.&#xA;&#xA;If the following warning appears:" measuredWidth="657" measuredHeight="266">
+ <font size="12px" bold="false"/>
+ <items x="20" y="16" width="137" height="16" text="In Windows with Gpg4win"/>
+ <items x="20" y="32" width="131" height="16" text="In macOS with GPGTools"/>
+ <items x="20" y="48" width="37" height="16" text="In Tails"/>
+ <items x="20" y="64" width="125" height="16" text="Using the command line"/>
+ <items x="41" y="176" width="249" height="16" text="Gpg4win documentation on verifying signatures"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="74" x="44" y="426" width="657" height="271" text="Then the ISO image is still correct according to the signing key that you downloaded. To remove this warning you need to authenticate the signing key through the OpenPGP Web of Trust.&#xA;&#xA;IN MACOS USING GPGTOOLS&#xA;&#xA; 1. Open Finder and navigate to the folder where you saved the ISO image and the signature.&#xA;&#xA; 2. Right-click on the ISO image and choose Services ▸ OpenPGP: Verify Signature of File." measuredWidth="657" measuredHeight="271">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="75" x="59" y="350" width="655" height="59" measuredWidth="655" measuredHeight="59" src="assets/1.png"/>
+ <widgets xsi:type="model:Note" id="101" x="12" y="7" width="800" height="32" text="These instructions appears when the user clicks on &quot;See instructions for basic OpenPGP verification...&quot;." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/OpenPGP_basic_2.screen b/wiki/src/blueprint/DAVE_2/OpenPGP_basic_2.screen
new file mode 100644
index 0000000..f172286
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/OpenPGP_basic_2.screen
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="125" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Text" id="118" x="43" y="529" width="657" height="111" text=" Verify the date of the signature to make sure that you downloaded the latest version.&#xA;&#xA;USING THE COMMAND LINE&#xA;&#xA; 1. Open a terminal and navigate to the folder where you saved the ISO image and the signature.&#xA;&#xA; 2. Execute:" measuredWidth="657" measuredHeight="111">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="119" x="87" y="418" width="447" height="82" measuredWidth="447" measuredHeight="82" src="assets/notification_in_tails.png"/>
+ <widgets xsi:type="model:Note" id="126" x="12" y="7" width="800" height="32" text="These instructions appears when the user clicks on &quot;See instructions for basic OpenPGP verification...&quot;." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="127" x="44" y="355" width="657" height="41" text=" 4. After the verification finishes, click on the notification counter in the bottom-right corner and on the notification with a &#xA; transparent background on the right of the notification area:" measuredWidth="657" measuredHeight="41">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="128" x="86" y="209" width="315" height="124" measuredWidth="315" measuredHeight="124" src="assets/verifying_in_tails.png"/>
+ <widgets xsi:type="model:Text" id="129" x="44" y="79" width="660" height="120" text="IN TAILS&#xA;&#xA; 1. Open the file browser and navigate to the folder where you saved the ISO image and the signature.&#xA;&#xA; 2. Right-click on the signature and choose Open With Verify Signature.&#xA;&#xA; 3. The verification of the ISO image starts automatically:" measuredWidth="660" measuredHeight="120">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/OpenPGP_basic_3.screen b/wiki/src/blueprint/DAVE_2/OpenPGP_basic_3.screen
new file mode 100644
index 0000000..9b96019
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/OpenPGP_basic_3.screen
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="128" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Text" id="108" x="58" y="138" width="657" height="20" text=" The output of this command should be the following:" measuredWidth="657" measuredHeight="20">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="109" x="70" y="86" width="641" height="28" measuredWidth="641" measuredHeight="28" src="assets/2.png"/>
+ <widgets xsi:type="model:Image" id="111" x="71" y="176" width="640" height="105" measuredWidth="640" measuredHeight="105" src="assets/3.png"/>
+ <widgets xsi:type="model:Text" id="125" x="60" y="304" width="657" height="54" text=" Verify the date of the signature to make sure that you downloaded the latest version.&#xA;&#xA; If the output also includes:" measuredWidth="657" measuredHeight="54">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="126" x="60" y="429" width="657" height="38" text=" Then the ISO image is still correct according to the signing key that you downloaded. To remove this warning you need to &#xA; authenticate the signing key through the OpenPGP Web of Trust." measuredWidth="657" measuredHeight="38">
+ <font size="12px" bold="false"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="127" x="71" y="370" width="644" height="37" measuredWidth="644" measuredHeight="37" src="assets/4.png"/>
+ <widgets xsi:type="model:Note" id="129" x="12" y="7" width="800" height="32" text="These instructions appears when the user clicks on &quot;See instructions for basic OpenPGP verification...&quot;." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/assets/1.png b/wiki/src/blueprint/DAVE_2/assets/1.png
new file mode 100644
index 0000000..46b0427
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/1.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/2.png b/wiki/src/blueprint/DAVE_2/assets/2.png
new file mode 100644
index 0000000..530fb2c
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/2.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/3.png b/wiki/src/blueprint/DAVE_2/assets/3.png
new file mode 100644
index 0000000..db0df6ec
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/3.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/4.png b/wiki/src/blueprint/DAVE_2/assets/4.png
new file mode 100644
index 0000000..240f083
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/4.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/allow.png b/wiki/src/blueprint/DAVE_2/assets/allow.png
new file mode 100644
index 0000000..d4f7436
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/allow.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/check.png b/wiki/src/blueprint/DAVE_2/assets/check.png
new file mode 100644
index 0000000..7583289
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/check.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/download.png b/wiki/src/blueprint/DAVE_2/assets/download.png
new file mode 100644
index 0000000..5be04cb
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/download.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/failed.png b/wiki/src/blueprint/DAVE_2/assets/failed.png
new file mode 100644
index 0000000..c1999e4
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/failed.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/install.png b/wiki/src/blueprint/DAVE_2/assets/install.png
new file mode 100644
index 0000000..cf3b4f1
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/install.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/notification_in_tails.png b/wiki/src/blueprint/DAVE_2/assets/notification_in_tails.png
new file mode 100644
index 0000000..562f8d4
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/notification_in_tails.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/verifying_in_tails.png b/wiki/src/blueprint/DAVE_2/assets/verifying_in_tails.png
new file mode 100644
index 0000000..8840dd6
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/verifying_in_tails.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/assets/warning.png b/wiki/src/blueprint/DAVE_2/assets/warning.png
new file mode 100644
index 0000000..bc57620
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/assets/warning.png
Binary files differ
diff --git a/wiki/src/blueprint/DAVE_2/moving_parts_1.screen b/wiki/src/blueprint/DAVE_2/moving_parts_1.screen
new file mode 100644
index 0000000..7255aaa
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/moving_parts_1.screen
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="96" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:WidgetGroup" id="89" x="134" y="69" measuredWidth="274" measuredHeight="180">
+ <widgets xsi:type="model:Window" id="85" width="273" height="180" measuredWidth="273" measuredHeight="180"/>
+ <widgets xsi:type="model:Text" id="87" x="11" y="27" width="263" height="144" text="BitTorrent is a peer-to-peer technology for file sharing that makes your download faster and easier to resume.&#xA;&#xA;You need to install a BitTorrent client on your computer, like [Transmission] (Windows, macOS, and Linux).&#xA;&#xA;BitTorrent doesn't work on Tails." measuredWidth="263" measuredHeight="144">
+ <font/>
+ <items x="77" y="80" width="70" height="16" text="Transmission"/>
+ </widgets>
+ </widgets>
+ <widgets xsi:type="model:Note" id="90" x="432" y="69" width="352" height="28" text="This is displayed when the user clicks on &quot;What is BitTorrent?&quot;." measuredWidth="352" measuredHeight="28" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="104" x="49" y="266" measuredWidth="360" measuredHeight="209">
+ <widgets xsi:type="model:Window" id="97" width="360" height="209" text="Enter name of file to save to..." measuredWidth="360" measuredHeight="209"/>
+ <widgets xsi:type="model:Tree" id="98" x="10" y="64" width="94" height="105" text="Desktop&#xA;Downloads&#xA;Music&#xA;Videos" measuredWidth="94" measuredHeight="105">
+ <items x="0" y="5" width="94" height="22" text="Desktop"/>
+ <items x="0" y="27" width="94" height="22" text="Downloads"/>
+ <items x="0" y="49" width="94" height="22" text="Music"/>
+ <items x="0" y="71" width="94" height="22" text="Videos"/>
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:TextField" id="99" x="57" y="29" width="293" text="tails-amd64-3.2.iso" measuredWidth="293" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="100" x="11" y="31" text="Name:" measuredWidth="40" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Panel" id="101" x="111" y="64" width="242" height="105" measuredWidth="242" measuredHeight="105"/>
+ <widgets xsi:type="model:Button" id="102" x="299" y="173" width="54" text="Save" measuredWidth="54" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="103" x="233" y="173" width="57" text="Cancel" measuredWidth="57" measuredHeight="26">
+ <font/>
+ </widgets>
+ </widgets>
+ <widgets xsi:type="model:Note" id="105" x="432" y="266" width="352" height="27" text="File chooser after clicking a download button or link." measuredWidth="352" measuredHeight="27" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:TextField" id="109" x="116" y="548" width="293" text="tails-amd64-3.2.iso.sig" measuredWidth="293" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="114" x="432" y="539" width="352" height="33" text="Default file name when downloading the OpenPGP signature." measuredWidth="352" measuredHeight="33" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="115" x="12" y="7" width="800" height="32" text="These are moving parts that are meant to be cut out on paper and used to simulate interaction during testing." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:TextField" id="116" x="116" y="598" width="293" text="tails-signing.key" measuredWidth="293" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="117" x="432" y="589" width="352" height="33" text="Default file name when downloading the signing key." measuredWidth="352" measuredHeight="33" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:TextField" id="118" x="116" y="498" width="293" text="tails-amd64-3.1.torrent" measuredWidth="293" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="119" x="432" y="489" width="352" height="33" text="Default file name when downloading the signing key." measuredWidth="352" measuredHeight="33" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/moving_parts_2.screen b/wiki/src/blueprint/DAVE_2/moving_parts_2.screen
new file mode 100644
index 0000000..79bf7a1
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/moving_parts_2.screen
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="98" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Label" id="99" x="141" y="82" text="Verification failed!" measuredWidth="106" measuredHeight="24">
+ <font bold="true"/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="100" x="429" y="73" width="355" height="61" text="This is displayed instead of &quot;Verify download...&quot; if the verification failed once." measuredWidth="355" measuredHeight="61" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="101" x="110" y="78" width="27" height="29" measuredWidth="27" measuredHeight="29" src="assets/failed.png"/>
+ <widgets xsi:type="model:Label" id="102" x="141" y="102" text="Please [try to download again...]" measuredWidth="166" measuredHeight="24">
+ <font/>
+ <items x="37" y="3" width="123" height="16" text="try to download again..."/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="103" x="141" y="379" text="Verification failed again!" measuredWidth="138" measuredHeight="24">
+ <font bold="true"/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="104" x="429" y="360" width="355" height="44" text="This is displayed instead of &quot;Verify download...&quot; if the verification failed more than once." measuredWidth="355" measuredHeight="44" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="105" x="110" y="375" width="27" height="29" measuredWidth="27" measuredHeight="29" src="assets/failed.png"/>
+ <widgets xsi:type="model:Text" id="106" x="141" y="402" width="314" height="34" text="Please try to download again from a&#xA;different place or a different computer…" measuredWidth="314" measuredHeight="34">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Window" id="170" x="43" y="166" width="375" height="164" measuredWidth="375" measuredHeight="164"/>
+ <widgets xsi:type="model:Link" id="110" x="318" y="82" text="Why?" measuredWidth="33" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="111" x="318" y="379" text="Why?" measuredWidth="33" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="156" x="62" y="192" text="Most likely, the verification failed because of an error or&#xA;interruption during the download.&#xA;&#xA;Less likely, the verification might have failed because of a&#xA;malicious download from our servers or due to an&#xA;network attack in your country or local network.&#xA;&#xA;Downloading again is usually enough to fix this problem." measuredWidth="299" measuredHeight="128">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="159" x="429" y="166" width="355" height="50" text="This is displayed when the user clicks on &quot;Why?&quot; from &quot;Verification failed!&quot;." measuredWidth="355" measuredHeight="50" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Window" id="172" x="43" y="463" width="375" height="164" measuredWidth="375" measuredHeight="164"/>
+ <widgets xsi:type="model:Text" id="166" x="63" y="497" text="The verification might have failed again because of:&#xA;&#xA;- A software problem in our verification extension&#xA;- A malicious download from our servers&#xA;- A network attack in your country or local network&#xA;&#xA;Trying from a different place or a different computer might solve&#xA;any of these issues." measuredWidth="336" measuredHeight="112">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="167" x="430" y="463" width="355" height="50" text="This is displayed when the user clicks on &quot;Why?&quot; from &quot;Verification failed again!&quot;." measuredWidth="355" measuredHeight="50" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="168" x="12" y="7" width="800" height="32" text="These are moving parts that are meant to be cut out on paper and used to simulate interaction during testing." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/moving_parts_3.screen b/wiki/src/blueprint/DAVE_2/moving_parts_3.screen
new file mode 100644
index 0000000..ed5dbb6
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/moving_parts_3.screen
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="98" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Note" id="151" x="12" y="7" width="800" height="32" text="These are moving parts that are meant to be cut out on paper and used to simulate interaction during testing." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="152" x="116" y="154" measuredWidth="219" measuredHeight="24">
+ <widgets xsi:type="model:Label" id="153" x="29" text="Install Firefox extension (no restart)" measuredWidth="190" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="154" width="25" height="21" measuredWidth="25" measuredHeight="21" src="assets/check.png"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="155" x="134" y="198" width="209" text="Verify download..." measuredWidth="209" measuredHeight="26" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="156" x="432" y="135" width="353" height="107" text="This is displayed instead of &quot;Install extension&quot;:&#xA;- After the extension is installed.&#xA;- If the extension is already installed and up-to-date.&#xA;- If the first verification failed and the user starts a new download." measuredWidth="353" measuredHeight="107" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="157" x="114" y="354" measuredWidth="229" measuredHeight="70">
+ <widgets xsi:type="model:WidgetGroup" id="158" measuredWidth="83" measuredHeight="24">
+ <widgets xsi:type="model:Label" id="159" x="29" text="Updated!" measuredWidth="54" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="160" width="25" height="21" measuredWidth="25" measuredHeight="21" src="assets/check.png"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="161" x="20" y="44" width="209" text="Verify download..." measuredWidth="209" measuredHeight="26" textAlignment="Left">
+ <font/>
+ </widgets>
+ </widgets>
+ <widgets xsi:type="model:Note" id="162" x="432" y="335" width="351" height="88" text="This is displayed instead of &quot;Install extension&quot; after the extension is updated." measuredWidth="351" measuredHeight="88" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="163" x="432" y="255" width="351" height="66" text="This is displayed instead of &quot;Install extension&quot; if the extension is already installed but outdated." measuredWidth="351" measuredHeight="66" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="164" x="134" y="258" measuredWidth="211" measuredHeight="50">
+ <widgets xsi:type="model:Button" id="165" y="24" text="Update Firefox extension (no restart)" measuredWidth="211" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="166" x="10" text="Your extension is an older version." measuredWidth="184" measuredHeight="24">
+ <font/>
+ </widgets>
+ </widgets>
+ <widgets xsi:type="model:Button" id="167" x="46" y="589" width="145" text="Next →" measuredWidth="145" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="168" x="432" y="569" width="352" height="61" text="This is displayed instead of &quot;Skip download&quot; after the verification is successful or the BitTorrent file or the OpenPGP signature is downloaded." measuredWidth="352" measuredHeight="61" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="169" x="143" y="523" text="Verification successful!" measuredWidth="126" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="170" x="114" y="523" width="25" height="21" measuredWidth="25" measuredHeight="21" src="assets/check.png"/>
+ <widgets xsi:type="model:Note" id="171" x="432" y="504" width="351" height="50" text="This is displayed instead of &quot;Verify download...&quot; if the verification is successful." measuredWidth="351" measuredHeight="50" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="172" x="143" y="460" text="Verifying tails-amd64-3.2.iso...." measuredWidth="172" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="173" x="432" y="441" width="351" height="50" text="This is displayed instead of &quot;Verify download...&quot; during the verification." measuredWidth="351" measuredHeight="50" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="176" x="38" y="80" measuredWidth="135" measuredHeight="28">
+ <widgets xsi:type="model:Link" id="177" x="38" y="2" text="Skip verification →" measuredWidth="97" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="182" width="31" height="28" measuredWidth="31" measuredHeight="28" src="assets/warning.png"/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="179" x="432" y="71" width="352" height="49" text="This is displayed instead of &quot;Skip download&quot; after the user starts a direct download." measuredWidth="352" measuredHeight="49" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="183" x="238" y="80" measuredWidth="135" measuredHeight="28">
+ <widgets xsi:type="model:Link" id="184" x="38" y="2" text="Skip verification →" measuredWidth="97" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="185" width="31" height="28" measuredWidth="31" measuredHeight="28" src="assets/warning.png"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="186" x="222" y="589" width="141" text="Next →" measuredWidth="141" measuredHeight="26">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/moving_parts_4.screen b/wiki/src/blueprint/DAVE_2/moving_parts_4.screen
new file mode 100644
index 0000000..652e761
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/moving_parts_4.screen
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="98" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Panel" id="112" x="42" y="84" width="375" height="120" measuredWidth="375" measuredHeight="120"/>
+ <widgets xsi:type="model:Label" id="113" x="393" y="81" width="24" text="×" measuredWidth="24" measuredHeight="40">
+ <font size="24px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="115" x="131" y="103" text="tails.boum.org" measuredWidth="85" measuredHeight="24">
+ <font bold="true"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="116" x="131" y="128" text="Firefox prevented this site from asking you to install&#xA;software on your computer." measuredWidth="271" measuredHeight="32">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="118" x="55" y="99" measuredWidth="69" measuredHeight="71" src="assets/allow.png"/>
+ <widgets xsi:type="model:Panel" id="121" x="42" y="225" width="375" height="156" measuredWidth="375" measuredHeight="156"/>
+ <widgets xsi:type="model:Label" id="122" x="393" y="222" width="24" text="×" measuredWidth="24" measuredHeight="40">
+ <font size="24px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="123" x="131" y="245" text="tails.boum.org" measuredWidth="85" measuredHeight="24">
+ <font bold="true"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="124" x="131" y="270" text="Downloading and verifying add-on..." measuredWidth="191" measuredHeight="16">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="126" x="58" y="242" measuredWidth="64" measuredHeight="69" src="assets/download.png"/>
+ <widgets xsi:type="model:ProgressBar" id="127" x="132" y="298" width="275" measuredWidth="275" measuredHeight="18" value="28"/>
+ <widgets xsi:type="model:Text" id="128" x="132" y="319" text="A few seconds remaining -- 5.8 of 27.2 KB" measuredWidth="222" measuredHeight="16">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="139" x="132" y="404" measuredWidth="275" measuredHeight="37">
+ <widgets xsi:type="model:ProgressBar" id="129" width="275" measuredWidth="275" measuredHeight="18" value="100"/>
+ <widgets xsi:type="model:Text" id="130" y="21" text="A few seconds remaining -- 27.2 of 27.2 KB" measuredWidth="229" measuredHeight="16">
+ <font/>
+ </widgets>
+ </widgets>
+ <widgets xsi:type="model:Panel" id="131" x="42" y="460" width="375" height="135" measuredWidth="375" measuredHeight="135"/>
+ <widgets xsi:type="model:Image" id="132" x="57" y="476" measuredWidth="66" measuredHeight="70" src="assets/install.png"/>
+ <widgets xsi:type="model:Label" id="133" x="131" y="477" text="tails.boum.org" measuredWidth="85" measuredHeight="24">
+ <font bold="true"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="134" x="131" y="501" text="This site would like to install an add-on in Firefox." measuredWidth="259" measuredHeight="16">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="135" x="131" y="528" text="Tails verification" measuredWidth="91" measuredHeight="16">
+ <font bold="true"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="136" x="242" y="559" width="81" text="Cancel" measuredWidth="81" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="137" x="332" y="559" width="75" text="Install" measuredWidth="75" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="138" x="393" y="456" width="24" text="×" measuredWidth="24" measuredHeight="40">
+ <font size="24px"/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="147" x="432" y="84" width="344" height="28" text="Firefox add-on installation process." measuredWidth="344" measuredHeight="28" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="148" x="336" y="169" width="71" text="Allow" measuredWidth="71" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="149" x="242" y="345" width="81" text="Cancel" measuredWidth="81" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="150" x="332" y="345" width="75" text="Install" measuredWidth="75" measuredHeight="26" state="disabled">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="151" x="12" y="7" width="800" height="32" text="These are moving parts that are meant to be cut out on paper and used to simulate interaction during testing." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/moving_parts_5.screen b/wiki/src/blueprint/DAVE_2/moving_parts_5.screen
new file mode 100644
index 0000000..6e3b08d
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/moving_parts_5.screen
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="98" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Note" id="151" x="12" y="7" width="800" height="32" text="These are moving parts that are meant to be cut out on paper and used to simulate interaction during testing." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Window" id="153" x="49" y="116" width="360" height="209" text="Open file..." measuredWidth="360" measuredHeight="209"/>
+ <widgets xsi:type="model:Tree" id="154" x="59" y="145" width="94" height="141" text="Desktop&#xA;Downloads&#xA;Music&#xA;Videos" measuredWidth="94" measuredHeight="141">
+ <items x="0" y="5" width="94" height="22" text="Desktop"/>
+ <items x="0" y="27" width="94" height="22" text="Downloads"/>
+ <items x="0" y="49" width="94" height="22" text="Music"/>
+ <items x="0" y="71" width="94" height="22" text="Videos"/>
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Panel" id="157" x="160" y="145" width="242" height="141" measuredWidth="242" measuredHeight="141"/>
+ <widgets xsi:type="model:Button" id="158" x="348" y="289" width="54" text="Open" measuredWidth="54" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="159" x="282" y="289" width="57" text="Cancel" measuredWidth="57" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="161" x="186" y="150" text="tails-amd64-3.2.iso" measuredWidth="111" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Icon" id="162" x="166" y="153" width="16" height="16" measuredWidth="16" measuredHeight="16" icon="new (large)"/>
+ <widgets xsi:type="model:Note" id="160" x="432" y="116" width="352" height="27" text="File chooser after clicking &quot;Verify download...&quot;" measuredWidth="352" measuredHeight="27" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Window" id="163" x="41" y="378" width="375" height="226" measuredWidth="375" measuredHeight="226"/>
+ <widgets xsi:type="model:Note" id="164" x="432" y="376" width="352" height="52" text="This is displayed when the user clicks on &quot;Why?&quot; from &quot;Verify using Firefox&quot;." measuredWidth="352" measuredHeight="52" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="165" x="49" y="409" text="- You might loose time if your download is incomplete or broken&#xA; due to an error during the download.&#xA; This is quite frequent." measuredWidth="349" measuredHeight="48">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="166" x="49" y="539" text="- You might get hacked when using Tails if your download is&#xA; modified by an attacker in your country or on your local network.&#xA; [This is possible for strong attackers.]" measuredWidth="362" measuredHeight="48">
+ <font/>
+ <items x="26" y="32" width="191" height="16" text="This is possible for strong attackers."/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="167" x="49" y="472" text="- You might get hacked when using Tails if our servers have been&#xA; compromised and are serving malicious downloads.&#xA; [This already happened to other operating systems.]" measuredWidth="349" measuredHeight="48">
+ <font/>
+ <items x="26" y="32" width="264" height="16" text="This already happened to other operating systems."/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/moving_parts_6.screen b/wiki/src/blueprint/DAVE_2/moving_parts_6.screen
new file mode 100644
index 0000000..5336eee
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/moving_parts_6.screen
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Panel" id="98" x="12" y="48" width="800" height="600" measuredWidth="800" measuredHeight="600"/>
+ <widgets xsi:type="model:Note" id="151" x="12" y="7" width="800" height="32" text="These parts are displayed progressively on the main screen." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="168" x="44" y="101" text="2. Verify your download using Firefox" measuredWidth="327" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="169" x="64" y="194" width="255" text="Install Tails verification extension (no restart)" measuredWidth="255" measuredHeight="26" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="170" x="440" y="101" text="2. Verify your download using BitTorrent" measuredWidth="355" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="171" x="461" y="143" width="314" height="34" text="Your BitTorrent client will automatically verify your download when it is complete." measuredWidth="314" measuredHeight="34">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="172" x="44" y="261" text="3. Continue installing" measuredWidth="187" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="173" x="61" y="145" width="31" height="28" measuredWidth="31" measuredHeight="28" src="assets/warning.png"/>
+ <widgets xsi:type="model:Text" id="174" x="99" y="144" text="*For your security, always verify your download.*&#xA;Our Firefox extension makes it quick and easy." measuredWidth="265" measuredHeight="32">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="175" x="440" y="261" text="3. Continue installing" measuredWidth="187" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="176" x="374" y="141" text="Why?" measuredWidth="33" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="177" x="65" y="304" width="145" text="Next →" measuredWidth="145" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="179" x="461" y="304" width="141" text="Next →" measuredWidth="141" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="180" x="64" y="379" text="Skip download →" measuredWidth="91" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Panel" id="181" x="32" y="368" width="156" height="45" measuredWidth="156" measuredHeight="45" alpha="192" border="none"/>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/no_JS.screen b/wiki/src/blueprint/DAVE_2/no_JS.screen
new file mode 100644
index 0000000..b2645f4
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/no_JS.screen
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Browser" id="1" x="12" y="48" width="800" height="600" text="Browser&#xA;http://tails.boum.org/install/download/" measuredWidth="800" measuredHeight="600">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="98" x="47" y="405" width="319" height="40" text="For your security, always verify your download. Our Firefox, Tor Browser, and Chrome extension makes it quick and easy." measuredWidth="319" measuredHeight="40">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="105" x="47" y="451" width="314" height="39" text="We failed to detect your browser, maybe because you disabled JavaScript." measuredWidth="314" measuredHeight="39">
+ <font italic="true"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="107" x="44" y="361" text="Verify using your browser" measuredWidth="322" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="109" x="41" y="499" text="Install Tails verification extension for Firefox or Tor Browser (no restart)" measuredWidth="392" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="110" x="41" y="531" text="Install Tails verification extension for Chrome or Chromium (no restart)" measuredWidth="387" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="111" x="11" y="8" width="801" height="31" text="This screen appears to people with JavaScript disabled." measuredWidth="801" measuredHeight="31" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="114" x="44" y="148" text="Download and verify" measuredWidth="365" measuredHeight="59">
+ <font size="40px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="115" x="44" y="230" text="Direct download" measuredWidth="209" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="116" x="440" y="230" text="BitTorrent download" measuredWidth="259" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:VLine" id="117" x="400" y="230" height="260" measuredWidth="6" measuredHeight="260"/>
+ <widgets xsi:type="model:Button" id="118" x="440" y="286" text="Download Tails 3.1 (Torrent file)" measuredWidth="190" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="119" x="440" y="361" text="Verify using BitTorrent" measuredWidth="282" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="120" x="440" y="405" width="314" height="34" text="Your BitTorrent client will automatically verify your download when it is complete." measuredWidth="314" measuredHeight="34">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="121" x="440" y="316" text="What is BitTorrent?" measuredWidth="104" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="122" x="44" y="572" text="Verify using OpenPGP (optional)" measuredWidth="401" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="123" x="44" y="285" text="Download Tails 3.1 (1.2 GB)" measuredWidth="168" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="124" x="650" y="540" text="Skip download →" measuredWidth="91" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:VScrollbar" id="125" x="795" y="100" height="548" measuredWidth="17" measuredHeight="548"/>
+ <widgets xsi:type="model:Text" id="126" x="42" y="619" width="605" height="29" text="If you know OpenPGP, you can also use it to verify your download instead, or in addition to, verifying using Firefox or BitTorrent." measuredWidth="605" measuredHeight="29">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/outdated_browser.screen b/wiki/src/blueprint/DAVE_2/outdated_browser.screen
new file mode 100644
index 0000000..18ae84e
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/outdated_browser.screen
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Browser" id="1" x="12" y="48" width="800" height="600" text="Browser&#xA;http://tails.boum.org/install/download/" measuredWidth="800" measuredHeight="600">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="97" x="47" y="322" width="288" height="73" text="Direct download is only available for:&#xA;- Firefox 38 and later&#xA;- Tor Browser 5 and later&#xA;- Chrome or Chromium 61 and later" measuredWidth="288" measuredHeight="73">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="100" x="47" y="407" width="314" height="19" text="Please update your browser to the latest version:" measuredWidth="314" measuredHeight="19">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="106" x="12" y="10" width="801" height="31" text="This screen appears to people with an outdated browser: earlier than Firefox 38." measuredWidth="801" measuredHeight="31" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="108" x="48" y="460" text="Download Firefox (latest version)" measuredWidth="194" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="109" x="47" y="290" text="You are using *Firefox 35*." measuredWidth="133" measuredHeight="16">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="110" x="44" y="148" text="Download and verify" measuredWidth="365" measuredHeight="59">
+ <font size="40px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="111" x="44" y="230" text="Direct download" measuredWidth="209" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="112" x="440" y="230" text="BitTorrent download" measuredWidth="259" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:VLine" id="113" x="400" y="230" height="294" measuredWidth="6" measuredHeight="294"/>
+ <widgets xsi:type="model:Button" id="114" x="440" y="286" text="Download Tails 3.1 (Torrent file)" measuredWidth="190" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="115" x="440" y="361" text="Verify using BitTorrent" measuredWidth="282" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="116" x="440" y="405" width="314" height="34" text="Your BitTorrent client will automatically verify your download when it is complete." measuredWidth="314" measuredHeight="34">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="117" x="440" y="316" text="What is BitTorrent?" measuredWidth="104" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="118" x="44" y="572" text="Verify using OpenPGP (optional)" measuredWidth="401" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="120" x="650" y="540" text="Skip download →" measuredWidth="91" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:VScrollbar" id="121" x="795" y="100" height="548" measuredWidth="17" measuredHeight="548"/>
+ <widgets xsi:type="model:Text" id="122" x="42" y="619" width="605" height="29" text="If you know OpenPGP, you can also use it to verify your download instead, or in addition to, verifying using Firefox or BitTorrent." measuredWidth="605" measuredHeight="29">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/supported_browser.screen b/wiki/src/blueprint/DAVE_2/supported_browser.screen
new file mode 100644
index 0000000..61791f0
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/supported_browser.screen
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Browser" id="1" x="12" y="48" width="800" height="600" text="Browser&#xA;http://tails.boum.org/install/download/" measuredWidth="800" measuredHeight="600">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Note" id="97" x="12" y="8" width="800" height="32" text="This screen appears to people on a compatible browser: Firefox, Chrome , or Tor Browser." measuredWidth="800" measuredHeight="32" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="2" x="44" y="118" text="Download and verify" measuredWidth="365" measuredHeight="59">
+ <font size="40px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="8" x="44" y="190" text="Direct download" measuredWidth="209" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="7" x="442" y="190" text="BitTorrent download" measuredWidth="259" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:VLine" id="9" x="410" y="190" height="363" measuredWidth="6" measuredHeight="363"/>
+ <widgets xsi:type="model:Button" id="11" x="462" y="285" text="Download Tails 3.1 Torrent file" measuredWidth="182" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="13" x="44" y="331" text="2. Verify your download using Firefox" measuredWidth="327" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="14" x="64" y="424" width="255" text="Install Tails verification extension (no restart)" measuredWidth="255" measuredHeight="26" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="24" x="440" y="331" text="2. Verify your download using BitTorrent" measuredWidth="355" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="25" x="461" y="373" width="314" height="34" text="Your BitTorrent client will automatically verify your download when it is complete." measuredWidth="314" measuredHeight="34">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="27" x="443" y="223" text="What is BitTorrent?" measuredWidth="104" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="63" x="44" y="572" text="Verify using OpenPGP (optional)" measuredWidth="401" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Button" id="67" x="64" y="285" text="Download Tails 3.1 ISO image (1.2 GB)" measuredWidth="225" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:VScrollbar" id="98" x="795" y="100" height="548" measuredWidth="17" measuredHeight="548"/>
+ <widgets xsi:type="model:Text" id="99" x="42" y="619" width="605" height="29" text="If you know OpenPGP, you can also use it to verify your download instead, or in addition to, verifying using Firefox or BitTorrent." measuredWidth="605" measuredHeight="29">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="100" x="66" y="528" text="Skip download →" measuredWidth="91" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="101" x="44" y="250" text="1. Download Tails" measuredWidth="160" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="102" x="44" y="491" text="3. Continue installing" measuredWidth="187" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Image" id="103" x="61" y="375" width="31" height="28" measuredWidth="31" measuredHeight="28" src="assets/warning.png"/>
+ <widgets xsi:type="model:Text" id="104" x="99" y="374" text="*For your security, always verify your download.*&#xA;Our Firefox extension makes it quick and easy." measuredWidth="265" measuredHeight="32">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="105" x="442" y="250" text="1. Download Tails (Torrent file)" measuredWidth="274" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="106" x="462" y="528" text="Skip download →" measuredWidth="91" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="107" x="440" y="491" text="3. Continue installing" measuredWidth="187" measuredHeight="34">
+ <font size="20px"/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="109" x="374" y="371" text="Why?" measuredWidth="33" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Panel" id="110" x="27" y="320" width="384" height="205" measuredWidth="384" measuredHeight="205" alpha="192" border="none"/>
+ <widgets xsi:type="model:Panel" id="112" x="429" y="320" width="366" height="205" measuredWidth="366" measuredHeight="205" alpha="192" border="none"/>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/DAVE_2/unsupported_browser.screen b/wiki/src/blueprint/DAVE_2/unsupported_browser.screen
new file mode 100644
index 0000000..45b3387
--- /dev/null
+++ b/wiki/src/blueprint/DAVE_2/unsupported_browser.screen
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<model:Screen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:model="http://wireframesketcher.com/1.0/model.ecore">
+ <widgets xsi:type="model:Browser" id="1" x="12" y="48" width="800" height="600" text="Browser&#xA;http://tails.boum.org/install/download/" measuredWidth="800" measuredHeight="600">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="97" x="47" y="323" width="288" height="73" text="Direct download is only available for:&#xA;- [Firefox 38 and later]&#xA;- [Tor Browser 5 and later]&#xA;- [Chrome or Chromium 61 and later]" measuredWidth="288" measuredHeight="73">
+ <font/>
+ <items x="20" y="16" width="101" height="16" text="Firefox 38 and later"/>
+ <items x="20" y="32" width="122" height="16" text="Tor Browser 5 and later"/>
+ <items x="20" y="48" width="177" height="16" text="Chrome or Chromium 61 and later"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="98" x="47" y="403" width="324" height="39" text="For your security, always verify your download. Our Firefox, Tor Browser, and Chrome extension makes it quick and easy." measuredWidth="324" measuredHeight="39">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="100" x="47" y="449" width="314" height="19" text="Copy and paste this link in Firefox, Chrome, or Tor Browser:" measuredWidth="314" measuredHeight="19">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:WidgetGroup" id="104" x="83" y="482" measuredWidth="228" measuredHeight="30">
+ <widgets xsi:type="model:Panel" id="102" width="228" height="30" measuredWidth="228" measuredHeight="30" background="#fff2cc" foreground="#fff"/>
+ <widgets xsi:type="model:Label" id="101" x="7" y="5" text=" https://tails.boum.org/install/download/" measuredWidth="218" measuredHeight="24" foreground="#b45f06">
+ <font/>
+ </widgets>
+ </widgets>
+ <widgets xsi:type="model:Note" id="106" x="12" y="10" width="801" height="31" text="This screen appears to people on an incompatible browser: Internet Explorer, Safari, etc." measuredWidth="801" measuredHeight="31" textAlignment="Left">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="109" x="47" y="291" text="You are using *Internet Explorer 11*." measuredWidth="187" measuredHeight="16">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="110" x="44" y="148" text="Download and verify" measuredWidth="365" measuredHeight="59">
+ <font size="40px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="111" x="44" y="230" text="Direct download" measuredWidth="209" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="112" x="440" y="230" text="BitTorrent download" measuredWidth="259" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:VLine" id="113" x="400" y="230" height="294" measuredWidth="6" measuredHeight="294"/>
+ <widgets xsi:type="model:Button" id="114" x="440" y="286" text="Download Tails 3.1 (Torrent file)" measuredWidth="190" measuredHeight="26">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="115" x="440" y="361" text="Verify using BitTorrent" measuredWidth="282" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Text" id="116" x="440" y="405" width="314" height="34" text="Your BitTorrent client will automatically verify your download when it is complete." measuredWidth="314" measuredHeight="34">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="117" x="440" y="316" text="What is BitTorrent?" measuredWidth="104" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:Label" id="118" x="44" y="572" text="Verify using OpenPGP (optional)" measuredWidth="401" measuredHeight="44">
+ <font size="28px"/>
+ </widgets>
+ <widgets xsi:type="model:Link" id="120" x="650" y="540" text="Skip download →" measuredWidth="91" measuredHeight="24">
+ <font/>
+ </widgets>
+ <widgets xsi:type="model:VScrollbar" id="121" x="795" y="100" height="548" measuredWidth="17" measuredHeight="548"/>
+ <widgets xsi:type="model:Text" id="122" x="42" y="619" width="605" height="29" text="If you know OpenPGP, you can also use it to verify your download instead, or in addition to, verifying using Firefox or BitTorrent." measuredWidth="605" measuredHeight="29">
+ <font/>
+ </widgets>
+ <hRuler/>
+ <vRuler>
+ <guides position="2305"/>
+ </vRuler>
+ <font size="12px"/>
+</model:Screen>
diff --git a/wiki/src/blueprint/Debian_Stretch.mdwn b/wiki/src/blueprint/Debian_Stretch.mdwn
index ff5db8d..f0ebd78 100644
--- a/wiki/src/blueprint/Debian_Stretch.mdwn
+++ b/wiki/src/blueprint/Debian_Stretch.mdwn
@@ -75,6 +75,10 @@ evaluate the idea of basing Tails on snapshots of Debian testing.
# Let's go rolling
+This material is mostly useful for a historical perspective. The next
+steps and up-to-date information are documented on
+[[blueprint/Debian_testing]] instead.
+
## Stretch cycle
Let's use this porting cycle to evaluate how being based on snapshots
@@ -357,8 +361,24 @@ Additional data that would be interesting:
### Documentation
-XXX:sajolida, please add whatever input data, feelings and analysis
-you can come up with.
+- sajolida spent 6.3 days of work on the update to 3.0 in 2017
+ (including amd64, Debian installation, new Greeter, KeePassX, etc.).
+ spriver and cbrownstein combined spent as much time. So let's say 15
+ days in total.
+- Release notes were a big chunk for sajolida (1.3 days).
+- But we (mostly spriver) also took time to go through all the
+ documentation and test it and that's probably ~2 days of work. I don't
+ think that's realistic or worth it to go through this every quarter so
+ we should think about alternatives:
+ * Get help from the Foundations team to spot what's worth testing
+ * based
+ on the underlying Debian packages?
+ * Only test core pages? Spread the load between different release
+ * (test some pages for some
+ release and some others for another release)?
+- This time we also updated our installation documentation to the new
+ Debian release. If we're based on Stretch we would have to do this at
+ a different time but that shouldn't be a problem.
Note: the following stats ignore PO files, the Icedove → Thunderbird
renaming, and the `blueprint`, `contribute`, `inc` and `news`
@@ -430,9 +450,6 @@ nicer:
- add steps to our existing tests to validate the screenshots we
have in our documentation.
-Clocking data: XXX (ideally, specify clearly what's accounted for,
-e.g. whether the work listed above as irrelevant here is).
-
### Summary
Looking at the data we have, my (intrigeri) general feeling is rather
diff --git a/wiki/src/blueprint/Debian_testing.mdwn b/wiki/src/blueprint/Debian_testing.mdwn
new file mode 100644
index 0000000..225f85f
--- /dev/null
+++ b/wiki/src/blueprint/Debian_testing.mdwn
@@ -0,0 +1,122 @@
+[[!meta title="Basing Tails on quarterly snapshots of Debian Testing"]]
+
+Tracking ticket: [[!tails_ticket 12615]]
+
+[[!toc levels=2]]
+
+# The big picture
+
+We've been thinking for a while of being based on quarterly snapshots
+of Debian testing. We've used the "porting Tails to Debian Stretch"
+cycle to evaluate how it would feel like. See the
+[[initial plan & analysis|blueprint/Debian_Stretch/#rolling]].
+
+## Calendar
+
+A two-years Debian release cycle could look like from our perspective,
+if we were based on quarterly snapshots of Debian testing:
+
+1. a new Debian stable is released
+2. 6 months during which Tails is based on Debian stable that was just
+ released, and we can get ready for the next stage
+3. 12 months during which Tails is based on quarterly snapshots of
+ (non-frozen) Debian testing taken at the beginning of each major
+ Tails release cycle
+4. 6 months during which Tails is based on a frozen Debian testing
+5. go back to (1)
+
+We would be based on a moving target half of the time; the remaining
+half of the time we are based on something that doesn't change much.
+
+## Why?
+
+- We'll need to track 2 Debian versions at the same time (and
+ continuously forward-port development that was based on the oldest
+ one) during 6-7 months maximum, compared to 19 months (Jessie cycle)
+ and 10 months (Stretch cycle). We would save lots of time there,
+ that could be re-invested in aspects of this proposal that will
+ require additional work.
+- no need to produce and maintain backports of Debian packages anymore
+- support new hardware better
+- upstream bugfixes trickle down faster and for free to Tails users
+ ⇒ greater incentive for us to fix bugs upstream instead of
+ implementing Tails-specific workarounds
+- we help stabilizing Debian testing
+- the Foundations Team prefers doing the "porting to next Debian" work
+ continuously than as a huge disruptive project every two years
+- no huge change every 2 years confusing users and creating huge burts
+ in the Help Desk and Foundations Team post-release workload
+- new features / modern software
+
+This idea is about doing a different kind of work, and doing it in
+different places than in the past. It probably won't lower the total
+amount of effort we have to do, but it likely will make such efforts
+generate less frustration, more happiness, and a warm feeling of being
+part of a broader community.
+
+# Fears, concerns & problems we need to address or mitigate
+
+- Security
+ * How to keep track of security issues that affect us, and whether
+ their fix has been uploaded and has migrated to testing yet?
+ See e.g. how security support for Debian testing [used to be
+ (briefly) done](http://secure-testing-master.debian.net/), and in
+ particular the
+ [Vulnerable source packages in the testing suite](https://security-tracker.debian.org/tracker/status/release/testing)
+ and the
+ [Candidates for DTSAs](https://security-tracker.debian.org/tracker/status/dtsa-candidates).
+ * more freeze exceptions in order to address security issues
+
+- Transitions
+ * How to deal with
+ [[!debwiki OngoingTransitions desc="ongoing transitions"]] that
+ block migration of security updates from sid to testing?
+ * How to select the right snapshot we shall take, e.g.
+ during transitions?
+ * Sometimes we'll need to rebuild on testing some packages we want
+ to cherry-pick from sid.
+
+- Consequences for users
+ * too many software regressions and not well tested new features
+ * confused users due to constant incremental changes
+ * bigger upgrades on average
+ * our users debug Debian testing on top of debugging Tails
+
+- Drawbacks for contributors & the Tails community
+ * more frequent regressions in ISO reproducibility
+ * harder to extract info from help desk
+ * harder for help desk to deal with user requests: having to
+ re-learn constantly how things work / what's broken
+ * spend too much mental space dealing with always changing software
+ * lack of Debian skills internally at the moment ⇒ we'll need to
+ invest time learning
+ * need to better study the delta between N & N+1 (for help desk,
+ release notes, security audits, etc.)
+
+- Communication
+ * needs new version numbering scheme
+ * feeling of stalled/slower project for users because no big
+ all-at-a-time changes
+ * how do we deal with our (implicit) hardware support promise? i.e.
+ "The hardware you purchase for Tails N.0 will work with N.x"
+ * harder to get press write stuff as we'll lack releases with tons
+ of changes like 2.0 or 3.0
+
+- Additional Software Packages: will they be pulled from current
+ testing or from our snapshot?
+
+# The plan
+
+* From now to the end of 2017-11: the Foundations Team tries to port
+ the code & test suite during sprints. If the work doesn't fit into
+ these sprints then we'll need to draw conclusions.
+* At the end of 2017-11:
+ 1. [[!tails_ticket 14578 desc="Decide"]] whether we want to release
+ Tails based on Debian testing
+ in 2018-01, 2018-04, or give up and rather release it mid-2019.
+ The following assumes "in 2018-01" and will need to be adjusted
+ if we decide something else.
+ 2. The Foundations Team tells technical writers what needs to be
+ updated ([[!tails_ticket 14579]])
+* November-January: technical writers update the documentation
+* January 16: first Tails release based on Debian testing
diff --git a/wiki/src/blueprint/RT_for_help_desk.mdwn b/wiki/src/blueprint/RT_for_help_desk.mdwn
index 192f3d3..6fccc9f 100644
--- a/wiki/src/blueprint/RT_for_help_desk.mdwn
+++ b/wiki/src/blueprint/RT_for_help_desk.mdwn
@@ -38,6 +38,15 @@ SHOULD
- Allow forwarding issues from and to other user support projects (Tor, Access Now)
- Allow users to express whether they were satisfied with our answers
- Be configurable using Puppet
+ - Allow for easy extraction, archiving, and metrics on hardware
+ compatibility. For example to update our list of known issues easily
+ or to know whether Tails (and which version) worked on this same
+ hardware based on other WhisperBack reports. Hardware that would be
+ interesting to track:
+ - Laptop model (for boot issues)
+ - USB stick (to clean up known issues)
+ - Graphic cards
+ - Wi-Fi cards
MAY
---
diff --git a/wiki/src/blueprint/TailsGreeter.mdwn b/wiki/src/blueprint/TailsGreeter.mdwn
index 7d6b878..38e6f6f 100644
--- a/wiki/src/blueprint/TailsGreeter.mdwn
+++ b/wiki/src/blueprint/TailsGreeter.mdwn
@@ -1,8 +1,6 @@
[[!meta title="tails-greeter"]]
tails-greeter is shipped in Tails 0.11 and later.
-Remaining action items and bugs are split into individual pages in
-[[!tails_todo "" desc="todo"]] and [[!tails_bug "" desc="bugs"]].
Archive
=======
diff --git a/wiki/src/blueprint/additional_software_packages.mdwn b/wiki/src/blueprint/additional_software_packages.mdwn
index fc13025..951f09e 100644
--- a/wiki/src/blueprint/additional_software_packages.mdwn
+++ b/wiki/src/blueprint/additional_software_packages.mdwn
@@ -1,5 +1,10 @@
[[!meta title="User interface for additional software packages"]]
+<div class="note">
+[[blueprint/remember_installed_packages]] overlaps with
+this blueprint.
+</div>
+
The persistence feature for additional software packages is a great tool
to make Tails more flexible for diverse scenarios without having to
bloat the ISO image.
@@ -21,7 +26,13 @@ Proposed user experience
1. When installing a new package, either through the command line or
through Synaptic, the user is asked whether she wants to make it
-persistent.
+persistent. XXX: long-term wise, we should probably focus on _GNOME
+Software_ instead of _Synaptic_; if something works for both, fine,
+but the PackageKit D-Bus interface might be easier to support than
+hooking APT/dpkg, so one option would be to only support installation
+& removal done via PackageKit (i.e. either with _GNOME Software_ or
+using `pkcon` on the command line) and not operations done directly
+with `apt` or _Synaptic_.
2. When removing a persistent package, the user is asked whether she
wants to remove it from the list of persistent packages.
diff --git a/wiki/src/blueprint/automated_builds_and_tests/testing.mdwn b/wiki/src/blueprint/automated_builds_and_tests/testing.mdwn
index 5a16d99..cce2dc1 100644
--- a/wiki/src/blueprint/automated_builds_and_tests/testing.mdwn
+++ b/wiki/src/blueprint/automated_builds_and_tests/testing.mdwn
@@ -15,7 +15,7 @@ This page is about tools that could allow us to improve it.
* examples from the eog source tree, that use *behave* and *dogtail*:
- [feature](https://git.gnome.org/browse/eog/tree/tests/actions.feature)
- [steps definition](https://git.gnome.org/browse/eog/tree/tests/steps/steps.py)
-* not in Debian (2014/08/05)
+* In [Debian](https://packages.qa.debian.org/b/behave.html) (in unstable since 2017/07/20)
* Python (with Jython) is now Sikuli's preferred scripting language;
it's also the language that has the best maintained bindings to
interact with libvirt, accessibility technologies, and more
@@ -23,8 +23,8 @@ This page is about tools that could allow us to improve it.
## dogtail
-* [homepage](https://fedorahosted.org/dogtail/)
-* actively maintained upstream as of 2016-02
+* [homepage](https://gitlab.com/dogtail/dogtail)
+* actively maintained upstream as of 2017-05-31
* GUI test tool and automation framework written in ​Python
* uses Accessibility (a11y) technologies to communicate with
desktop applications
diff --git a/wiki/src/blueprint/better_metrics.mdwn b/wiki/src/blueprint/better_metrics.mdwn
new file mode 100644
index 0000000..c3364cf
--- /dev/null
+++ b/wiki/src/blueprint/better_metrics.mdwn
@@ -0,0 +1,84 @@
+[[!meta title="Better metrics"]]
+
+## Current status
+
+- Metrics are collected:
+ - Manually
+ - Only by sajolida and intrigeri
+ - Into text files
+ - In the internal Git repo
+
+- We are collecting:
+ - Community metrics
+ - Subscribers to amnesia-news
+ - Messages on tails-dev
+ - Subscribers on tails-dev
+ - Twitter followers
+ - Help desk
+ - Messages on tails-bug
+ - WhisperBack reports
+ - Releases
+ - Date
+ - Size
+ - Usage
+ - Boots
+ - Downloads of the OpenPGP signature
+
+## Concerns
+
+- The workload is not shared
+- The data is not systematically published (some are in the monthly reports)
+- Manual process
+
+## Taking a step back...
+
+- Why are we collecting these metrics?
+- What shall we do with them?
+- What metrics are most important to collect?
+- What kind of tools and infrastructure shall we use to manage these metrics?
+- Where do we store them? Who has access to them?
+
+## Ideas of abstract goals behind the numbers
+
+From a brainstorming session, with no priorities or check on whether
+these are possible and worth it to gather.
+
+- Find how many users we do have? What are the trends?
+- How many bugs? Per category? Are we carrying around old bugs? Are we adding new bugs?
+- Are we reducing errors for users ?
+- Are we reducing the time needed for task completion?
+- Help desk reports
+- How technically skilled do you need to be to use Tails? How technically skilled are our users?
+- Donations
+ - How many donations do we get?
+ - How much are people donation?
+ - When do we get donation?
+- Incoming links? Who is endorsing Tails?
+- Where are the users located?
+- How big, diverse and active is our community?
+- Statistics on private and public meetings:
+ - How many people attended?
+ - How many meetings?
+ - How many newcomers?
+- Conferences
+ - Attended?
+ - How many mentions?
+- How fast to we solve problems?
+ - Security issues
+- How organized and accountable we are?
+- Conversion rate
+ - User agents
+- Heat map of the website usage
+ - Are people coming to download the image?
+ - Are people coming to read the documentation?
+- Why are people interested in Tails?
+
+## Possible ways to gather this data
+
+- Ticket tracker for help desk
+- Web analytic
+- Surveys
+
+## References
+
+- [Translating UX Goals into Analytics Measurement Plans](https://www.nngroup.com/articles/ux-goals-analytics/)
diff --git a/wiki/src/blueprint/better_task_manager.mdwn b/wiki/src/blueprint/better_task_manager.mdwn
index 336c0df..31fa151 100644
--- a/wiki/src/blueprint/better_task_manager.mdwn
+++ b/wiki/src/blueprint/better_task_manager.mdwn
@@ -1,4 +1,4 @@
-Our current approach to managing Tails [[!tails_todo "" desc="todo"]]
+Our current approach to managing Tails todo
does not scale. We have some ideas to improve it slightly, but it's
unlikely the result will be good enough, so we will instead migrate
to Redmine.
diff --git a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
index b71bf68..d736bbf 100644
--- a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
+++ b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
@@ -169,3 +169,8 @@ Cons:
give us more precise numbers.
* We need to trust a third-party somewhat.
+
+We could [request a grant from AWS](https://aws.amazon.com/grants/) to
+experiment with this approach.
+See
+[Arturo's report about how OONI took advantage of this grant program](https://lists.torproject.org/pipermail/tor-project/2017-August/001391.html).
diff --git a/wiki/src/blueprint/l10n_Italian.mdwn b/wiki/src/blueprint/l10n_Italian.mdwn
index 780cea8..e9d5b72 100644
--- a/wiki/src/blueprint/l10n_Italian.mdwn
+++ b/wiki/src/blueprint/l10n_Italian.mdwn
@@ -217,7 +217,9 @@ Ogni tanto (quando?) si fanno dei pacchi di traduzioni. Un pacco e' un insieme d
### Tradurre
-Supponiamo di tradurre la divina commedia, e di fare 3 pacchi: Inferno, Purgatorio e Paradiso. Petrarca si accolla di tradurre l'Inferno, e lo fa in una branch che chiama, appunto "inferno". traduce tutti i file `wiki/src/inferno/*.po`, (**TODO**: andrebbe anche fatti i check) quindi fa `git commit -m "inferno tradotto"`.
+Supponiamo di tradurre la divina commedia, e di fare 3 pacchi: Inferno, Purgatorio e Paradiso. Petrarca si accolla di tradurre l'Inferno, e lo fa in una branch che chiama, appunto "inferno". traduce tutti i file `wiki/src/inferno/*.po`, (**TODO**: andrebbe anche fatti i check) quindi fa `git commit -m "inferno translated"`.
+
+Sì, i commit vanno fatti in inglese.
### Revisionare
@@ -231,7 +233,7 @@ con:
[[immagine \"caronte.png\"`]]
-Laura corregge e fa commit sulla stessa branch `git commit wiki/src/inferno/terzocanto.po -m "fix immagine caronte" && git push origin inferno`.
+Laura corregge e fa commit sulla stessa branch `git commit wiki/src/inferno/terzocanto.po -m "fix image for caronte" && git push origin inferno`.
Non trova altri errori, quindi fa
git checkout master
diff --git a/wiki/src/blueprint/lizard_failover.mdwn b/wiki/src/blueprint/lizard_failover.mdwn
index f3148e5..d892e68 100644
--- a/wiki/src/blueprint/lizard_failover.mdwn
+++ b/wiki/src/blueprint/lizard_failover.mdwn
@@ -27,15 +27,13 @@ monitoring|blueprint/monitor_servers#services]].
This is about [[!tails_ticket 10243]].
-The goal is to specify what we'll likely need mid-2016.
+The goal is to specify what we'll likely need until end of 2018.
We also need datacenter-class bandwidth.
- APT repository:
- * CPU: reprepro can already be hungry; and once we have the
- freezable APT repo, depending on the chosen tools it may grow
- a lot (e.g. no idea how aptly behaves)
+ * CPU: reprepro can already be hungry
* RAM: currently low, but might grow for the same reason as CPU usage
- * storage: 425 GB, +25% each year
+ * storage: 1.8T
- bittorrent:
* CPU: low
* RAM: low
@@ -43,7 +41,7 @@ We also need datacenter-class bandwidth.
- Tor Browser archive:
* CPU: low
* RAM: low
- * storage: 60 GB, +40GB each year
+ * storage: 200G
- rsync server:
* CPU: low
* RAM: low
@@ -55,6 +53,6 @@ We also need datacenter-class bandwidth.
**Total**:
- * CPU: currently low but must be easily upgradable
+ * CPU: currently low but must be easily upgradable.
* RAM: 2 GB should be enough for now, but must be easily upgradable
- * storage: 500 GB mid-2016; 650 GB mid-2017
+ * storage: 2T (preferabily RAID) to cover up until end 2018.
diff --git a/wiki/src/blueprint/monthly_meeting.mdwn b/wiki/src/blueprint/monthly_meeting.mdwn
index c5b0752..326b241 100644
--- a/wiki/src/blueprint/monthly_meeting.mdwn
+++ b/wiki/src/blueprint/monthly_meeting.mdwn
@@ -19,8 +19,8 @@ Availability and plans for the next weeks
Discussions
===========
- - [[!tails_ticket 12402 desc="Include Yubico Authenticator in Tails"]]
- - [[!tails_ticket 12098 desc="Spurious screensaver activation while synchronizing the system clock"]]
+ - A short one: [the monthly report is looking for coordinators!](https://tails.boum.org/blueprint/monthly_report/) for the next few month: if you want to coordinate the creation process of a memorable
+ piece of literature, pleace add your name to a specific month in the linked page (or if you
+want to build a team, gang together and add multiple names!)
- [[!tails_ticket 12437 desc="Save coredumps to a sticky directory"]]
- - [[!tails_ticket 7439 desc="Decide whether to remove the clock synchronization notification"]]
- [[!tails_ticket 7224 desc="Link different design documentations from user documentation"]]
diff --git a/wiki/src/blueprint/monthly_report.mdwn b/wiki/src/blueprint/monthly_report.mdwn
index 11609bd..c3ab272 100644
--- a/wiki/src/blueprint/monthly_report.mdwn
+++ b/wiki/src/blueprint/monthly_report.mdwn
@@ -16,15 +16,21 @@ 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: u
- - February:emmapeel
- - March: intrigeri
- - April: spriver
- - May: u
- - June: intrigeri
- - July: sajolida
- - August: spriver
- - September: emmapeel
+ - 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:
+ - February 2018:
+
Checklist
=========
@@ -74,7 +80,7 @@ Template
========
\[[!meta title="Tails report for MONTH, YEAR"]]
- \[[!meta date="DATE"]]
+ \[[!meta date="DATE (eg. Tue Aug 8 12:34:56 2018)"]]
\[[!toc]]
@@ -97,20 +103,36 @@ Template
Code
====
- XXX: List important code work that is not covered already by the Release
- section (for example, the changes being worked on for the next version).
+ 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: Explore the Git history:
+ 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: Check the archives of tails-ux: https://mailman.boum.org/pipermail/tails-ux/
+ 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
==============
@@ -171,6 +193,6 @@ Template
* 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]]
+ \[[How do we know this?|support/faq#boot_statistics]]
- XXX: Ask tails@boum.org for these numbers.
+ XXX: Ask <tails@boum.org> for these numbers.
diff --git a/wiki/src/blueprint/monthly_report/report_2017_09.mdwn b/wiki/src/blueprint/monthly_report/report_2017_09.mdwn
index 74276a4..ddab0a6 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_09.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2017_09.mdwn
@@ -32,11 +32,24 @@ XXX: Explore the Git history:
git log --patch --since='1 October' --until='1 November' origin/master -- "*.*m*"
+ * We greatly improved our [[instructions for building the Tails ISO image|contribute/build/]] and created a new section about how to [[verify that the Tails ISO image is reproducible|contribute/build/reproducible/]].
+
User experience
===============
XXX: 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
==============
@@ -67,6 +80,8 @@ Past events
Upcoming events
---------------
+* Some of us will attend the Reproducible Builds summit, Berlin
+
On-going discussions
====================
diff --git a/wiki/src/blueprint/monthly_report/report_2017_10.mdwn b/wiki/src/blueprint/monthly_report/report_2017_10.mdwn
index 00e0ed2..546747d 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_10.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2017_10.mdwn
@@ -37,6 +37,17 @@ User experience
XXX: 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
==============
diff --git a/wiki/src/blueprint/monthly_report/report_2017_11.mdwn b/wiki/src/blueprint/monthly_report/report_2017_11.mdwn
index df101d0..cf296de 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_11.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2017_11.mdwn
@@ -37,6 +37,17 @@ User experience
XXX: 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
==============
diff --git a/wiki/src/blueprint/monthly_report/report_2017_12.mdwn b/wiki/src/blueprint/monthly_report/report_2017_12.mdwn
index 64c631a..868c51a 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_12.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2017_12.mdwn
@@ -37,6 +37,17 @@ User experience
XXX: 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
==============
diff --git a/wiki/src/blueprint/monthly_report/report_2017_07.mdwn b/wiki/src/blueprint/monthly_report/report_2018_01.mdwn
index 06974d6..345a001 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_07.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2018_01.mdwn
@@ -1,7 +1,7 @@
-[[!meta title="Tails report for July, 2017"]]
-[[!meta date="DATE"]]
+[[!meta title="Tails report for January, 2018"]]
+[[!meta date="DATE (eg. Tue Aug 8 12:34:56 2018)"]]
-[[!toc ]]
+[[!toc]]
Releases
========
@@ -22,39 +22,36 @@ XXX: Copy the "Changes" section of the release notes, and compact a bit:
Code
====
-XXX: List important code work that is not covered already by the Release
- section (for example, the changes being worked on for the next version).
+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
=========================
-- We improved our [[installation instructions for
- Ubuntu|install/debian/usb#ubuntu]] to configure the PPA through
- **Software & Updates** instead of the command line.
+XXX: If you feel like it and technical writers don't do it
+ themselves, explore the Git history:
-- We published instructions on [[how to repair a Tails
- 3.0.1|news/rescue_3.0.1]] broken by the automatic upgrade.
+ git log --patch --since='1 October' --until='1 November' origin/master -- "*.*m*"
-- We documented that Tails fails to start on [[computers with NVIDIA
- Maxwell graphics|support/known_issues#nvidia-maxwell]].
+User experience
+===============
-- We updated the terminology on our website to stop mentioning SD cards
- and always talk about *Tails USB stick* instead of *Tails device*.
- [[!tails_ticket 9965]]
+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/>
-- We made it clearer in the system requirements that Tails doesn't work
- on handheld devices.
+Hot topics on our help desk
+===========================
-- We improved the link and QR code to get back to the same step when
- switching device during installation. [[!tails_ticket 12319]]
+XXX: Ask tails-bugs@boum.org to list hot topics for the last month.
-- We updated our command line instructions to use `apt` instead of
- `apt-get`.
+1.
-- We renamed *Mac OS X* as *macOS*, it's new name.
+1.
-- We improved the inlining mechanism that links to release notes during
- upgrades. [[!tails_ticket 13341]]
+1.
Infrastructure
==============
@@ -77,8 +74,6 @@ 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>.
-Next INpact started a [[https://www.nextinpact.com/news/104659-edito-vie-privee-et-securite-nos-donnees-comment-mieux-soutenir-informer-et-proteger.htm|donation campaign]] to support Tails, Tor and VeraCrypt using 33% of total donations.
-
Outreach
========
@@ -96,7 +91,7 @@ XXX: Link to the thread on <https://mailman.boum.org/pipermail/tails-XXX/>.
Press and testimonials
======================
-XXX: Copy content from press/media_appearances_2017.mdwn
+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.
@@ -115,6 +110,8 @@ 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.
-* 160 bug reports were received through WhisperBack.
+* WHISPERBACK bug reports were received through WhisperBack.
+
+[[How do we know this?|support/faq#boot_statistics]]
-XXX: Ask tails@boum.org for these numbers.
+XXX: Ask <tails@boum.org> for these numbers.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_02.mdwn b/wiki/src/blueprint/monthly_report/report_2018_02.mdwn
new file mode 100644
index 0000000..9931847
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_02.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for February, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_03.mdwn b/wiki/src/blueprint/monthly_report/report_2018_03.mdwn
new file mode 100644
index 0000000..6d419d4
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_03.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for March, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_04.mdwn b/wiki/src/blueprint/monthly_report/report_2018_04.mdwn
new file mode 100644
index 0000000..1d0781e
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_04.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for April, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2017_08.mdwn b/wiki/src/blueprint/monthly_report/report_2018_05.mdwn
index 21ce3db..747a19f 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_08.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2018_05.mdwn
@@ -1,7 +1,7 @@
-[[!meta title="Tails report for August, 2017"]]
-[[!meta date="DATE"]]
+[[!meta title="Tails report for May, 2018"]]
+[[!meta date="DATE (eg. Tue Aug 8 12:34:56 2018)"]]
-[[!toc ]]
+[[!toc]]
Releases
========
@@ -22,20 +22,36 @@ XXX: Copy the "Changes" section of the release notes, and compact a bit:
Code
====
-XXX: List important code work that is not covered already by the Release
- section (for example, the changes being worked on for the next version).
+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: Explore the Git history:
+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: Check the archives of tails-ux: https://mailman.boum.org/pipermail/tails-ux/
+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
==============
@@ -75,7 +91,7 @@ XXX: Link to the thread on <https://mailman.boum.org/pipermail/tails-XXX/>.
Press and testimonials
======================
-XXX: Copy content from press/media_appearances_2017.mdwn
+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.
@@ -96,4 +112,6 @@ Metrics
* SIGS downloads of the OpenPGP signature of Tails ISO from our website.
* WHISPERBACK bug reports were received through WhisperBack.
-XXX: Ask tails@boum.org for these numbers.
+[[How do we know this?|support/faq#boot_statistics]]
+
+XXX: Ask <tails@boum.org> for these numbers.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_06.mdwn b/wiki/src/blueprint/monthly_report/report_2018_06.mdwn
new file mode 100644
index 0000000..4da9fa4
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_06.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for June, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_07.mdwn b/wiki/src/blueprint/monthly_report/report_2018_07.mdwn
new file mode 100644
index 0000000..99005a2
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_07.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for July, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_08.mdwn b/wiki/src/blueprint/monthly_report/report_2018_08.mdwn
new file mode 100644
index 0000000..781deef
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_08.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for August, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_09.mdwn b/wiki/src/blueprint/monthly_report/report_2018_09.mdwn
new file mode 100644
index 0000000..acaa704
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_09.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for September, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_10.mdwn b/wiki/src/blueprint/monthly_report/report_2018_10.mdwn
new file mode 100644
index 0000000..ab8382c
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_10.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for October, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_11.mdwn b/wiki/src/blueprint/monthly_report/report_2018_11.mdwn
new file mode 100644
index 0000000..5a53a56
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_11.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for November, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/monthly_report/report_2018_12.mdwn b/wiki/src/blueprint/monthly_report/report_2018_12.mdwn
new file mode 100644
index 0000000..9739bc1
--- /dev/null
+++ b/wiki/src/blueprint/monthly_report/report_2018_12.mdwn
@@ -0,0 +1,117 @@
+[[!meta title="Tails report for December, 2018"]]
+[[!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.
diff --git a/wiki/src/blueprint/network_connection.mdwn b/wiki/src/blueprint/network_connection.mdwn
index 90a6a00..e0b977a 100644
--- a/wiki/src/blueprint/network_connection.mdwn
+++ b/wiki/src/blueprint/network_connection.mdwn
@@ -92,9 +92,12 @@ At Tor:
- [A Usability Evaluation of Tor Launcher](https://trac.torproject.org/projects/tor/wiki/doc/TorLauncherUX2016)
- [UX testing of circumvention features of Tor Browser](https://github.com/lindanlee/circumvention-ux-tor)
- <https://github.com/lindanlee/PETS2017-paper/blob/master/lindas-ms-paper/lindas-ms-paper.pdf>
+ - Tor UX team's design of new Tor launcher: <https://marvelapp.com/3f6102d>
- [Feedback on design decision for Tor Launcher](https://lists.torproject.org/pipermail/tbb-dev/2017-February/000473.html)
discussion on the tbb-dev mailing list (spread over 2017-02 and 2017-03)
At Whonix:
- - <https://www.whonix.org/blog/connection-bridge-wizard>
+ - <https://forums.whonix.org/t/graphical-gui-whonix-setup-wizard-anon-connection-wizard-technical-discussion/650/303>
+ - <https://github.com/irykoon/anon-connection-wizard>
+ (or: <https://github.com/Whonix/anon-connection-wizard>)
diff --git a/wiki/src/blueprint/personas.mdwn b/wiki/src/blueprint/personas.mdwn
index 99e06d0..995fb62 100644
--- a/wiki/src/blueprint/personas.mdwn
+++ b/wiki/src/blueprint/personas.mdwn
@@ -8,11 +8,22 @@ This is about [[!tails_ticket 11162]].
# External resources about personas
- - [Gus Andrew's User Personas for Privacy and Security](https://medium.com/@gusandrews/user-personas-for-privacy-and-security-a8b35ae5a63b#.8lyxpkom4)
- - [Personas on usability.gov](http://www.usability.gov/how-to-and-tools/methods/personas.html)
- - [AccessNow's A First Look at Digital Security](https://www.accessnow.org/a-first-look-at-digital-security/)
- is formatted a bit like personas.
- - [Developing Personas from the Internet Freedom Needfinding Framework](http://internetfreedom.secondmuse.com/framework-elements/developing-personas/)
+ - General
+ - [Personas on usability.gov](http://www.usability.gov/how-to-and-tools/methods/personas.html)
+ - [Focus on the Job, Not the Customer](https://blog.intercom.com/when-personas-fail-you/)
+ - [User Profile Randomizer](https://github.com/seamustuohy/user_profile_randomizer)
+ - [Describing personas](https://medium.com/@indiyoung/describing-personas-af992e3fc527)
+ - Privacy and security
+ - [Gus Andrew's User Personas for Privacy and Security](https://medium.com/@gusandrews/user-personas-for-privacy-and-security-a8b35ae5a63b#.8lyxpkom4)
+ - [AccessNow's A First Look at Digital Security](https://www.accessnow.org/a-first-look-at-digital-security/)
+ is formatted a bit like personas.
+ - [Developing Personas from the Internet Freedom Needfinding Framework](http://internetfreedom.secondmuse.com/framework-elements/developing-personas/)
+ - [USABLE.tools](https://usable.tools/personas/)
+ - [Waxing Poetic with SwiftOnSecurity](https://swiftonsecurity.tumblr.com/post/98675308034/a-story-about-jessica)
+ - Accessibility and inclusion
+ - [Designing for the extremes (or why your average user doesn’t exist)](https://sugoru.com/2013/07/14/designing-for-the-extremes/)
+ - [Personas for Accessible UX](https://www.slideshare.net/whitneyq/personas-for-accessible-ux)
+ - [Inclusive Design at Microsoft](https://www.microsoft.com/en-us/design/inclusive)
# Data sources
@@ -42,11 +53,11 @@ This is about [[!tails_ticket 11162]].
- [Tails-project: Regarding USB sticks for domestic violence
survivors](https://mailman.boum.org/pipermail/tails-project/2017-March/000757.html)
-# User scenarios
+# Collective brainstorming in August 2016
-From a discussion in August 2016:
+Use cases:
-- A small group of English-speaking journalists use Tails to analyse an
+- A small group of English-speaking journalists use Tails to analyze an
archive of leaked documents and prepare articles about them.
- A well-established music teacher uses Tails to bypass the software and
@@ -116,3 +127,369 @@ From a discussion in August 2016:
- A person without the need for a big storage uses Tails as their main
operating system to have more privacy.
+
+<a id="2017-08"></a>
+
+# Collective process from August 2017
+
+Summary of a 2 hours session we did with 12 core contributors.
+
+This process is inspired by the workshop described in _The Essential
+Persona Lifecycle_ by Tamara Adlin and John Pruitt, Chapter 4 *Persona
+conception and gestation*.
+
+- General explanation of what personas are and why they are useful (15')
+
+- Everybody prepares, in silent, sticky notes describing a user and their goal. (15')
+
+ For example:
+
+ - "*Women that go through domestic violence and wants to escape from that.*"
+ - "*Webmasters of a sensitive website that wants to hack on it.*"
+
+- All together we assimilate these sticky notes and the ones identified
+ in August 2016 by *types of users*. (30')
+
+ We start with predefined categories based on last year's output and
+ adding new ones or splitting existing ones as needed. There should be
+ no more than 10 stick notes per category.
+
+ - Predefined categories:
+ - Activist
+ - Censorship evader
+ - Contributor
+ - Darknet customer
+ - Information freedom fighter
+ - Nomadic
+ - Privacy geek
+ - Surveilled at home
+
+ - Final categories:
+ - Activist
+ - Censorship evader
+ - Contributor
+ - Darknet customer
+ - Evil people
+ - Information freedom fighter
+ - Journalist or researcher
+ - Law enforcement
+ - Nomadic
+ - People helping others in shit
+ - People we don't want to help
+ - Privacy geek
+ - Sensitive content creator
+ - Surveilled at home
+ - Surveilled at work
+
+- The facilitator takes pictures of the resulting assimilation and
+ removes the user categories.
+
+- All together we assimilate again the same stick notes and group them
+ by *user goals* (45').
+
+ User goals are short sentences starting with "*I want...*" or "*I need...*".
+ There should be no more than 10 stick notes per category. Sticky notes
+ that fit in more than one goal can be duplicated.
+
+- All together we summarize these goals by identifying main goals and
+ subgoals. (10')
+
+ - Final goals:
+
+ A. I want to hide personally identifying information or sensitive information about myself
+ - I want to keep content & information secret from my government
+ - I want to keep information secret from my family and close people
+ - I want to access sensitive information stealthily
+ - I want to hide my identity
+ - I want to hide my location and identity
+ - I want to hide my location
+ - I don't want to raise suspicion
+
+ B. I want to communicate and collaborate securely
+ - I want to communicate securely with known peers
+ - I want to communicate securely with unknown peers
+ - I want to communicate with others who are under surveillance
+ - We want to share and work on documents privately
+
+ C. I want to store information safely
+ - I need to safely store my data
+ - I want to edit or anonymize my data
+
+ D. I want to leave no trace on the computer
+ - I need to use a computer that is not mine
+
+ E. I want information to be free
+ - I want to access censored information online
+ - I want to publish sensitive information
+
+ F. I want to avoid corporate & governmental information gathering on my data
+ - I want to understand people using Tails
+ - I just want more privacy
+
+# Skeletons
+
+After this collective session, the core team working on the personas (3
+people) started preparing skeletons, rough descriptions of each persona,
+based on the main goals identified earlier. Each persona is primarily
+focused on a single main goal but also corresponds to some subgoals of
+other categories.
+
+On top of demographics, background, and technical skills information,
+our framework includes holistic security and threat modeling information
+(based on the [Personas Framework for Internet
+Freedom](http://internetfreedom.secondmuse.com/framework-elements/developing-personas/)
+developed by SecondMuse):
+
+ 1. Name (genderneutral)
+ 2. Occupation
+ 3. Background
+ 4. Motivations
+ 5. Challenges and threats
+ 6. Communications
+ 7. Goals
+ 8. Use cases
+ 9. Definition of security
+ 10. Key Technologies used regularly
+ a. Features used in Tails
+ b. Features used outside of Tails
+ 11. Threat perception
+ 12. Security precautions
+
+## Kim
+
+- **Occupation**
+
+- **Background**
+
+ - Kim is a gay youth from Nigeria that has been institutionalized.
+ - Kim has been abused at home.
+ - Kim is using a shared a computer.
+
+- **Motivations**
+
+ - Kim is searching for help and support groups online and also tries
+ to find solidarity.
+ - Kim wants to feel normal.
+ - Kim wants to avoid surveillance from mentors in the institution they
+ lives in.
+ - Kim does not want to leave traces on the shared computer and prefers
+ to hide their identity by accessing information stealthily.
+
+- **Challenges and threats**:
+
+ - The computer room is crowded
+ - Can't meet with support groups openly and has to do it online
+ - Surveillance from mentors
+ - Time is limited
+ - Fear of previous abusers
+ - Worried about saving information safely
+ - Needs to know keyboard shortcuts for switching applications in case
+ somebody walks behind them
+ - Needs safe storage for email addresses and nicknames
+ - Needs access to books online
+ - Needs to use a pseudonym
+ - Needs a stealth or dedicated email address
+ - Needs to store data in the cloud or an encrypted device in case Kim
+ gets searched
+
+- **Communications**
+
+ - Support groups online: forums, websites
+ - Known peers: chat, email
+ - Unknown peers: chat, email, forums
+ - Psychologist online: forums, websites
+
+- **Goals**
+
+ A. I want to hide personally identifying information or sensitive information about myself
+ - I want to keep content & information secret from my government
+ - I want to keep information secret from my family and close people
+ - I want to access sensitive information stealthily
+ - I want to hide my identity
+ - I want to hide my location and identity
+ - I want to hide my location
+ - I don't want to raise suspicion
+
+ B. I want to communicate and collaborate securely
+ - I want to communicate securely with known peers
+ - I want to communicate securely with unknown peers
+
+ D. I want to leave no trace on the computer
+ - I need to use a computer that is not mine
+
+ E. I want information to be free
+ - I want to access censored information online
+
+- **Use cases**
+
+- **Definition of security**
+
+- **Key technologies used regularly**
+
+ a. Features used in Tails
+
+ b. Features used outside of Tails
+
+- **Threat perception**
+
+- **Security precautions**
+
+## Alex
+
+- **Occupation**
+
+ - Alex is an investigative journalist doing high stake reporting on
+ the government, and in particular some members of the government who
+ are involved in corruption, drug and human trafficking.
+
+- **Background**
+
+ - Alex lives in Mexico and reports on the mafia and drug related
+ corruption of politicians.
+ - Alex is visiting the country to interview locals and needs to get
+ out of the country with the collected information and media safely.
+ - Alex needs to communicate with journalistic partners and sources and
+ to protect these communications as well as the identity of Alex'
+ interview partners.
+ - Alex needs to store and edit the collected information safely. They
+ also need to keep metadata in order to prove the evidence.
+ Furthermore they also need to send big videos files over the
+ Internet for somebody else to edit it.
+
+- **Motivations**
+
+ - Publish information about corrupted politicians and harm they did.
+ - Turn public opinion against these people.
+
+- **Challenges**
+
+ - Access information
+ - Publish under pseudonyms
+ - Hide their location and identity
+ - Stealth research by visiting journalists
+ - Bring information outside of the country
+
+- **Communications**
+
+- **Goals**
+
+ A. I want to hide personally identifying information or sensitive information about myself
+ - I want to keep content & information secret from my government
+ - I want to access sensitive information stealthily
+ - I want to hide my identity
+ - I don't want to raise suspicion
+
+ B. I want to communicate and collaborate securely
+ - I want to communicate securely with known peers
+ - I want to communicate securely with unknown peers
+ - I want to communicate with others who are under surveillance
+ - We want to share and work on documents privately
+
+ C. I want to store information safely
+ - I need to safely store my data
+ - I want to edit or anonymize my data
+
+ E. I want information to be free
+ - I want to publish sensitive information
+
+- **Use cases**
+
+- **Definition of security**
+
+- **Key technologies used regularly**
+
+ a. Features used in Tails
+
+ b. Features used outside of Tails
+
+- **Threat perception**
+
+- **Security precautions**
+
+## Riou
+
+- **Occupation**
+
+ Riou is a student in Hong Kong, who participates in the Umbrella
+ movement.
+
+- **Background**
+
+ - Riou organizes a public massive protest against new government
+ policies and laws. The organizers need to be stealthy and anonymous,
+ but the protest needs to be public and advertised. The organizers
+ need to send out strategic information to the press and to the
+ public so that citizens actually know where to show up. In order to
+ publish this information they use websites which are not in the
+ country, so that the government cannot censor this information.
+
+ - During the protest they leave their phones at home. They are doing
+ most of their communication beforehand. Although they take photos
+ and videos of the protests and try to publish this information on
+ websites which are censored within the country. They got to get it
+ online as soon as it's produced on social media and they also want
+ to stream the protest and speeches. They might want to do that on
+ devices that are not theirs, so that they can hide their involvement
+ in the organization of this protest.
+
+- **Motivations**
+
+- **Challenges**
+
+ - Use networks
+ - Access information online
+ - Use applications that the government is not monitoring
+ - Use mesh applications
+
+- **Communications**
+
+ - Local group chat
+ - Encrypted emails
+
+- **Goals**
+
+ A. I want to hide personally identifying information or sensitive information about myself
+ - I want to keep content & information secret from my government
+ - I want to hide my identity
+ - I want to hide my location
+ - I don't want to raise suspicion
+
+ B. I want to communicate and collaborate securely
+ - I want to communicate securely with known peers
+
+ E. I want information to be free
+ - I want to access censored information online
+ - I want to publish sensitive information
+
+- **Use cases**
+
+- **Definition of security**
+
+- **Key technologies used regularly**
+
+ a. Features used in Tails
+
+ b. Features used outside of Tails
+
+- **Threat perception**
+
+- **Security precautions**
+
+Next steps
+==========
+
+1. Create tickets for the following steps [[!tails_ticket 14525]]
+1. Draft "*Privacy geek*" skeleton
+1. Check back yellow post-it notes
+1. Refine good enough draft skeletons
+ - Link to actual stories or research if we have it
+1. Ask for comments on tails-project@boum.org
+1. Ask the project to prioritize the 4 skeletons according to different dimensions
+1. Write 1st version of foundation document:
+ - Find images (photos or drawings) for the personas
+ - Consider using 2 images per persona so that we have a
+ genderneutral persona
+ - Reference data
+1. Prepare summary for developers:
+ - Two A4 pages per persona?
+ - Have a detailed version and a condensed version?
diff --git a/wiki/src/blueprint/randomness_seeding.mdwn b/wiki/src/blueprint/randomness_seeding.mdwn
index 28d4d87..0838f66 100644
--- a/wiki/src/blueprint/randomness_seeding.mdwn
+++ b/wiki/src/blueprint/randomness_seeding.mdwn
@@ -1,51 +1,51 @@
# /dev/random and /dev/urandom radomness seeding in Tails
/dev/random and /dev/urandom are special Linux devices that provide access from
-user land to the Linux kernel Pseudo Random Number Generator (PRNG). This
-generator is used for almost every security protocol, like TLS/SSL key
-generation, choosing TCP sequences, ASLR offsets, and GPG key generation [1]. In
-order for this seed to be cryptographically secure, a source with 'good'
-entropy must be used. The Linux kernel collects entropy from several sources,
-for example keyboard typing, mouse movement, among others.
-
-## Problem
-
-Because of the Tails nature of being amnesic, and run from a (USB) live device,
-care must be taken to ensure the system still gets enough entropy and boots with enough randomness. For example by providing a random seed through different means.
-
-Although these problem have been documented since a long time (see [7] and [8]),
-there's not much done to tackle the problem. We looked at notes and research from LiveCD OS's and supply them here for completements sake. Whonix has a [wiki
-page](https://www.whonix.org/wiki/Dev/Entropy) with some notes, and Qubes has tickets
-about this.
-
-The Qubes tickets can be found at footnotes [3],[4],[5] and [6] for more information.
+user land to the Linux kernel Cryptographically Secure Pseudo Random Number
+Generator (CSPRNG). This generator is used for almost every security protocol,
+like TLS/SSL key generation, choosing TCP sequences, ASLR offsets, and GPG key
+generation [1]. In order for this CSPRNG to be really cryptographically secure,
+it's recommended to seed it with a 'good' entropy source, even though The Linux
+kernel collects entropy from several sources, for example keyboard typing,
+mouse movement, among others.
+
+Because of the Tails nature of being amnesic, and run from different type of
+live devices (from DVDs to USB sticks), special care must be taken to ensure
+the system still gets enough entropy and boots with enough randomness. This is
+not easy in the Tails context, where the system is almost always booting the
+same way. Even the squashfs file is ordered to optimize boot time.
+
+Although these problem have been documented since a long time (see [7] and
+[8]), there's not much done to tackle the problem. We looked at notes and
+research from LiveCD OS's and supply them here for completements sake. Whonix
+has a [wiki page](https://www.whonix.org/wiki/Dev/Entropy) with some notes, and
+Qubes has tickets about this ([3],[4],[5] and [6]).
## Current situation
See the related [[design document|contribute/design/random]]
-Tails has stopped shipping /var/lib/urandom/random-seed, since it is a fixed known value
-for every Tails installation which means its entropy contribution is zero.
+Tails do not ship /var/lib/urandom/random-seed in the ISO, since it means
+shipping a fixed known value for every Tails installation which means its
+entropy contribution is zero, and breaks reproducibility of the ISO image.
-Without this random seed, systemd-random-seed load won't write anything to
-/dev/urandom (so we rely purely on the kernel and current system entropy to get
-/dev/urandom). This new behavior can't be much worse, and the fact it's the new
-debootstrap and systemd default behavior tends to be reassuring.
+Without this random seed, systemd-random-seed won't write anything to
+/dev/urandom, so we rely purely on the kernel CSPRNG and current system entropy
+to get /dev/urandom. It's commonly admitted to be quite good, but given the
+Live nature of Tails, and the fact that good cryptography is a must, we may
+want to add additional measures to ensure any Tails system has enough entropy.
-Tails also ships Haveged since a while, and rngd since 2.6. Note that in
-Stretch, Haveged will be started very early at boot time (after the apparmor
-profiles loading), before any userland application needs randomness. Still there
-are concerns about Haveged's reliability to provide cryptographically secure
-randomness.
+Tails ships Haveged and rngd since a while. Still there are concerns about
+Haveged's reliability to provide cryptographically secure randomness, and rngd
+is only really useful when random generator devices are used.
-So the situation may not be that bad, but given the Live nature of Tails,
-and the fact that good cryptography is a must, we may want to add additional
-measures to ensure any Tails system has enough entropy.
+Taking other measures to seed the Linux Kernel CSPRNG with good material is
+something worst spending efforts on.
## Use cases
-We have several use cases, which may require different solutions, depending on
-how the Tails OS is installed.
+Tails is used in different ways with different live devices. That requires
+different solutions, depending on how and what the Tails OS is installed.
### DVD
@@ -62,7 +62,7 @@ So we may eventually just document somewhere to users that they MUST NOT use
this type of installation if they want to rely on good cryptograpy for their
communications and key generation, or that they should wait after having
interacting a long (but hard to define) time with the system so that it had time
-to collect entropy, and does not rely on Haveged + rngd only.
+to collect entropy, and does not rely on the CSPRNG, Haveged and rngd only.
We could also add some kind of notification to users when entropy gets too low,
or just saying them that the way they use Tails is not compatible with strong
@@ -81,16 +81,16 @@ seed, and adding one is very difficult if not impossible (except with the
Windows installation where we may ask upstream to implement that in the
Universal USB Installer, but well...).
-That's also not really the way we push to users to use Tails, so as with DVD
+That's also not really the way we encourge users to use Tails, so as with DVD
there's maybe no point to fix the situation here, and the same workaround could
-may apply.
+be applied (document it).
### Final USB
That's supposed to be the standard way to use Tails.
-Note that in this case, there are two situations: using this installation with
-persistence enabled, and without.
+Note that in this case, there are two situations: booting this installation
+with persistence enabled, and without.
It is worth noting too that the first time this Tails installation is booted,
most of the time the first step is to configure persistence, which means
@@ -99,7 +99,7 @@ probably very little entropy, so this may weaken the LUKS volume encryption.
### Virtual Machines
-That's a way to use Tails, and one of the worste cases: it is of public
+That's a way to use Tails, and one of the worst cases: it is of public
knowledge that entropy in VMs is very poor. It's not really clear how the
entropy gathering daemons we have would help, but there are mechanisms now in
libvirt to pass randomness from the host using the Virtio RNG feature (even if
@@ -109,37 +109,37 @@ it may not be enough by itself).
### Persist entropy pool seeds [[!tails_ticket 7675]]
-We hope to improve this situation for users who enable the persistence storage
-option using some randomness from the previous session to help bootstrap with
-some "well" generated randomness.
+We hope to improve this situation for users who enable the persistent storage
+option by storing a seed from the previous session to help bootstrap
+with some "well" generated randomness.
Storing it in the persistent partition will be implemented using a default
-hidden persistence setting. But it does not solve the problem for the first time
-Tails is booted, which is likely when the encrypted persistence partition is
-created.
+(hidden to the user) persistence setting. But it does not solve the problem for
+the first time Tails is booted, which is likely when the encrypted persistence
+partition is created.
### Use the Tails installer to create a better seed [[!tails_ticket 11897]]
Tails installer can be used on Debian and Ubuntu, and is the tool people
running OSX or Windows are told to use to install their final Tails
-USB stick with.
+USB stick with, by using an intermediary Tails to create the final USB.
Tails installer could store a seed in the FAT filesystem of the system
partition. That would workaround this first boot problem not handled by the
persistence option.
We can't sadly update this seed while running Tails, as mounting RW the system
-FAT partition at that moment does not work. So we'll have to update it at the
-system shutdown. This will mean remount this partition, write the new random
-seed, then unmount it and start the shutdown of the system. Obviously we can
-do this only in normal shutdown process, and will have to avoid it in emergency
-shutdown mode.
+FAT partition during a Tails session does not work. So the question whether updating it
+or not is open.
-Using this in addition to the persistent seed mentionned above may thus be the
-way to go.
+If we want to do so, we'll have to update it at the system shutdown. This will
+mean remount this partition, write the new random seed, then unmount it and
+start the shutdown of the system. Obviously we can do this only in normal
+shutdown process, and will have to avoid it in emergency shutdown mode.
-This solution is partial since it only works for Tails Installer+USB stick, and
-we don't know if and how we will use the Tails installer in the future (see [[!tails_ticket 11679]]).
+We may alternatively not update it, and use it only when the persistence is not
+enabled. That would still be a unique source of entropy per Tails installation,
+so that would be a better situation that the current one.
One drawback: this would break the ability to verify this system partition with
a simple shasum operation.
@@ -161,7 +161,8 @@ already](https://volumelabs.net/best-random-data-software/)
Possible candidates:
* [entropy gathering daemon](http://egd.sourceforge.net/): not packaged into Debian.
-* [twuewand](http://www.finnie.org/software/twuewand/): used by Finnix LiveCD, packaged into Ubuntu only.
+* [twuewand](http://www.finnie.org/software/twuewand/): used by Finnix LiveCD
+ (so made for this kind of environment), packaged into Ubuntu only.
* [timer entropy daemon](https://www.vanheusden.com/te/): not packaged into Debian
* randomsound: probably a bad idea in the Tails context as we're discussing a
Greeter option to deactivate the microphone.
@@ -185,7 +186,9 @@ on average how much time that blocking would last. [Sycamoreone] [[!tails_ticket
An idea that has been mentioned several time is to have a service that
check if the available entropy is high enough, and notify the user if
-it's not the case.
+it's not the case. One downside, is that observing the entropy pool costs
+randomness, so this may have to be implemented with care or is worth
+discussing/researching the costs/benefits.
## Related tickets
diff --git a/wiki/src/blueprint/remember_installed_packages.mdwn b/wiki/src/blueprint/remember_installed_packages.mdwn
index 2f4ce35..3b77456 100644
--- a/wiki/src/blueprint/remember_installed_packages.mdwn
+++ b/wiki/src/blueprint/remember_installed_packages.mdwn
@@ -1,3 +1,8 @@
+<div class="note">
+[[blueprint/additional_software__packages]] overlaps with
+this blueprint.
+</div>
+
When user have enabled persistence, it could be nice to remember which
extra packages they have installed.
diff --git a/wiki/src/blueprint/replace_Pidgin.mdwn b/wiki/src/blueprint/replace_Pidgin.mdwn
index 9613ecd..d5ecf0b 100644
--- a/wiki/src/blueprint/replace_Pidgin.mdwn
+++ b/wiki/src/blueprint/replace_Pidgin.mdwn
@@ -76,7 +76,19 @@ The client must support SASL authentication.
## Tor Messenger ([[!tails_ticket 8577]])
* Documentation, downloads and tickets in Tor's [Trac](https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger)
-* Tor Messenger supports XMPP, IRC and some other protocols.
+* Satisfies all our requirements (listed above, as of commit
+ `8e3157d5f4cd7894bca21adf6b95a6b49d9beb01`) except the TODO about
+ StartTLS (I bet it has the code for it though, since Thunderbird
+ supports it, but I in the GUI there is only "Enable SSL" as options
+ for IRC and XMPP).
+* The GUI is very similar to Pidgin's, which might be a bonus point
+ since we are looking for a "Pidgin replacement".
+* It has support for "temporary XMPP accounts" that require no
+ registration (no user input!) which would be useful for our support
+ channel (see [[!tails_ticket 11307]]).
+* FWIW: Tor Messenger got 30K USD funding in 2017!
+* FWIW: anonym has been happy using it exclusively for chatting since
+ September, 2016.
## CoyIM (based on xmpp-client) ([[!tails_ticket 8574]])
diff --git a/wiki/src/blueprint/survey_platform.mdwn b/wiki/src/blueprint/survey_platform.mdwn
index 39a4fee..e071dba 100644
--- a/wiki/src/blueprint/survey_platform.mdwn
+++ b/wiki/src/blueprint/survey_platform.mdwn
@@ -15,55 +15,92 @@ Requirements
and two attention check questions could be useful but then that's
maybe a bit annoying for humans.
+[[!toc levels="2"]]
+
LimeSurvey
==========
- <https://www.limesurvey.org/>
- PHP + MySQL
+- Demo site: <https://demo.limesurvey.org/>
+- Features: Very complete.
+- Embedding: Works in an iframe but the template would need some
+ adjustment.
+- Captcha: You can add a captcha *before* accessing the survey. I
+ couldn't find how to add a captcha right before submitting.
+- Versions and packaging: Daily "stable" releases in ZIP files. LTS and
+ "one-click" auto-upgrade for pay.
+
+Basic form builders
+===================
-- WordPress plugin: <https://wordpress.org/plugins/surveypress/>
-- Drupal plugin: <https://www.drupal.org/project/limesurvey_sync>
+TellForm
+--------
-Quick Survey
-============
+- <http://www.tellform.com/>
+- NodeJS
+- Demo site: <https://admin.tellform.com>
+- Features: Basic.
+- Embedding: Offers an iframe but the SSL is broken on the demo site.
+- Captcha: No.
+- Versions and packaging: One Alpha release on GitHub from April 2016.
+ Docker image advertised on the website.
-- <https://apps.sandstorm.io/app/wupmzqk4872vgsye9t9x5dmrdw17mad97dk21jvcm2ph4jataze0>
-- Sandstorm app
+Kinto
+-----
-- https://www.fourmilieres.net/#/
+- <https://www.fourmilieres.net/>
+- Python + PostgreSQL
+- Demo site: <https://www.fourmilieres.net/#/>
+- Features: Basic.
+- Embedding: Not specified.
+- Captcha: No.
+- Versions and packaging: Several releases per month on GitHub. Docker
+ image advertised on the website.
SumoSurvey
-==========
+----------
- <https://github.com/mattjdev/sumosurvey>
- NodeJS + MySQL
+- Demo site: <https://sumosurvey.herokuapp.com/>
+- Features: Very basic.
+- Embedding: Not specified.
+- Captcha: No.
+- Versions and packaging: Zero releases on GitHub.
-Kinto
-=====
-
-- <https://www.fourmilieres.net/>
-- Python + PostgreSQL
-
-Webform
+Weirdos
=======
-- <https://www.drupal.org/project/webform>
-- Drupal plugin
-- Framaforms: <https://framaforms.org/>
-
-TellForm
-========
+Ikiwiki
+-------
-- <http://www.tellform.com/>
-- NodeJS
+- <https://ikiwiki.info/ikiwiki/directive/poll/>
+- Features: Very basic, only multiple choices with public stats.
+- Embedding: in ikwiki yes :)
+- Captcha: No.
Formr
-=====
+-----
- <https://formr.org/>
- PHP
+- Demo site: <https://formr.org/>
+- Features: Couldn't create a survey from the demo website. Not very
+ promising...
+- Embedding: Not specified.
+- Captcha: Unclear.
-Ikiwiki
-=======
+Plugins for other web applications
+==================================
-- <https://ikiwiki.info/ikiwiki/directive/poll/>
+Quick Survey (Sandstorm)
+------------------------
+
+- <https://apps.sandstorm.io/app/wupmzqk4872vgsye9t9x5dmrdw17mad97dk21jvcm2ph4jataze0>
+
+Webform (Drupal)
+----------------
+
+- <https://www.drupal.org/project/webform>
+- Framaforms: <https://framaforms.org/>