Nominate @dramforever

[infinisil]

Migrating nomination from #50 (comment) as part of switching to PR-based process: #34

I would like to nominate @dramforever. While they do not have super many contributions yet, their interactions have always shown a great understanding about nixpkgs internals.

Examples here are:

• qemu: Fix Python deps, the third time nixpkgs#436516 (comment), complex cross-compiling setups around qemu+python
• cargoSetupHook, rustc: Force frame pointers for !isx86_32 nixpkgs#420797, compiler hardening flags (frame pointers) for rust

As well as some more recent, maybe even more ambitious projects (albeit unfinished as of now):

• Partially fix cross compilation for Zig nixpkgs#438621 (working towards a cross-enabled Zig)

Our compilers are a mess. Emily is cleaning up old LLVMs, and we still have build failures to GCC 14 around, while we are working on making GCC 15 default just now. Expertise with compilers is sparse, i believe extra help in reviewing compiler changes could be of use.

Dram is also active on more obscure platforms, having fixed occasional mips builds and joined the loongarch team. They maintain only few packages, though the packages they do maintain are kept up to date. They have been welcome to newbies both on matrix and first contributions on github, something that should hold some value in my opinion.

Their contributions here might not be enough to qualify for commit bit yet, that decision is for the committer delegation to make. Personally, i do value their reviews on the occasion our work intersects.

Originally posted by @LordGrimmauld in #50

Thank you @LordGrimmauld for your nomination. Assuming the relatively few contributions wouldn't be a problem, if i get the commit bit, I expect to mainly use it to, where it makes sense to do so, push forward:

• Newcomer contributions
• Fixes in areas I'm familiar with

In addition to merging those contributions that are good and ready but are otherwise falling through the cracks, having the commit bit would be a strong motivation for me to review these changes as well. Even though I can submit reviews already, it is a slight bummer for the author that, after implementing the dozen "request changes" comments from me, the next course action is to find someone else to actually merge it.

My own "specialty" is in cross and exotic, as have been noted, but my idea of using the commit bit would be mainly to unblock the contributions of others. I guess with a touch that I'd be trying to have new packages in Nixpkgs work with cross from the get go, if possible.

Originally posted by @dramforever in #50

[infinisil]

Strong endorsement for @dramforever, who has helped me with kernel and Rust-related Nixpkgs stuff multiple times on Matrix and reliably has good insights and taste.

Originally posted by @emilazy in #50

[wolfgangwalther]

Approved. Thank you for your contributions!

Please feel free to reach out to @emilazy, who has volunteered to be a mentor, if you run into any situations you’re uncertain about.