Nominate @mdaniels5757

[infinisil]

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

I'm nominating @mdaniels5757 for commit access. He has only been contributing since May this year, but has already been acting like a committer. On paper, he is only maintaining four packages himself - but with 265 reviewed and 236 merged PRs, he is clearly taking care of Nixpkgs as a whole.

He is doing a lot of the daily maintenance work that the project needs: Package updates, backports and cleanups like dropping packages or inactive maintainers. With commit access, he could work much more efficiently by directly pushing to r-ryantm PRs instead of replacing them. He has not worked much on NixOS or more fundamental changes, I think, but has demonstrated to be well aware of our contribution guidelines from the very beginning. I trust his judgement for which things he'd be comfortable committing.

My interactions with him were always positive, he communicates clearly and politely and would be good addition to the team!

Originally posted by @wolfgangwalther in #50

Thank you for the nomination, @wolfgangwalther!

As you said, I've mostly been focused on updates and cleanups (most recently dealing with r-ryantm updates that were in some way defective). A commit bit would be a great help with these: both to merge others' PRs, and to be able to undraft and push to r-ryantm's PRs.

A few of my other contributions you may have noticed:

• Unbreaking many packages that were broken by GCC 14 (tracking issue: Tracking: package failing with GCC 14 nixpkgs#388196)
• Updating or dropping packages with security vulnerabilities
• Lots and lots of manual backports!

And a few of my reviews:

• python3.pkgs.sphinx-version-warning: Fix build with sphinx-prompt=1.10.0 nixpkgs#426455
• [Backport release-25.05] paretosecurity: 0.2.38 -> 0.3.2 nixpkgs#431393
• vscode-extension-update: Fix usage of experimental Nix features nixpkgs#427027 (although the other review that I was somewhat responding to seems to have disappeared...)
• protobuf_28: remove nixpkgs#414681

I understand that I haven't been doing this for that long, and that there's plenty I don't know. (Of course, I would not merge things in areas I'm not confident that I understand!) But I think there's still plenty that a commit bit would help me do for nixpkgs.

Originally posted by @mdaniels5757 in #50

[philiptaron]

I co-sign what Wolfgang wrote. Let's say yes to @mdaniels5757.

[niklaskorz]

Michael was of great help in dealing with the Tarmageddon Rust CVE in nixpkgs

[iedame]

Michael will be a great addition to nixpkgs!

[wolfgangwalther]

Approved. Thank you for your contributions!

We recognize that the tenure in the project is shorter here than most new committers, but believe that the widely‐scoped maintenance and review work is valuable and worth empowering.

[philiptaron]

Congratulations!