Project

General

Profile

Feature #14544

Spend software developer time on smallish UX improvements

Added by intrigeri about 1 year ago. Updated 15 days ago.

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

0%

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.


Subtasks

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

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


Related issues

Related to Tails - Feature #15131: Identify USB Wi-Fi adapters that are easily available and work with Tails Confirmed 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: Activate persistent storage without the need to restart Confirmed 06/13/2016
Related to Tails - Feature #15028: Rename "Tor Browser" shortcuts and folders Confirmed 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: Remove "Tor is not ready" popup when launching the Tor Browser 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 Confirmed 03/18/2017
Related to Tails - Bug #15168: Improve UX when hardware clock is set to localtime in a timezone >> 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 #15678: Improve UX of saving files in Tor Browser Confirmed 10/26/2015
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 Confirmed 12/31/2015
Related to Tails - Feature #12069: Greeter revamp: phase 1.2 Confirmed 03/03/2015
Related to Tails - Bug #11628: Error message on not-enough-free-space in Tails Upgrader is confusing In Progress 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 11/17/2015
Related to Tails - Feature #5502: Notify user if hardware 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 05/09/2018
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 In Progress 05/05/2018
Related to Tails - Feature #15613: Prepare our 2019Q3 → 2020Q2 budget Confirmed 05/22/2018
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

History

#1 Updated by intrigeri about 1 year ago

  • Description updated (diff)

#2 Updated by intrigeri 12 months 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 12 months 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 10 months ago

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

#6 Updated by sajolida 8 months 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 8 months 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 5 months ago

#10 Updated by intrigeri 5 months ago

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

#11 Updated by sajolida 5 months ago

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

#12 Updated by sajolida 5 months ago

  • Related to Feature #11529: Activate persistent storage without the need to restart added

#13 Updated by sajolida 5 months ago

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

#14 Updated by sajolida 5 months ago

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

#15 Updated by sajolida 5 months ago

  • Related to Bug #8061: Remove "Tor is not ready" popup when launching the Tor Browser added

#16 Updated by sajolida 5 months ago

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

#17 Updated by sajolida 5 months ago

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

#18 Updated by sajolida 4 months ago

#19 Updated by intrigeri 4 months ago

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

#20 Updated by intrigeri 4 months ago

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

#21 Updated by sajolida 4 months ago

  • Description updated (diff)

#22 Updated by sajolida 4 months ago

#23 Updated by sajolida 4 months ago

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

#24 Updated by sajolida 4 months ago

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

#25 Updated by sajolida 3 months ago

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

#26 Updated by sajolida 3 months ago

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

#27 Updated by sajolida about 1 month ago

#28 Updated by sajolida about 1 month ago

#29 Updated by intrigeri about 1 month ago

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

#30 Updated by sajolida about 1 month ago

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

#31 Updated by sajolida about 1 month ago

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

#32 Updated by sajolida about 1 month ago

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

#33 Updated by sajolida about 1 month ago

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

#34 Updated by sajolida about 1 month ago

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

#35 Updated by sajolida about 1 month ago

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

#36 Updated by sajolida 27 days ago

  • Related to Feature #5502: Notify user if hardware requirements are not met added

#37 Updated by sajolida 27 days 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 27 days ago

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

#39 Updated by sajolida 27 days ago

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

#40 Updated by sajolida 21 days ago

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

#41 Updated by sajolida 21 days ago

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

#42 Updated by sajolida 19 days ago

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

#43 Updated by sajolida 19 days ago

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

#44 Updated by sajolida 19 days ago

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

#45 Updated by sajolida 17 days ago

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

#46 Updated by intrigeri 16 days ago

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

#47 Updated by sajolida 15 days ago

  • Target version deleted (Tails_3.10)

#48 Updated by intrigeri 15 days ago

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

#49 Updated by intrigeri 15 days ago

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

#50 Updated by sajolida 11 days ago

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

#51 Updated by sajolida 11 days ago

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

Also available in: Atom PDF