Add a section on resolving disagreements between core developers
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Read the existing sections at devguide.python.org/coredev/#what-it-means and devguide.python.org/langchanges/ first. Identify where a new section on escalating tracker disagreements fits, then document the path through python-ideas, python-dev, and the PEP process with links and clear stopping points.
Written by the indexing model from the issue text.
Description
I'm not sure how we'd structure this, but I realised that the principle of "Escalate tracker disagreements to python-ideas and python-dev discussions, and potentially all the way to the PEP process" isn't clearly documented anywhere.
Once a discussion reaches the "This needs a PEP" stage, then there's https://devguide.python.org/langchanges/
I also gave a very brief overview of the concept when describing the extra responsibilities taken on by core developers in https://devguide.python.org/coredev/#what-it-means.
(Prompted by this Twitter thread, where I wanted a link for "Here is how our issue escalation process works", and couldn't find one: https://twitter.com/ncoghlan_dev/status/979228826126360577)
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 12
Contributor guide
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.
More from python/devguide
-
type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
topic-building python type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
needs: decision topic-test type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
topic-dev process type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·