@@ -9,14 +9,14 @@ The purpose is to provide some institutional memory of who was given access
9
9
and why.
10
10
11
11
The first entry starts in April 2005. In keeping with the style of Misc/NEWS,
12
- newer entries should be added to the top. Entries should include the initials
13
- of the project admin who made the change or granted access. The procedure for
14
- adding or removing users is described in :ref: `altering-access `.
12
+ newer entries should be added to the top. Entries should include the name
13
+ or initials of the project admin who made the change or granted access. The
14
+ procedure for adding or removing users is described in :ref: `altering-access `.
15
15
16
16
Note, when giving new commit permissions, be sure to get a contributor agreement
17
- from the committer. See http://www.python.org/psf/contrib/ for details. When
18
- the agreement is signed, please note it in this log. SSH keys of the committer
19
- should be sent to hgaccounts@python.org .
17
+ from the committer. See http://www.python.org/psf/contrib/ for details. Commit
18
+ privileges should not be given until the contributor agreement has been signed
19
+ and received .
20
20
21
21
This file is encoded in UTF-8. If the usual form for a name is not in
22
22
a Latin or extended Latin alphabet, make sure to include an ASCII
@@ -479,18 +479,11 @@ Initials of Project Admins
479
479
Procedure for Granting or Dropping Access
480
480
-----------------------------------------
481
481
482
- To be granted the ability to manage SSH keys for committers, you must first
483
- submit a pull request to the `psf-salt repo
484
- <https://github.com/python/psf-salt/blob/master/salt/hg/config/hg-account-admins> `_
485
- to add your own SSH key to the hgaccounts account.
486
-
487
- Once you have been added to the hgaccounts accout, obtain a checkout of the keys
488
- repo::
489
-
490
- hg clone ssh://hgaccounts@hg.python.org/repo
491
-
492
- The key files are stored in the form ``first.last ``. Simply create or remove the
493
- appropriate file, commit the change, and push. A hook on the server should
494
- automatically regenerate the ``authorized_keys `` file for the ``hg `` user. Make
495
- sure to update the developer log above.
482
+ To be granted the ability to manage who is a committer, you must be a
483
+ team maintainer of the `Python core team `_ on GitHub. Once you have
484
+ that privilege you can add people to the team. They will be asked to
485
+ accept the membership which they can do by visiting
486
+ https://github.com/python and clicking on the appropriate button that
487
+ will be displayed to them in the upper part of the page.
496
488
489
+ .. _Python core team : https://github.com/orgs/python/teams/python-core
0 commit comments