Project

General

Profile

Feature #14544

Spend software developer time on smallish UX improvements

Added by intrigeri over 1 year ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
08/31/2018
Due date:
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

This is about finding a way to do so, e.g. adding it to our Core budget for next year.

This is on our 2018-2019 roadmap but we need to act now so it can actually happen.

For sajolida, "smallish" could mean pretty much anything that wouldn't be worth justifying on its own in a grant application :)

For intrigeri, "smallish" means tasks that can fit into a short sprint (2-4 days), all inclusive.

small improvements.ods (27.8 KB) sajolida, 01/23/2019 05:31 PM


Subtasks

Feature #15887: Analyze the user value of tickets related to #14544Resolvedsajolida

Feature #15888: Analyze the development cost of tickets related to #14544Resolved


Related issues

Related to Tails - Feature #15131: Identify USB Wi-Fi adapters that are easily available and work with Tails Resolved 08/30/2018
Related to Tails - Feature #7439: Decide whether to remove the "clock synchronization" notification Confirmed 06/22/2014
Related to Tails - Feature #11529: Save data to Persistence when it is created (no need to restart) In Progress 06/13/2016
Related to Tails - Feature #15028: Rename "Tor Browser" shortcuts and folders In Progress 03/27/2018
Related to Tails - Feature #9473: Improve "Unable to connect" error message from Tor Browser Confirmed 05/26/2015
Related to Tails - Bug #8061: Customize error messages in Tor Browser and remove the "Tor is not ready" popup Confirmed 10/11/2014
Related to Tails - Feature #15586: Instruct about the possibility of creating a persistent storage when there is none Confirmed 05/05/2018
Related to Tails - Bug #15573: Ask for confirmation when starting without unlocking the persistent storage Confirmed 05/05/2018
Related to Tails - Feature #15262: GNOME Software In Progress 03/18/2017
Related to Tails - Bug #15168: Improve UX when hardware clock is set to localtime in a timezone too far from UTC In Progress 01/15/2018
Related to Tails - Bug #10790: Too many non-Tails folders on Nautilus sidebar In Progress 12/23/2015
Related to Tails - Bug #15101: Add feedback when opening desktop launchers Resolved 12/25/2017
Related to Tails - Feature #15268: Research explaining admin password in graphical polkit prompt Confirmed 01/29/2018
Related to Tails - Feature #8447: Propose to delete data from a persistence feature when it is deactivated Confirmed 12/16/2014
Related to Tails - Feature #11643: Greeter revamp: Phase 1.1 Rejected 12/31/2015
Related to Tails - Feature #12069: Greeter revamp: phase 1.2 Rejected 03/03/2015
Related to Tails - Bug #11628: Error message on not-enough-free-space in Tails Upgrader is confusing Rejected 08/10/2016
Related to Tails - Feature #14534: Propose a better UX when Wi-Fi is not working Confirmed 12/29/2017
Related to Tails - Feature #10553: Add "Don't ask me again" option to notifications where appropriate Confirmed 11/16/2015
Related to Tails - Feature #5722: Default to Mac keyboard layout on Mac hardware Confirmed
Related to Tails - Feature #6254: Make it easy to empty Trash on persistent volume Confirmed 09/03/2013
Related to Tails - Feature #10064: Warn when persistent volume is getting full Confirmed 08/20/2015
Related to Tails - Bug #10559: MAC spoofing failure notification should point to the corresponding documentation Confirmed 01/23/2019
Related to Tails - Feature #5502: Next time we bump RAM requirements: notify user at runtime if RAM requirements are not met Confirmed
Related to Tails - Bug #10114: Tails Installer should display accurate progress information instead for freezing on "Synchronizing data on disk..." Confirmed 08/28/2015
Related to Tails - Feature #10060: Warn when the in-memory filesystem is getting full Confirmed 08/18/2015
Related to Tails - Feature #7782: Warn the user when available RAM / memory is low Confirmed 08/14/2014
Related to Tails - Feature #15875: Make it possible to resume an IUK download from within Tails Confirmed 08/30/2018
Related to Tails - Bug #10976: persistence.conf lost, recoverable by reconfiguring In Progress 02/12/2019
Related to Tails - Bug #15767: Inserting encrypted USB drive does not prompt for decryption Confirmed 08/06/2018
Related to Tails - Feature #15900: Consider mounting external drives automatically (enable automount) Confirmed 09/02/2018
Related to Tails - Bug #15902: No error message when saving to a volume that is not mounted Confirmed 09/02/2018
Related to Tails - Feature #15584: Wrap apt to download lists if there are none Confirmed 05/05/2018
Related to Tails - Feature #15613: Prepare our 2019Q3 → 2020Q2 budget In Progress 05/22/2018 06/30/2019
Related to Tails - Feature #15766: Prevent accidental Tor Browser window maximizing Confirmed 08/06/2018
Related to Tails - Feature #15768: Use desktop background to warn users when their Tails needs to be updated Confirmed 08/06/2018
Related to Tails - Bug #16030: SquashFS errors during boot lead to false-positives on graphics card error reports Confirmed 10/03/2018
Related to Tails - Bug #13438: Parts of Greeter translations are not applied Fix committed 07/07/2017
Related to Tails - Feature #10048: Improve some terminology and phrasing of the Persistence wizard Confirmed 08/15/2015
Related to Tails - Feature #15109: Rename 'Persistence wizard' as 'Persistence assistant' Confirmed 12/26/2017
Related to Tails - Feature #15572: Redesign UI for the creation of the persistent storage Confirmed
Related to Tails - Bug #11292: Bopomofo input for Chinese is not working Resolved 03/31/2016
Related to Tails - Feature #16094: Have simplified and traditional Chinese in the list of languages in Tails Greeter Confirmed 11/04/2018
Related to Tails - Bug #16093: Remove untranslated Chinese languages from Tails Greeter Confirmed 11/04/2018
Related to Tails - Feature #16095: Curate the list of languages in Tails Greeter Confirmed 11/04/2018
Related to Tails - Feature #12003: Set a warning message in RCs and alpha releases In Progress 11/28/2016
Related to Tails - Bug #16293: Skip the first screen of Tor Launcher Confirmed 01/05/2019
Related to Tails - Feature #15827: Give feedback while the persistence setup is starting Confirmed 08/21/2018
Related to Tails - Bug #15169: Keyboard layout is not updated in Administration Password fields in Greeter Confirmed 01/16/2018
Related to Tails - Bug #13447: Inconsistent administration password setting process at Greeter Confirmed 07/09/2017
Related to Tails - Bug #12638: Automatic language → keyboard selection is broken when selecting some languages Confirmed 06/04/2017
Related to Tails - Feature #5501: Persistence preset: locale and accessibility options (language, keyboard, and formats) in Greeter Confirmed 12/31/2015
Related to Tails - Feature #6284: Display time in local timezone Confirmed 10/27/2015
Related to Tails - Feature #12251: Clarify error message when the Unsafe Browser was launched without network connection Confirmed 02/18/2017
Related to Tails - Bug #15830: Use a username that makes more sense to our users Confirmed 08/21/2018
Related to Tails - Feature #5881: Add a "Restart now" button to persistence setup assistant Duplicate
Related to Tails - Bug #16384: Force restarting after creating persistent storage Confirmed 01/23/2019
Related to Tails - Bug #16461: Backup persistence.conf before modifying it in t-p-s Resolved 02/12/2019
Related to Tails - Bug #16568: Make writing persistence.conf.bak more robust Resolved 03/17/2019
Related to Tails - Bug #16611: Propose users to add relevant internationalization Debian packages Confirmed
Related to Tails - Bug #16669: Inconsistent "Encrypted" (vs "Encrypted?") for locked VeraCrypt volumes in GNOME Files Confirmed

History

#1 Updated by intrigeri over 1 year ago

  • Description updated (diff)

#2 Updated by intrigeri over 1 year ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

I'll start by dumping some thoughts about this topic in the hope it starts a discussion and helps building a suitable proposal later on.

I'd like this to have a dedicated time budget (both for developers & UX person), not mixed with the existing Foundations Team and UX core work budget lines: otherwise I don't trust us much to prioritize this above the other many things that are in scope for these existing core work roles. I could elaborate if you want but I guess you get the idea.

I'm not sure if we should call this core work initially. I think this would be the first time we add improvements (as opposed to maintenance, fixing regressions and keeping relevant) to Core work:

  • If we do that, then it opens a much broader discussion, i.e. why not add improvements in other areas such as security too?
  • This year we were not able to fund all the core work, and some people had to do big parts of it as volunteers. If we add this new role to Core work, we'll need to be extremely careful wrt. how we prioritize paying it vs. paying other (really really needed) jobs. Let's take care of our team dynamics and do whatever we can to avoid frustration, especially when money is involved.

Ideally we would have data to select what actual improvement has the best cost/benefit. Thankfully we have initiated changes (in the Help Desk's mission, in having some budget for UX research) that will help us estimate the benefit; our developers can guesstimate costs.

I think we need a team built of:

  • one or two developers who are able to work on most of our code bases (i.e. proficiency in at least Python + shell + OS/desktop integration glue, and ideally Perl too although that can be delegated in an ad-hoc way); I think that restricts our realistic options to three individuals (I'll go into details privately);
  • one UX person.

Alternatively, the UX person could pick whatever developer has time and required skills, depending on the task. But I don't see a good way to make this work in a fluid manner with the cost/benefit approach proposed above. A permanent team has the advantage that it increases the chances the developer is involved in the process of picking the tasks, feels like they own the tasks more, is more motivated & less frustrated, and has a more user-centric approach to the problems at hand.

If I'm one the main developer, then I don't want this to be yet another set of WIP tasks that take months to complete: I don't need this in my mental space. And even if I'm not on board, a more focused approach to this work will save lots of context switches, waiting time between round-trips, and bureaucratic overhead. So I would go for a sprint approach (maybe twice a year?), piggy-backing on other sprints if possible, with the entire team (dev + UX) present face-to-face. This fits well with the smallish aspect, i.e. it forces us to pick a set of tasks that fits in a 2-4 days sprint. And it makes my "time budget" proposal realistic even with team members who don't clock their work usually.

#4 Updated by intrigeri over 1 year ago

  • Assignee changed from intrigeri to sajolida

Also, in 2018 we want to work on #11679. I doubt we can do both at the same time, and I'd rather bring #11679 to the point where we know what we want to do exactly and how much it will cost, before we start this other area of UX improvements work => I would start this only in 2018Q4 + 2019Q1.

anonym, sajolida, what do you think?

#5 Updated by sajolida over 1 year ago

  • Target version changed from Tails_3.3 to Tails_3.5

#6 Updated by sajolida over 1 year ago

  • Assignee changed from sajolida to intrigeri

Yeap. I'll also be myself quite busy with core + OTF UX work in the first part of 2018.

Maybe we should take advantage of the summit to decide on which improvements we want to work on. If so maybe 2018Q3 would be the time to identify candidates before the summit and prepare the coding work if we need to do some prototyping and testing before the actual coding.

So I agree with you, coding could start in 2018Q4 but UX work could start in 2018Q3.

Does that answer your question?

#7 Updated by intrigeri over 1 year ago

  • Assignee changed from intrigeri to sajolida
  • Target version changed from Tails_3.5 to Tails_3.9

sajolida.

Maybe we should take advantage of the summit to decide on which improvements we want to work on. If so maybe 2018Q3 would be the time to identify candidates before the summit

Agreed ⇒ setting the target version accordingly. Do you want to lead this process?

and prepare the coding work if we need to do some prototyping and testing before the actual coding.
So I agree with you, coding could start in 2018Q4 but UX work could start in 2018Q3.

I'm not sure that anything that requires enough prototyping and testing done in advance fits well with the "smallish" aspect of what I had in mind. At least to start with I'd rather pick tasks that can fit into a short sprint, all inclusive. But I feel it would be premature to discuss this in details right now, so whatever.

Does that answer your question?

Yes, thank you.

@anonym: your input would be welcome but no pressure (no emergency anymore since this won't make it into our budget for next year, and to be blunt: the fact you did not find time to answer here is already a partial answer).

intrigeri:

I don't think we have the means to recruit, onboard and get up to speed someone else.

Actually we're going to try and onboard 2-3 new people on the Foundations Team. This job could be a good way to help do that :)

#8 Updated by intrigeri about 1 year ago

#10 Updated by intrigeri about 1 year ago

  • Related to Feature #15131: Identify USB Wi-Fi adapters that are easily available and work with Tails added

#11 Updated by sajolida about 1 year ago

  • Related to Feature #7439: Decide whether to remove the "clock synchronization" notification added

#12 Updated by sajolida about 1 year ago

  • Related to Feature #11529: Save data to Persistence when it is created (no need to restart) added

#13 Updated by sajolida about 1 year ago

  • Related to Feature #15028: Rename "Tor Browser" shortcuts and folders added

#14 Updated by sajolida about 1 year ago

  • Related to Feature #9473: Improve "Unable to connect" error message from Tor Browser added

#15 Updated by sajolida about 1 year ago

  • Related to Bug #8061: Customize error messages in Tor Browser and remove the "Tor is not ready" popup added

#16 Updated by sajolida about 1 year ago

  • Related to Feature #15586: Instruct about the possibility of creating a persistent storage when there is none added

#17 Updated by sajolida about 1 year ago

  • Related to Bug #15573: Ask for confirmation when starting without unlocking the persistent storage added

#18 Updated by sajolida about 1 year ago

#19 Updated by intrigeri 12 months ago

  • Related to Bug #15168: Improve UX when hardware clock is set to localtime in a timezone too far from UTC added

#20 Updated by intrigeri 12 months ago

  • Related to Bug #10790: Too many non-Tails folders on Nautilus sidebar added

#21 Updated by sajolida 12 months ago

  • Description updated (diff)

#22 Updated by sajolida 12 months ago

#23 Updated by sajolida 12 months ago

  • Related to Bug #15101: Add feedback when opening desktop launchers added

#24 Updated by sajolida 12 months ago

  • Related to Feature #15268: Research explaining admin password in graphical polkit prompt added

#25 Updated by sajolida 11 months ago

  • Related to Feature #15678: Improve UX of saving downloaded files from Tor Browser added

#26 Updated by sajolida 11 months ago

  • Related to Feature #8447: Propose to delete data from a persistence feature when it is deactivated added

#27 Updated by sajolida 9 months ago

#28 Updated by sajolida 9 months ago

#29 Updated by intrigeri 9 months ago

  • Related to Bug #11628: Error message on not-enough-free-space in Tails Upgrader is confusing added

#30 Updated by sajolida 9 months ago

  • Related to Feature #14534: Propose a better UX when Wi-Fi is not working added

#31 Updated by sajolida 9 months ago

  • Related to Feature #10553: Add "Don't ask me again" option to notifications where appropriate added

#32 Updated by sajolida 9 months ago

  • Related to Feature #5722: Default to Mac keyboard layout on Mac hardware added

#33 Updated by sajolida 9 months ago

  • Related to Feature #6254: Make it easy to empty Trash on persistent volume added

#34 Updated by sajolida 9 months ago

  • Related to Feature #10064: Warn when persistent volume is getting full added

#35 Updated by sajolida 9 months ago

  • Related to Bug #10559: MAC spoofing failure notification should point to the corresponding documentation added

#36 Updated by sajolida 9 months ago

  • Related to Feature #5502: Next time we bump RAM requirements: notify user at runtime if RAM requirements are not met added

#37 Updated by sajolida 9 months ago

  • Related to Bug #10114: Tails Installer should display accurate progress information instead for freezing on "Synchronizing data on disk..." added

#38 Updated by sajolida 9 months ago

  • Related to Feature #10060: Warn when the in-memory filesystem is getting full added

#39 Updated by sajolida 9 months ago

  • Related to Feature #7782: Warn the user when available RAM / memory is low added

#40 Updated by sajolida 9 months ago

  • Related to Feature #15875: Make it possible to resume an IUK download from within Tails added

#41 Updated by sajolida 9 months ago

  • Related to Bug #10976: persistence.conf lost, recoverable by reconfiguring added

#42 Updated by sajolida 9 months ago

  • Related to Bug #15767: Inserting encrypted USB drive does not prompt for decryption added

#43 Updated by sajolida 9 months ago

  • Related to Feature #15900: Consider mounting external drives automatically (enable automount) added

#44 Updated by sajolida 9 months ago

  • Related to Bug #15902: No error message when saving to a volume that is not mounted added

#45 Updated by sajolida 9 months ago

  • Related to Feature #15584: Wrap apt to download lists if there are none added

#46 Updated by intrigeri 9 months ago

  • Target version changed from Tails_3.9 to Tails_3.10.1

#47 Updated by sajolida 9 months ago

  • Target version deleted (Tails_3.10.1)

#48 Updated by intrigeri 9 months ago

  • Related to Feature #15613: Prepare our 2019Q3 → 2020Q2 budget added

#49 Updated by intrigeri 9 months ago

Next step (after the subtasks) is to include this in our budget next year (#15613).

#50 Updated by sajolida 8 months ago

  • Related to Feature #15766: Prevent accidental Tor Browser window maximizing added

#51 Updated by sajolida 8 months ago

  • Related to Feature #15768: Use desktop background to warn users when their Tails needs to be updated added

#52 Updated by intrigeri 8 months ago

  • Related to Bug #16030: SquashFS errors during boot lead to false-positives on graphics card error reports added

#53 Updated by intrigeri 7 months ago

  • Related to Bug #13438: Parts of Greeter translations are not applied added

#54 Updated by sajolida 7 months ago

  • Related to Feature #10048: Improve some terminology and phrasing of the Persistence wizard added

#55 Updated by sajolida 7 months ago

  • Related to Feature #15109: Rename 'Persistence wizard' as 'Persistence assistant' added

#56 Updated by sajolida 7 months ago

  • Related to Feature #15572: Redesign UI for the creation of the persistent storage added

#57 Updated by sajolida 7 months ago

  • Related to Bug #11292: Bopomofo input for Chinese is not working added

#58 Updated by sajolida 7 months ago

  • Related to Feature #16094: Have simplified and traditional Chinese in the list of languages in Tails Greeter added

#59 Updated by sajolida 7 months ago

  • Related to Bug #16093: Remove untranslated Chinese languages from Tails Greeter added

#60 Updated by sajolida 7 months ago

  • Related to Feature #16095: Curate the list of languages in Tails Greeter added

#61 Updated by intrigeri 6 months ago

  • Related to Feature #12003: Set a warning message in RCs and alpha releases added

#62 Updated by sajolida 5 months ago

  • Related to Bug #16293: Skip the first screen of Tor Launcher added

#63 Updated by sajolida 5 months ago

  • Related to Feature #15827: Give feedback while the persistence setup is starting added

#64 Updated by sajolida 4 months ago

  • Related to Bug #16260: Notification on MAC spoofing failure is truncated added

#65 Updated by sajolida 4 months ago

  • Related to Bug #15169: Keyboard layout is not updated in Administration Password fields in Greeter added

#66 Updated by sajolida 4 months ago

  • Related to Bug #13447: Inconsistent administration password setting process at Greeter added

#67 Updated by sajolida 4 months ago

  • Related to Bug #12638: Automatic language → keyboard selection is broken when selecting some languages added

#68 Updated by sajolida 4 months ago

  • Related to Feature #5501: Persistence preset: locale and accessibility options (language, keyboard, and formats) in Greeter added

#69 Updated by sajolida 4 months ago

#70 Updated by sajolida 4 months ago

  • Related to Feature #12251: Clarify error message when the Unsafe Browser was launched without network connection added

#71 Updated by sajolida 4 months ago

  • Related to Bug #15830: Use a username that makes more sense to our users added

#72 Updated by sajolida 4 months ago

  • Related to Feature #5881: Add a "Restart now" button to persistence setup assistant added

#73 Updated by intrigeri 4 months ago

  • Related to Bug #16384: Force restarting after creating persistent storage added

#74 Updated by intrigeri 4 months ago

  • Related to deleted (Feature #15678: Improve UX of saving downloaded files from Tor Browser)

#75 Updated by sajolida 4 months ago

Here's the spreadsheet that we came up with together with intrigeri today. The value and cost estimated are super rough but that's probably good enough to get a first list of candidates.

I put in bold the top 8 of the pile, without taking UX cost into account.

And here are some tickets that the Foundations Team could start looking into right now without having to wait for a lot of UX work (value/cost in parenthesis):

  • #13438: Parts of Greeter translations are not applied (6)
  • #16094: Have simplified and traditional Chinese in the list of languages in Tails Greeter (2)
  • #16095: Curate the list of languages in Tails Greeter (3)
  • #15169: Keyboard layout is not updated in Administration Password fields in Greeter (2)
  • #13447: Inconsistent administration password setting process at Greeter (2)
  • #12638: Automatic language → keyboard selection is broken when selecting some languages (3)
  • #15168: Improve UX when hardware clock is set to localtime in a timezone too far from UTC (2)

#76 Updated by intrigeri 4 months ago

And here are some tickets that the Foundations Team could start looking into right now without having to wait for a lot of UX work:

Woohoo, I'm very happy we have this list! Adding to the agenda of the next FT meeting.

#77 Updated by intrigeri 3 months ago

  • Related to Bug #16461: Backup persistence.conf before modifying it in t-p-s added

#78 Updated by intrigeri 2 months ago

  • Related to Bug #16568: Make writing persistence.conf.bak more robust added

#79 Updated by sajolida about 2 months ago

  • Related to Bug #16611: Propose users to add relevant internationalization Debian packages added

#80 Updated by sajolida 20 days ago

  • Related to Bug #16669: Inconsistent "Encrypted" (vs "Encrypted?") for locked VeraCrypt volumes in GNOME Files added

#81 Updated by sajolida 16 days ago

  • Related to deleted (Bug #16260: Notification on MAC spoofing failure is truncated)

Also available in: Atom PDF