summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/src/blueprint')
-rw-r--r--wiki/src/blueprint/Linux_containers.mdwn2
-rw-r--r--wiki/src/blueprint/Port_Tails_Installer_to_OS_X.mdwn2
-rw-r--r--wiki/src/blueprint/UX_roadmap.mdwn14
-rw-r--r--wiki/src/blueprint/backups.mdwn8
-rw-r--r--wiki/src/blueprint/backups/Duplicate.desktop9
-rw-r--r--wiki/src/blueprint/backups/duplicate.bash161
-rw-r--r--wiki/src/blueprint/bootstrapping.mdwn4
-rw-r--r--wiki/src/blueprint/bootstrapping/installer.mdwn22
-rw-r--r--wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn45
-rw-r--r--wiki/src/blueprint/intercept_interviews.mdwn2
-rw-r--r--wiki/src/blueprint/l10n_Italian.mdwn21
-rw-r--r--wiki/src/blueprint/monthly_meeting.mdwn5
-rw-r--r--wiki/src/blueprint/monthly_report.mdwn4
-rw-r--r--wiki/src/blueprint/monthly_report/report_2017_06.mdwn256
-rw-r--r--wiki/src/blueprint/monthly_report/report_2017_07.mdwn33
-rw-r--r--wiki/src/blueprint/usb_install_and_upgrade/future_spec.mdwn4
-rw-r--r--wiki/src/blueprint/vagrant-libvirt.mdwn10
-rw-r--r--wiki/src/blueprint/web_browser_profile_with_no_CA.mdwn2
18 files changed, 294 insertions, 310 deletions
diff --git a/wiki/src/blueprint/Linux_containers.mdwn b/wiki/src/blueprint/Linux_containers.mdwn
index e7a9e84..a39a76f 100644
--- a/wiki/src/blueprint/Linux_containers.mdwn
+++ b/wiki/src/blueprint/Linux_containers.mdwn
@@ -109,7 +109,7 @@ Running GUI applications in containers
* [Subuser](http://subuser.org/): essentially Docker + Xpra
* [GNOME sandboxed
applications](https://wiki.gnome.org/Projects/SandboxedApps), aka.
- Flatpack (formerly `xdg-app`); their concept of "portals" is very interesting.
+ Flatpak (formerly `xdg-app`); their concept of "portals" is very interesting.
- [GNOME Developer Experience hackfest: xdg-app + Debian](http://smcv.pseudorandom.co.uk/2016/xdg-app/)
- LWN on [An initial release of Flatpak portals for GNOME](https://lwn.net/Articles/694291/)
- [The flatpak security model – part 1: The basics](https://blogs.gnome.org/alexl/2017/01/18/the-flatpak-security-model-part-1-the-basics/)
diff --git a/wiki/src/blueprint/Port_Tails_Installer_to_OS_X.mdwn b/wiki/src/blueprint/Port_Tails_Installer_to_OS_X.mdwn
index 4ca6162..2a3bd26 100644
--- a/wiki/src/blueprint/Port_Tails_Installer_to_OS_X.mdwn
+++ b/wiki/src/blueprint/Port_Tails_Installer_to_OS_X.mdwn
@@ -1,6 +1,6 @@
# Introduction
-This is an on-going feasibility on how to port the Tails Installer to the Mac OS X operating system.
+This is an on-going feasibility on how to port the Tails Installer to the macOS operating system.
## Considerations
diff --git a/wiki/src/blueprint/UX_roadmap.mdwn b/wiki/src/blueprint/UX_roadmap.mdwn
index a7dd540..5df94aa 100644
--- a/wiki/src/blueprint/UX_roadmap.mdwn
+++ b/wiki/src/blueprint/UX_roadmap.mdwn
@@ -11,7 +11,7 @@ We organized several workshops at NUMA to improve the usability of Tails. We rea
- to install Tails;
- to boot Tails.
-We want to improve this situation.
+We want to improve this situation.
First-time visitors on the Tails website should be able to enjoy a consistent experience, from understanding if Tails is the right tool for them, to achieving their actual goals by using it.
@@ -44,9 +44,9 @@ Next
* Screen locker [[!tails_ticket 5684]]
* User-friendly backup system [[!tails_ticket 5301]]
* Localized clock [[!tails_ticket 6284]]
-* Tails Installer on Mac OS X [[!tails_ticket 8559]]
+* Tails Installer on macOS [[!tails_ticket 8559]]
* OpenPGP Applet [[!tails_ticket 7778 ]]
-* Shut down [[!tails_ticket 5417 ]]
+* Shut down [[!tails_ticket 5417 ]]
2. Installation
@@ -55,7 +55,7 @@ Next
A big work in done in 2015 to [[improve the installation workflow|blueprint/bootstrapping/]].
1. Refactor the installation documentation and add visual aids.
-2. Automatic ISO verification [[!tails_ticket 7552]]
+2. Automatic ISO verification [[!tails_ticket 7552]]
3. Multiplatform installer [[!tails_ticket 7544]]
In 2016, we want to go on:
@@ -105,9 +105,3 @@ Depending on grants and availibilities, here are the big steps we could do:
-----------
- 2018 : Promote Tails outside of the website, regarding the differents people and use cases where Tails could be usefull.
-
-
-
-
-
-
diff --git a/wiki/src/blueprint/backups.mdwn b/wiki/src/blueprint/backups.mdwn
index 84160d1..f2cf665 100644
--- a/wiki/src/blueprint/backups.mdwn
+++ b/wiki/src/blueprint/backups.mdwn
@@ -76,7 +76,7 @@ Pros:
Cons:
- Uses duplicity as back end with the following drawbacks:
- - It forces full backups no and then making them unexpectedly
+ - It forces full backups now and then, making them unexpectedly
extremelly slower than regular incremental ones.
- Restoring a single file is slow.
- Impossible to navigate the file system, either of the last or past
@@ -308,3 +308,9 @@ Implementation
- Write the code in GTK3 for Tails 1.1 which will be the next major release,
based on Debian Wheezy.
+
+Script by a2
+============
+
+- [[Duplicate.desktop]]
+- [[duplicate.bash]]
diff --git a/wiki/src/blueprint/backups/Duplicate.desktop b/wiki/src/blueprint/backups/Duplicate.desktop
new file mode 100644
index 0000000..0275beb
--- /dev/null
+++ b/wiki/src/blueprint/backups/Duplicate.desktop
@@ -0,0 +1,9 @@
+[Desktop Entry]
+Encoding=UTF-8
+Name=Duplicate Tails USB Drive
+Comment=Launch DirSyncPro
+Exec=gnome-terminal -e "sudo /home/amnesia/Persistent/.duplicate.bash 2>/dev/null"
+Icon=media-removable
+Type=Application
+GenericName[en_US.UTF-8]=Duplicate Entire USB Drive
+Comment[en_US.UTF-8]=
diff --git a/wiki/src/blueprint/backups/duplicate.bash b/wiki/src/blueprint/backups/duplicate.bash
new file mode 100644
index 0000000..f6b7c07
--- /dev/null
+++ b/wiki/src/blueprint/backups/duplicate.bash
@@ -0,0 +1,161 @@
+#!/bin/bash
+
+I_DEV=""
+O_DEV=""
+OUSB=""
+IUSB=""
+
+#
+# only root can run
+#
+if [ `whoami` != "root" ];then
+ zenity --title="Insufficient Permission" \
+ --info --text="Only root can run this command; aborting." --timeout=5 2>/dev/null
+ exit 1
+fi
+
+zenity --title="Close all programs" \
+ --info \
+ --text="It is strongly recommended you close all programs before starting the duplication process.\nIt typically takes 30 minutes or more to complete.\n\nPlease close any running programs now and Click OK to continue." 2>/dev/null
+
+
+#
+# Find USB drives.
+# default first one is the INPUT and the SECOND is backup
+#
+for d in `readlink -e /dev/disk/by-id/usb*0:0|sort`; do
+ if [ "$I_DEV" = "" ];then
+ I_DEV="TRUE $d"
+ else
+ # If there are more than two USB drives, create a list
+ I_DEV="$I_DEV FALSE $d"
+ fi
+done
+
+#
+# select the input device, set IUSB
+IUSB=`zenity --title="Select Source Device" \
+ --list \
+ --radiolist \
+ --text="Select Source USB Device" \
+ --column="Select" \
+ --column="Device" \
+ $I_DEV 2>/dev/null`
+
+if [ $? -ne 0 ];then
+ zenity --title="Aborting..." \
+ --info \
+ --text="Duplication Aborted, no source device selected." --timeout=5 2>/dev/null
+ exit 1;
+fi
+
+#
+# Confirm IUSB is the boot device!
+#
+udevadm info $IUSB |grep -q "^S: TailsBootDev"
+if [ $? -ne 0 ];then
+ zenity --title="Invalid Source" \
+ --question \
+ --text="WARNING: Source Device, $IUSB, is not bootable.\nPlease confirm you want to duplicate another USB drive." 2>/dev/null
+ if [ $? -ne 0 ];then
+ zenity --title="Aborting..." \
+ --info --text="Aborted, did not confirm source device: $IUSB" --timeout=5 2>/dev/null
+ exit 1
+ fi
+fi
+
+## Now, get the Output device list
+## excluding the selected one from the target
+for d in `readlink -e /dev/disk/by-id/usb*0:0|sort`; do
+ if [ "$d" = "$IUSB" ];then
+ : ;
+ elif [ "$O_DEV" = "" ];then
+ O_DEV="TRUE $d"
+ else
+ # If there are more than two USB drives, create a list
+ O_DEV="$O_DEV FALSE $d"
+ fi
+done
+if [ "$O_DEV" = "" ];then
+ zenity --title="Aborting..." \
+ --info \
+ --text="Aborted, no valid target device found." \
+ --timeout=10 2>/dev/null
+ exit 1
+fi
+
+
+OUSB=`zenity --title="Select Target Device" \
+ --list \
+ --radiolist \
+ --text="Select Target USB Device" \
+ --column="Select" \
+ --column="Device" \
+ $O_DEV 2>/dev/null`
+
+if [ $? -ne 0 ];then
+ zenity --title="Aborting..." \
+ --info \
+ --text="Duplication Aborted, no target device selected." \
+ --timeout=5 2>/dev/null
+ exit 1;
+fi
+
+#
+# Check OUSB boot status!
+#
+udevadm info $OUSB |grep -q "^S: TailsBootDev"
+if [ $? -eq 0 ];then
+ zenity --title="Invalid Target" \
+ --question \
+ --text="WARNING: Target Device, $OUSB, is bootable.\nPlease confirm you want to clobber your current boot device!!!\n\nWARNING: NOT RECOMMENDED! Abort Recommended (click No)." 2>/dev/null
+ if [ $? -ne 0 ];then
+ zenity --title="Aborting..." \
+ --info --text="Aborted, did not confirm target device: $OUSB" --timeout=5 2>/dev/null
+ exit 1
+ fi
+fi
+#
+# Confirm , are you sure you want to proceed? really?
+#
+zenity --title="WARNING: Please confirm" \
+ --question \
+ --default-cancel \
+ --text="WARNING! WARNING!! WARNING!!! \n\nAll contents on $OUSB will be lost!\n\nClick 'Yes' to start duplication of $IUSB to $OUSB!\n" 2>/dev/null
+
+if [ $? -eq 0 ];then
+ ###
+ ### Well ok, HERE WE GO! Let the backup begin!!!
+ ###
+ sync;
+ s=`date`
+ (sleep 2;dd if=${IUSB} of=${OUSB} bs=8M) |
+ zenity --progress \
+ --title="Duplicating $IUSB to $OUSB in progress..." \
+ --pulsate \
+ --text="Please be patient.\nThe Duplication can take 30 minutes or more.\nStarted at: ${s}" \
+ --auto-kill --auto-close 2>/dev/null
+ DDRESULT=$?
+ e=`date`
+
+ ###
+ ### all done!
+ ###
+ if [ ${DDRESULT} -eq 0 ];then
+ result="Succeeded."
+ else
+ result="Aborted, $OUSB very likely corrupted."
+ fi
+ # report the resulrts...
+ zenity --title="Duplication Complete" \
+ --info \
+ --text="Duplication ${result}\nStarted: ${s}\nEnded: ${e}" 2>/dev/null
+ exit 0
+
+elif [ $? -eq 1 ];then
+ # phew! dodged a bullet!
+ zenity --info \
+ --text="Duplication Aborted, no changes were made." \
+ --timeout=5 2>/dev/null
+ exit 1
+fi
diff --git a/wiki/src/blueprint/bootstrapping.mdwn b/wiki/src/blueprint/bootstrapping.mdwn
index 6f7df77..c6326c9 100644
--- a/wiki/src/blueprint/bootstrapping.mdwn
+++ b/wiki/src/blueprint/bootstrapping.mdwn
@@ -61,7 +61,7 @@ Notes:
- **Debian** is a path for Debian derivatives where Tails Installer is
available. That will be the case of Ubuntu starting from 15.10,
Debian Jessie backports, and Debian Stretch ([[!tails_ticket 8805]]).
-- **Other OS** is Windows, Mac OS X, Fedora, etc.
+- **Other OS** is Windows, macOS, Fedora, etc.
- **OpenPGP with Debian keyring** are command line instructions for verifying the
Tails signing key against the Debian keyring.
- **Extension from Debian** takes for granted that the ISO verification
@@ -122,7 +122,7 @@ The comments, placed after ':' correspond to our rough objectives for
- Next LTS, 16.04: Tails Installer? [[!tails_ticket 8806]]
- Next, 15.10: Tails Installer? [[!tails_ticket 8806]]
- Windows: UUI
- - Mac OS X: command line or new graphical tool? [[!tails_ticket 8802]]
+ - macOS: command line or new graphical tool? [[!tails_ticket 8802]]
- Virtualization: VirtualBox, GNOME Boxes, virt-manager
- Upgrade from ISO (full upgrade or nightly)
- Full upgrade
diff --git a/wiki/src/blueprint/bootstrapping/installer.mdwn b/wiki/src/blueprint/bootstrapping/installer.mdwn
index e590eb0..4a02122 100644
--- a/wiki/src/blueprint/bootstrapping/installer.mdwn
+++ b/wiki/src/blueprint/bootstrapping/installer.mdwn
@@ -16,7 +16,7 @@ requires having two USB sticks and going through manual installation
steps, often using command line.
We want to eliminate the need for a first temporary Tails and have Tails
-Installer available on Linux, Windows, and Mac OS.
+Installer available on Linux, Windows, and macOS.
As part of the ISO verification process we also want to push more
verification logic to Tails Installer. See the [[blueprint on ISO
@@ -34,8 +34,8 @@ Roadmap
----
In 2015 we will work on porting Tails Installer to Debian. This is a
-first step before having Tails available on any other platform.
-This requires rethinking the scenarios in which Tails Installer is
+first step before having Tails available on any other platform.
+This requires rethinking the scenarios in which Tails Installer is
used ([[!tails_ticket 7046]]) and adapting its interface accordingly.
Those are the improvements that we propose for 2015:
@@ -67,22 +67,22 @@ First of all:
2. Simplify the splash screen a bit thanks to the autodetection code:
merge "Clone and Install" and "Clone and Upgrade" into one single
"Clone" button: Depending on whether the destination device already
- has Tails installed or not, dynamically change the label of main
+ has Tails installed or not, dynamically change the label of main
action button to "Install" or "Upgrade" (for the second device).
- (Note: this breaks the "re-installing Tails from scratch" use case,
- but IIRC we already have documented how to uninstall Tails, so that's
+ (Note: this breaks the "re-installing Tails from scratch" use case,
+ but IIRC we already have documented how to uninstall Tails, so that's
no big deal). ([[!tails_ticket 9006]])
3. If the destination device already has Tails installed, add a second
- button below or side-by-side with the "Install" button with the label
- "Upgrade". This allows to choose once more to either reinstall Tails
+ button below or side-by-side with the "Install" button with the label
+ "Upgrade". This allows to choose once more to either reinstall Tails
from scratch or to upgrade the exisiting installation.
4. When using the installer in Tails (as opposed to using the installer
- from another platform), remove the splash screen and add a "Clone"
+ from another platform), remove the splash screen and add a "Clone"
button to the main interface. ([[!tails_ticket 8859]])
And then:
-- If using the installer outside of Tails, point to the website to
+- If using the installer outside of Tails, point to the website to
download the ISO. ([[!tails_ticket 8867]])
- Make it possible to "Upgrade from ISO" from
the command line. See the [[Debian Hacker|bootstrapping#tools]] bootstrapping path. ([[!tails_ticket 8861]])
@@ -90,7 +90,7 @@ And then:
the command line. See the [[Debian Hacker|bootstrapping#tools]] bootstrapping path. ([[!tails_ticket 8861]]).
- Store version of Tails on destination key after install and upgrade. ([[!tails_ticket 8863]])
- This would allow to display version in "Target Device". ([[!tails_ticket 8862]])
-- Have Tails Installer available on Mac OS as there is currently no suitable other
+- Have Tails Installer available on macOS as there is currently no suitable other
installation technique using a graphical interface.
Future
diff --git a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
index 1d52bb3..b71bf68 100644
--- a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
+++ b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
@@ -124,5 +124,48 @@ Cons:
* We need to learn how to manage systems in the cloud, how to deal
with billing, and how to control these systems from Jenkins.
- * On-going cost: XXX (unknown so far, would need to be researched)
+ * On-going cost: XXX (unknown so far, would need to be researched);
+ very rough estimate, assuming 1. we run all ISO builds and tests on
+ EC2 `m4.xlarge` instances; 2. they perform exactly like my local
+ Jenkins (i7-6770HQ, 2.60GHz); and 3. [[!tails_ticket 12576]] is
+ fixed:
+
+ - builds & tests as usual so far: (35 minutes per build + 105 minutes
+ per test suite run) / 60 * 700 builds+tests * $0.2 = $327/month
+ - second build for reproducibility ([[!tails_ticket 13436]]):
+ 35 minutes / 60 * 200 builds * $0.2 = $23 / month
+ - total = $350 / month
+
+ Now, to be more accurate:
+
+ - we can keep running _some_ of our builds and tests on our own
+ infra instead of on EC2: the
+ [Jenkins EC2 plugin](https://plugins.jenkins.io/ec2) allows
+ starting EC2 instances on demand when the local cluster is
+ overloaded, and shuts them down after a configurable idle time;
+ so basically one option is that EC2 would only be used during
+ burst periods;
+ - this assumes we run nightly.t.b.o on EC2 too, which adds to the
+ cost (instance + storage + data transfer to the Internet);
+ otherwise uploading build artifacts to lizard adds to the costs;
+ - booting the VM from its persistent root volume and updating it
+ takes some additional billed time;
+ - storage (EBS) costs money on top of that; the more data we share
+ between instances (e.g. root volume, Vagrant baseboxes), the
+ less it costs; to give an idea, if we stored all the data of our
+ 4 isobuilders + 6 isotesters + nightly.t.b.o there without
+ sharing anything at all, i.e. the worst case scenario that's
+ highly unlikely (at least the scratch space to build Vagrant
+ baseboxes should be easy to share, and the root volumes
+ shouldn't be much of a problem either):
+ (32.5 * 4 + 11 * 6 + 300) * $0.10/GB/month = $50/month
+ - likely these instances will be faster than my local Jenkins,
+ thanks to higher CPU clock rate, which should save some money;
+ only actual testing will give us more precise numbers.
+ - more powerful instance types might save money as well, and
+ improve developer experience BTW: e.g. `c4.2xlarge` for ISO
+ builds, if they are more than twice faster, given they cost
+ a bit less than twice more. Here again, only actual testing will
+ give us more precise numbers.
+
* We need to trust a third-party somewhat.
diff --git a/wiki/src/blueprint/intercept_interviews.mdwn b/wiki/src/blueprint/intercept_interviews.mdwn
index 4c7e0e7..69f62ca 100644
--- a/wiki/src/blueprint/intercept_interviews.mdwn
+++ b/wiki/src/blueprint/intercept_interviews.mdwn
@@ -26,6 +26,8 @@ Interview script
- Introduction
- Who I am, what I am doing, and why I'm conducting the interview.
+
+- Getting the interviewee's consent:
- You can answer my questions to the extend that you feel comfortable
and stop at any moment.
- We want to keep this information publicly available for contributors
diff --git a/wiki/src/blueprint/l10n_Italian.mdwn b/wiki/src/blueprint/l10n_Italian.mdwn
index 3c5719d..780cea8 100644
--- a/wiki/src/blueprint/l10n_Italian.mdwn
+++ b/wiki/src/blueprint/l10n_Italian.mdwn
@@ -172,11 +172,11 @@ Crea e configura la partizione resistente attivando le seguenti funzionalità (A
Aggiorna la lista dei pacchetti disponibili, scrivendo in un terminale:
- sudo apt-get update
+ sudo apt update
Installa i seguenti pacchetti:
- sudo apt-get install libyaml-perl libyaml-libyaml-perl po4a \
+ sudo apt install libyaml-perl libyaml-libyaml-perl po4a \
perlmagick libyaml-syck-perl ikiwiki
Clona il nostro repository Git in una cartella della partizione persistente:
@@ -213,12 +213,17 @@ In breve:
* merge dentro master
-Ogni tanto (quando?) si fanno dei pacchi di traduzioni. Un pacco e' un insieme di filename che vanno tradotti. Ogni pacco viene tradotto da una persona.
+Ogni tanto (quando?) si fanno dei pacchi di traduzioni. Un pacco e' un insieme di filename che vanno tradotti. Ogni pacco viene tradotto da una persona. Nell'estate 2017 abbiamo deciso di fare pacchi _piccoli_, in modo da rendere il lavoro più fluido.
+
+### 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"`.
-A questo punto qualcuno deve revisionare la branch. Si fa avanti Laura. Laura fa `git fetch origin && git checkout origin/inferno`. Prima guarda le differenze introdotte da Petrarca, con `git log -p origin/inferno`.
-Gli sembrano ok, ma per controllare che si vedano anche bene nel wiki lo builda con `./build-website` e poi lo guarda da firefox. Nota che Petrarca, sbadato, ha fatto alcuni piccoli errori nel markup del wiki che "rompono" delle immagini. Petrarca aveva tradotto la riga:
+### Revisionare
+
+A questo punto qualcuno deve revisionare la branch. Si fa avanti Laura. Laura manda un'email alla lista dicendo che sta per tradurre la branch `inferno`: la manda non quando decide che vorrebbe farlo, ma proprio un minuto prima di farlo davvero.
+Laura fa `git fetch origin && git checkout origin/inferno`. Prima guarda le differenze introdotte da Petrarca, con `git log -p origin/inferno`.
+Gli sembrano ok, ma per controllare che si vedano anche bene nel wiki va a vedere il sito [[https://tailsit.degenerazione.xyz/branch.html]] e clicca su `origin/inferno`. Così può vedere il risultato della build. Questo è equivalente a "buildare" il wiki localmente con `./build-website`, ma è più rapido e meno soggetto ad errori. Nota che Petrarca, sbadato, ha fatto alcuni piccoli errori nel markup del wiki che "rompono" delle immagini. Petrarca aveva tradotto la riga:
[[!immagine \"caronte.png`"]]
@@ -230,13 +235,15 @@ Laura corregge e fa commit sulla stessa branch `git commit wiki/src/inferno/terz
Non trova altri errori, quindi fa
git checkout master
- git merge inferno
+ git merge --no-ff inferno
Potrebbe subito fare `git push origin master` ma, per non sbagliare, fa un diff:
git diff origin/master..master
-E controlla se tutto torna. Ci sono conflitti? Quel cambiamento al `!img` c'e' ancora? bene, ora possiamo fare
+E controlla se tutto torna. Ci sono conflitti? Quel cambiamento al `!img` c'e' ancora?
+Aspetta qualche minuto e poi torna a guardare il solito [[https://tailsit.degenerazione.xyz/branch.html]] per vedere se si è "preso" il nuovo commit sulla branch inferno. Quando ha fatto (ci può mettere anche 15 minuti a volte) va a guardare se il risultato è anche graficamente corretto. Tutto ok?
+bene, ora possiamo fare
git push origin master
diff --git a/wiki/src/blueprint/monthly_meeting.mdwn b/wiki/src/blueprint/monthly_meeting.mdwn
index ec43d4d..c5b0752 100644
--- a/wiki/src/blueprint/monthly_meeting.mdwn
+++ b/wiki/src/blueprint/monthly_meeting.mdwn
@@ -19,11 +19,8 @@ Availability and plans for the next weeks
Discussions
===========
- - [[!tails_ticket 9900 desc="Improve Website search"]]:
- are we ok with externalising the search feature?
- [[!tails_ticket 12402 desc="Include Yubico Authenticator in Tails"]]
- [[!tails_ticket 12098 desc="Spurious screensaver activation while synchronizing the system clock"]]
- [[!tails_ticket 12437 desc="Save coredumps to a sticky directory"]]
- - [[!tails_ticket 12257 desc="Put a screenshot of Tails one the Tails homepage"]]
- [[!tails_ticket 7439 desc="Decide whether to remove the clock synchronization notification"]]
- - [[!tails_ticket 7224 desc="Link different design documentations from user documentation"]]
+ - [[!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 fa88ed9..11609bd 100644
--- a/wiki/src/blueprint/monthly_report.mdwn
+++ b/wiki/src/blueprint/monthly_report.mdwn
@@ -22,8 +22,8 @@ beginning of May.
- April: spriver
- May: u
- June: intrigeri
- - July: spriver
- - August: sajolida
+ - July: sajolida
+ - August: spriver
- September: emmapeel
Checklist
diff --git a/wiki/src/blueprint/monthly_report/report_2017_06.mdwn b/wiki/src/blueprint/monthly_report/report_2017_06.mdwn
deleted file mode 100644
index f663211..0000000
--- a/wiki/src/blueprint/monthly_report/report_2017_06.mdwn
+++ /dev/null
@@ -1,256 +0,0 @@
-[[!meta title="Tails report for June, 2017"]]
-[[!meta date="2017-07-06 12:34:56 +0000"]]
-
-[[!toc levels=2]]
-
-Releases
-========
-
-* [[Tails 3.0 was released on June 13|news/version_3.0]] (major release).
-
-* Tails 3.1 is [[scheduled for August 8|contribute/calendar]].
-
-Tails 3.0 is the first version of Tails based on Debian 9 (Stretch).
-It brings a completely new startup and shutdown experience, a lot of
-polishing to the desktop, security improvements in depth, and major
-upgrades to a lot of the included software. We cannot list all the
-improvements it brings here (see the
-[[announcement|news/version_3.0]]), but let's still highlight a few
-major changes:
-
-- *Tails Greeter*, the application to configure Tails at startup, has
- been completely redesigned for ease of use.
-- The shutdown experience has also been redesigned in order to be
- more reliable and more discrete.
-- Tails 3.0 works on <span
- class="definition">[[!wikipedia x86-64 desc="64-bit computers"]]</span>
- only and not on 32-bit computers anymore.
-
-Code
-====
-
-Thanks to
-[multiprocess](https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox)
-Firefox, we started working on
-[[!tails_ticket 12679 desc="sandboxing Tor Browser's content renderer processes more strictly with AppArmor"]].
-We now have a working draft and are waiting for our
-[pull request](https://github.com/micahflee/torbrowser-launcher/pull/280)
-to be merged upstream.
-
-We started fixing regressions introduced in Tails 3.0, such as
-[[!tails_ticket 12481 desc="SSH_AUTH_SOCK occasionally not being set in GNOME Terminal"]]
-and
-[[!tails_ticket 12696 desc="Tails Installer rejects working USB drives, pretending they're not removable"]].
-Our Help Desk and Foundation Team met and prioritized the remaining ones
-from a user-centric point of view.
-
-## Reproducible Builds
-
-We are still working on making Tails ISO images build reproducibly.
-We've seen some images build in such a deterministic manner in March and
-even during a testing session. However, in some build environments it
-does not work reliably yet and some new issues have manifested
-themselves which need to be fixed until we can claim that our ISO
-images are really reproducible, such as
-[[!tails_ticket 12641 desc="Comment changes in POT files make ISO non reproducible"]].
-Besides, we need to draw a line wrt. what kind of build environment
-variations we want to support.
-
-Furthermore, we are still working on documenting the new release process and
-verification options for our users
-([[!tails_ticket 12616]], [[!tails_ticket 12629]], [[!tails_ticket 12630]]).
-
-User experience
-===============
-
-- We discussed strategies to [porting our Download and Verify extension
- for Firefox to *Web
- Extensions*](https://mailman.boum.org/pipermail/tails-ux/2017-June/003394.html),
- a requirement for the upcoming Firefox 57 (November 14), as this will
- affect the design of our download instructions.
-
-- We finished the redesign of *Tails Installer* to get rid of the
- initial splash screen. ([[!tails_ticket 8859]])
-
-- We installed a [prototype of
- *Piwik*](https://mailman.boum.org/pipermail/tails-ux/2017-June/003398.html),
- a free web analytics platform, to evaluate how well it would work
- against our privacy constraints and metrics needs.
-
-- We agreed on increasing the size of the system partition from 2.5 to 4
- GiB minimum starting from Tails 3.2 (October 3) to allow for more
- automatic upgrades before a manual upgrade is needed. ([[!tails_ticket
- 12705]])
-
-Infrastructure
-==============
-
-## Improving communication & transparency wrt. our core teams' priorities
-
-We have
-[set up](https://mailman.boum.org/pipermail/tails-project/2017-June/000873.html)
-some infrastructure bits so that all contributors have more visibility
-and power over our core teams's priorities.
-
-## HTTPS mirror pool
-
-We've switched our mirror pool to mirrors serving files over HTTPS
-only ([[!tails_ticket 12837]]). Our round-robin fallback DNS
-pool is still serving files over HTTP, and we are currently thinking
-about how to switch those to HTTPS too ([[!tails_ticket 12833]]).
-
-## Reproducible builds
-
-Remaining issues on our CI infrastructure include:
-
-* [[!tails_ticket 12618 desc="Retrieving ISO build artifacts sometimes fails on Jenkins"]]
-* [[!tails_ticket 13302 desc="/var/lib/libvirt/images sometimes gets filled on isobuilders, take 2"]]
-* [[!tails_ticket 12595 desc="Not enough space in /var/lib/jenkins on isobuilders"]]
-* [[!tails_ticket 12681 desc="reproducibly_build_Tails_ISO_* Jenkins jobs are buggy when building from a tag"]]
-
-## Sysadmin
-
-We [[!tails_ticket 13232 desc="kept our systems up and running"]],
-which was not always easy since we've deployed our updated
-infrastructure for reproducible builds before upgrading our capacity
-accordingly, not mentioning a kernel regression caused by the initial
-*Stack Clash* fix that broke our CI.
-
-We deployed [[!tails_ticket 11523 desc="some"]]
-[[!tails_ticket 5894 desc="work"]] done by groente, who is in the
-process of joining our sysadmin team.
-
-## tails-support mailing list
-
-We closed the [[`tails-support@boum.org` mailing
-list|news/closing_tails-support]].
-
-Funding
-=======
-
-- We've created a page listing our partners, previous and current [[grants, private companies and individuals who help keep Tails alive|partners]] by supporting us financially. [[Do you want to partner with us too?|partners/become]]
-
-- We are making good progress on our proposal with OTF, and we hope
- we'll be able to share great news soon :)
-
-- We kept working on migrating our European fiscal sponsor from Zwiebelfreunde
- to [CCT, the Center for the Cultivation of Technology](https://techcultivation.org/).
-
-- We have bootstrapped a process to do our budget forecasting for next year.
-
-Outreach
-========
-
-Past events
------------
-
-* Tails was presented at
- [Pas Sage en Seine Festival](https://passageenseine.fr/), in
- Choisy-Le-Roi, France.
-* Tails was presented (among other tools) in an
- [independent journalists event](http://48h.pigiste.org/) in
- Rennes, France.
-* Tails 3 was presented at the annual festivities of the
- [EKH](http://med-user.net/~ekh/) in Vienna, Austria
-
-Upcoming events
----------------
-
-* Tails contributors will attend
- [DebConf17](https://debconf17.debconf.org/), the annual conference
- for Debian contributors and users interested in improving Debian.
-
-* A Tails contributor proposed a talk about Tails for the
- [BalCCon2k17](https://2k17.balccon.org/index.php?title=BalCCon2k17)
- (Balkan Computer Congress).
-
-On-going discussions
-====================
-
-XXX: Link to the thread on <https://mailman.boum.org/pipermail/tails-XXX/>.
-
-Press and testimonials
-======================
-
-The Tails 3.0 release was abundantly covered on the web.
-
-Translation
-===========
-
-## All programs
-
- - ar: 47 translated messages, 9 fuzzy translations, 6 untranslated messages.
- - az: 47 translated messages, 9 fuzzy translations, 6 untranslated messages.
- - bg: 62 translated messages.
- - ca: 62 translated messages.
- - cs: 54 translated messages, 6 fuzzy translations, 2 untranslated messages.
- - cy: 44 translated messages, 11 fuzzy translations, 7 untranslated messages.
- - da: 62 translated messages.
- - de: 62 translated messages.
- - el: 62 translated messages.
- - en_GB: 62 translated messages.
- - es: 62 translated messages.
- - es_AR: 62 translated messages.
- - fa: 62 translated messages.
- - fi: 62 translated messages.
- - fr: 62 translated messages.
- - fr_CA: 62 translated messages.
- - he: 54 translated messages, 6 fuzzy translations, 2 untranslated messages.
- - hr_HR: 62 translated messages.
- - hu: 62 translated messages.
- - id: 62 translated messages.
- - is: 62 translated messages.
- - it: 62 translated messages.
- - ja: 62 translated messages.
- - km: 45 translated messages, 11 fuzzy translations, 6 untranslated messages.
- - ko: 62 translated messages.
- - lv: 62 translated messages.
- - nb: 62 translated messages.
- - nl: 62 translated messages.
- - nn: 62 translated messages.
- - pl: 62 translated messages.
- - pt: 62 translated messages.
- - pt_BR: 62 translated messages.
- - ro: 62 translated messages.
- - ru: 62 translated messages.
- - sk: 54 translated messages, 6 fuzzy translations, 2 untranslated messages.
- - sk_SK: 62 translated messages.
- - sl_SI: 47 translated messages, 9 fuzzy translations, 6 untranslated messages.
- - sq: 62 translated messages.
- - sr: 54 translated messages, 6 fuzzy translations, 2 untranslated messages.
- - sv: 62 translated messages.
- - tr: 62 translated messages.
- - uk: 62 translated messages.
- - vi: 62 translated messages.
- - zh: 0 translated messages, 62 untranslated messages.
- - zh_CN: 62 translated messages.
- - zh_HK: 62 translated messages.
- - zh_TW: 62 translated messages.
-
-## All the website
-
- - de: 57% (2863) strings translated, 6% strings fuzzy, 51% words translated
- - fa: 43% (2162) strings translated, 9% strings fuzzy, 46% words translated
- - fr: 89% (4428) strings translated, 1% strings fuzzy, 87% words translated
- - it: 31% (1547) strings translated, 4% strings fuzzy, 27% words translated
- - pt: 26% (1335) strings translated, 8% strings fuzzy, 23% words translated
-
-Total original words: 52933
-
-## [[Core pages of the website|contribute/l10n_tricks/core_po_files.txt]]
-
- - de: 78% (1492) strings translated, 10% strings fuzzy, 79% words translated
- - fa: 36% (690) strings translated, 9% strings fuzzy, 38% words translated
- - fr: 98% (1869) strings translated, 1% strings fuzzy, 98% words translated
- - it: 75% (1434) strings translated, 11% strings fuzzy, 76% words translated
- - pt: 46% (886) strings translated, 14% strings fuzzy, 48% words translated
-
-Total original words: 17298
-
-Metrics
-=======
-
-* Tails has been started more than 695 672 times this month.
- This makes 23 189 boots a day on average.
-* 15 508 downloads of the OpenPGP signature of the Tails ISO from our website.
-* 215 bug reports were received through WhisperBack.
diff --git a/wiki/src/blueprint/monthly_report/report_2017_07.mdwn b/wiki/src/blueprint/monthly_report/report_2017_07.mdwn
index cf6a343..06974d6 100644
--- a/wiki/src/blueprint/monthly_report/report_2017_07.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2017_07.mdwn
@@ -28,14 +28,33 @@ XXX: List important code work that is not covered already by the Release
Documentation and website
=========================
-XXX: Explore the Git history:
+- We improved our [[installation instructions for
+ Ubuntu|install/debian/usb#ubuntu]] to configure the PPA through
+ **Software & Updates** instead of the command line.
- git log --patch --since='1 October' --until='1 November' origin/master -- "*.*m*"
+- We published instructions on [[how to repair a Tails
+ 3.0.1|news/rescue_3.0.1]] broken by the automatic upgrade.
-User experience
-===============
+- We documented that Tails fails to start on [[computers with NVIDIA
+ Maxwell graphics|support/known_issues#nvidia-maxwell]].
-XXX: Check the archives of tails-ux: https://mailman.boum.org/pipermail/tails-ux/
+- 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]]
+
+- We made it clearer in the system requirements that Tails doesn't work
+ on handheld devices.
+
+- We improved the link and QR code to get back to the same step when
+ switching device during installation. [[!tails_ticket 12319]]
+
+- We updated our command line instructions to use `apt` instead of
+ `apt-get`.
+
+- We renamed *Mac OS X* as *macOS*, it's new name.
+
+- We improved the inlining mechanism that links to release notes during
+ upgrades. [[!tails_ticket 13341]]
Infrastructure
==============
@@ -58,6 +77,8 @@ 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
========
@@ -94,6 +115,6 @@ Metrics
* Tails has been started more than BOOTS/MONTH times this month. This makes BOOTS/DAY boots a day on average.
* SIGS downloads of the OpenPGP signature of Tails ISO from our website.
-* WHISPERBACK bug reports were received through WhisperBack.
+* 160 bug reports were received through WhisperBack.
XXX: Ask tails@boum.org for these numbers.
diff --git a/wiki/src/blueprint/usb_install_and_upgrade/future_spec.mdwn b/wiki/src/blueprint/usb_install_and_upgrade/future_spec.mdwn
index 3558a5a..bb67e20 100644
--- a/wiki/src/blueprint/usb_install_and_upgrade/future_spec.mdwn
+++ b/wiki/src/blueprint/usb_install_and_upgrade/future_spec.mdwn
@@ -56,8 +56,8 @@ Distribution
============
Tails installer shall be available and working on a few selected non-Tails
-operating systems, such as Debian GNU/Linux, Ubuntu, Microsoft Windows
-or Mac OS X. This would allow one-step installation of Tails, instead of the
+operating systems, such as Debian GNU/Linux, Ubuntu, Microsoft Windows
+or macOS. This would allow one-step installation of Tails, instead of the
current way of doing things, that requires an intermediate step: either burning
a DVD or cat'ing a hybrid'ed ISO to a temporary USB stick.
diff --git a/wiki/src/blueprint/vagrant-libvirt.mdwn b/wiki/src/blueprint/vagrant-libvirt.mdwn
index 1d5cd1d..d5e3619 100644
--- a/wiki/src/blueprint/vagrant-libvirt.mdwn
+++ b/wiki/src/blueprint/vagrant-libvirt.mdwn
@@ -7,7 +7,7 @@
This is currently easiest to set up (to avoid backporting, see below)
on a Debian Sid box with libvirt installed:
- sudo apt-get install vagrant
+ sudo apt install vagrant
vagrant plugin install vagrant-libvirt
After this, the Tails branch `feature/vagrant-libvirt` makes
@@ -149,10 +149,10 @@ might just as well update the system and take steps to reduce the
image size:
unset HISTFILE
- sudo apt-get update
- sudo apt-get upgrade
- sudo apt-get install rsync
- sudo apt-get remove virtualbox*
+ sudo apt update
+ sudo apt upgrade
+ sudo apt install rsync
+ sudo apt remove virtualbox*
sudo apt-get autoremove
sudo apt-get clean
sudo rm -rf /var/lib/apt/lists/*
diff --git a/wiki/src/blueprint/web_browser_profile_with_no_CA.mdwn b/wiki/src/blueprint/web_browser_profile_with_no_CA.mdwn
index e010368..5222aab 100644
--- a/wiki/src/blueprint/web_browser_profile_with_no_CA.mdwn
+++ b/wiki/src/blueprint/web_browser_profile_with_no_CA.mdwn
@@ -43,7 +43,7 @@ According to [a blog
post](http://blog.rupamsunyata.org/2008/06/30/consolation-prize.xhtml),
`certutil` may be an adequate tool for the task:
- apt-get install libnss3-tools
+ apt install libnss3-tools
certutil -d $HOME/.mozilla/firefox/$HLAGHLLAGHGAAHLGALHHGHLAGH.default -A -n 'CA Cert Signing Authority - Root CA' -t CT,C,C -i /etc/ssl/certs/root.pem
What does not work is to disable this module for the no-CAs profile