@@ -6,8 +6,8 @@ process itself is in the hands of the Coordination Committee according to
6
6
7
7
Note some of the steps below are highlighted as specific for maintainers.
8
8
Maintainers are the people who keep a package or sub-package working. In
9
- particular, they review and merge PRs, keep track of what's going on and
10
- organize ideas for future development (see
9
+ particular, they review and merge PRs, keep track of what's going on and
10
+ organize ideas for future development (see
11
11
https://www.astropy.org/team.html#Subpackage_maintainer
12
12
for details). Therefore, a maintainer requires particular Github permissions,
13
13
which is highlighted in the process below.
@@ -30,6 +30,7 @@ The process is:
30
30
final decision based on any feedback.
31
31
6 . If the appointment is confirmed, the nominee is added to the roles page
32
32
(i.e., the PR created in step 4 can be merged).
33
- 7 . The nominee receives the necessary Github or other permissions for the new role.
34
- 8 . The Coordination Committee member sends a confirmation message to the nominee
33
+ 7 . The nominee receives the necessary GitHub or other permissions for the new role.
34
+ 8 . The nominee gets added to the astropy-core-maintainers mailing list.
35
+ 9 . The Coordination Committee member sends a confirmation message to the nominee
35
36
to complete the process.
0 commit comments