-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
the README of the Debian GH orga says:
Lines 22 to 24 in 4b668ce
| The signature needs to be made with your PGP key currently in the | |
| Debian keyring. | |
| All active Debian Developers will be approved. |
there's a github action in place that tries to enforce this policy, by automatically closing applications that are not from "a Debian person".
the test that is currently performed is, whether the applicant is able to sign some text with a key that is available via https://keyring.debian.org/
as the author of the github action, i took it for granted that:
- the set of
All active Debian Developersis identical to the set of owners of aPGP key currently in the Debian keyring - any key that is in the
Debian keyringcan be obtained from hkp://keyring.debian.org/
recently someone applied for membership in the Debian GH-organization:
obviously they are Debian Maintainers but not Debian Developers (in the strict sense), which means:
- the key they used to sign the application form can be found on hkp://keyring.debian.org/
- the key (as obtained from the keyring) does not contain a
@debian.orgemail address.
I don't think it is required to actively add your@debian.orgaddress to your key (in the debian-keyring). however, this triggered closer inspection of the application - neither the key, nor any email associated with it (nor the username, as given in the application) could be found on https://db.debian.org/ - leading to the question: "is this a valid application"?
so I'd like to clarify which people are allowed in this GH organization:
- just "DD (uploading)"
- anybody on the keyring as served by hkp://keyring.debian.org/
(I did some research, but I'm afraid I still do not know which group of keys exactly are served via keyring.debian.org) - something in between? (e.g. "DDs(uploading)+DDs(nonuploading)")
the README should be updated to clarify this.
Metadata
Metadata
Assignees
Labels
No labels