Skip to content

Commit cbb14bd

Browse files
committed
add document about maintainer addition
1 parent 90fc725 commit cbb14bd

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

policies/adding-new-maintainers.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
This document describes the process for adding new people to maintainer roles.
2+
"Maintainer" here basically means any role with github write powers. The
3+
process is in the hands of the Coordination Committee according to
4+
[APE0](https://github.com/astropy/astropy-APEs/blob/main/APE0.rst), which also
5+
requires the comment period. The process is:
6+
7+
1. Either the Coordination Committee or any community member including the
8+
nominee may nominate someone for a role via private or public email,
9+
Slack message, in person request that is then recorded in meeting notes, etc.
10+
2. A Coordination Committee member then sends a message to the person
11+
nominated, making sure they understand the role, its responsibilities, and
12+
confirming that the nominee agrees. Suggested text of that message is
13+
[here](https://github.com/astropy/astropy-project/blob/main/messages/maintainer_access.md).
14+
3. If the nominee does not accept, the process stopps here.
15+
4. If the nominee does accept, a message goes out to the community, starting
16+
a two-week clock on the feedback period [as required by APE0](https://github.com/astropy/astropy-APEs/blob/main/APE0.rst#responsibilities-and-authority).
17+
The Coordination Committee member overseeing the process can make a PR at
18+
this time adding the member to the roles page as a place for public comment.
19+
5. Once the two week period has elapsed, the coordination committee makes a
20+
final decision based on any feedback. If the appointment is confirmed,
21+
6. The nominee is added to the roles page (i.e., the PR created in step 4 can
22+
be merged), and the nominee receives the necessary Github or other
23+
permissions and a confirmation message to complete the process.

0 commit comments

Comments
 (0)