Repository navigation
Triager log/How to become a triager #852
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 Machine-parsable developers list #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
Activity
ezio-melotti commentedon May 4, 2022
Another thing that should be documented (if it isn't already), is the "Python Triage Membership" requests found at https://github.com/python/core-workflow/issues/new/choose (e.g. python/core-workflow#416).
Currently it's not obvious if these issues are requesting the addition to someone to the GitHub Triage team, or if it's a request to consider them as potential candidate. It is also not entirely clear who should act on these issues and what should be done.
As far as I understand:
pythonorg (if he isn't already part of it)python-triageteam (this might automatically send an invite to join the org)I suggest to:
core-workflowrepoezio-melotti commentedon May 5, 2022
I just found out that there is a
docs-triagersteam too. Maybe they should also be included.More info at https://discuss.python.org/t/documentation-triagers/13850