Skip to content

Nominate @keenanweaver - #160

Open
keenanweaver wants to merge 1 commit into
NixOS:mainfrom
keenanweaver:keenanweaver
Open

keenanweaver wants to merge 1 commit into
NixOS:mainfrom
keenanweaver:keenanweaver

Conversation

@keenanweaver

Copy link
Copy Markdown
Member

Figured it was time to throw my hat into the ring. For those that haven't seen my face around, I've been mostly contributing to the gaming ecosystem of nixpkgs, typically through reviews, but I've contributed code as well. If you're looking at gaming related flakes outside of nixpkgs, you may have seen me contribute to one of those as well.

To be completely honest, this is a hobby for me and I'm not interested in making this a second job, so I want to focus on stuff I actually care about, which is gaming. I'd be glad to offer input, mentoring, or guidance on any work in nixpkgs, but I'm not particularly interested in scopes outside of gaming related leaf packages and governance. I feel support is currently lagging behind other efforts in nixpkgs and I see a great opportunity, especially with the newly established gaming team, to rectify these issues.

I have no qualms with (respectfully) pinging other maintainers in nixpkgs or authors upstream to get work over the finish line. A lot of my recent work has been enabled by @iedame's invaluable Nixkeeper tool which brings observability and accountability to nixpkgs.

Some goals of mine, both long- and short- term:

  • Get writableDirWrapper merged: writableDirWrapper: init nixpkgs#361114
  • Formalize policies for 'legal gray areas' with regard to gaming in nixpkgs. See the discussion that occurred in the PR perfect_dark perfect_dark: init at 0-unstable-2025-08-25 nixpkgs#306767
  • Bump and modernize all gaming packages, and ensure automation and maintainership is in place for their continued upkeep.
  • Make nixpkgs a fun place for people to devote their time. I see a lot of dismissive, curt, and (frankly) tactless reviews. I admit I have been all of those at certain points. We're all people here and each of us deserves time & respect. We want people to contribute, so let's make it an accommodating place.

If you're all OK with that, I'd be glad to continue my goal my making nixpkgs a premier gaming ecosystem, but as a committer.

If I don't meet qualifications, please let me know so I can improve. Thanks.

Here are my stats:


@keenanweaver

# # excluding @r-ryantm
PRs authored 122 N/A
PRs authored & merged 103 N/A
PRs reviewed 367 308
PRs otherwise commented 30 23
PRs otherwise involved 11 7
Issues authored 90 N/A
Issues otherwise commented 40 N/A
Issues otherwise involved 4 N/A

Generated with https://gist.github.com/pbsds/7af827a53c103cd3d40902f9b0b21843.

@iedame

iedame commented Oct 24, 2026 •

Copy link
Copy Markdown

Keenan has a bright mind and always provides useful feedback in the fields he is familiar with. Even before we started the Gaming team, he was one of the first people I had in mind when I needed a second opinion.

Right now, we have thousands of gaming-related packages that need more attention to stay updated, work properly, and get added to Nixpkgs. These packages are often very niche, require more time and testing, and frequently require the proper game licenses just to test them.

I know some people question the presence of games in Nixpkgs, especially older ones that often rely on EOL or vulnerable dependencies. I was actually discussing this with Keenan recently, and we both believe legacy games need a proper and secure out-of-tree home so they do not block security cleanups when the time comes. Granting Keenan the commit bit would allow us to smoothly move these ideas forward.

I'm sure Keenan would be a great addition to Nixpkgs as a committer, even if accepted at a later date, so I definitely approve this.

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

Projects

Status: Open

Development

Successfully merging this pull request may close these issues.

8 participants