fix the verbiage for adding new repository #293
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sam-herman
requested review from
CEHENKLE,
dblock,
mch2,
peternied and
saratvemulapalli
as code owners
Signed-off-by: Samuel Herman <[email protected]>
Signed-off-by: Samuel Herman <[email protected]>
sam-herman
force-pushed
the
adding-new-repository
branch
from
3ec1c52 to
99c7bca
Compare
peternied
previously approved these changes
Feb 25, 2025
andrross
approved these changes
Feb 25, 2025
dblock
requested changes
Feb 26, 2025
| @@ -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. | |||
There was a problem hiding this comment.
While the admins above have admin-level permissions, they do not have permissions to create new repositories or move repositories into the organization.
Is this true? I believe the admins actually do have permissions now to do this.
There was a problem hiding this comment.
@dblock how to confirm this?
ADMINS.md
Outdated
|
|
||
| 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 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). |
There was a problem hiding this comment.
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.
I believe the right process is to open a ticket in .github. The admins are not in the #maintainers channel either.
There was a problem hiding this comment.
make sense, will modify here.
There was a problem hiding this comment.
@dblock modified per your recommendation.
Signed-off-by: Samuel Herman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The current verbiage for adding new repositories still lists Amazon as the responsible party.
This change fixes it to mention the new governance structure with the OpenSearch Software Foundation.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.