| A | B | C | D | E | F | G | H | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Value Category | Item Nickname | Status | Solution Opportunity note: many of these items are cut/pasted from team Jean-Philippe's contribs to Nina's OTF Response GDoc, or an email from Marek to Nina. FYI. | Who (primary) | Who (secondary, tertiary) | User Need | Problem | Evidence? | Item Origin | Priority | UX Research Dependent? | Status | Effort | |||||||||||||||
2 | Access | Transifex Workflows | 90% | Translations have already happened, but gettext hooks are missing and workflows to put the translations into the build have yet to get put into Transifex. Maya has been working on this thru 2019, and it's mostly done. | As a Qubes community member | or, as a hired translator | I want to translate Qubes OS content, with confidence it will make it into a near-term release once the translation reaches 100% | Translations need to make it into builds; today, that is not happening. | Team discussion | Must Grant Critical | No | Needs Completion | (Dev) 240 Hours | ||||||||||||||||
3 | Access, Security | Docs Translations | 90% | I think Maya did this, too? | As a non-English speaking user | or, as a Qubes community member | I want to use Qubes, but I don't speak English | Documentation needs to exist in languages Qubes is translated to support | Team discussion | Must | No | tbd | tbd | ||||||||||||||||
4 | Stability | Testing Infrastructure | 90% | improve testing infrastructure - to save developers time spent on manual testing as much as possible | As a Qubes Developer | or, as any user seeking quick/reliable update deploys | I want to get shit done & deploy reliable code | Dev productivity is slow | Marek | Won't | mostly done? | ||||||||||||||||||
5 | Experience | Screenshot Tool | 90% | An integrated screenshot tool which does not require using the terminal in dom0 (already re-implemented by multiple people) | As a non-technical user | as End User | I want to capture a confusing or questionable screen, message, or other interaction, as an image to share with Support | I don't understand something and need help. | JP (Community) | Started/Stalled | |||||||||||||||||||
6 | As a Qubes Developer | as IT manager | I need visibility into stack-traces experienced by users when they encounter errors | Bugs exist, and developers need to know why. | JP (Community) | Started/Stalled | |||||||||||||||||||||||
7 | as a support person | I need end-users to be able to easily send me stack-traces when they encounter bug errrors | Users aren't QA testers, and if we don't make it easy for them they'll never submit bug evidence. | JP (Community) | Started/Stalled | ||||||||||||||||||||||||
8 | Sustainability | Initial User Research | Needs UX | No research has ever been done to date, to give quantitative structure to who Qubes users are; where their needs or interests lie, etc. The team has enthusiastically embraced anecdotal evidence from forums and download metrics, but that's it—and likely not good enough for larger funders. To persue any of the below, it's my (Nina's) suspicion they could use some data to validate prioritization and strategic planning. | As the project team | As the project lead | We need insight into where user needs truly are, and where value/effort will be felt the strongest. | Team decisionmaking currently rooted in anecdotal guesses from GH and Forums discussions. | |||||||||||||||||||||
9 | Usability | Visual VM Disambiguation | Needs UX | support for differentiating VMs using some identifier other than color, which is an identified problem area for color-blind users as well as practitioners of heavy compartmentalization where the number of VMs greatly exceeds the number of available colors. Some kind of stippling patterns have been suggested. | As a power-user | I need to be able to easily distinguish my many, many open VMs from one another | Beyond 6 VMs, colors become harder to distinguish apart from each other. Also: colorblind users. | User feedback via support community | JP (Community) | Could | Needs UX | ||||||||||||||||||
10 | (currently done as VM colors) | ||||||||||||||||||||||||||||
11 | Usability, Experience | Qube (System) Manager | Needs UX | - Existing XFCE/Gnome thing sucks - Everyone wants something better - Create a UI that speaks to Qubes mental models Brennan's Work - Main window design from Brennan sucks - Detailed control windows clean/good | As any damn user | I need to clearly see the status of my system and its components, so that I can optimise things or drill-into problem areas. | Existing Qube Manager sucks | ||||||||||||||||||||||
12 | - Old ticket from Brennan | ||||||||||||||||||||||||||||
13 | - Old project from Brennan | ||||||||||||||||||||||||||||
14 | Usability, Experience | Notifications Tray | Needs UX | - Create a way for all notifications to be viewable in a cohesive "Historic" view - Help alleviate sea of OMTWTF notifications tsunami, w/o removing visibility - Consider in parallel w/ improved Updater and System Health things | |||||||||||||||||||||||||
15 | Access, Experience | Intro to Qubes | Needs design, discovery | Marta's idea... for users totally new to Qubes, would be great to have a WYSIWYG orienting thingydo. Georgia cited OTF Learning Lab as opportune funding partner for this. | As a non-technical user | ||||||||||||||||||||||||
16 | Usability | App/System Menu | Needs UX dev funding incl in MOSS | - Organize by Qube or by App? - One design, largely done - Current implementation uses XFCE, sought to create new one from scratch | |||||||||||||||||||||||||
17 | Stability? | Incorporation and Maintenence | ?? | No idea what this is—was included in MOSS application. Is this the "plan for unpredictable ecosystem things happening" item? | |||||||||||||||||||||||||
18 | Usability, Experience | Clipboard | Needs UX | Existing experience needs improvement | As a non-technical user | or, as an Enterprise user, or any non-hacker-type Qubes user | I want to be able to easily cut-and-paste, keeping in mind I've been cognitively trained to expect Command-C/Command-V | Cut-and-paste in Qubes sucks. | User feedback via support community | Team discussion | Could | Yes | New | ||||||||||||||||
19 | Usability, Experience | Holistic Components, Behavior, and Status Visualisation | Needs UX | Qubes is its own operating system with unique mental models. It deserves a family of its own windows, panes, menus, etc., that can unify around its unique needs. Bending TinyMCE and Gnome and Nautilis stuff around Qubes' needs has gotten exhausting. | As a non-technical user | or, as an Enterprise user, or any non-hacker-type Qubes user | I want intuitive insight into where things are happening across my Qubes system, and intuitive/visual access to modify my system. | Majority of Qubes' functionality today is isolated among silo'd widgets of tables, dropdowns, right-clicks, and checkboxes. Today the learning curve for Qubes is too high for average user adoption. The goal with this would be to flatten that curve, significantly. | Apple vs Windows. Which OS is loved and more readily adopted, by users? Mac's OS (generally, not any one version) is the bar of welcomingness, intuitiveness, and ease of adoption I seek to bring to Qubes OS. | Team discussion | Should Important for project growth and sustainability | Yes | Not started | (UxD) Significant, hours TBD (UxR) Significant, hours TBD (Dev) Significant, hours TBD on determined solution | |||||||||||||||
20 | Usability, Access, Experience, Security | Content Audit | 50% | For Transifex things, Marta said content has all been gathered. Audit, TBD. | As a non-technical user | or, as an Enterprise customer, or any non-hacker-type Qubes user | When I see words or icons in the Qubes UI I want them to make sense to me, and to quickly/easily/usably communicate the right things to me without imposing undue cognitive burden on me. | Inconsistent copy, busy icons, and technically-worded error messages, have been observed to be confusing to users in SecureDrop testing | Nina | Must | No (although research to iterate on comprehension of messaging would be ideal) | Not started | (CxD) 120 Hours (Dev) XX Hours | ||||||||||||||||
21 | Usability | Humane Messaging | Needs UX | All messaging to date in Qubes UI done piecemeal; unified styleguide w/ intentional voice/tone and consistent vocabulary, needed. | As a non-technical user | or really, all users | I want to know in plain-language when Qubes encounters a bug | Exposing stack-trace messages to users = wtf confusion | SecureDrop User testing to date | Nina | Must | No | Not Started | (CxD) 40 Hours | |||||||||||||||
22 | Usability, Experience | Device/VM Attachment | 20% | Revisit device attachment experience (note: calling it an "experience" because depending upon a silo'd widget is the current experience—and that's inadequate, on an aside from the widget itself having usability issues) | As a non-technical user | or really, all users | I want a streamlined and intuitive means to attach a printer, thumb drive, or keyboard, to each's appropriate VM | Current device widget dependent upon unfamliliar mental model for non-technical/non-Unix users... "Attach, whaa? Why?" | SecureDrop User testing to date | Nina | Must | Yes | New | (UxD) 60 Hours (UxR) 20 Hours (DEV) TBD | |||||||||||||||
23 | Needs UX | A tool which safely lists flash drive contents, only allowing “safe” actions such as document sanitization. | As a journalist | or as any high risk user | I want to save/use data to/from devices, without straining my brain to protect my own ass | Files can infect machines | Marek | Could | No | ||||||||||||||||||||
24 | 0% | Solve long-standing issues where users of machines with USB keyboards enable sys-usb and result in an unusable machine, where in many cases the only clear remediation is to reinstall and lose all their data | As a desktop machine user | or as a strange laptop user needing a second keyboard | I want to easily use an externally-connected keyboard | USB keyboards bork machines | ?? | JP (Community) | Should | No | Needs Dev | ||||||||||||||||||
25 | Needs UX dev funding requested in MOSS app | a GUI which makes it easier to handle device passthrough, with optional policy enforcement. For example, “you’ve plugged in a flash drive, what would you like to do?” | As a journalist | or as any high risk user | I want to be able to use USB drive(s), printer(s), microphone(s), or other devices, seamlessly | "Devices Widget" a high-friction experience and counter-intuitive mental model" | JP (Community) | Must | Yes | Needs UX | — See M7 — | ||||||||||||||||||
26 | Experience, Security | Policy Manager | - VM tagging on backend - Allow users to edit OEM policies, create new policies | As a power-user | as any high risk user | I wanna go power-Qubes on things? | Seems to be the sexiest thing Marek is excited about? | Should | |||||||||||||||||||||
27 | Experience | Qubes Air | far off the radar | ability to run selected VMs on remote/cloud machines (Qubes Air) | ?? | ?? | ?? | ?? | Marek | Won't | Massive!!! | ||||||||||||||||||
28 | Access | Installation Wizard | far off the radar | - Qubes currently using Fedora Installer - Maybe Alpine installer? - Debian’s installer makes more sense. | New Qubes user | non-technical Qubes user | |||||||||||||||||||||||
29 | Experience | Power Management | Included in MOSS app | Make powerstate management and reporting to user, clearer | Everyone | ||||||||||||||||||||||||
30 | ?? | Screenlocker | UX needed? | Not sure — Included in MOSS application | |||||||||||||||||||||||||
31 | GPU Passthrough | ?? | Not sure — Included in MOSS application | ||||||||||||||||||||||||||
32 | Stability, Security | Reproducable Builds | ?? | Important for project maturity/growth | |||||||||||||||||||||||||
33 | Debian Packaging | ?? | Not sure — Included in MOSS application | ||||||||||||||||||||||||||
34 | Incorporation & Maintenence | ongoing? | Not sure — Included in MOSS application | ||||||||||||||||||||||||||
35 | Access | Non-Western Alphabet Access | far off the radar | Exposing user configuration of existing GUI-agent / GUI-daemon settings such as reduced filtering of window titles in other character sets (currently disabled by default due to potential security implications, and no easy way for users of non-ASCII character sets to enable if needed) (non-western Alphabet access) | As a non-Western language speaker | As anyone with a Polish or Russian last name | I want or need to use the keyboard in my own language (Hindi, Chinese, etc) | Unicode vs ASCII suckage | Marek & Marta's last name as shown on windows on their own machines | JP (Community) | Won't | No | Too hard | ||||||||||||||||
36 | Stability | Hardware Compatability | 0% | Improve reliability via partnership with ONE device maker | As a non-technical user As an enterprise customer | I just want things to dependably work | Qubes currently too unstable to be trusted consumer product | Could | |||||||||||||||||||||
37 | Experience & Access | far off the radar | Expand hardware compatability | As a user with limited resources | or an organization seeking to deploy Qubes across a device fleet | I want to acquire a laptop within my means, to run Qubes on | Today's hardware compatability is very limited | "Higher adoption blocker than usability" -user feedback according to Marek | Marek | Won't? | No | Too pie-in-sky | Insane | ||||||||||||||||
38 | Access, Experience | Improve Windows OS | far off the radar | Improve and stabilize Windows support | As a non-technical user | or, as an Enterprise customer | I need to use the same crappy software the rest of the world uses | FOSS + Microsoft ≠ Love, but real users need to use the same tools as their friends, colleagues, and customers | Marek | Should | |||||||||||||||||||
39 | Security | VPN via ProxyVM | far off the radar | Integration of easy-setup “leak-proof” VPNs through ProxyVMs (currently only Tor-integrated Whonix is supported) | As a Security-savvy user | or any high-risk user | ?! | Fortification in response to a specific threat model | JP (Community) | Could | Started/Stalled | ||||||||||||||||||
40 | Access, Experience | Graphics Acceleration | far off the radar | GUI domain (prerequisite for graphics acceleration) | As any Qubes user | or, as a future Qubes user yet to purchase hardware | I want zippy performance of VMs, and for a nice display to work. | ?? | Marek | Won't | Not a priority | ||||||||||||||||||
41 | far off the radar | graphics acceleration available for VMs (more and more software require it, and also more and more common 4K+ displays makes it hard to rely on software rendering only) | Marek | Won't | Not a priority | ||||||||||||||||||||||||
42 | Security | Cross-VM Link Opening Browser Extension | Needs UX | Browser extension to open links in other VMs | As any high-risk user | or Enterprise IT Manager | I want to open a webpage in a separate VM, from an email or document I'm looking at in a different VM | Fortification in response to a specific threat model | JP (Community) | Could | Started/Stalled | ||||||||||||||||||
43 | Experience | Auto VM Shutdown | far off the radar | Optional auto-shutdown of inactive VMs | As any user | I need to conserve memory | VMs = memory hogs | JP (Community) | Could | Started/Stalled | |||||||||||||||||||
44 | Experience | Admin API Performance | far off the radar | Currently, many Qubes GUI tools become frustratingly slow with large numbers of VMs due to trade-offs in the Qubes Admin API which sacrificed performance in favor of security. In order to improve the usability experience of these tools, performance of the Admin API (core Qubes OS code) could be improved, but needs to be done very carefully with detailed attention to security. | As any user | I want Qubes to not become frustratingly slow | Either: a) Too many "GUI tools" b) Admin API performance improved | JP (Community) | Could | Needs Dev | |||||||||||||||||||
45 | Experience | Template Manager | far off the radar | a GUI to allow the discovery, installation, and management of OS templates (a “template manager”) (advanced users) | As a non-technical user | or, as an IT person configuring many workstations | Selecting an appropriate template to use should be easy. | Today, it's not? | User feedback via support community | JP (Community) | Could | Needs UX | |||||||||||||||||
46 | Usability, Experience, Security | a GUI to access pre-defined configurations, which would enable the ability to easily set up a computer for a SecureDrop-using investigative journalist | User feedback via support community | JP (Community) | Could | Needs UX | |||||||||||||||||||||||
47 | - Provide easy, accessible pre-defined configurations - Improve template discovery - template manager (?) | User feedback via support community | Marek | Could | |||||||||||||||||||||||||
48 | Experience | Encrypted external storage | far off the radar | a GUI which makes it easier to safely and use encrypted external storage in a way that is difficult to accidentally misuse and leak sensitive information. | As a journalist | As a high-risk user | I need to be able to safely store data, and in a fashion I won't fuck-up | Encryption is hard, and I'm too prone to user error to safely be trusted using it. | JP (Community) | Won't | Needs UX | ||||||||||||||||||
49 | Experience | ??? | improve measured launch (AEM, make it UEFI compatible at least) | ?? | ?? | ?? | ?? | Marek | Won't | ||||||||||||||||||||
50 | Security | File Manager Improvements | Needs UX | A file manager extension which overrides default actions per file type with Qubes-specific actions (such as “open in disposable VM”) to increase safety without requiring as much user attention and discipline | As a high-risk user | or Enterprise IT Manager | I want to be able to open all file types as safely as possible, and without much thought | Different file types each carry unique vunlerabilities that each require knowledge to address. | JP (Community) | Started/Stalled | |||||||||||||||||||
51 | Usability, Experience | Needs UX | Easily-accessible shortcuts for opening new file managers & terminals in the front-most VM (also re-implemented by multiple people independently) | As a non-technical user | I want an intuitive path to easily access my files from any Qube | File Manger(s) not easy/intuitive to discover and/or use | JP (Community) | Should | Yes | Started/Stalled | |||||||||||||||||||
52 | Usability | Terminal Discovery | maybe done? | As a technical user | I want an intuitive path to easily access Terminal | Terminal not easy/intuitive to discover | JP (Community) | Could | Started/Stalled | ||||||||||||||||||||
53 | Stability | Widgets Debugging | far off the radar | Fixing known bugs in the Qubes widgets (running VMs get out of sync, etc.) | JP (Community) | Needs Dev | |||||||||||||||||||||||
54 | Experience | File Sanitize Utility | far off the radar | Sanitizers for file types other than PDFs (video, sound, powerpoint slides, etc.) | As a Journalist | or, any high-risk users | I want to be able to scrub metadata or any security threats, from files I bring to my machine. | • Infected files can compromise the user's security • Metadata can implicate individuals | User feedback via support community | JP (Community) | Could | Needs Dev | |||||||||||||||||
55 | ??? | Salt Formulas UI | ?? | salt formulas + UI for managing them | Salt makes food taste better? | Nina's drawing a blank | Marek | Won't | |||||||||||||||||||||
56 | ??? | Qrexec | easier to maintain qrexec policy (including user friendly tools to edit it) | ?? | ?? | ?? | ?? | Marek | Won't | ||||||||||||||||||||
57 | Security, Experience | Wayland Support | Wayland support (gives overall performance improvement, less memory usage and better in-VM hardening; also, more and more software require Wayland for some functionality - for example flatpak) | ?? | ?? | ?? | ?? | Marek | Won't | ||||||||||||||||||||
58 | |||||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||||
100 |