Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Morten Linderud
Arch Linux Keyring
Commits
feab8a68
Verified
Commit
feab8a68
authored
Apr 29, 2021
by
Levente Polyak
🚀
Browse files
doc: split and add checks to issue templates according to responsibilities
Signed-off-by:
Levente Polyak
<
anthraxx@archlinux.org
>
parent
71a5af7f
Changes
2
Hide whitespace changes
Inline
Side-by-side
.gitlab/issue_templates/New Main Key.md
View file @
feab8a68
...
...
@@ -26,11 +26,29 @@ https://www.gnupg.org/gph/en/manual/x135.html
## Checks
### New key owner
-
[ ] The
[
workflow for adding a new main
key
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-main-key
)
has been followed
-
[ ] The key pair has been validated according to the
[
best
practices
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair
)
-
[
] The data in the [Details
](
#details
)
section is attached to this issue as
a clearsigned document
-
[ ] The revocation certificate h
older verified the revocation certificate as
working in a comment to this issue
-
[ ] The revocation certificate h
as been sent in an encrypted message to the
revocation certificate holder
-
[ ] The public key has been uploaded to the SKS infrastructure
### Keyring maintainer
-
[ ] The key pair has been validated according to the
[
best
practices
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair
)
-
[
] The data in the [Details
](
#details
)
section is correct and signed with a
valid and trusted packager key, which is part of
`pacman-key`
### Revocation Certificate Holder
-
[ ] The revocation certificate has been
[
verified
as working
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/verify-a-revocation-certificate
)
and confirmed in a comment to this issue
-
[ ] The revocation certificate has been backed up in a dedicated encrypted backup storage
.gitlab/issue_templates/New Packager Key.md
View file @
feab8a68
...
...
@@ -33,10 +33,25 @@ needs to do the signature.
## Checks
### New key owner
-
[ ] The
[
workflow for adding a new packager
key
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key
)
has been followed
-
[ ] The key pair contains one user ID with a valid
`<username>@archlinux.org`
email address
used for signing
-
[ ] The key pair has been validated according to the
[
best
practices
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair
)
-
[
] The data in the [Details
](
#details
)
section is attached to this issue as
a clearsigned document
-
[ ] The public key has been uploaded to the SKS infrastructure
-
[ ] The public key has been signed by at least three valid main keys
### Keyring maintainer
-
[ ] The key pair contains one user ID with a valid
`<username>@archlinux.org`
email address
used for signing
-
[ ] The key pair has been validated according to the
[
best
practices
](
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair
)
-
[
] The data in the [Details
](
#details
)
section is correct and signed with a
valid and trusted packager key, which is part of
`pacman-key`
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment