From 125cf58567ccbab5a2ac7239561c720dd81c3c38 Mon Sep 17 00:00:00 2001 From: Mariatta Date: Fri, 9 Aug 2019 12:39:53 -0700 Subject: [PATCH 1/5] Add procedure for adding people to the Python Triage team Based on discussion: https://discuss.python.org/t/criteria-for-promoting-people-to-the-python-triage-team/2105/ Closes https://github.com/python/devguide/issues/308 --- triaging.rst | 29 +++++++++++++++++++++++++---- 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/triaging.rst b/triaging.rst index 2f09d078d..ec6a8a5a4 100644 --- a/triaging.rst +++ b/triaging.rst @@ -43,11 +43,32 @@ or a veteran core developer, they're actively choosing to voluntarily donate the time towards the improvement of Python. As is the case with any member of the Python Software Foundation, always follow the `PSF Code of Conduct`_. -.. note:: +Becoming a member of Python Triage team +--------------------------------------- + +Any Python core developers are welcome to invite a Python contributor to the +Python Triage team. Do note that the responsibilities of a Python Triage member +is more elevated than a bug triager in bpo. For example, the Python Triage member +has access to more repositories than just CPython. Triages will be responsible +to handle not just issues, but also pull requests, and even commanding backports. + +Any existing triagers in b.p.o can transition to the Python Triage role. +They can request this to any core developer, and the core developer +can pass the request to the Python organization admin on GitHub. The request +can be made privately via DM in Zulip or Discourse, or publicly by opening +an issue in core-workflow. + +Any contributor who is not already a triager in b.p.o can also self-nominate +to be a member of Python Triage team. They can request this to any core developer, +via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow. +If a core developer agrees and willing to vouch for them, the core developer +can pass the request to the administrator. They should also be added as +triager in bpo. + +For every new triager, it would be great to announce them in Python-committers +mailing list and core-workflow category in Discourse. `Example announcement +`_. - Existing members with the "Developer" role on the `issue tracker`_ are welcome to - self-nominate for triage team membership if they are interested. - GitHub Labels for PRs ''''''''''''''''''''' From ff7549b58c7d6707de289e2e1a5333851023dce8 Mon Sep 17 00:00:00 2001 From: Mariatta Date: Mon, 12 Aug 2019 11:05:51 -0700 Subject: [PATCH 2/5] Apply suggestions from code review Co-Authored-By: Kyle Stanley --- triaging.rst | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/triaging.rst b/triaging.rst index ec6a8a5a4..78fa122ae 100644 --- a/triaging.rst +++ b/triaging.rst @@ -43,29 +43,29 @@ or a veteran core developer, they're actively choosing to voluntarily donate the time towards the improvement of Python. As is the case with any member of the Python Software Foundation, always follow the `PSF Code of Conduct`_. -Becoming a member of Python Triage team +Becoming a member of the Python triage team --------------------------------------- Any Python core developers are welcome to invite a Python contributor to the -Python Triage team. Do note that the responsibilities of a Python Triage member -is more elevated than a bug triager in bpo. For example, the Python Triage member -has access to more repositories than just CPython. Triages will be responsible -to handle not just issues, but also pull requests, and even commanding backports. +Python triage team. Do note that the responsibilities of a Python triager +is more elevated than a developer on bpo. For example, the Python triager +has access to more repositories than just CPython. Triagers will be responsible +to handle not just issues, but also pull requests, and even managing backports. -Any existing triagers in b.p.o can transition to the Python Triage role. +Any existing developers on b.p.o can transition into becoming a Python triager. They can request this to any core developer, and the core developer can pass the request to the Python organization admin on GitHub. The request -can be made privately via DM in Zulip or Discourse, or publicly by opening -an issue in core-workflow. +can be made privately via a DM in Zulip or Discourse, or publicly by opening +an issue in the core-workflow repository. -Any contributor who is not already a triager in b.p.o can also self-nominate -to be a member of Python Triage team. They can request this to any core developer, +Any contributor who is not already a developer on b.p.o can also self-nominate +to be a member of Python triage team. They can request this to any core developer, via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow. -If a core developer agrees and willing to vouch for them, the core developer -can pass the request to the administrator. They should also be added as -triager in bpo. +If a core developer agrees and is willing to vouch for them, the core developer +can pass the request to the GitHub administrator. They should also be added as +developer on bpo. -For every new triager, it would be great to announce them in Python-committers +For every new triager, it would be great to announce them in the python-committers mailing list and core-workflow category in Discourse. `Example announcement `_. From a9e1c15b616230b5c48f25d82e596736759a5585 Mon Sep 17 00:00:00 2001 From: Mariatta Date: Mon, 12 Aug 2019 11:16:36 -0700 Subject: [PATCH 3/5] Update triaging.rst --- triaging.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/triaging.rst b/triaging.rst index 78fa122ae..ac72f2524 100644 --- a/triaging.rst +++ b/triaging.rst @@ -44,7 +44,7 @@ time towards the improvement of Python. As is the case with any member of the Python Software Foundation, always follow the `PSF Code of Conduct`_. Becoming a member of the Python triage team ---------------------------------------- +------------------------------------------- Any Python core developers are welcome to invite a Python contributor to the Python triage team. Do note that the responsibilities of a Python triager From 6a1716b3c747e1b0999bf810739e04c0cfad7d51 Mon Sep 17 00:00:00 2001 From: Mariatta Date: Mon, 12 Aug 2019 11:17:52 -0700 Subject: [PATCH 4/5] link to the triage membership template --- triaging.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/triaging.rst b/triaging.rst index ac72f2524..f5e7561b9 100644 --- a/triaging.rst +++ b/triaging.rst @@ -56,7 +56,8 @@ Any existing developers on b.p.o can transition into becoming a Python triager. They can request this to any core developer, and the core developer can pass the request to the Python organization admin on GitHub. The request can be made privately via a DM in Zulip or Discourse, or publicly by opening -an issue in the core-workflow repository. +an `issue in the core-workflow repository +`_. Any contributor who is not already a developer on b.p.o can also self-nominate to be a member of Python triage team. They can request this to any core developer, From cb06a4c9082ab85fdc012f1cca87661416e1238b Mon Sep 17 00:00:00 2001 From: Mariatta Date: Thu, 15 Aug 2019 12:54:18 -0700 Subject: [PATCH 5/5] Link to org admin document also change from privately -> confidentially --- triaging.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/triaging.rst b/triaging.rst index f5e7561b9..464248984 100644 --- a/triaging.rst +++ b/triaging.rst @@ -54,14 +54,16 @@ to handle not just issues, but also pull requests, and even managing backports. Any existing developers on b.p.o can transition into becoming a Python triager. They can request this to any core developer, and the core developer -can pass the request to the Python organization admin on GitHub. The request -can be made privately via a DM in Zulip or Discourse, or publicly by opening +can pass the request to the `Python organization admin +`_ +on GitHub. The request +can be made confidentially via a DM in Zulip or Discourse, or publicly by opening an `issue in the core-workflow repository `_. Any contributor who is not already a developer on b.p.o can also self-nominate to be a member of Python triage team. They can request this to any core developer, -via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow. +confidentially via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow. If a core developer agrees and is willing to vouch for them, the core developer can pass the request to the GitHub administrator. They should also be added as developer on bpo.