Create an explicit list of all Release Manager GPG keys
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 700
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 11
Description
Instead of recommending users import GPG keys by ID (a process which can be fallible) we should provide a file containing all public keys of release managers both current and historical and document a direct import method to GPG instead of by key ID.
This will also be useful for future folks who may find it difficult to discover the authoritative keys.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing documentation that recommends importing Release Manager GPG keys by ID, then identify the authoritative current and historical public keys. Add a maintained file containing those keys and document direct GPG import from that file; done means users no longer need key IDs and both current and historical keys are covered.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100