Commit 79c968d4 authored by intrigeri's avatar intrigeri
Browse files

Merge remote-tracking branch 'origin/master' into feature/stretch

parents da87f68d 6e80f34e
......@@ -22,3 +22,4 @@ Discussions
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"]]
......@@ -39,6 +39,9 @@ This is about [[!tails_ticket 11162]].
is an interesting story about the use of Chromebooks in schools and
the internal resistance about its threat to privacy.
- [Tails-project: Regarding USB sticks for domestic violence
survivors](https://mailman.boum.org/pipermail/tails-project/2017-March/000757.html)
# User scenarios
From a discussion in August 2016:
......
......@@ -229,28 +229,28 @@ in a way that makes it easy enough to add this property later.
Following a discussion, we decided to implement it this way as a first iteration:
* We will encode in our Git repo which vagrant basebox should be used to build
the ISO. This way we'll be able to use a dedicated basebox for a branch if
it needs changes in the build system. The vagrant/Vagrantfile file is
probably the right place to do that as it already encode the basebox name,
which contains a timestamp almost similar than the one we use for APT
snapshots.
* The basebox APT sources will be configured to use a specific APT snapshot, so
that we can freeze the build environment.
* This APT snapshot will have a long `Valid-Until` field, set to something like 6
months.
* To freeze the build environment, we use APT snapshots in the same way
we do in the Tails build system, by storing the serials for the various
APT repositories in a directory inside the vagrant one.
* Only the debian-security APT source will be using Debian's APT repository, so
that we get security fixes. This will probably not influence the
reproducibility of the ISO.
* We'll update the basebox at every Debian point release. [[!tails_ticket 11982]]
* To ensure that changes in the build process are still taken into account when
using a basebox, we dynamically set the name of the basebox by
appending the short ID of the last commit in the vagrant directory in
the related branch, as well as its date, to the name of the basebox.
* We update the basebox APT snapshots serials at every Debian point
release. [[!tails_ticket 11982]]
* Thus, the APT snapshots will have a long `Valid-Until` field, set to
something like 6 months.
* A new VM will be created from the basebox for each build. After the build,
the VM is destroyed. [[!tails_ticket 11980]] and [[!tails_ticket 11981]]
* The VM will encode (in a file) the branch for which it has been created for.
The ISO build will abort if the branch being built is not the same as the
The ISO build aborts if the branch being built is not the same as the
one for which the VM has been created initially.
* To ensure that the `apt-cacher-ng` cache is not lost when the VM is destroyed,
it will be moved in a dedicated virtual disk, and plugged into every new VM.
In our Jenkins setup we will instead use the `apt-cacher-ng` we have to share
it is moved in a dedicated virtual disk, and plugged into every new VM.
In our Jenkins setup we instead use the `apt-cacher-ng` we have to share
the APT cache between build VMs and save disk space. [[!tails_ticket 11979]]
* In a later iteration, we could add an option so that the VM is kept running
......@@ -332,14 +332,18 @@ builds reproducible, and even more so for Debian-based projects.
## Adjust our infrastructure accordingly
We will adapt our server infrastructure to support this project.
We will re-use the Vagrant-based build system we have created for
developers: that build system will need to support reproducible builds
anyway.
There are two aspects to it.
First of all, we will need to host a number of "frozen" build
environments, and make them available through the Internet.
Depending on how long we want to keep build environments about past
Tails releases available, this may require a lot of disk space and
bandwidth, so we will probably need to adjust our
infrastructure accordingly.
First of all, we will need to host a number of baseboxes that the
isobuilders will generate before each build (if locally unavailable).
This way they can re-use them rather than rebuild them each time. This
means having enough disk space for the vagrant.d directory in the
Jenkins user home, as well as in the libvirt storage partition.
Secondly, we will enable our existing QA processes to build ISO
images:
......@@ -350,16 +354,11 @@ images:
the output (we may want to use an up-to-date build environment
instead of a frozen one).
To achieve this, we will most likely re-use the Vagrant-based build
system we have created for developers: that build system will need to
support reproducible builds anyway. Still, the integration into our
Jenkins setup will require us to go through a few additional steps,
such as:
Still, the integration into our Jenkins setup will require us to go
through a few additional steps, such as:
* The virtual machines used as Jenkins "slaves" to build ISO images
will need fast access to various frozen build environments (that
is, a bunch of large files). We can do this e.g. via network file
sharing, or by maintaining a local cache.
will need to store a number of different baseboxes.
* For simplicity and security reasons, we will be using nested
virtualization, i.e. Vagrant will start the desired ISO build
......
- **<span class="application">Tails Greeter</span>**
Without an article. Not *the Greeter*. Note the formatting as an application.
- **startup options**
To refer to the kernel command line options that can be specified from
the *Boot Loader Menu*.
* *For example:* Adding `radeon.dpm=0` to the [[startup
options|/doc/first_steps/startup_options#boot_menu]].
......@@ -4,6 +4,13 @@ User testing is an irreplaceable tool to understand user experience and
take decisions while doing design iterations. Here are a few guidelines
to take the most of it.
1. Prepare the test:
- Provide a mouse and a desktop keyboard because not everybody is
comfortable with laptop keyboards and touchpads.
- Prepare gifts for the participants. For example USB sticks,
stickers, etc.
1. Welcome the tester:
- Do a little icebreaker to present yourself, gather context information about the tester and make everybody at ease.
......
......@@ -522,12 +522,12 @@ msgstr ""
#~ msgid ""
#~ "<p>We recommend you to read the [[!inline pages=\"inc/"
#~ "stable_amd64_release_notes\" raw=\"yes\"]]\n"
#~ "stable_i386_release_notes\" raw=\"yes\"]]\n"
#~ "for the latest version. They document all the changes in this new version:"
#~ "</p>\n"
#~ msgstr ""
#~ "<p>Wir empfehlen Ihnen, die [[!inline pages=\"inc/"
#~ "stable_amd64_release_notes.de\" raw=\"yes\"]]\n"
#~ "stable_i386_release_notes.de\" raw=\"yes\"]]\n"
#~ "für die neueste Version zu lesen. Sie beschreiben alle Änderungen in "
#~ "dieser neuen Version:</p>\n"
......
......@@ -519,12 +519,12 @@ msgstr ""
#~ msgid ""
#~ "<p>We recommend you to read the [[!inline pages=\"inc/"
#~ "stable_amd64_release_notes\" raw=\"yes\"]]\n"
#~ "stable_i386_release_notes\" raw=\"yes\"]]\n"
#~ "for the latest version. They document all the changes in this new version:"
#~ "</p>\n"
#~ msgstr ""
#~ "<p>Nous vous recommandons de lire les [[!inline pages=\"inc/"
#~ "stable_amd64_release_notes.fr\" raw=\"yes\"]]\n"
#~ "stable_i386_release_notes.fr\" raw=\"yes\"]]\n"
#~ "de la dernière version. Elles documentent tous les changements de cette "
#~ "nouvelle version :</p>\n"
......
......@@ -522,12 +522,12 @@ msgstr ""
#~ msgid ""
#~ "<p>We recommend you to read the [[!inline pages=\"inc/"
#~ "stable_amd64_release_notes\" raw=\"yes\"]]\n"
#~ "stable_i386_release_notes\" raw=\"yes\"]]\n"
#~ "for the latest version. They document all the changes in this new version:"
#~ "</p>\n"
#~ msgstr ""
#~ "<p>Nós recomendamos que você leia as [[!inline pages=\"inc/"
#~ "stable_amd64_release_notes.pt\" raw=\"yes\"]]\n"
#~ "stable_i386_release_notes.pt\" raw=\"yes\"]]\n"
#~ "da a última versão. Elas documentam todas as mudanças nesta nova versão:</"
#~ "p>\n"
......
......@@ -18,7 +18,7 @@ msgstr ""
#. type: Content of: <div><p>
msgid ""
"We recommend you read the [[!inline pages=\"inc/stable_amd64_release_notes\" "
"We recommend you read the [[!inline pages=\"inc/stable_i386_release_notes\" "
"raw=\"yes\" sort=\"age\"]] for the latest version. They document all the "
"changes in this new version:"
msgstr ""
......
......@@ -17,10 +17,10 @@ msgstr ""
#. type: Content of: <div><p>
msgid ""
"We recommend you read the [[!inline pages=\"inc/stable_amd64_release_notes\" "
"We recommend you read the [[!inline pages=\"inc/stable_i386_release_notes\" "
"raw=\"yes\" sort=\"age\"]] for the latest version. They document all the "
"changes in this new version:"
msgstr "پیشنهاد می‌کنیم آخرین نسخه [[!inline pages=\"inc/stable_amd64_release_notes\" sort=\"age\" raw=\"yes\"]] را بخوانید. تمام تغییرات در این نسخهٔ جدید مستندسازی شده‌اند:"
msgstr "پیشنهاد می‌کنیم آخرین نسخه [[!inline pages=\"inc/stable_i386_release_notes\" sort=\"age\" raw=\"yes\"]] را بخوانید. تمام تغییرات در این نسخهٔ جدید مستندسازی شده‌اند:"
#. type: Content of: <div><ul><li>
msgid "new features"
......
......@@ -18,10 +18,10 @@ msgstr ""
#. type: Content of: <div><p>
msgid ""
"We recommend you read the [[!inline pages=\"inc/stable_amd64_release_notes\" "
"We recommend you read the [[!inline pages=\"inc/stable_i386_release_notes\" "
"raw=\"yes\" sort=\"age\"]] for the latest version. They document all the "
"changes in this new version:"
msgstr "Nous vous recommandons de lire les [[!inline pages=\"inc/stable_amd64_release_notes.fr\" raw=\"yes\" sort=\"age\"]] de la dernière version. Elles documentent tout ce qui a changé dans la nouvelle version :"
msgstr "Nous vous recommandons de lire les [[!inline pages=\"inc/stable_i386_release_notes.fr\" raw=\"yes\" sort=\"age\"]] de la dernière version. Elles documentent tout ce qui a changé dans la nouvelle version :"
#. type: Content of: <div><ul><li>
msgid "new features"
......
<div class="tip">
<!-- Note for translators: make sure that the translation of this string
integrates well with /inc/stable_amd64_release_notes. -->
integrates well with /inc/stable_i386_release_notes. -->
<p>We recommend you read the [[!inline pages="inc/stable_amd64_release_notes" raw="yes" sort="age"]]
<p>We recommend you read the [[!inline pages="inc/stable_i386_release_notes" raw="yes" sort="age"]]
for the latest version. They document all the changes in this new version:</p>
<ul>
......
......@@ -18,7 +18,7 @@ msgstr ""
#. type: Content of: <div><p>
msgid ""
"We recommend you read the [[!inline pages=\"inc/stable_amd64_release_notes\" "
"We recommend you read the [[!inline pages=\"inc/stable_i386_release_notes\" "
"raw=\"yes\" sort=\"age\"]] for the latest version. They document all the "
"changes in this new version:"
msgstr ""
......
......@@ -18,10 +18,10 @@ msgstr ""
#. type: Content of: <div><p>
msgid ""
"We recommend you read the [[!inline pages=\"inc/stable_amd64_release_notes\" "
"We recommend you read the [[!inline pages=\"inc/stable_i386_release_notes\" "
"raw=\"yes\" sort=\"age\"]] for the latest version. They document all the "
"changes in this new version:"
msgstr "Recomendamos a leitura das [[!inline pages=\"inc/stable_amd64_release_notes\" raw=\"yes\" sort=\"age\"]] da última versão. Elas documentam todas as mudanças nesta nova versão:"
msgstr "Recomendamos a leitura das [[!inline pages=\"inc/stable_i386_release_notes\" raw=\"yes\" sort=\"age\"]] da última versão. Elas documentam todas as mudanças nesta nova versão:"
#. type: Content of: <div><ul><li>
msgid "new features"
......
......@@ -11,7 +11,7 @@ msgstr ""
"PO-Revision-Date: 2015-10-25 10:06+0000\n"
"Last-Translator: sprint5 <translation5@451f.org>\n"
"Language-Team: Persian <http://weblate.451f.org:8889/projects/tails/"
"stable_amd64_release_notes/fa/>\n"
"stable_i386_release_notes/fa/>\n"
"Language: fa\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment