There are problems with the existing Qubes HCL (Hardware Compatibility List).
Examples are:
opened 06:51AM - 21 Jul 21 UTC
C: website
P: default
diagnosed
### Qubes OS version
n/a
### Which [testing](https://www.qubes-os.org/doc/… testing/) repositories are you using, if any?
n/a
### Are you providing feedback about a specific package or packages in testing?
n/a
### Affected component(s) or functionality
HCL list (website)
-----
### Brief summary
Sorting by the credit column behaves in unexpected ways
### How reproducible
1. Go to https://www.qubes-os.org/hcl/
2. Sort by Credit column (click on column header)
### Steps to reproduce
see above
### Expected behavior
The column should be sorted lexically.
### Actual behavior
The column is sorted in some other, unknown way. (Maybe numerical?)

### Solutions you've tried
none
### Additional context
https://github.com/QubesOS/qubes-issues/issues/6784
-----
### Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted
n/a
### Related, [non-duplicate](https://www.qubes-os.org/doc/issue-tracking/#new-issues-should-not-be-duplicates-of-existing-issues) issues
https://github.com/QubesOS/qubes-issues/issues/6784
opened 04:55PM - 08 May 23 UTC
help wanted
C: website
accessibility
P: default
[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/)
#… ## The problem you're addressing (if any)
The crucial 'works' information is currently not shown as text but only as color-coding. Since I recently started using an eInk monitor I realized this must be an issue not only for me but basically everyone not able to see colors or reading the screen with other methods (screen reader).
### The solution you'd like
Add a column with the 'works' information.
### The value to a user, and who that user might be
Improve accessibility
opened 10:46PM - 18 Jul 21 UTC
C: website
ux
P: default
<!--(Before filing this issue, please read:
https://www.qubes-os.org/doc/issue-… tracking/
Please use this issue template. Do not delete it.)-->
### The problem you're addressing (if any)
<!--(A clear and concise description of the problem, if any, that this
enhancement is intended to address.)-->
@andrewdavidwong recently added the terrific functionality to the HCL table, of sortable headers. Hooray! Unfortunately, a few small interactive and visual cues are missing, to let folks know that in fact, these headers are sortable.
**Today's HCL Table**
No cursor-change or color change of the text on hover, to signify to users the item is live.
https://user-images.githubusercontent.com/8262612/126083911-36ed2bdc-75f2-46e8-ba12-6cabe5c0a1ac.mov
### Describe the solution you'd like
<!--(If you have something in mind, a clear and concise description of what you
want to happen. If you don't have something in mind, indicate as much.)-->
Generally I'm a strong advocate of interaction patterns documented by [patternfly.org](https://www.patternfly.org/v4) (maintained by RedHat, oddly enough!) or [Material.io](https://material.io/components/data-tables#anatomy) as a solid reference—yet both have specs for sortable headers, that kinda stink. Menus are more common to sort tables with, these days, as a pattern with richer options, than just table headers—which I suspect is why.
_Key attributes that are missing from today's implementation are:_
- The user's cursor should change when hovering over the general area of a sortable header
- The color of the header text should change on hover
- An icon of some sort should be visible both on static and on hover, to indicate sortability
- When the list changes direction, the arrow(s) should indicate that.
**Wikipedia**
Wikipedia's sortable table was mentioned in the Forum. It is highly usable, and is identical to the Bootstrap 4 spec for sortable table headers, but it is also quite busy/cluttered and lacks bolded headers that change color on hover. Like, the arrows don't **_have_** to be that big... but I'm also sure this implementation gets an A+ accessibility rating, which is not easy.
https://user-images.githubusercontent.com/8262612/126083921-d396f730-b3cf-474d-b7f7-cc9b9cd19783.mov
**GDrive**
Two different types of sorting. I do like the dot behind the arrow, as an extra "ting" of discoverability.
[This is the Material Style for Tables](https://material.io/components/data-tables/web#data-tables), that might be an option to implement?
https://user-images.githubusercontent.com/8262612/126083901-84c7c452-9ecc-4ec2-85c7-4ae6714c80d1.mov
**My Bank**
Note that often in tables, some headers are sortable and others are not. Users will probably expect that in this table, too. While I feel the arrows here and in the Wikipedia example, above, are needlessly clunky—you can't deny that they're not clear.
https://user-images.githubusercontent.com/8262612/126083896-c85ef6ff-31cd-4a5c-88d4-d8acfab203e0.mov
**Harvest**
My favorites of the ones I just poked around for, is from my invoicing software (Harvest). My only nits with it, are that 1. There should be pale gray arrows on hover, and 2. The column widths forcing the arrow to wrap onto the next line, is weird.
https://user-images.githubusercontent.com/8262612/126083906-04f41124-3894-4c1b-840a-b89c29af9a38.mov
TL;DR, my fav is the Google Material table, first. If you could literally implement just that. The Bootstrap Table standard would also get the job done. :)
### Where is the value to a user, and who might that user be?
<!--(Which users is this most likely to benefit? What user needs does this
address? How might a user summarize this change or new thing?)-->
Discussed [in forums](https://forum.qubes-os.org/t/plans-to-add-search-filter-functionality-to-the-hcl/5099).
### Describe any alternative solutions you've considered
<!--(A clear and concise description of any alternative solutions or features
you've considered.)-->
The current first implementation of sorting is a great first step, but regrettably the sorting is not discoverable.
### Additional context
Nopitty nope, nope.
-----
### Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted
<!--(Provide a list of any relevant documentation you've consulted. We do not
know what you've already read unless you tell us. If you do not list anything,
we will assume that you haven't read any relevant documentation. If you're not
aware of any relevant documentation, write "None" (or "N/A" if not
applicable).)-->
### Related, [non-duplicate](https://www.qubes-os.org/doc/issue-tracking/#new-issues-should-not-be-duplicates-of-existing-issues) issues
<!--(Provide a list of any related issues of which you're aware. Do not
describe any other unreported bugs, features, or tasks here. We do not know
which issues you've already seen unless you tell us. If there is another issue
that seems like a duplicate, and you did not mention it here, we will assume
that you were not aware of it. If you didn't find any related issues, write
"None found.")-->
opened 05:35AM - 22 Nov 23 UTC
C: other
C: website
P: default
### The problem you're addressing (if any)
## HCL report table and `qubes-hcl-r… eport` should be completely remade
I think the current app for making HCL reports `qubes-hcl-report` and the resulting table should be remade completely. Currently its reports are almost **useless**. When user opens [current HCL table](https://www.qubes-os.org/hcl/), **the most valuable column for them is `Remark`** and link "see more" if available. It destroys the whole concept of having a table.
All other columns, that were generated by `qubes-hcl-report` are nearly useless for different reasons:
* Some of them can be filled from device specs even without touching hardware,
* Some of them are outdated for modern hardware (like HVM, it should not be present green by default, only huge red sign in case it is not available),
* Some of them are not relevant, e.g. TPM column is almost completely filled with `unknown` value. It should be removed and add to Remarks in rare cases when it's known, or filled based on specs.
* Some of them does not mean much without additional tests (e.g. number of USB controllers, it can be 3, but in fact it is only 1 available to the user and all devices connected to it, quite common situation).
* Qubes, Xen, Kernel versions should stay, but not sure how important to have them as columns, because they do not reflect the device properties, just version it was tested on.
**=> Almost all columns expect `Remark` are kind of useless**. Something should be changed, and reorganized with HCL reports and HCL table.
Some users send report without Remarks and such reports can go directly to trash, because they are not giving valuable info on choosing/buying the reported device.
## What user really wants?
To know what is working and what is not:
* installation process (latest kernel? additional options were required?),
* sound,
* video,
* ethernet,
* wifi,
* bluetooth,
* suspend,
* do wifi and bluetooth survive suspend,
* maximum RAM possible to get,
* video performance (CPU info?),
* work of available ports (e.g. HDMI port and etc).
* maybe the number of USB controllers and what those are connected to.
* and etc.
The full list can be made based on good HCL reports on the forum with a lot of details.
## The main problem we should solve: the HCL table is not helping with choosing the laptop
Currently the HCL table is not providing enough information to choose the laptop at all, we see it on forum all the time. Also there is not mass market laptop available that would be recommended to users. Some of modern Thinkpads are working quite well with Qubes OS and can be recommended, because not everybody can nor want to buy certified model with delivery over the sea.
## What HCL report application should do instead?
The HCL report application should ask user about all that, preferably providing buttons to test it if possible, or at least instructions what should be done to check each point. User can skip points if they like. All the lsusb, lspci outputs should still be preserved, user can be asked about the removal of serial numbers and preview the results of such steps.
## Some valuable columns instead of current ones can be:
1. Year the device was presented. And age filtering is desired, to avoid seeing 15 years old devices that are impossible to buy new.
2. `Max Memory` column. Not out of box memory but how much can be added in total.
3. CPU scores. Laptop models can have different CPU models, their single/total score should be present for all options or as a range. Because Qubes OS experience is very much about CPU and memory. Good source of comparable CPU scores: https://www.cpubenchmark.net/singleCompare.php.
## Loosing potential users of Qubes OS community
I think Qubes OS is loosing a lot of potential users, who want to buy hardware and try Qubes OS, but there are:
1. No proper guides what exactly to buy on mass market,
2. No way to understand it from HCL table,
3. Even when people on forum ask about it, they got actual no solution, except info that a couple of certified models are supported.
People leave the forum and Qubes OS dissatisfied, staying on GNU/Linux or something like that.
There are good resources on making pretty beautiful filterable, sortable tables via bootstrap. For example:
An extended Bootstrap table with radio, checkbox, sort, pagination, and other added features.
If you have prior experience with bootstrap and/or web development and you are willing to spare some time to improve the HCL page, your help is highly appreciated.
5 Likes