Skip to content

Commit 7669322

Browse files
committed
Remove GitHub 2FA blurb
and add in info for automated access section.
1 parent 0c3ff26 commit 7669322

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

policies/permissions.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,16 +17,12 @@ a duty primarily performed at the moment by the Coordination Committee.
1717
Temporary permissions should instead use the "collaborator" feature on Github to
1818
make it clear that these permissions are temporary in nature.
1919

20-
Regardless of access level, even if it is temporary,
21-
[GitHub two-factor authentication](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)
22-
must be enabled for the affect user accounts.
23-
2420
Additionally, the granter of permissions (usually the Coordination Committee)
2521
should send a message to the new recipient of write permissions listing the
2622
responsibilities and expectations that go with this - a template for this email
2723
is available [in this repo](../messages/maintainer_access.md). That message may
2824
contain a prompt for a response, which should be cc-ed/forwarded to
29-
coordinators@astropy.org .
25+
`coordinators[at]astropy.org`.
3026

3127
## Access levels
3228

@@ -41,6 +37,9 @@ Coordinated package maintainers receive **admin access** to the coordinated
4137
package repositories via the **<package name> maintainers** GitHub team (e.g.,
4238
'astroquery maintainers').
4339

40+
Lower priviledge access (e.g., write, triage) could be assigned to additional
41+
contributors as separate teams (e.g., 'Astroquery Triage').
42+
4443
### Core package release coordinators
4544

4645
Core package release coordinators receive **admin access** to the core
@@ -74,7 +73,10 @@ which might not cover all cases, other ways include:
7473

7574
### Automated access
7675

77-
(TODO: Fill in info from the automated invite bot that Matt Craig deployed.)
76+
We have an automated workflow to
77+
[invite organization members based on merged PRs](https://github.com/astropy/astropy-tools/actions/workflows/update_org_members.yml).
78+
However, we are open to suggestions on how to improve it
79+
over at [astropy-tools GitHub Issue 178](https://github.com/astropy/astropy-tools/issues/178).
7880

7981
### Manual request
8082

0 commit comments

Comments
 (0)