Difference between revisions of "PineNote Development/TODOs"
Jump to navigation
Jump to search
Aarondabomb (talk | contribs) |
Aarondabomb (talk | contribs) |
||
Line 14: | Line 14: | ||
# How do we control the backlight? | # How do we control the backlight? | ||
# How do we build alacritty correctly? | # How do we build alacritty correctly? | ||
# How do we force a screen refresh? See converstaion here: https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$tfumBpnP2UPouNpaeFrggR40ZkrD_pHAtJdQmQvzL-o?via=matrix.org&via=kde.org&via=tchncs.de |
Revision as of 08:07, 23 August 2022
These are a list of open questions that pertain to configurations necessary for the OS to function nicely in the short-term during development and in the long term for people. If you know the answer to one of these or want something to do, please make a page with this info and link it here :)
Configuration TODOs
Configuration unknowns that are helpful during development
- How do we pin packages so Mesa isn't updated when we update using our package manger?
Configurations that will likely be needed long-term
- What're good configurations for GNOME?
- How do we get a mouse playing nicely?
Documentation TODOs
Note: These are things we know how to do, but they just haven't been documented in the wiki yet.
- How do we control the backlight?
- How do we build alacritty correctly?
- How do we force a screen refresh? See converstaion here: https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$tfumBpnP2UPouNpaeFrggR40ZkrD_pHAtJdQmQvzL-o?via=matrix.org&via=kde.org&via=tchncs.de