Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Create an explicit list of all Release Manager GPG keys

Open
#2,530 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale

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.

Description

admin backend

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.

Dominant language
Python
Stars
1.7k
Forks
700
Avg merge
1d 23h
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/pythondotorg

All issues in python/pythondotorg

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.