Skip to content

[2024-2025] Nixpkgs committer nominations #50

Description

@Mic92

This issue is not used anymore, refer to this section instead: https://github.com/NixOS/nixpkgs-committers?tab=readme-ov-file#nominations

Original Hi, the purpose of this issue is to nominate new nixpkgs contributors for commit access to nixpkgs. The process is described in [nixpkgs-committers org documentation](https://github.com/NixOS/org/blob/main/doc/nixpkgs-committers.md).

@lorenzleutgeb also wrote a script to summarize past GitHub contributions. However more importantly we value when nominees work well together in the community and take ownership for their mistakes.

If you have questions regarding becoming a nixpkgs maintainer, you can contact the Nixpkgs committer delegation team:

Activity

  1. mweinelt commented on Jul 4, 2024

    @mweinelt
    Member

    I want to nominate @emilazy, who recently carried the OpenSSH SIGALARM vulnerability across all branches and even wrote an advisory and took the time to answer questions and construct a timeline.

    Emily has 75 merged PRs and over 100 reviewed PRs. She has been contributing on and off since 2019, and contributed for example the initrd OpenSSH migration.

    I think it would be beneficial to further enable a capable person like her.

  2. emilazy commented on Jul 4, 2024

    @emilazy
    Member

    Thank you for the nomination! I’d be happy to accept the commit bit if offered. I’ve frequently had long absences from FOSS work in the past several years, so I can’t guarantee availability, but I’d like to be able to contribute more consistently going forward. In the wider ecosystem I’m also a nix-darwin committer so I’m reasonably familiar with the module system, and I helped nix-darwin and Home Manager migrate from the old DocBook documentation toolchain to unblock its removal from Nixpkgs. The biggest thing I’ve done recently was working on removing Mesa as a channel blocker on Darwin, which had caused significant issues and friction in the past. I’m a user of both macOS and Linux and would like to continue to help bridge the gap between the two platforms in terms of maintenance and quality.

  3. willcohen commented on Jul 4, 2024

    @willcohen

    I’d like to apply for the commit bit (and also happy to wait if that makes more sense.)

    My first contribution and introduction to Nix was in 2021-2022, to upstream to QEMU an old patchset to enable 9pfs on Darwin, thus allowing for fixing up remote file support on QEMU and thus lima and podman on Mac, with many thanks to @alyssais and @domenkozar in guiding me through all that: NixOS/nixpkgs#122420

    Since then, I’ve added a couple smaller packages and fixed up others to work better on Mac. My focuses are around GIS software on Mac (my longstanding white whale is to get QGIS working on Mac, which is both close and far: NixOS/nixpkgs#157862), keeping emscripten up to date (usually some LLVM tip of tree backports with the help of @RaitoBezarius), Clojure stuff, the occasional dabbling in random JS or Perl packages here and there, and fixing broken things on Mac. I’ve been a little quieter the last year as work focuses pulled me a bit away from programming, but I’m working my way back in to it this summer. I know there’s a perennial need for capacity on Darwin (ie NixOS/nixpkgs#323144) and that a combo of lack of testing and lack of ability to review or land fixes is a big pain point, and would mostly like to help keep those PRs moving in a timely manner.

    58 merged PRs: https://github.com/NixOS/nixpkgs/pulls?q=sort:updated-desc+is:pr+author:willcohen+is:merged

    52 reviews:
    https://github.com/NixOS/nixpkgs/pulls?q=sort:updated-desc+is:pr+reviewed-by:willcohen+-author:willcohen (edited to remove my own PRs, thanks @eclairevoyant)

    No NixOS modules yet — I’m still predominantly Mac-centric, though I sometime play with it in a VM.

  4. eclairevoyant commented on Jul 4, 2024

    @eclairevoyant

    76 reviews of closed PRs, though probably a third of those are nixpkgs-review output of my own PRs:

    You can filter those out with -author:willcohen; filtering out own PRs should be done in general for all PR review queries.

  5. lorenzleutgeb commented on Jul 9, 2024

    @lorenzleutgeb
    Member

    You can filter those out with -author:willcohen; filtering out own PRs should be done in general for all PR review queries.

    I added this condition to the script mentioned in OP.

  6. gador commented on Jul 20, 2024

    @gador
    Member

    I like to express my interest in a commit bit, too.
    I've been working with NixOS and nixpkgs since 2021 and started contributing since then. Currently I maintain or co-maintain 51 packages.
    Recently I wrote the blendfarm module and updated a few modules in the past.
    I have the most experience with python, but also some experience with c++, qt, shell and a bit of go. My usual systems involve x86_64-linux, but I also have aarch64-linux and aarch64-darwin systems on which I can test packages or modules.

    I'd like to use my commit bit to help merge already reviewed packages and to reduce the time it takes to merge simple updates. When time permits, I look through the pr ready for review thread on discourse and add my 2 cents.

  7. Mic92 commented on Jul 22, 2024

    @Mic92
    MemberAuthor

    @emilazy @gador @willcohen Welcome to the team! Sorry for the delay. We (nixpkgs team admins) are currently discussing, where we are moving future applications, but until then we stick to this issue.

  8. infinisil commented on Jul 25, 2024

    @infinisil
    Member

    I'd like to nominate @philiptaron! They've been super helpful in co-maintaining https://github.com/NixOS/nixpkgs-check-by-name, but have also been active in Nixpkgs with

  9. donovanglover commented on Jul 28, 2024

    @donovanglover
    Member
  10. mattpolzin commented on Jul 30, 2024

    @mattpolzin

    I'm interested in commit privileges. I reckon I'm on the low end for existing contributions to nixpkgs so no hard feelings if I just don't have the exposure yet to warrant committing; I think my bid for more responsibility is as much grounded in my record of maintenance across a number of OSS communities (most recently Idris2 and beam-community) as it is in nixpkgs PRs merged thus far. The reason I believe that is relevant is because I know how to show restraint and gradually assert myself in more places as I gain confidence that I know the established precedents.

    My primary areas of interest in nixpkgs are: The Elixir ecosystem (PRs), Idris2 (PRs), and Darwin (PRs). I also have a vested interest in the Ruby ecosystem, NixOS, and the overall health and success of nixpkgs!

  11. Mic92 commented on Jul 31, 2024

    @Mic92
    MemberAuthor

    @philiptaron welcome to the team.

  12. Mic92 commented on Aug 2, 2024

    @Mic92
    MemberAuthor

    @donovanglover welcome to the team as well.

  13. Mic92 commented on Aug 2, 2024

    @Mic92
    MemberAuthor

    @mattpolzin Not a reject, but none of us (@jtojnar, @NickCao and me) knows you very well, so we would like to know if there is a person from the community you have interacted with and who can vouch for you?

  14. mattpolzin commented on Aug 2, 2024

    @mattpolzin

    @Mic92 Sure, that's fair. I'm not sure if any single existing Nixpkgs committer has interacted with me in more than one context so it's quite possible no one would say they know me well (yet). I'd mention @happysalada or @fabianhjr who I think have had positive experiences working with me in the context of Elixir and Idris2 packaging but I definitely won't feel slighted if they don't feel they are ready to vouch for me at this point. I believe the folks maintaining Bruno with me have seen me be responsive, knowledgable, constructive, etc. but last I checked none of us are committers (so no one to suggest vouches for me there).

  15. fabianhjr commented on Aug 2, 2024

    @fabianhjr
    Member

    Can vouch about positive interactions here on nixos and on some idris stuff a while back

  16. 194 remaining items

  17. LordGrimmauld commented on Nov 4, 2025

    @LordGrimmauld
    Contributor

    I think you missed mine from 3 months ago: #50 (comment)

    i did not list the nominations from before the last committer delegation decision (#50 (comment)). However, between the last collected batch by wolfgang (#50 (comment)) and that decision, you made your application. I had assumed the committer delegation considered that application when they made their last decision, but i don't actually know whether that is the case. I'll add you to the above batch.

  18. transferred this issue fromNixOS/nixpkgson Nov 5, 2025
  19. infinisil commented on Nov 5, 2025

    @infinisil
    Member

    As part of #34, I've now migrated all nominations and endorsements since #50 (comment) to individual issues:

    For nominations that were previously not addressed by the commit delegators, please open a new nomination.

    See this section on how to nominate going forward.

    To get notified of new nominations, you can subscribe to this issue: #35

  20. locked as resolved and limited conversation to collaborators on Nov 5, 2025
  21. changed the title [-]Nixpkgs committers interest list[/-] [+][2024-2025] Nixpkgs committer nominations[/+] on Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions