From 006dfc6cd7c053b0fb102997a74186f0f22b6509 Mon Sep 17 00:00:00 2001 From: Harsha Vamsi Kalluri Date: Wed, 19 Oct 2022 05:47:09 -0700 Subject: [PATCH] Updating current maintainers: adding @VachaShah, @dblock, @harshavamsi (#219) * Updating maintainers: adding @VachaShah @dblock @harshavamsi Signed-off-by: Harsha Vamsi Kalluri * Fix formatting Signed-off-by: Harsha Vamsi Kalluri * Fix admin names and text Signed-off-by: Harsha Vamsi Kalluri * Add rushi to emeritus Signed-off-by: Harsha Vamsi Kalluri * Removing rushi from codeowners Signed-off-by: Harsha Vamsi Kalluri Signed-off-by: Harsha Vamsi Kalluri --- .github/CODEOWNERS | 2 +- ADMINS.md | 34 +++----------------- MAINTAINERS.md | 80 ++++++++-------------------------------------- 3 files changed, 20 insertions(+), 96 deletions(-) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 74f7d882..aa3ed1a5 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1,2 +1,2 @@ # This should match the team set up in https://github.com/orgs/opensearch-project/teams and include any additional contributors -* @opensearch-project/clients @axeoman @deztructor \ No newline at end of file +* @VachaShah @dblock @harshavamsi @axeoman @deztructor @Shephalimittal \ No newline at end of file diff --git a/ADMINS.md b/ADMINS.md index e2ca0596..0393d900 100644 --- a/ADMINS.md +++ b/ADMINS.md @@ -1,38 +1,14 @@ -- [Overview](#overview) - [Current Admins](#current-admins) - [Admin Responsibilities](#admin-responsibilities) - - [Prioritize Security](#prioritize-security) - - [Enforce Code of Conduct](#enforce-code-of-conduct) - - [Adopt Organizational Best Practices](#adopt-organizational-best-practices) - -## Overview - -This document explains who the admins are (see below), what they do in this repo, and how they should be doing it. 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 | -| -------------------------| ----------------------------------------------------| ----------- | -| Charlotte | [CEHENKLE](https://github.com/CEHENKLE) | Amazon | -| Henri Yandell | [hyandell](https://github.com/hyandell) | Amazon | -| Rushi Agrawal | [rushiagr](https://github.com/rushiagr) | Amazon | -| Shephali Mittal | [Shephalimittal](https://github.com/Shephalimittal) | Amazon | +| Admin | GitHub ID | Affiliation | +| ---------------- | --------------------------------------- | ----------- | +| Charlotte Henkle | [CEHENKLE](https://github.com/CEHENKLE) | Amazon | +| Henri Yandell | [hyandell](https://github.com/hyandell) | Amazon | ## Admin Responsibilities -As an admin you own stewartship of the repository and its settings. Admins have [admin-level permissions on a repository](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization). Use those privileges to serve the community and protect the repository as follows. - -### Prioritize Security - -Security is your number one priority. Manage security keys and safeguard access to the repository. - -Note that this repository is monitored and supported 24/7 by Amazon Security, see [Reporting a Vulnerability](SECURITY.md) for details. - -### Enforce Code of Conduct - -Act on [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) violations by revoking access, and blocking malicious actors. - -### Adopt Organizational Best Practices - -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. \ No newline at end of file +[This document](https://github.com/opensearch-project/.github/blob/main/ADMINS.md#admin-responsibilities) explains what admins do in this repo, and how they should be doing it. \ No newline at end of file diff --git a/MAINTAINERS.md b/MAINTAINERS.md index e5d34a2e..9082c269 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -1,76 +1,24 @@ - [Overview](#overview) - [Current Maintainers](#current-maintainers) -- [Maintainer Responsibilities](#maintainer-responsibilities) - - [Uphold Code of Conduct](#uphold-code-of-conduct) - - [Prioritize Security](#prioritize-security) - - [Review Pull Requests](#review-pull-requests) - - [Triage Open Issues](#triage-open-issues) - - [Backports](#backports) - - [Be Responsive](#be-responsive) - - [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo) - - [Use Semver](#use-semver) - - [Release Frequently](#release-frequently) - - [Promote Other Maintainers](#promote-other-maintainers) +- [Emeritus](#emeritus) ## Overview -This document explains who the maintainers are (see below), what they do in this repo, and how they should be doing it. If you're interested in contributing, see [CONTRIBUTING](CONTRIBUTING.md). +[This document](https://github.com/opensearch-project/.github/blob/main/MAINTAINERS.md#maintainer-responsibilities) explains who the maintainers are (see below), what they do in this repo, and how they should be doing it. If you're interested in contributing, see [CONTRIBUTING](CONTRIBUTING.md). ## Current Maintainers -| Maintainer | GitHub ID | Affiliation | -|-----------------|-----------------------------------------------------|-------------| -| Aleksei Atavin | [axeoman](https://github.com/axeoman) | Aiven | -| Denis Zalevskiy | [deztructor](https://github.com/deztructor) | Aiven | -| Rushi Agrawal | [rushiagr](https://github.com/rushiagr) | Amazon | -| Shephali Mittal | [Shephalimittal](https://github.com/Shephalimittal) | Amazon | +| Maintainer | GitHub ID | Affiliation | +| -------------------- | --------------------------------------------------- | ----------- | +| Vacha Shah | [VachaShah](https://github.com/VachaShah) | Amazon | +| Daniel Doubrovkine | [dblock](https://github.com/dblock) | Amazon | +| Harsha Vamsi Kalluri | [harshavamsi](https://github.com/harshavamsi) | Amazon | +| Aleksei Atavin | [axeoman](https://github.com/axeoman) | Aiven | +| Denis Zalevskiy | [deztructor](https://github.com/deztructor) | Aiven | +| Shephali Mittal | [Shephalimittal](https://github.com/Shephalimittal) | Amazon | -## Maintainer Responsibilities +## Emeritus -Maintainers are active and visible members of the community, and have [maintain-level permissions on a repository](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization). Use those privileges to serve the community and evolve code as follows. - -### Uphold Code of Conduct - -Model the behavior set forward by the [Code of Conduct](CODE_OF_CONDUCT.md) and raise any violations to other maintainers and admins. - -### Prioritize Security - -Security is your number one priority. Maintainer's Github keys must be password protected securely and any reported security vulnerabilities are addressed before features or bugs. - -Note that this repository is monitored and supported 24/7 by Amazon Security, see [Reporting a Vulnerability](SECURITY.md) for details. - -### Review Pull Requests - -Review pull requests regularly, comment, suggest, reject, merge and close. Accept only high quality pull-requests. Provide code reviews and guidance on incomming pull requests. Don't let PRs be stale and do your best to be helpful to contributors. - -### Triage Open Issues - -Manage labels, review issues regularly, and triage by labelling them. - -All repositories in this organization have a standard set of labels, including `bug`, `documentation`, `duplicate`, `enhancement`, `good first issue`, `help wanted`, `blocker`, `invalid`, `question`, `wontfix`, and `untriaged`, along with release labels, such as `v1.0.0`, `v1.1.0` and `v2.0.0`, and `backport`. - -Use labels to target an issue or a PR for a given release, add `help wanted` to good issues for new community members, and `blocker` for issues that scare you or need immediate attention. Request for more information from a submitter if an issue is not clear. Create new labels as needed by the project. - -### Backports - -The Github workflow in [backport.yml](.github/workflows/backport.yml) creates backport PRs automatically when the original PR with an appropriate label `backport ` is merged to main. To backport a PR to `1.x`, add a label `backport 1.x` to the PR, once this PR is merged to main, the workflow will create a backport PR to the `1.x` branch. - -### Be Responsive - -Respond to enhancement requests, and forum posts. Allocate time to reviewing and commenting on issues and conversations as they come in. - -### Maintain Overall Health of the Repo - -Keep the `main` branch at production quality at all times. Backport features as needed. Cut release branches and tags to enable future patches. - -### Use Semver - -Use and enforce [semantic versioning](https://semver.org/) and do not let breaking changes be made outside of major releases. - -### Release Frequently - -Make frequent project releases to the community. - -### Promote Other Maintainers - -Assist, add, and remove [MAINTAINERS](MAINTAINERS.md). Exercise good judgement, and propose high quality contributors to become co-maintainers. +| Maintainer | GitHub ID | Affiliation | +| ------------- | --------------------------------------- | ----------- | +| Rushi Agrawal | [rushiagr](https://github.com/rushiagr) | Amazon |