Commit e3604833 authored by intrigeri's avatar intrigeri
Browse files

Merge branch 'devel' into feature/stretch

parents 2550b2c9 f4948e1a
......@@ -31,7 +31,7 @@ VAGRANT_PATH = File.expand_path('../vagrant', __FILE__)
STABLE_BRANCH_NAMES = ['stable', 'testing']
# Environment variables that will be exported to the build script
EXPORTED_VARIABLES = ['http_proxy', 'MKSQUASHFS_OPTIONS', 'TAILS_RAM_BUILD', 'TAILS_CLEAN_BUILD', 'TAILS_OFFLINE_BUILD']
EXPORTED_VARIABLES = ['http_proxy', 'MKSQUASHFS_OPTIONS', 'TAILS_RAM_BUILD', 'TAILS_CLEAN_BUILD', 'TAILS_OFFLINE_MODE']
# Let's save the http_proxy set before playing with it
EXTERNAL_HTTP_PROXY = ENV['http_proxy']
......
......@@ -61,5 +61,8 @@ Options
### RT
- http://bestpractical.com/rt/
- https://bestpractical.com/rtir/
- AccessNow have a RT behind their help desk. It's run by Gustaf
Björksten <gustaf@accessnow.org>.
- https://www.bestpractical.com/docs/rt/4.2/RT/Crypt/GnuPG.html
- https://forge.puppetlabs.com/darin/rt
......@@ -4,7 +4,7 @@ Issue number: [[!tails_ticket 11669]]
## Introduction
The Tails Social Contract is a set of commitments that we as contributors to the Tails project stand by. This work is derived from the Debian Social Contract and Tor Project's Social Contract. If you have any questions or comments, feel free to email: <tails-project@boum.org>.
The Tails Social Contract is a set of commitments that we as contributors to the Tails project stand by. This work is derived from the Debian Social Contract and the Tor Social Contract. If you have any questions or comments, feel free to email: <tails-project@boum.org>.
This is a promise from our developer community to the rest of the world, affirming a commitment to our beliefs.
......@@ -34,6 +34,8 @@ Bugfixes, code improvements, Debian packaging, as well as work on usability issu
We want to produce Tails in a way that encourages participation, which requires publicly documenting what can be improved.
As Tails is created in such a transparent manner, anyone is encouraged to participate, review it and point out problems.
To make our community a welcoming place for everybody we agreed on a [[Code of Conduct|contribute/working_together/code_of_conduct]].
## 5. We will never harm our users intentionally.
We will always do our best to create secure and usable tools. We will never willingly include backdoors or malicious software nor will we cooperate with any entity wanting us to harm our users.
......
......@@ -269,6 +269,13 @@ Other solutions
GNOME frontend. It does snapshots with hardlinks to reduce space.
Can do local and SSH as remote.
spideroak
---------
[SpiderOak](https://spideroak.com/) is a commercial online encrypted
backup service. Reading their website might be useful for the user
research part of this project.
User experience
===============
......
......@@ -19,7 +19,7 @@ Interview script
- Introduction
- Who I am, what I am doing, and why I'm conducting the interview.
- You can answer our questions to the extend that you feel comfortable
- 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
of the project but in generic terms, removing personally
......@@ -46,11 +46,11 @@ Interview script
Template email for validating the output
----------------------------------------
> Thank you so much for taking some time to answer our questions about
> Thank you so much for taking some time to answer my questions about
> Tails the other day!
>
> I'm sending you here what I plan to store in our public working
> documents on our website. Feel free to correct me if I misunderstood
> documents on our website. Please correct me if I misunderstood
> something or if you want me to remove some bits.
Jeanne, February 2017
......
Documentación de los traductores al español de Tails
====================================================
[[!toc levels=2]]
Repositorios
------------
Si quiero traducir al español cómo puedo empezar
------------------------------------------------
Ahora mismo tenemos un repo especial, en el que hemos generado los archivos de traducción en algunos idiomas que se ha dicho de comenzar a traducir pero que todavía no son parte de Tails.
Se puede clonar más nuevo en
<https://translate.tails.boum.org/git/tails/index/>
o si no en
<https://git-tails.immerda.ch/weblate/tails/>
1. Suscribirte a la lista de correos: Tenemos la lista de todos los traductores de Tails a todos los idiomas, y la de traducción al español:
- <https://mailman.boum.org/listinfo/tails-l10n>
- <https://mailman.boum.org/listinfo/tails-l10n'spanish>
2. Puedes traducir con git (un poco más complicado), o hacer una cuenta en la plataforma de traduccion en pruebas (Ver abajo)
Plataforma en pruebas
---------------------
Plataforma de traducción
------------------------
Estamos testeando una plataforma de traducción del website con weblate, una aplicación web de traducción:
<https://translate.tails.boum.org/>
Perfil
------
- El correo o nombre que decidas usar se publicará en el repo.
- Al hacerte una cuenta edita tu perfil:
- El idioma al que quieres traducir
- Suscribete al Proyecto Tails en Subscriptions.
- Lo más importante es traducir las 'core pages'. Estan en <https://translate.tails.boum.org/#list-core>
- Para ver el estado de la traducción al castellano:
<https://translate.tails.boum.org/languages/es/tails/>
- Puedes ir sugiriendo traducciones y otras personas tienen que votar o validar la traducción.
Traducir con git
----------------
Ahora mismo tenemos un repo especial, en el que hemos generado los archivos de traducción en algunos idiomas que se ha dicho de comenzar a traducir pero que todavía no son parte de Tails.
Al hacerte una cuenta edita tu perfil, especialmente el idioma al que quieres traducir, y suscribete al Proyecto Tails en Subscriptions.
Se puede clonar con:
Lo más importante es traducir las 'core pages'. En [translate] estan en <https://translate.tails.boum.org/#list-core>
git clone https://translate.tails.boum.org/git/tails/index/
Para ver el estado de la traducción al castellano:
<https://translate.tails.boum.org/languages/es/tails/>
Se pueden seguir las instrucciones de
<https://tails.boum.org/contribute/how/translate/with_Git/>
......@@ -11,6 +11,26 @@ This is about [[!tails_ticket 11162]].
- [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)
# Data sources
- [*Rick Wash & Emilee Rader*, Too Much Knowledge? Security Beliefs and
Protective Behaviors Among United States Internet
Users](http://www.rickwash.com/papers/security-survey.pdf): studies a
large representative sample of United States Internet users about
different causal beliefs related to computer security, and about the
actions they regularly undertake to protect their computers.
- [*Javier Garza Ramos*, Journalist Security in the Digital
World](http://www.cima.ned.org/wp-content/uploads/2016/03/CIMA-Journalist-Digital-Tools-03-01-15.pdf)
is a survey of 154 journalists worldwide on their digital security
practices.
- [Jennifer R. Henrichsen](https://www.asc.upenn.edu/people/jennifer-r-henrichsen) is
doing a research with journalists and digital security trainers to
shed light on journalists' perceptions toward digital security
technologies, including motivations to adopt and barriers to adoption.
In March 2017, the results of her research were not published yet.
# User scenarios
From a discussion in August 2016:
......
......@@ -7,6 +7,14 @@ Requirements
- SHOULD
- Be possible to integrate in ikiwiki (to avoid people having to go elsewhere to answer questions)
- Captchas: How do we prevent spam on the survey platform, both from
robots and humans.
- Captcha can deal with robots.
- Attention check questions can deal with humans.
- How can we get both without being annoying? Maybe having no captcha
and two attention check questions could be useful but then that's
maybe a bit annoying for humans.
LimeSurvey
==========
......
......@@ -7,10 +7,6 @@ Furthermore, the current process makes it hard to add new languages, as often a
Corresponding ticket: [[!tails_ticket 9049]]
* We are currently setting up a weblate install, read
[[!tails_ticket 11759]] for more information.
MUST
====
......@@ -60,4 +56,16 @@ MAY
Weblate setup
=============
We are testing a [weblate instance](https://translate.tails.boum.org/) to see if it fits our requirements. Read [[!tails_ticket 11759]] for more information.
What we plan to do is:
[Schematics of the different Git repos, ikiwiki instances, and their relationships.](https://labs.riseup.net/code/attachments/download/1551/weblate.svg)
Currently the repo is following Tails master repo, but the changes it generates are not fed back onto Tails master.
You can check out weblate-generated Tails repo with:
git clone https://translate.tails.boum.org/git/tails/index/
......@@ -34,3 +34,13 @@
to focus on getting support for non-nested volumes
only... especially if actual Tails+TC users do not use this
feature, so we shouldn't spend time on it any way.)
User research
=============
- Check what security guides are recommending:
- Talking to Security-in-a-Box we should focus on file containers and
hidden volumes in file containers. Because people are using other
tools for disk encryption and file containers also limit a bit the
amount of access that other operating systems have to the files
(avoids to have the partition full of viruses).
......@@ -3,7 +3,8 @@
Like the technical community as a whole, the Tails team and community
is made up of a mixture of people from all over the world, working on
every aspect of the mission &mdash; including mentorship, teaching, and
connecting people.
connecting people. <!-- The commitments that we stand by as a community
are described in the [[Tails Social Contract|XXX-Fix-this-link]]. -->
Diversity is one of our huge strengths, but it can also lead to
communication issues and unhappiness. To that end, we have a few
......
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