From dbf54c24ffee9c11a4d2a614aad3ce4a5110ca2e Mon Sep 17 00:00:00 2001 From: Samuel Herman Date: Tue, 25 Feb 2025 09:21:30 -0800 Subject: [PATCH 1/4] fix the verbiage for adding new repository Signed-off-by: Samuel Herman --- ADMINS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ADMINS.md b/ADMINS.md index cc8e913c49d..280226bc8e1 100644 --- a/ADMINS.md +++ b/ADMINS.md @@ -52,8 +52,8 @@ Adopt organizational practices documented in this repo, work in the open, and co 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. This will change shortly following the [formation of the OpenSearch Software Foundation](https://foundation.opensearch.org/). While the admins above have admin-level permissions, they do not have permissions to create new repositories or move repositories into the organization. +[The OpenSearch Software Foundation](https://foundation.opensearch.org) 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. -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). +All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore require the repository maintainers 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). 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. To request moving a repo into this organization, please open a proposal in your repo, have repo maintainers confirm they wish to move, and engage admins via the [#admin-requests channel on the public Slack](https://opensearch.slack.com/archives/C051CKVFB2A). From 99c7bca4590db01cabbb43f401407854cc75179d Mon Sep 17 00:00:00 2001 From: Samuel Herman Date: Tue, 25 Feb 2025 09:26:39 -0800 Subject: [PATCH 2/4] fix verbiage to expect Signed-off-by: Samuel Herman --- ADMINS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ADMINS.md b/ADMINS.md index 280226bc8e1..74350726e66 100644 --- a/ADMINS.md +++ b/ADMINS.md @@ -54,6 +54,6 @@ There are currently two ways new repositories may appear in the opensearch-proje [The OpenSearch Software Foundation](https://foundation.opensearch.org) 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. -All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore require the repository maintainers 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). +All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore expect the repository maintainers 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). 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. To request moving a repo into this organization, please open a proposal in your repo, have repo maintainers confirm they wish to move, and engage admins via the [#admin-requests channel on the public Slack](https://opensearch.slack.com/archives/C051CKVFB2A). From 9048f4730dd2a362605fc9929fd155ecdccd9e01 Mon Sep 17 00:00:00 2001 From: Samuel Herman Date: Wed, 26 Feb 2025 14:34:58 -0800 Subject: [PATCH 3/4] add also change of process to include a ticket to .github repo Signed-off-by: Samuel Herman --- ADMINS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ADMINS.md b/ADMINS.md index 74350726e66..44e73eca7e6 100644 --- a/ADMINS.md +++ b/ADMINS.md @@ -54,6 +54,6 @@ There are currently two ways new repositories may appear in the opensearch-proje [The OpenSearch Software Foundation](https://foundation.opensearch.org) 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. -All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore expect the repository maintainers 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). +All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore expect the repository maintainers to be engaged when necessary. If you wish to create a repository in this organization, or move a repository into opensearch-project, please create a ticket in this [repo](https://github.com/opensearch-project/.github), like this [example](https://github.com/opensearch-project/.github/issues/291). 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. To request moving a repo into this organization, please open a proposal in your repo, have repo maintainers confirm they wish to move, and engage admins via the [#admin-requests channel on the public Slack](https://opensearch.slack.com/archives/C051CKVFB2A). From 78ea33ff5fa2ac7162d42c92efe3c0ada2b165aa Mon Sep 17 00:00:00 2001 From: sam-herman <97131656+sam-herman@users.noreply.github.com> Date: Tue, 4 Mar 2025 18:48:05 -0800 Subject: [PATCH 4/4] Update ADMINS.md Co-authored-by: Peter Nied Signed-off-by: sam-herman <97131656+sam-herman@users.noreply.github.com> --- ADMINS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ADMINS.md b/ADMINS.md index 44e73eca7e6..9961e5d2bc0 100644 --- a/ADMINS.md +++ b/ADMINS.md @@ -54,6 +54,6 @@ There are currently two ways new repositories may appear in the opensearch-proje [The OpenSearch Software Foundation](https://foundation.opensearch.org) 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. -All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore expect the repository maintainers to be engaged when necessary. If you wish to create a repository in this organization, or move a repository into opensearch-project, please create a ticket in this [repo](https://github.com/opensearch-project/.github), like this [example](https://github.com/opensearch-project/.github/issues/291). +All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore expect the repository maintainers to be engaged when necessary. If you wish to create a repository in this organization, or move a repository into opensearch-project, please create a ticket in this [repo](https://github.com/opensearch-project/.github), like this [example](https://github.com/opensearch-project/.github/issues/291). 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. To request moving a repo into this organization, please open a proposal in your repo, have repo maintainers confirm they wish to move, and engage admins via the [#admin-requests channel on the public Slack](https://opensearch.slack.com/archives/C051CKVFB2A).