You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, the granter of permissions (usually the Coordination Committee)
25
21
should send a message to the new recipient of write permissions listing the
26
22
responsibilities and expectations that go with this - a template for this email
27
23
is available [in this repo](../messages/maintainer_access.md). That message may
28
24
contain a prompt for a response, which should be cc-ed/forwarded to
29
-
coordinators@astropy.org.
25
+
`coordinators[at]astropy.org`.
30
26
31
27
## Access levels
32
28
@@ -41,6 +37,9 @@ Coordinated package maintainers receive **admin access** to the coordinated
41
37
package repositories via the **<packagename> maintainers** GitHub team (e.g.,
42
38
'astroquery maintainers').
43
39
40
+
Lower priviledge access (e.g., write, triage) could be assigned to additional
41
+
contributors as separate teams (e.g., 'Astroquery Triage').
42
+
44
43
### Core package release coordinators
45
44
46
45
Core package release coordinators receive **admin access** to the core
@@ -74,7 +73,10 @@ which might not cover all cases, other ways include:
74
73
75
74
### Automated access
76
75
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).
0 commit comments