Nominate @otavio

[otavio]

Motivation

I'm nominating myself for nixpkgs committer access to help merge and maintain the set of packages I already look after, primarily in the embedded Linux / Yocto / Zephyr / Rust tooling space.

Contribution history

• 158 merged PRs out of 177 authored — https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+author%3Aotavio
• 438 PRs reviewed — https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+reviewed-by%3Aotavio
• Maintainer entry: maintainers/maintainer-list.nix → otavio

Packages I maintain

• Yocto / OpenEmbedded tooling: oelint-adv, python3Packages.oelint-parser, bitbake-language-server, git-repo
• Embedded device flashing / management: uuu (NXP USB Updater), snagboot, mcuboot-imgtool, mcumgr-client, smpmgr, python3Packages.smp, python3Packages.smpclient, python3Packages.zcbor, python3Packages.lpc-checksum, python3Packages.tftpy
• Renode embedded simulator: renode, renode-bin, renode-dts2repl
• Rust development tooling: cargo-msrv, cargo-valgrind, cargo-cross, cargo-limit, cargo-rr, cargo-wipe
• Terminals / tmux ecosystem: rio, tmuxp, python3Packages.libtmux
• Other: shellhub-agent, linuxPackages.rtl88x2bu, robotframework-tidy, python3Packages.junit2html

Why committer access helps

Most of what I do is keep this corner of nixpkgs current — version bumps, moves to pkgs/by-name, fixing build regressions, and reviewing PRs from contributors in the same space. Committer access would let me close the loop on straightforward updates and reviews for these packages without needing to ping another committer each time.

[emilazy]

Hi @otavio, sorry for the long response time here, and thank you for your contributions!

On the committer delegation team, a big part of what we do is evaluate how prospective committers engage as reviewers, and we haven't seen enough substantive review from you to be able to do that. Contributors' experiences of committer review are very important for the health of the project, so it's important for us to get a sense of how a prospective committer would review, even if the expectation is that that committer would mostly use their commit privileges to accelerate their own work. For that reason we don't feel we can accept your application right now.

As a side note, we want to clarify that the requirements of the new automation policy apply to communication within development spaces, including PR text and comments.

We'd be happy to re-evaluate in future when there are more in-depth reviews from you for us to look at.