@@ -62,32 +62,15 @@ the Python Software Foundation, always follow the `PSF Code of Conduct`_.
62
62
Becoming a member of the Python triage team
63
63
===========================================
64
64
65
- Any Python core developers are welcome to invite a Python contributor to the
65
+ All Python core developers are welcome to invite a Python contributor to the
66
66
Python triage team. Triagers will be responsible to handle not just issues, but
67
67
also pull requests, and even managing backports. A Python triager has access to
68
68
more repositories than just CPython.
69
69
70
- Any existing active contributor to the Python repository on GitHub can
71
- transition into becoming a Python triager. They can request this to any core
72
- developer, and the core developer can pass the request to the `Python
73
- organization admin
74
- <https://devguide.python.org/devcycle/?highlight=organization%20admin#current-owners> `_
75
- on GitHub. The request can be made confidentially via a DM in Discourse, or
76
- publicly by opening an `issue in the core-workflow repository
77
- <https://github.com/python/core-workflow/issues/new?template=triage_membership.md> `_.
78
-
79
- For every new triager, it would be great to announce them in the python-committers
80
- mailing list and core-workflow category in Discourse. `Example announcement
81
- <https://discuss.python.org/t/abhilash-raj-has-been-granted-triage-role-on-github/2089> `_.
82
-
83
-
84
- Gaining the "Triager" Role on the Issue Tracker
85
- ===============================================
86
-
87
70
When you have consistently shown the ability to properly
88
71
help triage issues without guidance, you may request that you
89
- be given the "Triager" role on the `issue tracker `_ . You can make the request
90
- to any person who already has the Triager role . If they decide you are ready
72
+ be given the "Triager" role on the :ref: `issue tracker < tracker >` . You can make the request
73
+ to any core developer . If they decide you are ready
91
74
to gain the extra privileges on the tracker they will then act as a mentor to
92
75
you until you are ready to do things entirely on your own. There is no set rule
93
76
as to how many issues you need to have helped with before or how long you have
@@ -102,4 +85,16 @@ an issue for you in order to properly triage something. This will not only help
102
85
speed up and simplify your work in helping out, but also help lessen the
103
86
workload for everyone by gaining your help.
104
87
105
- .. _issue tracker : https://devguide.python.org/tracker/
88
+ Any existing active contributor to the Python repository on GitHub can
89
+ transition into becoming a Python triager. They can request this to any core
90
+ developer, either confidentially via a DM in Discourse, or
91
+ publicly by opening an `issue in the core-workflow repository
92
+ <https://github.com/python/core-workflow/issues/new?template=triage_membership.md> `_.
93
+ If the core devloper decides you are ready to gain the extra privileges on the
94
+ tracker, they will ask a :ref: `Python organization admin <current owners >`
95
+ to invite you to the Python organisation, and then act as a mentor to you until
96
+ you are ready to do things entirely on your own.
97
+
98
+ For every new triager, it would be great to announce them in the python-committers
99
+ mailing list and core-workflow category in Discourse. `Example announcement
100
+ <https://discuss.python.org/t/abhilash-raj-has-been-granted-triage-role-on-github/2089> `_.
0 commit comments