PEP 588: add how to nosy the expert (#1141)
Also mention that discussions can happen in Discourse.
This commit is contained in:
parent
e81fa07b63
commit
5326c3a38d
23
pep-0588.rst
23
pep-0588.rst
|
@ -210,17 +210,22 @@ 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
|
||||
-------------------
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
===========
|
||||
|
||||
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.
|
||||
|
||||
|
||||
A GitHub account should not be a requirement
|
||||
--------------------------------------------
|
||||
|
||||
|
@ -267,7 +272,9 @@ Further questions and discussions
|
|||
|
||||
There is a dedicated `#pep581
|
||||
<https://python.zulipchat.com/#narrow/stream/130206-pep581>`_ stream
|
||||
in python.zulipchat.com.
|
||||
in python.zulipchat.com. Alternatively, you can post questions
|
||||
on Discourse under the
|
||||
`Core-Workflow <https://discuss.python.org/c/core-workflow>`_ category.
|
||||
|
||||
|
||||
Acknowledgements
|
||||
|
|
Loading…
Reference in New Issue