Triager log/How to become a triager
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
- Domain
- documentation
Research direction
Start by reading the developer log, core developer, and triaging pages linked in the issue, then review the file proposed in #848. Done means the triager log exists, the becoming-triager guidance covers the listed onboarding steps, and the relevant pages link to one another.
Written by the indexing model from the issue text.
Description
Currently we have:
- a developer log
- an how to become a core developer pages
As far as I know, there is no equivalent to the developer log for triagers, and there is a section about becoming triagers.
I think we should:
- Add a triager log (possibly generated by the file proposed in #848)
- Add a link to the "becoming a core dev" page to the "becoming triager" section, or move both to the same page
- Improve the documentation on how to become a triager, including steps such as
- making an official announcement on Discourse
- adding the new triager to the triagers team on GitHub
- reclaiming the GitHub mannequin
- join the Discord server
- Add links between the developer/triager logs and the "becoming *" section and the other way around
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·