Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tracking] Options for improving Qubes on low-resource hardware #6131

Closed
tabbyrobin opened this issue Oct 19, 2020 · 1 comment
Closed

[Tracking] Options for improving Qubes on low-resource hardware #6131

tabbyrobin opened this issue Oct 19, 2020 · 1 comment
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: not applicable E.g., help/support requests, questions, discussions, "not a bug," not enough info, not actionable. T: task Type: task. An action item that is neither a bug nor an enhancement.

Comments

@tabbyrobin
Copy link

Qubes OS version (if applicable)
All versions / recent and future releases.

Affected component(s) or functionality (if applicable)
Hardware support, performance, general user experience.

Brief summary
This is (intended to be a helpful) meta/tracking issue for assessing options to make Qubes work better on limited / low-resource hardware. (Limited RAM, disk, battery, limited cpu virt features, for low-budget users, etc.)

Additional context
One of the main barriers to Qubes is hardware (the other being technical knowlege). For folks without a lot of spare cash this is a particular challenge. By "low-resource" i mean a huge range from making Qubes work better on a laptop with only 8gb RAM, to perhaps eventually Qubes on arm/phones.

Relevant documentation you've consulted
A bunch, but none particularly relevant here.

Related, non-duplicate issues

#3925
#2233
#5298
#2826
#5696
#4398
#3725
#1310
#5041
#3887
#5520
#5371
#4120
#1919
#2766

@tabbyrobin tabbyrobin added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: task Type: task. An action item that is neither a bug nor an enhancement. labels Oct 19, 2020
@andrewdavidwong
Copy link
Member

andrewdavidwong commented Oct 19, 2020

I appreciate the effort and intention to be helpful. However, I suggest posting this in the forum rather than qubes-issues. In order to keep qubes-issues useful as a practical day-to-day tool for the devs, our issue reporting guidelines require that every issue must be about a single, actionable thing, and this issue does not appear to satisfy that requirement. However, the forum has no such requirement. The forum also facilitates discussion and supports additional features that may be beneficial for this type of use case. Therefore, the forum would be more a more appropriate venue for this post. Thank you for your understanding.

@andrewdavidwong andrewdavidwong added the R: not applicable E.g., help/support requests, questions, discussions, "not a bug," not enough info, not actionable. label Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: not applicable E.g., help/support requests, questions, discussions, "not a bug," not enough info, not actionable. T: task Type: task. An action item that is neither a bug nor an enhancement.
Projects
None yet
Development

No branches or pull requests

2 participants