Commit 9cffb5d3 authored by sajolida's avatar sajolida
Browse files

Merge remote-tracking branch 'origin/master' into doc/14589-additional-software

parents 14526932 87820c6e
......@@ -326,7 +326,7 @@ msgid ""
"cryptographic tool that provides encryption, authentication and deniability."
msgstr ""
"Protege suas conversações em comunicadores instantâneos usando <span class="
"\"definition\">[[!wikipedia Off-the-Record_Messaging desc=\"OTR\"]]</span> "
"\"definition\">[[!wikipedia_pt Off-the-Record_Messaging desc=\"OTR\"]]</span> "
"(Off-the-Record Messaging, apenas em inglês), uma ferramenta criptográfica "
"para cifrar, autenticar e permitir negação plausível."
......
......@@ -45,11 +45,11 @@ questions (and instead uses default values as answers).
### When a package is installed with a persistent storage unlocked
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - add.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - add.png"/>
### When a package is installed with no persistent storage
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - add without persistent storage.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - add without persistent storage.png"/>
### When a package is installed with a persistent storage locked
......@@ -74,11 +74,11 @@ When running from a DVD, virtual machine, or intermediary Tails.
To be displayed only once per session, not to bother people too much.
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - impossible persistent storage.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - impossible persistent storage.png"/>
### When a package is uninstalled
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - remove.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - remove.png"/>
Notifications when starting Tails with additional software
----------------------------------------------------------
......@@ -89,7 +89,7 @@ persistent storage every time the user starts Tails.
### When the installation starts
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - installing.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - installing.png"/>
If the summary is too long (here 62 characters), use instead only:
......@@ -102,7 +102,7 @@ installing.
### When the installation succeeds
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - installed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - installed.png"/>
XXX: the configure button here is tricky to implement. Can we live without it?
......@@ -117,11 +117,11 @@ Notifications of failures
### When the installation fails
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - installation failed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - installation failed.png"/>
### When the upgrade fails
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - upgrade failed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - upgrade failed.png"/>
### When the configuration fails (addition to/removal from the package list)
......@@ -166,15 +166,15 @@ Software** feature in the persistent storage settings.
### If there is no persistent storage
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software - without persistent storage.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software - without persistent storage.png"/>
### Before any package is added
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software - empty.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software - empty.png"/>
### When some packages are already added
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software.png"/>
XXX: please define what happens when clicking on the links "Synaptic Package Manager" or "APT on the command line".
......@@ -187,17 +187,17 @@ By clicking on the delete cross.
Removing packages from the list doesn't require any validity check.
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software - remove.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software - remove.png"/>
### If the persistent storage is locked
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software - locked persistent storage.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software - locked persistent storage.png"/>
### It is impossible to have a persistent storage
For example, when running from a DVD or virtual machine.
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software - impossible persistent storage.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software - impossible persistent storage.png"/>
Persistent storage configuration
--------------------------------
......@@ -211,9 +211,9 @@ Persistent storage configuration
- MAY replace the custom widgets of the persistent storage configuration
by the following GTK3 pattern:
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/persistent storage - configuration changed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/persistent storage - configuration changed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/persistent storage - confirm restart.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/persistent storage - confirm restart.png"/>
### Backend
......
......@@ -25,7 +25,7 @@ and add your topic here:
### Gather comments on our draft personas
Chapter 1: [[Kim, the surveilled at home|personas#kim]]
Chapter 2: [[Cris, the sensitive information gatherer|personas#cris]]
From the work that we did at the last summit, we drafted skeletons of
personas: a very basic description of what kind of users they are.
......
......@@ -35,6 +35,13 @@ XXX: If you feel like it and technical writers don't do it
git log --patch --since='1 October' --until='1 November' origin/master -- "*.*m*"
- We merged the former /install/os into [[/install|install]] to
streamline a bit more our installation instructions.
- We changed the style of the purple headers that we had on our homepage
to look less like buttons. We're now consistently using green for
clickable elements and purple for non-clickable elements.
User experience
===============
......
......@@ -70,6 +70,21 @@ Please add to this list!
* Media streaming
* Icecast
* SSH
* Surveys (LimeSurvey)
* Being able to run surveys without relying on Google Forms seems to
be a frequent need among the Internet freedom community. The topic
was raised twice on OTF-Talk:
- "Secure way to run a survey?" on 2017-10-17
- "Secure survey tool" on 2018-04-02
In both cases the use case was to conduct anonymous surveys of a
target audience.
I've also been asked by another digital security trainer about the
same thing. The use cases could also cover organizing sensitive
events and having a better control of personally identifiable
information, like who registered for a given security training.
# Design
......
......@@ -152,3 +152,22 @@ can be fed back to Weblate by cherry picking.
On the long term, we will automate this process by
- pulling automatically from tails/master and applying a merge strategy
for po [[!tails_ticket ]]
Weblate installation and maintenance - a hybrid approach
--------------------------------------------------------
The Tails infrastructure uses Puppet to make it easier to enforce and replicate system configuration, and usually relies on Debian packages to ensure stability of the system. But the effort to maintain a stable system somehow conflicts with installing and maintaining Weblate, a Python web application, which requires using up-to-date versions of Weblate itself and of its dependencies.
Having that in mind, and taking into account that we already started using Docker to replicate the translation server environment to experiment with upgrading and running an up-to-date version of Weblate, it can be a good trade-off to use Puppet to provide an environment to run Docker, and to use a Docker container to actually run an up-to-date Weblate installation.
From the present state of the Docker image, which currently uses (slightly modified/updated) Puppet code to configure the environment and then sets up Weblate, the following steps could be taken to achieve a new service configuration as described above:
* Move the database to a separate Docker service.
* Remove all Puppet code from the Docker image: inherit from the simplest possible Docker image and setup a Weblate Docker image with all needed dependencies.
* Modify the Puppet code to account for setting up an environment that has Docker installed and that runs the Weblate Docker image.
* Set up persistence for the Weblate git repository and configuration.
* Set up persistence and backups for the database service.
* Update the Puppet code to run tmserver (if/when it's needed -- latest Weblate accounts for basic suggestions using its own database).
After that, we should have a clear separation between stable infrastructure maintenance using Debian+Puppet in one side and up-to-date Weblate application deployment using Docker in the other side. The Docker image would have to be constantly maintained to account for Weblate upgrades, but that should be easier cleaner than deploying Weblate directly in the server.
......@@ -46,7 +46,7 @@ All times are referenced to Berlin and Paris time.
* 2018-08-13: Release 3.9~rc1 — anonym
* 2018-08-21: **Release 3.9** (Firefox 60.2, major release) — anonym is the RM
* 2018-09-05: **Release 3.9** (Firefox 60.2, major release) — anonym is the RM
- includes VeraCrypt support + major Additional Software Packages improvements
## 2018Q4
......
......@@ -4,7 +4,7 @@
<p>Tails documentation would greatly benefit from your help.</p>
[[!toc levels=1]]
[[!toc levels=2]]
</div>
......@@ -12,7 +12,7 @@ Good documentation is difficult to keep up-to-date. If you find a typo
or an error in the documentation please let us know — ideally, by
submitting a patch with your correction.
# Writing
# Find a task
The documentation on the website is not freely editable. The way we
document things has serious security implications. People should be able
......@@ -34,20 +34,16 @@ But there are still many ways you can start contributing:
[GitLab](https://gitlab.com/Tails/tails)). In general,
documentation changes should be based on the `master` branch.
Documentation writers coordinate themselves on [[tails-dev@boum.org
mailing list|about/contact#tails-dev]], our development mailing list.
Documentation writers should also read our [[documentation
guidelines|guidelines]].
New documentation should be wrapped to 80 characters; however, please
do not submit patches that merely re-wrap existing text, as this makes
it harder to read the git history.
We recommend you to [[build an offline version of the
documentation|contribute/build/website]] to test your contributions
before sharing them with us.
# Guidelines and style
- [[Documentation guidelines|guidelines]]
- [[Documentation style guide|style_guide]]
- [[Checklist for writing release notes|release_notes]]
# Tools
## Find documentation pages impacted by changes in Tails
......@@ -72,7 +68,7 @@ format is something like this:
- All string values can use globs and pathspec magic features like
`{foo,bar}`.
To use this tools, please first install the dependencies:
To use these tools, please first install the dependencies:
apt install ruby ruby-deep-merge ruby-git ruby-test-unit
......@@ -102,16 +98,9 @@ To use this tools, please first install the dependencies:
QR-Code:https://tails.boum.org/
# Translating
We want Tails [[end-user documentation|doc]] to be translated in
as many languages as possible. See the [[guidelines for
translators|contribute/how/translate]] for details.
# Related pages
- [[Documentation guidelines|guidelines]]
- [[Checklist for release notes|release_notes]]
- [[Translating Tails|contribute/how/translate]]
# Talk to us
......
......@@ -136,8 +136,8 @@ using <span class="application">OpenPGP Applet</span>.</p>
<a id="screenshot"></a>
About screenshots
=================
Screenshots
===========
We limit the number of screenshots in the documentation to the minimum.
The GNOME Documentation Style Guide explains very well the
......@@ -202,6 +202,13 @@ Ikiwiki shortcuts
The `\[[!wikipedia ..]]` strings you can find in some files are ikiwiki [[shortcuts]].
You might also need to understand [[ikiwiki directives|ikiwiki/directive]].
Wrap to 80 characters but only when needed
==========================================
New documentation should be wrapped to 80 characters. However, please do
not submit patches that merely re-wrap existing text, as this makes it
harder to read the Git history.
Related online resources
========================
......
[[!meta title="Documentation style guide"]]
- **bulleted lists**
Refer to this article from NN/g on [presenting bulleted
lists](https://www.nngroup.com/articles/presenting-bulleted-lists/).
- **Debian and Ubuntu version**
- **Debian and Ubuntu versions**
Refer to Debian versions primarily by their number, and additionally
by their codename.
Refer to Debian and Ubuntu versions primarily by their numbers, and additionally
by their codenames.
* *For example*:
- Tails 3.0 is based on Debian 9 (Stretch)
......
......@@ -26,6 +26,20 @@ Resources
- [[Paper prototyping and *WireframeSketcher*|user_experience/paper_prototyping]]
- [[Survey platform (*LimeSurvey*)|user_experience/limesurvey]]
- [[Guidelines for user testing|user_experience/testing]]
- [[Recording user testing|user_experience/recording]]
- Participant Bill of Rights (adapted from
[Simply Secure](https://simplysecure.org/knowledge-base/)):
- [English ODT](https://github.com/sajolida/tails-ux/raw/master/tools/bill_of_rights.en.fodt)
- [Spanish ODT](https://github.com/sajolida/tails-ux/raw/master/tools/bill_of_rights.es.fodt)
- System Usability Scale (SUS) questionnaire:
- [English ODT](https://github.com/sajolida/tails-ux/raw/master/tools/SUS.en.fodt)
- [Spanish ODT](https://github.com/sajolida/tails-ux/raw/master/tools/SUS.es.fodt)
- Checklist for user testing:
- [English ODT](https://github.com/sajolida/tails-ux/raw/master/tools/user_testing_checklist.fodt)
- Rainbow table:
- [Template ODS](https://github.com/sajolida/tails-ux/raw/master/tools/rainbow_table.fods)
- Spreadsheet to select participants from a LimeSurvey screener:
- [Template ODS](https://github.com/sajolida/tails-ux/raw/master/tools/participants_screener.fods)
Talk to us
==========
......
......@@ -34,9 +34,9 @@ Wireframe library for GNOME and Tails
This Git repository contains wireframes from past projects:
<https://github.com/sajolida/tails-wireframes>
<https://github.com/sajolida/tails-ux>
In the *generic* folder, you can find reusable wireframes and icons for
GNOME and Tails, like the desktop or *Files*:
<https://github.com/sajolida/tails-wireframes/tree/master/generic>
<https://github.com/sajolida/tails-ux/tree/master/generic>
[[!meta title="Recording user testing"]]
[[!toc levels=2]]
Recording with a camera using <span class="application">VLC</span>
==================================================================
Recording the screen with an external camera has the following
advantages over recording with a screencast:
- Recording a whole session, even if the user restarts Tails.
- Saving the video directly to your computer and not relying on the
computer used for the tests.
You can use a document camera. The [Ziggi-HD Plus by
IPEVO](https://www.ipevo.com/) works fine from Tails.
1. Move the <span class="guilabel">AF</span> switch of the camera to <span class="guilabel">C</span> to have continuous autofocus.
1. Install <span class="application">VLC</span>:
<p class="pre command">apt install vlc</p>
### Prepare the camera for recording
1. In <span class="application">VLC</span>, choose
<span class="menuchoice">
<span class="guimenu">Media</span>&nbsp;▸
<span class="guimenuitem">Open Capture Device...</span></span>.
1. In the <span class="guilabel">Capture Device</span> tab, select:
- <span class="guilabel">Video device name</span>: /dev/video1
- <span class="guilabel">Audio device name</span>: hw:1,0
1. Click the <span class="button">Play</span> button.
1. Make sure that the microphone of the camera is captured as well.
1. Adjust the orientation of the camera to capture as much of the screen as
possible while not obfuscating the light of sight of the participant.
### Start recording
1. In <span class="application">VLC</span>, choose
<span class="menuchoice">
<span class="guimenu">Media</span>&nbsp;▸
<span class="guimenuitem">Convert / Save...</span></span>.
1. In the <span class="guilabel">Capture Device</span> tab, select:
- <span class="guilabel">Video device name</span>: /dev/video1
- <span class="guilabel">Audio device name</span>: hw:1,0
1. Click the <span class="button">Convert / Save</span> button.
1. In the <span class="guilabel">Convert</span> dialog:
- Select the
<span class="guilabel">Video - H.264 + MP3 (MP4)</span> profile.
- Specify a destination file under
<span class="filename">~/Persistent/</span>.
Recording a screencast
======================
Recording the screen with a screencast has the following advantages over
recording with an external camera:
- Better image quality
- Lighter setup
Using <span class="application">recordMyDesktop</span>
------------------------------------------------------
You can use
[<span class="application">recordMyDesktop</span>](http://recordmydesktop.sourceforge.net/)
from Tails:
1. Install <span class="application">recordMyDesktop</span>:
<p class="pre command">apt install recordmydesktop</span>
1. Navigate to a folder under <span class="filename">~/Persistent/.
1. Start <span class="application">recordMyDesktop</span>:
<p class="pre command">recordmydesktop --on-the-fly-encoding --buffer-size 8192 --fps 10 --channels 1 <span class="command-placeholder">output.ogv</span></p>
Using GNOME Shell
-----------------
Press <span class="keycap">Ctrl+Alt+Shift+R</span> in GNOME to start or stop
capturing a screencast.
The video is saved to <span class="filename">~/Videos/</span>.
<div class="bug">
<p>The screencast stops after 30 seconds. See [[!tails_ticket
12723]].</p>
<p>The screencast has no sound.</p>
</div>
[[!meta title="May 2018 online meeting"]]
[[!toc levels=2]]
# Meta
- Attendees: emmapeel, masha, sajolida, segfault, spriver, u
- [[Logs|201805/logs.txt]]
# Volunteers to handle "Hole in the roof" tickets this month
- In April we made some progress on [[!tails_ticket 6907]].
# Volunteers to handle important tickets flagged for next release, but without assignee
None
<a id="kim"></a>
# Gather comments on our draft personas
Chapter 1: [[Kim, the surveilled at home|blueprint/personas#kim]]
- Windows camouflage
- *emmapeel: kim would have liked windows camouflage*
- Institutionalized
- *u: "that has been institutionalized" -> do you mean s/he has been in psychiatry ?*
- *emmapeel: i think in this context institutionalized could also be
on an orphanage*
- Bitcoin
- *emmapeel: to have his own savings outside of the institution*
- *emmapeel: its on my private idaho*
- *emmapeel: specially if kim is underage, they are not going to let
him handle his savings*
- Alison
- Ask Alison from Tor about the story she told emmapeel and sajolida.
- Feeling normal
- *masha: I dislike the "Kim wants to feel normal", I'd rather put
"feel safe"*
- *masha: well, when you're queer of color, you're not "normal" and
the world reminds you every day, so what you want is the end of
homophobia/racism for example. And the "want to be normal" might
merge with being invisible, and put everything too queer being
closed doors.*
- *masha: maybe the point is that "normal" leaves way too much room
for interpretation*
- Homeless
- *emmapeel: i just want to say that a very high percentage of
homeless youth in the world is queer. they get kicked out from home
for being queer*
- *emmapeel: but the gay kids go on the streets and they get
institutionalized*
- Computer room
- *u: i think the Kim persona sounds very stressful (limited time,
mentor surveillance...). and surveilled at home can be much less
extreme than this case.*
- *u: i think for example the fact that the computer room is crowded
is an extra stress factor which we could make a bit less extreme by
writing "the computer room is sometimes croweded"*
- *sajolida: an option would be to add that they sometimes also borrow
the computer of a trusted friend inside the institution*
- *u: that could be an option (trusted friend's computer)*
- *emmapeel: if kim has no computer, and uses a computer of a friend,
is good to have tails...*
- Too many threats
- *u: Kim's case has two angles: the surveillance at home by mentors
and peers, and the sharia in nigeria as well as internet censorship*
- *u: sajolida: so kim's case actually has three angles and if we
would replace kim by someone who lives with their abuser, there
would not be the whole censorship and legal part*
- *u: i could imagine to have one person who is either
institutionalized or living with their abuser and one gay youth in
nigeria, but not necessarily under surveillance at home*
- *sajolida: u: if we keep a gay youth in Nigeria who is not
instituationalized, their issues would be censorship circumvention,
State surveillance, and identity management, right?*
- *sajolida: then it would look very much like Riou*
- *emmapeel: yeah maybe he could have a blog....*
- *sajolida: but maybe you're right and we should refocus Kim to be
more strongly about surveillance at home and not so much about other
things as well*
- *sajolida: so remove their societal and State oppression and stick to
the domestic oppression*
- Religious family
- *sajolida: Kim could be gay in a super religious US family for
example*
- *u: fine with me, yes, gay/trans in a religious family in any
fanatic religious family.*
- Transsexual
- *spriver: (how about transsexual, that'd be me)*
- *emmapeel: yeah if you are trans you also have to get out*
- Resources
- <https://en.wikipedia.org/wiki/My_Own_Private_Idaho>
- <https://en.wikipedia.org/wiki/LGBT_rights_in_Nigeria>
- <http://internetfreedom.secondmuse.com/wp-content/uploads/2015/03/if_ugandaLGBT_Final.pdf>
- <http://the-ipf.com/2016/06/09/homosexuality-nigeria-young-lgbt/>
- <http://williamsinstitute.law.ucla.edu/wp-content/uploads/Durso-Gates-LGBT-Homeless-Youth-Survey-July-2012.pdf>
- *spriver: I can share a bit of my story though*
This diff is collapsed.
......@@ -54,30 +54,30 @@ The full list of interfaces that we designed can be seen on our
[[blueprint|blueprint/additional_software_packages/gui]].
The complete XML wireframes are on
[GitHub](https://github.com/sajolida/tails-wireframes/tree/master/additional%20software)
[GitHub](https://github.com/sajolida/tails-ux/tree/master/additional%20software)
and here are the most relevant parts.
When installing a Debian package:
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - add.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - add.png"/>
When starting Tails with some additional packages configured:
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - installing.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - installing.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/notification - installed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/notification - installed.png"/>
Additional Software feature in the persistent storage configuration:
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/persistent storage - configuration changed.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/persistent storage - configuration changed.png"/>
Example list of additional software:
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software.png"/>
When no software has been added yet:
<img src="https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional software/png/additional software - empty.png"/>
<img src="https://raw.githubusercontent.com/sajolida/tails-ux/master/additional software/png/additional software - empty.png"/>
## B.2. Write technical design documentation
......
......@@ -10,15 +10,26 @@ Everything in this report is public.
## A.4 Add VeraCrypt support to udisks
We continued working with upstream on the udisks pull request [#495](https://github.com/storaged-project/udisks/pull/495).
Our udisks pull request
[#495](https://github.com/storaged-project/udisks/pull/495)
has been merged upstream so this deliverable is now completed.
## A.6 Add VeraCrypt support to GNOME Files
We added support to unlock VeraCrypt containers via the unlock dialog opened by gvfs-udisks2-volume-monitor, which now allows unlocking encrypted volumes via GNOME Files or when the storage device is plugged in ([[!tails_ticket 15218]]).
We added support to unlock VeraCrypt containers via the unlock dialog
opened by `gvfs-udisks2-volume-monitor`, which now allows unlocking
encrypted volumes via GNOME Files or when the storage device is
plugged in ([[!tails_ticket 15218]]).
## A.10 Port to the latest version of GNOME
Instead of developing for the GNOME version we use in Tails and forward-porting our patches, we decided to develop for the latest version of GNOME and backport the patches to the version we use in Tails. Therefore, we backported our udisks and GNOME Disks patches ([[!tails_ticket 15253]], [[!tails_ticket 15515]]) and created Debian packages to use them in Tails ([[!tails_ticket 15522]], [[!tails_ticket 15523]]).
Instead of developing for the GNOME version we use in Tails and
forward-porting our patches, we decided to develop for the latest
version of GNOME and backport the patches to the version we use in
Tails. Therefore, we backported our udisks and GNOME Disks patches
([[!tails_ticket 15253]], [[!tails_ticket 15515]]) and created Debian
packages to use them in Tails ([[!tails_ticket 15522]],
[[!tails_ticket 15523]]).