User:Sam/TODO

Security

 * Tooling to make security work easier, like pinging maintainers, changing whiteboards, and so on
 * Investigate if any additional gcc flags should be added to hardened profile
 * Test and merge CET changes (done!)
 * Relevant:
 * Add useful searches / tips to wiki pages?
 * Audit maintainer-needed packages, possibly dev-java too, and maybe www-apps for known vulns w/o bugs

Documentation

 * Add mention of circular dependencies to handbook?
 * Add mention of circular dependencies page to Portage?

Ongoing

 * Work on any devmanual items in notes
 * Work on any wiki items in notes

Bugs

 * Report bash malloc bug on HPPA upstream -
 * dev-lang/R bits on HPPA -
 * Report R unaligned access noticed during build
 * ... ICE when building sometimes?
 * Report original build failure too. OK with lapack.

Misc

 * Revive 'notes' idea for metadata.xml
 * gentoo-dev post
 * Python PGO, ideally trained on Portage unit tests
 * PGO itself is now done!
 * Add further examples to the musl notes
 * Summarise modern-day Hardened profile, update wiki pages, etc
 * Improve wiki pages on nattka / stabilisation requests
 * Add warnings on dhcp client to NetworkManager page
 * Make sure docs on SIGNED_OFF_BY etc are on wiki (done)

Improving upgrades

 * Wait a few months before using new EAPIs in tree (require stable Portage to have supported it for.. 3? months)
 * News item when a new EAPI is introduced to help folks who inevitably hit issues with their Portage being too stale (see also: )
 * Take longer to drop support entirely for older Pythons in the eclasses (just python-exec is the main issue here)
 * In particular, makes it harder to upgrade Portage if it's too old (even with nodeps and such).
 * One ends up with lots of errors like:
 * One ends up with lots of errors like:
 * Improve the "rescue Portage" documentation (done: Project:Portage/Fixing_broken_portage)
 * Of particular note is this kind of error which appears when using an older Portage with a freshly synced tree:

arm64
[02:29:43]  leio and others: Does much support CPU_FLAGS_ARM on arm64? [02:29:57]  As in, actually in tree. Or is it all just arm stuff. [02:30:06]  Just wondering if that's an avenue I should look into at some point. [02:30:36]  Also, would there be any value in CPU_FLAGS_ARM64, or not really? I imagine all it'd do is simplify ebuilds wanting to support arm64 but who need to do something different to arm in order to do so.
 * CPU_FLAGS_ARM64?

Things to package

 * Various IRCds
 * Homeworld SDL (new link?)
 * Preeny
 * psi-notify
 * Termshark
 * sdhcp
 * gitui
 * Penrose
 * Convos
 * Ropper
 * Pwntools (github)
 * PyLink
 * box86
 * Spigot
 * texlab
 * sqlmap
 * wpscan
 * pdf-tools
 * Ghidra
 * Srain (in GURU at the moment)
 * managesieve?
 * 010 editor?

Attic
Packages which were on my list but are packaged now (not necessarily by me):
 * Various IRCds
 * ergo
 * plocate
 * xmrig
 * Ananicy
 * lsp-mode