User:CodingKoopa
Contact
For public matters, please ping me in #archlinux-wiki. I am usually codingkoopa, though sometimes my client appends numbers at the end due to connection issues :)
For private matters, feel free to email me.
My hours are either EST or PST, and I check my messages either once a day or once every few months.
About
I'm a full-time performance engineer (with bachelor's degrees in CS and Math) mostly interested in systems-level software, though I have also done DevOps and webdev work. Some of my personal values are, with descending relevance:
- I care a lot about high-quality, concise documentation and minimizing signal-to-noise. I do my best to maintain good notes wherever I go!
- I like to be helpful and friendly, and encourage more people to be curious
- I use open-source software in many places (and am hoping to replace more online services eventually).
- I avoid private transportation when possible, largely for ideological reasons.
My personal website is at https://koopa.sh/.
I use she/her pronouns.
Projects
Current projects:
- QPA in Qt (WIP at User:CodingKoopa/Qt)
- create User:CodingKoopa/Direct_Rendering_Infrastructure
- rewrite intel_pstate on CPU_frequency_scaling (on hold)
Future ideas:
- drop qt4
- I think others have taken care of this already!
- get more archived page from [1] [2]
- KDE#System-wide
- revisit Intel graphics issue
- Fine tune Firefox smooth scrolling (this looks terrible... why is there zero documentation?)
- Clarify Bluetooth 5.1 (but i don't wanna read the spec)
- wayland in Arch boot process
- Document KDE D-Bus interfaces
- ArchWiki talk:Requests#Update for new WirePlumber configuration format (if nobody else does)
- youtube-dl update for yt-dlp (follow KeePass)
- better landing page for alternate means of installation of Arch
- Special:PermanentLink/772926#Tips for finding and using D-Bus interfaces
- move GPT before MBR, such as in Partitioning
- article on piecing together your own DE (but using a WM and finding the other parts)
- kinda like what File manager functionality does
- wayland first policy (in how we order sections and sentences)
- GTK/QT ordering (HiDPI, Wayland, unified look and feel)
- outreach thing: 2-monthly archwiki digest of big things that have changed (e.g. a config section previously recommended no longer being necessary, or a big new section added). would work best if other parts of the arch team were also in on it
Some policies I have had thoughts about:
- Unified page header structure (I either pitched this in IRC or in some discussion but it didn't have much traction/support).
- Having guidelines on regional English varieties (Special:Permalink/735176#American_vs._British_English_Usage)
More
See User:CodingKoopa/Showcase for my favorite content additions/edits.
Other pages in my userwiki: