From 5326c3a38d9b74370662e9106fc9ac38e75b8325 Mon Sep 17 00:00:00 2001 From: Mariatta Date: Sat, 10 Aug 2019 09:10:07 -0700 Subject: [PATCH] PEP 588: add how to nosy the expert (#1141) Also mention that discussions can happen in Discourse. --- pep-0588.rst | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/pep-0588.rst b/pep-0588.rst index 31cb9fe8afc..fc766e80e2a 100644 --- a/pep-0588.rst +++ b/pep-0588.rst @@ -210,16 +210,21 @@ For GitHub, we need to add ``origin: https://bugs.python.org/issueXYZ``. For bpo, add a new field ``moved to: https://github.com/python/cpython/issue/XYZ``. +Nosy-ing the expert +------------------- -Open issues -=========== +A current functionality in bpo is to automatically nosy people who are listed +as an expert of certain area. Several Python core developers have expressed that +they prefer not having to subscribe to everything on GitHub, but only getting notified +for issues related to their area of interest and expertise. -Experts index -------------- - -At the moment, there is a mechanism to automatically add people in the experts -index to the nosy list. We need to replicate this functionality. +To help with this situation, we can develop a bot that can notify people +whenever an issue has been categorized using labels. For example, when an issue +was labeled with `area-windows`, the windows experts can be notified. +The notification can be in the form of email notification, or @-mention on GitHub. +Open issues +=========== A GitHub account should not be a requirement -------------------------------------------- @@ -267,7 +272,9 @@ Further questions and discussions There is a dedicated `#pep581 `_ stream -in python.zulipchat.com. +in python.zulipchat.com. Alternatively, you can post questions +on Discourse under the +`Core-Workflow `_ category. Acknowledgements