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

[pep8002] Django clarifications and acknowledgements

This commit is contained in:
Łukasz Langa 2018-09-14 13:32:41 -07:00
parent 495a6be130
commit 8ccc9a2887
No known key found for this signature in database
GPG Key ID: B26995E310250568
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-8002.rst
View File

@ -503,10 +503,10 @@ Key people and their functions
The project recognizes three kinds of contributors. Members of the
core team, the Technical Board, and Fellows. Regular core committers
no longer exercise their "commit bit", instead they rely on pull
requests being reviewed and accepted. There is a bot which merges
the pull request. The Technical Board steers technical choices.
Fellows are hired contractors who triage new tickets and review patches
from the community, including non-trivial ones.
requests being reviewed and accepted. The Technical Board steers
technical choices. Fellows are hired contractors who triage new
tickets, review and merge patches from the committers and community,
including non-trivial ones.
Core team members are added by nomination and vote within the core
team, with technical board veto (so far not exercised). Technical
@ -747,6 +747,9 @@ The Project Jupyter Steering Council created the Main Governance Document for
Project Jupyter, and Carol Willing summarized the key points of that documennt
for the Jupyter section.
Thank you to Carl Meyer from the Django team for explanation how their
project's governance is set up.
Annex 1: Template questions
===========================