maintainers: add FKouhai

[FKouhai]

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[Shawn8901]

As i found as comment from drupol super nice formulated, i cite:

Hello,

Thank you for your request.

Could you please provide some context or motivation behind your request to be added to the maintainer list? It would be helpful for us to understand how this aligns with your intentions or contributions to the project.

In my opinion, it might be more effective to create a PR that demonstrates why being included in the maintainer list is relevant. For instance:

Are you planning to contribute to nixpkgs?
Do you intend to adopt and maintain specific packages?

If your goal is to adopt packages, there's no need for a separate PR for this request. Instead, you can include a commit in a PR where it's clear which packages you'd like to maintain.

Please note that this is not about discouraging new contributors, on the contrary! We value new maintainers, and some contextual information will help us streamline the process and support your contributions effectively.

Thank you.

So no need for a PR that just adds you to the maintainer list, just include that commit as first into the PR for the package/module that you like to contribute to or adopt.

[FKouhai]

@Shawn8901 oh, thanks for feedback, I thought I had to split my PR's, I have this PR as well for a new package(it isnt okay I still need to push some changes I thought I made)
#371906

[Shawn8901]

No problem. Welcome on board!
Just cherry-pick this commit into your branch that inits the package, and re-order the commits (you can do that whilst rebasing), that should be okay then.
This PR you can close this PR after cherry-picking.