Documented admin permissions for adding maintainers and creating repo…

…s. (#174) * Documented admin permissions for adding maintainers and creating repos. Signed-off-by: dblock <[email protected]> * Removed internal Amazon link. Signed-off-by: dblock <[email protected]> * Added a bit of info of how admins became admins. Signed-off-by: dblock <[email protected]> * Renamed Organizational Best Practices to Organizational Practices. Signed-off-by: dblock <[email protected]> --------- Signed-off-by: dblock <[email protected]>
opensearch-project · Sep 20, 2023 · 17519a8 · 17519a8
1 parent 7e9f536
commit 17519a8
Showing 1 changed file with 31 additions and 16 deletions.
diff --git a/ADMINS.md b/ADMINS.md
@@ -4,27 +4,30 @@
   - [Prioritize Security](#prioritize-security)
   - [Enforce Code of Conduct](#enforce-code-of-conduct)
   - [Add/Remove Maintainers](#addremove-maintainers)
-  - [Adopt Organizational Best Practices](#adopt-organizational-best-practices)
+  - [Adopt Organizational Practices](#adopt-organizational-practices)
+- [New Repos](#new-repos)
 
 ## Overview
 
-This document explains who the admins are (see below), what they do in opensearch-project, and how they should be doing it. They are added with Admin-level permissions to every repositories in opensearch-project organization.  If you're interested in becoming a maintainer, see [MAINTAINERS](MAINTAINERS.md). If you're interested in contributing, see [CONTRIBUTING](CONTRIBUTING.md).
+This document explains who the admins are (see below), what they do in opensearch-project, and how they should be doing it. These individuals are members of an "admin" GitHub team that is given Admin-level permissions to every repository in opensearch-project organization. These are individuals that worked on creating the OpenSearch fork, and those that currently support the organization-wide infrastructure, such as the public [CI/CD](https://build.ci.opensearch.org/).
+
+If you're interested in becoming a maintainer, see [MAINTAINERS](MAINTAINERS.md). If you're interested in contributing, see [CONTRIBUTING](CONTRIBUTING.md).
 
 ## Current Admins
 
-| Admin              | GitHub ID                               | Affiliation |
-| ------------------ | --------------------------------------- | ----------- |
-| Daniel Doubrovkine | [dblock](https://github.com/dblock)     | Amazon      |
-| Nick Knize         | [nknize](https://github.com/nknize)     | Amazon      |
-| Peter Nied         | [peternied](https://github.com/peternied)     | Amazon      |
-| William Beckler    | [wbeckler](https://github.com/wbeckler) | Amazon      |
-| Rishabh Singh      | [rishabh6788](https://github.com/rishabh6788) | Amazon      |
+| Admin              | GitHub ID                                           | Affiliation |
+| ------------------ | --------------------------------------------------- | ----------- |
+| Daniel Doubrovkine | [dblock](https://github.com/dblock)                 | Amazon      |
+| Nick Knize         | [nknize](https://github.com/nknize)                 | Amazon      |
+| Peter Nied         | [peternied](https://github.com/peternied)           | Amazon      |
+| William Beckler    | [wbeckler](https://github.com/wbeckler)             | Amazon      |
+| Rishabh Singh      | [rishabh6788](https://github.com/rishabh6788)       | Amazon      |
 | Prudhvi Godithi    | [prudhvigodithi](https://github.com/prudhvigodithi) | Amazon      |
-| Sayali Gaikawad    | [gaiksaya](https://github.com/gaiksaya) | Amazon      |
+| Sayali Gaikawad    | [gaiksaya](https://github.com/gaiksaya)             | Amazon      |
 | Peter Zhu          | [peterzhuamazon](https://github.com/peterzhuamazon) | Amazon      |
-| Barani bbarani     | [bbarani](https://github.com/bbarani) | Amazon      |
-| Charlotte Henkle   | [CEHENKLE](https://github.com/CEHENKLE) | Amazon      |
-| Zelin Hao          | [zelinh](https://github.com/CEHENKLE) | Amazon      |
+| Barani Bikshandi   | [bbarani](https://github.com/bbarani)               | Amazon      |
+| Charlotte Henkle   | [CEHENKLE](https://github.com/CEHENKLE)             | Amazon      |
+| Zelin Hao          | [zelinh](https://github.com/CEHENKLE)               | Amazon      |
 
 ## Admin Permissions
 
@@ -42,8 +45,20 @@ Act on [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) violations by revoking access, and
 
 ### Add/Remove Maintainers
 
-Perform administrative tasks, such as [adding](MAINTAINERS.md#adding-a-new-maintainer) and [removing maintainers](MAINTAINERS.md#removing-a-maintainer).
+Perform administrative tasks, such as [adding](RESPONSIBILITIES.md#adding-a-new-maintainer) and [removing maintainers](RESPONSIBILITIES.md#removing-a-maintainer).
+
+Please note that maintainers typically do not have admin-level permissions in their repos in this organization. Admin-level permissions allow for sensitive and destructive actions, such as managing security, or deleting a repository. Therefore, admin access in opensearch-project was designed to be deliberately centralized in ways that requires that two people to make any one sensitive change. If you need to perform an admin function, such as adding or removing a maintainer, please [follow the maintainer nomination process](RESPONSIBILITIES.md#becoming-a-maintainer), then ask to effect permissions by tagging `@admin` in your pull request, or the [#maintainers channel on the public Slack](https://opensearch.slack.com/archives/C05L60S4UBT). One of the above-mentioned admins will make this change for you.
+
+### Adopt Organizational Practices
+
+Adopt organizational practices documented in this repo, work in the open, and collaborate with other admins by opening issues before making process changes. Prefer consistency, and avoid diverging from practices in the opensearch-project rganization.
+
+## New Repos
+
+There are currently two ways new repositories may appear in the opensearch-project organization: creating a new repo and adopting, or moving a repo from outside of the organization into it. The process is the same.
+
+The AWS Open Source Program Office (OSPO) currently owns and manages the opensearch-project organization, and has permissions to create a new repo. While the admins above have admin-level permissions, they do not have permissions to create new repositories or move repositories into the organization.
 
-### Adopt Organizational Best Practices
+All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore require an Amazon team to be engaged when necessary. If you wish to create a repository in this organization, or move a repository into opensearch-project, please contact one of the above-mentioned admins via the [#maintainers channel on the public Slack](https://opensearch.slack.com/archives/C05L60S4UBT).
 
-Adopt organizational best practices, work in the open, and collaborate with other admins by opening issues before making process changes. Prefer consistency, and avoid diverging from practices in the opensearch-project organization.
+While the opensearch-project organization has adopted [opensearch-plugin-template-java](https://github.com/opensearch-project/opensearch-plugin-template-java), or [opensearch-project/opensearch-learning-to-rank-base](https://github.com/opensearch-project/opensearch-learning-to-rank-base) in the past, we generally encourage you to start and run with your open-source project outside of the organization, and only consider making it part of it when you wish to include your already very popular component or tool in the "official" distribution.