Skip to content

Nominate @Zaczero#104

Closed
Zaczero wants to merge 1 commit into
NixOS:mainfrom
Zaczero:main
Closed

Nominate @Zaczero#104
Zaczero wants to merge 1 commit into
NixOS:mainfrom
Zaczero:main

Conversation

@Zaczero
Copy link
Copy Markdown
Member

@Zaczero Zaczero commented Mar 27, 2026

Hello,

I like nixpkgs and it's apparent to me that it lacks people to commit stuff.

https://github.com/NixOS/nixpkgs/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aopen+author%3AZaczero

9 out of my 40 prs have a approval but are never commited. Stuff like that demotivates.

While I don't intend to review/commit other, unrelated PRs, at least I hope I can help nixpkgs by committing changes that I am related to in some way. I am hoping to help the Python team too, because, as you can see here, it's dead:

NixOS/nixpkgs#446725

NixOS/nixpkgs#446749

NixOS/nixpkgs#494800

(not that I'll commit it without other people's actual review, just providing it as a reference)

and I'm a Python-first dev and I care about high quality Python and AI packaging in nixpkgs.

I was brought to nixpkgs and then nixos because of the idea of having a large package set that works on any distro. The beauty of nixos modules and reproducibility really changed the way I manage my personal servers and develop software. I want to help benefit my and others' workflows.

@emilazy
Copy link
Copy Markdown
Member

emilazy commented Apr 14, 2026

We understand that we have a triage problem in Nixpkgs and that it’s frustrating to have your work go unmerged. However, due to the importance of code review and security for a widely‐used central package repository like Nixpkgs, we discourage self‐merging outside of specific circumstances, and consider good communication and collaboration in triaging, reviewing and merging the contributions of others to be the main role of a committer. As a result, we can’t accept your application.

We don’t think it’s fair to say that Python maintenance is dead. The Python maintainers do a huge amount of work in Nixpkgs and it’s unfortunately natural that sometimes contributions will struggle to get a timely review as a result. We have the Nixpkgs Review Requests Matrix room and PRs ready for review Discourse thread for PRs that have been sitting for more than a week without review. Since the PRs you linked concern the Python interpreter itself, you might want to try raising them in the Nixpkgs Python Matrix room for expert attention.

It looks like some of your other PRs have been approved or previous reviewed by committers (red/green icon next to the reviews) – I’d suggest pinging them again to take another look if they’ve approved without merging or you’ve addressed their previous feedback.

There’s a good practical contributing advice section of our contributor documentation that can help out with getting your PRs merged. In particular, the “How can I get a committer to look at my PR?” and “Committers work on a push-basis” sub‐sections have advice expanding on my suggestions here.

We do take the triage problem seriously and agree that there’s room for improvement here. The Nixpkgs merge bot allows non‐committer maintainers to merge a subset of pull requests, and we’ve expanded the criteria recently. Onboarding new committers is important too, but only improves the triage situation if they’re active in reviewing other people’s contributions. Substantive reviews from non‐committers help PRs get triaged too, and is the primary thing we look for when reviewing committer applications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants