Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add policy for adding new role #460

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add policy for adding new role #460

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion policies/adding-new-role-members.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,4 +34,4 @@ The process is:
8. The nominee receives the necessary GitHub or other permissions for the new role.
9. The nominee gets added to the astropy-core-maintainers mailing list.
10. The Coordination Committee member sends a confirmation message to the nominee
to complete the process.
to complete the process.
23 changes: 23 additions & 0 deletions policies/adding-new-roles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
This document describes the process for adding new named roles. This
document is *not* about how people are added to the roles, which is covered under
[adding-new-role-members.md](https://github.com/astropy/astropy-project/blob/main/policies/adding-new-role-members.md).

The process is:

1. A voting member or maintainer in a related role, after consulting with other members in
related roles, opens a PR to [astropy.github.com](https://github.com/astropy/astropy.github.com)
to add this new role. The PR must describe clearly why this role is essential to the Astropy
Project and has clear description of associated responsibilities. If this role has sub-roles,
those must be clarified as well in the same manner. This new role must be declared Unfilled
for now (separation of concerns). This new role cannot duplicate any existing roles.
2. The PR author sends out a notice of this PR to astropy-dev mailing list, with cc to the
Coordination Committee, starting 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).
3. Once the two week period has elapsed, the Coordination Committee makes a
final decision based on any feedback.
4. If the new role is confirmed, the PR is merged. Otherwise, it is closed without merge.
5. The Coordination Committee member sends an update to the astropy-dev notice
with an update, regardless of the decision.
6. If new role is accepted in Step 4, proceed to
[adding-new-role-members.md](https://github.com/astropy/astropy-project/blob/main/policies/adding-new-role-members.md)
for the next steps.