docs: maintainer list

we should reflect that we are now on forgejo and have a diffrent process
to the nixos org
This commit is contained in:
isabel roses 2024-06-30 09:08:03 +01:00
parent 9ed579059e
commit c9bbdf19f1
Signed by: isabelroses
GPG key ID: 08A97B9A107A1798

View file

@ -1,67 +1,63 @@
/* List of NixOS maintainers. /*
```nix List of Aux maintainers.
handle = { ```nix
# Required handle = {
name = "Your name"; # Required
name = "Your name";
forgejo = "forgejoUsername";
forgejoId = your-forgejo-id;
# Optional, but at least one of email, matrix or githubId must be given # Optional, but at least one of email or matrix must be given
email = "address@example.org"; email = "address@example.org";
matrix = "@user:example.org"; matrix = "@user:example.org";
github = "GithubUsername";
githubId = your-github-id;
keys = [{ keys = [{
fingerprint = "AAAA BBBB CCCC DDDD EEEE FFFF 0000 1111 2222 3333"; fingerprint = "AAAA BBBB CCCC DDDD EEEE FFFF 0000 1111 2222 3333";
}]; }];
}; };
``` ```
where where
- `handle` is the handle you are going to use in nixpkgs expressions, - `handle` is the handle you are going to use in nixpkgs expressions,
- `name` is a name that people would know and recognize you by, - `name` is a name that people would know and recognize you by,
- `email` is your maintainer email address, - `email` is your maintainer email address,
- `matrix` is your Matrix user ID, - `matrix` is your Matrix user ID,
- `github` is your GitHub handle (as it appears in the URL of your profile page, `https://github.com/<userhandle>`), - `forgejo` is your forgejo handle (as it appears in the URL of your profile page, `https://git.auxolotl.org/<userhandle>`),
- `githubId` is your GitHub user ID, which can be found at `https://api.github.com/users/<userhandle>`, - `forgejoId` is your forgejo user ID, which can be found at `https://git.auxolotl.org/api/v1/users/<username>`,
- `keys` is a list of your PGP/GPG key fingerprints. - `keys` is a list of your PGP/GPG key fingerprints.
Specifying a GitHub account ensures that you automatically: `handle == forgejo` is strongly preferred whenever `forgejo` is an acceptable attribute name and is short and convenient.
- get invited to the @NixOS/nixpkgs-maintainers team ;
- once you are part of the @NixOS org, OfBorg will request you review
pull requests that modify a package for which you are a maintainer.
`handle == github` is strongly preferred whenever `github` is an acceptable attribute name and is short and convenient. If `forgejo` begins with a numeral, `handle` should be prefixed with an underscore.
```nix
_1example = {
forgejo = "1example";
};
```
If `github` begins with a numeral, `handle` should be prefixed with an underscore. Add PGP/GPG keys only if you actually use them to sign commits and/or mail.
```nix
_1example = {
github = "1example";
};
```
Add PGP/GPG keys only if you actually use them to sign commits and/or mail. To get the required PGP/GPG values for a key run
```shell
gpg --fingerprint <email> | head -n 2
```
To get the required PGP/GPG values for a key run !!! Note that PGP/GPG values stored here are for informational purposes only, don't use this file as a source of truth.
```shell
gpg --fingerprint <email> | head -n 2
```
!!! Note that PGP/GPG values stored here are for informational purposes only, don't use this file as a source of truth. More fields may be added in the future, however, in order to comply with GDPR this file should stay as minimal as possible.
More fields may be added in the future, however, in order to comply with GDPR this file should stay as minimal as possible. When editing this file:
* keep the list alphabetically sorted, check with:
nix-instantiate --eval maintainers/scripts/check-maintainers-sorted.nix
* test the validity of the format with:
nix-build lib/tests/maintainers.nix
When editing this file: See `./scripts/check-maintainer-github-handles.sh` for an example on how to work with this data.
* keep the list alphabetically sorted, check with:
nix-instantiate --eval maintainers/scripts/check-maintainers-sorted.nix
* test the validity of the format with:
nix-build lib/tests/maintainers.nix
See `./scripts/check-maintainer-github-handles.sh` for an example on how to work with this data. When adding a new maintainer, be aware of the current commit conventions
documented at [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions)
When adding a new maintainer, be aware of the current commit conventions file located in the root of the Nixpkgs repo.
documented at [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions)
file located in the root of the Nixpkgs repo.
*/ */
{ {