iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 581: Add info about bug triage team and CLA assistant (#916)

This commit is contained in:
Mariatta 2019-03-07 10:22:57 -08:00 committed by GitHub
parent 33dc2afa5f
commit f4f2f158c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
pep-0581.rst
View File

@ -161,9 +161,24 @@ The current CLA process itself is not ideal. Currently, contributors to
devguide, peps, and core-workflow need to sign a CLA, and it requires a bpo
account. A bpo account should not be required for those projects.
Currently, the CLA process requires personnel to manually check the records.
Question: Will it be possible to completely automate the CLA process, so
it does not require human intervention?
There is an ongoing effort to start using our own instance of CLA assistant
instead of the current CLA process in place. Discussion about this has been
started in `core-workflow mailing list <https://mail.python.org/archives/list/core-workflow@python.org/thread/JBV3XJVD2DLDX5DY7TZEA6CO5YPNHJ2C/>`_ as
well as on `Discourse <https://discuss.python.org/t/using-cla-assistant-for-python/990>`_.
Create Bug Triage Team on GitHub
--------------------------------
The bug triagers on bpo are valuable to the core Python workflow, and we
definitely would need even more help with triaging issues on GitHub.
It has been `proposed on Discourse <https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992/5>`_
for us to create a "bug triage" team on GitHub to help with closing issues,
notifying the appropriate parties, as well as applying labels to issues
and pull requests. We can grant the "write" permission to the "bug triage"
team, while limiting merging pull requests to "CPython core developer" team
on GitHub.
Create labels for issue triage
------------------------------
@ -184,6 +199,9 @@ We will create the corresponding labels::
In addition, we'll create a ``needs triage`` label.
The final "labels" to be created can be decided at a later time when
it is time to start switching to GitHub issues.
Create issue templates
----------------------