summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2018-07-01 18:52:04 +0000
committerintrigeri <intrigeri@boum.org>2018-07-01 18:52:04 +0000
commitc5cfc08cde4b93e333b7a6bd81fecceaff62d86a (patch)
tree8256e17f4946458f5bad02263d90cf30d8793fc6
parent66d0b5d9b42259fda98ee7ae69ecae3c563c6a37 (diff)
parentaef5c0733f75cefa07e5597cddfb36512c45b845 (diff)
Merge branch 'stable' into web/15688-better-tablesweb/15688-better-tables
-rw-r--r--Rakefile2
-rwxr-xr-xconfig/chroot_local-hooks/20-enigmail-version19
-rwxr-xr-xconfig/chroot_local-includes/usr/local/bin/thunderbird15
-rwxr-xr-xconfig/chroot_local-includes/usr/local/sbin/live-persist30
-rw-r--r--debian/changelog6
-rw-r--r--wiki/src/blueprint/RT_for_help_desk.mdwn139
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_06.mdwn20
-rw-r--r--wiki/src/blueprint/user_survey.mdwn1
-rw-r--r--wiki/src/contribute/calendar.mdwn8
9 files changed, 128 insertions, 112 deletions
diff --git a/Rakefile b/Rakefile
index fb7097e..921fe44 100644
--- a/Rakefile
+++ b/Rakefile
@@ -647,7 +647,7 @@ namespace :basebox do
boxes.sort! { |a, b| basebox_date(a) <=> basebox_date(b) }
boxes.pop
boxes.each do |box|
- if basebox_date(box) < Date.today - 365.0/3.0
+ if basebox_date(box) < Date.today - 365.0/2.0
clean_up_basebox(box)
end
end
diff --git a/config/chroot_local-hooks/20-enigmail-version b/config/chroot_local-hooks/20-enigmail-version
deleted file mode 100755
index 37c6c5c..0000000
--- a/config/chroot_local-hooks/20-enigmail-version
+++ /dev/null
@@ -1,19 +0,0 @@
-#! /bin/sh
-
-set -e
-set -u
-
-echo "Configure Enigmail's version"
-
-# Import set_mozilla_pref()
-. /usr/local/lib/tails-shell-library/tor-browser.sh
-
-# Rationale: the only way to suppress Enigmail's "first run" wizard is
-# to have *some* version configured. But too old versions might
-# trigger work-around code to run unnecessarily.
-version="$(dpkg-query --show \
- --showformat='${source:Upstream-Version}' \
- enigmail)"
-set_mozilla_pref /etc/xul-ext/enigmail.js \
- extensions.enigmail.configuredVersion \
- "\"${version}\""
diff --git a/config/chroot_local-includes/usr/local/bin/thunderbird b/config/chroot_local-includes/usr/local/bin/thunderbird
index a4c2dec..cb085f9 100755
--- a/config/chroot_local-includes/usr/local/bin/thunderbird
+++ b/config/chroot_local-includes/usr/local/bin/thunderbird
@@ -34,21 +34,6 @@ start_thunderbird() {
configure_default_incoming_protocol
- # Apply only the relevant parts of Debian's Icedove → Thunderbird
- # migration procedure.
- TB_PROFILE_FOLDER="${THUNDERBIRD_CONFIG_DIR}"
- if [ ! -f "${TB_PROFILE_FOLDER}/.migrated" ]; then
- # Debian's migration helpers are not designed to have set -e
- # or -u enabled.
- set +e
- set +u
- . /usr/lib/thunderbird/thunderbird-wrapper-helper.sh
- do_fix_mimetypes_rdf
- do_create_migrated_mark_file
- set -e
- set -u
- fi
-
exec /usr/bin/thunderbird --class "Thunderbird" -profile "${PROFILE}" "${@}"
}
diff --git a/config/chroot_local-includes/usr/local/sbin/live-persist b/config/chroot_local-includes/usr/local/sbin/live-persist
index f9f3c25..fe1eb93 100755
--- a/config/chroot_local-includes/usr/local/sbin/live-persist
+++ b/config/chroot_local-includes/usr/local/sbin/live-persist
@@ -128,21 +128,6 @@ migrate_persistence_preset()
fi
}
-migrate_icedove_to_thunderbird() {
- local CONFIG="${1}"
- local PERSISTENCE_DIR="$(dirname "${CONFIG}")"
- if [ -d "${PERSISTENCE_DIR}/thunderbird" ] || \
- ! [ -d "${PERSISTENCE_DIR}/icedove" ]
- then
- return
- fi
- mv "${PERSISTENCE_DIR}/icedove" "${PERSISTENCE_DIR}/thunderbird"
- add_persistence_preset /home/amnesia/.thunderbird thunderbird "${conf}"
- remove_persistence_preset /home/amnesia/.icedove "${conf}"
- # The script /usr/local/bin/thunderbird takes care of the rest of
- # the migration when starting Thunderbird.
-}
-
# We override live-boot's logging facilities to get more useful error messages
log_warning_msg ()
{
@@ -384,21 +369,6 @@ activate_volumes ()
fi
done
- # Migrate persistence settings
- for conf in $(ls /live/persistence/*_unlocked/persistence.conf || true)
- do
- migrate_icedove_to_thunderbird "${conf}"
-
- # Let's make sure to get rid of any Enigmail configuredVersion
- # that we previously used to set in a way that would become
- # persistent in these files (see #12680).
- tb_profile="$(dirname "${conf}")/thunderbird/profile.default"
- rm -f "${tb_profile}/preferences/0000tails.js"
- sed -i --regexp-extended \
- '/^(user_)?pref\("extensions\.enigmail\.configuredVersion",/d' \
- "${tb_profile}/prefs.js"
- done
-
# Fix permissions on persistent directories that were created
# with unsafe permissions.
for persistent_fs in $(ls -d /live/persistence/*_unlocked || true)
diff --git a/debian/changelog b/debian/changelog
index c48c731..3ef43d5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+tails (3.8.1) UNRELEASED; urgency=medium
+
+ * Dummy entry for next release.
+
+ -- Tails developers <tails@boum.org> Tue, 26 Jun 2018 16:51:31 +0000
+
tails (3.8) unstable; urgency=medium
* Security fixes
diff --git a/wiki/src/blueprint/RT_for_help_desk.mdwn b/wiki/src/blueprint/RT_for_help_desk.mdwn
index 6fccc9f..fe21e68 100644
--- a/wiki/src/blueprint/RT_for_help_desk.mdwn
+++ b/wiki/src/blueprint/RT_for_help_desk.mdwn
@@ -1,77 +1,132 @@
-[[!meta title="Request tracker (RT) for help desk"]]
+[[!meta title="Request tracker for help desk"]]
-We want a tool that allows our help desk to
-===========================================
+Having a request tracker powering our help desk will be key to fulfilling their
+[[updated mission|contribute/working_together/roles/help_desk]]:
+
+**Gather qualitative and quantitative data to understand better our users and
+prioritize our work.**
+
+Requirements
+============
MUST
----
- - Track easily what's been done and what's left from previous shifts:
+ - Track easily what's been done and what's left from previous help desk shifts:
- Make it easy to ensure everything is answered
- - Be able to follow an issue from the beginning to the end
+ - Allow a single person to follow an issue from the beginning to the end
- Statistics:
- - Know how many users encountered the same issue. Spot the "Top bug".
+ - Know how many users encountered the same issue. Spot the "Top bugs"
- Be able to have stats on common issues
- - Security of the platform:
- - Allow secure deletion of information over time. Not keep a database forever (how long? what to keep?)
- - Handle incoming OpenPGP emails
- - Handle outgoing OpenPGP emails
- - Be able to search into emails archive
- - Better interaction between user support and devs:
- - Provide logs to devs
- - Make it easy to drop more dev-related issues to devs
+ - Be able to categorize issues ("tags")
+ - Allow building a responsible data retention policy
+ - The platform will handle sensitive information (email addresses of
+ users, their hardware, their problems, etc.). We'll have to do some
+ threat modeling to figure out how to store each piece of
+ information and for how long. The platform might have built-in
+ capacity for this...
+ - Handle incoming and outgoing OpenPGP emails
+ - Allow searching in the archive of tickets
+ - Plain text search
+ - Search on metadata (eg. filter by the version of Tails)
+ - Make it easy to forward logs to devs (who might not have a direct
+ access to the platform)
- Provide a separate queue of tickets per language [[!tails_ticket 9080]]
- - Make it easy to get new mates on board
+ - Make it easy to onboard new help desk members
- Keep a database of template answers
+ - Allow cross-referencing Redmine tickets and help desk tickets
+ - For example, in order to know when a particular issue will be fixed
+ - Make it easy to contact the user back when there is a solution
+ - Parse automatically at least some metadata from WhisperBack reports
+ - We might want to parse automatically all kind of data from
+ WhisperBack reports but that might be hard to do (eg. hardware
+ information) but the platform should at least parse automatically the
+ WhisperBack headers (email address, version number, etc.)
SHOULD
------
- - Make it easy to contact the user back when there is a solution
- - Hardware information
- - Parse cleverly WhisperBack data (hardware, gpg, etc)
- - Keep track of hardware compatibility (Tails works on XYZ, Wi-Fi card XYZ doesn't work)
- - Shift management:
- - Replace the calendar of shifts and do something smart about that (send notifications to the person on duty)
- - Automatically clock user support time
- - Replace the list of bad users. Flag them as nasty automatically
- - Allow forwarding issues from and to other user support projects (Tor, Access Now)
+ - Keep track of hardware compatibility (Tails works on XYZ, Wi-Fi card XYZ doesn't work)
+ - Replace the list of bad users and flag them automatically as nasty
- 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
---
+ - As a start we'll aim at creating a tool that's only accessible to
+ help desk members (and maybe a few other core contributors) but not
+ to members of the Foundations and UX team in general.
+ But for the future, the platform might have built-in capacity to
+ handle different type of accesses to the data in terms of privacy.
+ - Shift management:
+ - Replace the calendar of shifts and do something smart about that (send notifications to the person on duty)
+ - Automatically clock user support time
+ - Allow forwarding issues from and to other user support projects (Tor, Access Now)
- Have a disposable chat system for tricky cases (Tor does that)
-Resources
+Budgeting
=========
- - [[!wikipedia Comparison_of_help_desk_issue_tracking_software]] (Wikipedia)
+This work is directly related to the work of four of our core team:
+
+- [[Help Desk|contribute/working_together/roles/help_desk]]: they will
+ use the platform to do their work.
+- [[Foundations
+ Team|contribute/working_together/roles/foundations_teams]]: they will
+ use the data of the platform to investigate for example hardware
+ compatibility issues.
+- [[UX Designes|contribute/working_together/roles/ux]]: they will use
+ the data of the platform to investigate usability issues and help
+ prioritizing our work.
+- [[Sysadmins|contribute/working_together/roles/sysadmins]]: they will
+ administer the platform.
+
+Making sure that the platform will work for them is part of the core
+work of these teams (eg. building the requirements).
+
+But researching implementation options doesn't fit in their scope of
+work and should be budgeted apart. This work could either be:
+
+- Clocked and paid only once we'll find a grant or a budget to build the
+ platform.
+
+- Paid after requesting an exceptional budget line to tails@boum.org.
+ For example, if we decide to get the help from external contractors
+ for the research phase.
+
+ If we decide to work with external contractors, we'll have to be
+ careful about not spending more time being the point of contact than
+ doing the work ourselves (for example, this might not work for
+ intrigeri).
+
+It might be good if the researcher and the implementer are the same
+person. This might be groente but not before the end of the year.
Options
=======
+ - [[!wikipedia Comparison_of_help_desk_issue_tracking_software]] (Wikipedia)
+
### OTRS
- - http://www.otrs.com/
- - https://otrs.github.io/doc/manual/admin/3.1/en/html/configure-pgp.html
+ - <http://www.otrs.com/>
+ - <https://otrs.github.io/doc/manual/admin/3.1/en/html/configure-pgp.html>
### RT
- - http://bestpractical.com/rt/
- - https://bestpractical.com/rtir/
+ - <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
+ - <https://www.bestpractical.com/docs/rt/4.2/RT/Crypt/GnuPG.html>
+ - <https://forge.puppetlabs.com/darin/rt>
- Koumbit is using RT and told us about their experience in <ead91b4d-8a87-5855-de55-2c4ffcb40377@koumbit.org>
+
+### Faveo
+
+ - <https://www.faveohelpdesk.com/>
+ - Online demo: <https://www.faveohelpdesk.com/online-demo/>
+
+### Helpy
+
+ - <https://helpy.io/>
diff --git a/wiki/src/blueprint/monthly_report/report_2018_06.mdwn b/wiki/src/blueprint/monthly_report/report_2018_06.mdwn
index 32aa54d..3135c12 100644
--- a/wiki/src/blueprint/monthly_report/report_2018_06.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2018_06.mdwn
@@ -27,6 +27,26 @@ XXX: If you feel like it and developers don't do it themselves,
Release section (for example, the changes being worked on for
the next version).
+- We have worked on improving support for recent graphics cards and in
+ particular those produced by NVIDIA. We've sent
+ a [call for testing](https://mailman.boum.org/pipermail/tails-testers/2018-June/001018.html)
+ and
+ [updated](https://mailman.boum.org/pipermail/tails-testers/2018-June/001029.html)
+ it. If the feedback is good, we will probably include these changes
+ in Tails 3.9.
+
+- We have kept working on fixing the EFAIL attacks against
+ encrypted email ([[!tails_ticket 15602]]). Tails 3.8 fixed most of
+ them and Tails 3.9 should fix the remaining ones.
+
+- We have worked on detecting earlier changes that would break
+ automatic upgrades ([[!tails_ticket 15419]])… and already identified
+ one we need to fix in time for Tails 3.9 ([[!tails_ticket 15695]]).
+
+- Chris Lamb prepared a fix for the most infamous rendering issue (raw PO
+ content being inserted in some page) that affects our website
+ ([[!tails_ticket 6907]]).
+
Documentation and website
=========================
diff --git a/wiki/src/blueprint/user_survey.mdwn b/wiki/src/blueprint/user_survey.mdwn
index 8b250b6..b3f0486 100644
--- a/wiki/src/blueprint/user_survey.mdwn
+++ b/wiki/src/blueprint/user_survey.mdwn
@@ -13,6 +13,7 @@ Similar surveys
- <https://matomo.org/blog/2011/06/piwik-community-survey-here-are-the-results/>
- <https://survey.piwik.org/index.php/151125>
- <https://matomo.org/blog/2017/11/community-survey-revealed-discover-the-profile-of-a-piwik-user/>
+ - <https://www.limesurvey.org/about-us/blog/2100-must-have-survey>
Possible research questions
---------------------------
diff --git a/wiki/src/contribute/calendar.mdwn b/wiki/src/contribute/calendar.mdwn
index 86b8a69..7cdc80b 100644
--- a/wiki/src/contribute/calendar.mdwn
+++ b/wiki/src/contribute/calendar.mdwn
@@ -2,13 +2,11 @@
All times are referenced to Berlin and Paris time.
-## 2018Q2
-
-* 2018-06-01: Beta release of VeraCrypt
+## 2018Q3
-* 2018-06-28, 16:00: Foundations Team meeting
+* 2018-07-01: Beta release of VeraCrypt
-## 2018Q3
+* 2018-07-02, 15:00: VeraCrypt meeting
* 2018-07-03, 19:00: [[Contributors meeting|contribute/meetings]]