Nominate @PerchunPak

[PerchunPak]

I would like to nominate myself for the commit bit

I have been active in nixpkgs since March 2024, and started by reviewing the backlog for all new Vim plugins (the Vim maintainer figsoda did not respond for a few months, and so there were a lot of unreviewed PRs). After that, I became one of the maintainers of the new NixOS/neovim team. I proceeded with mostly reviewing new plugins but also creating a bunch of PRs, including the Vim ecosystem.

Highlights of my contributions:

• pluginupdate.py: add support for adding/updating individual plugins nixpkgs#336137

  Just showcasing it here to show that I can make my hands dirty, if a feature was requested years ago. I still have PTSD from that script though

  This also fixed many bugs, like randomized order of plugins in the result file (I wonder how many megabytes are wasted every time you git clone nixpkgs because of constant rearrangements of plugins in every vimPlugins update over the years)

• Helped with the bump of nvim-treesitter to their new version, which is a complete rewrite. PRs: vimPlugins.nvim-treesitter: master -> main update nixpkgs#470883, vimPlugins.nvim-treesitter-legacy: init nixpkgs#472119.

  In particular, the first one mentioned the second in the release notes, but we forgot to merge the second one before everyone went on the new year holidays. I was probably the only one active during that period, and could unbreak user configs if I had merge access.

Other than Vim, I also created several new ecosystems in nixpkgs:

• PR astal: building blocks for app shells (like quickshell)
• PR Heavily refactored bat-extras (basically rewritten from scratch) to a modular system, just like astal
• PR And not yet merged calibrePlugins: plugins for the Calibre e-book reader

In total:

• I am a maintainer of 48 packages (excluding 1786 auto-generated Vim plugins and 46 non-generated, that are maintained by me and the Neovim team)
• 100 PRs merged
• 412 PRs reviewed

[emilazy]

Thank you for your work on Nixpkgs, and sorry for the delayed response. We appreciate your substantial contributions, especially to the Vim ecosystem. However, we heard concerns privately from multiple people about communication patterns that they felt were hostile and deterred collaboration. In light of this, we don’t feel we can grant the commit bit at this time.

We can give further detail on request (including privately), although per our guidelines we can’t discuss who shared feedback without their consent.