-
Notifications
You must be signed in to change notification settings - Fork 123
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.
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
Update Maintainers List #308
Merged
VachaShah
merged 1 commit into
opensearch-project:main
from
nhtruong:maintainers_update
Oct 17, 2022
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Validating CODEOWNERS rules …
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1 @@ | ||
# This should match the team set up in https://github.com/orgs/opensearch-project/teams and include any additional contributors | ||
* @opensearch-project/clients | ||
* @ananzh @boktorbb @kavilla @mihirsoni @seanneumann @dblock @VachaShah @nhtruong | ||
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,41 +1,16 @@ | ||
- [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). | ||
# OpenSearch JavaScript Client Admins | ||
|
||
## Current Admins | ||
|
||
| Admin | GitHub ID | Affiliation | | ||
| --------------------- | ------------------------------------------------- | ----------- | | ||
| Anan Zhuang | [ananzh](https://github.com/ananzh) | Amazon | | ||
| Bishoy Boktor | [boktorbb-amzn](https://github.com/boktorbb-amzn) | Amazon | | ||
| Charlotte | [CEHENKLE](https://github.com/CEHENKLE) | Amazon | | ||
| Henri Yandell | [hyandell](https://github.com/hyandell) | Amazon | | ||
| Kawika (Rocky) Avilla | [kavilla](https://github.com/kavilla) | Amazon | | ||
| Mihir Soni | [mihirsoni](https://github.com/mihirsoni) | Amazon | | ||
| Sean Neumann | [seanneumann](https://github.com/seanneumann) | Amazon | | ||
| Tommy Markley | [tmarkley](https://github.com/tmarkley) | 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. | ||
| Admin | GitHub ID | Affiliation | | ||
|-----------------------|-----------------------------------------------|-------------| | ||
| Anan Zhuang | [ananzh](https://github.com/ananzh) | Amazon | | ||
| Bishoy Boktor | [boktorbb](https://github.com/boktorbb) | Amazon | | ||
| Charlotte | [CEHENKLE](https://github.com/CEHENKLE) | Amazon | | ||
| Henri Yandell | [hyandell](https://github.com/hyandell) | Amazon | | ||
| Kawika (Rocky) Avilla | [kavilla](https://github.com/kavilla) | Amazon | | ||
| Mihir Soni | [mihirsoni](https://github.com/mihirsoni) | Amazon | | ||
| Sean Neumann | [seanneumann](https://github.com/seanneumann) | Amazon | | ||
|
||
[This document](https://github.com/opensearch-project/.github/blob/main/ADMINS.md) | ||
explains what an admin's responsibilities are. |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,78 +1,18 @@ | ||
- [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) | ||
|
||
## 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). | ||
# OpenSearch JavaScript Client Maintainers | ||
|
||
## Current Maintainers | ||
|
||
| Maintainer | GitHub ID | Affiliation | | ||
| --------------------- | ------------------------------------------------- | ----------- | | ||
| Anan Zhuang | [ananzh](https://github.com/ananzh) | Amazon | | ||
| Bishoy Boktor | [boktorbb-amzn](https://github.com/boktorbb-amzn) | Amazon | | ||
| Kawika (Rocky) Avilla | [kavilla](https://github.com/kavilla) | Amazon | | ||
| Mihir Soni | [mihirsoni](https://github.com/mihirsoni) | Amazon | | ||
| Sean Neumann | [seanneumann](https://github.com/seanneumann) | Amazon | | ||
| Tommy Markley | [tmarkley](https://github.com/tmarkley) | Amazon | | ||
|
||
## Maintainer Responsibilities | ||
|
||
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 <backport-branch-name>` 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 | | ||
|-----------------------|-----------------------------------------------|-------------| | ||
| Anan Zhuang | [ananzh](https://github.com/ananzh) | Amazon | | ||
| Bishoy Boktor | [boktorbb](https://github.com/boktorbb) | Amazon | | ||
| Kawika (Rocky) Avilla | [kavilla](https://github.com/kavilla) | Amazon | | ||
| Mihir Soni | [mihirsoni](https://github.com/mihirsoni) | Amazon | | ||
| Sean Neumann | [seanneumann](https://github.com/seanneumann) | Amazon | | ||
| Daniel Doubrovkine | [dblock](https://github.com/dblock) | Amazon | | ||
| Vacha Shah | [VachaShah](https://github.com/VachaShah) | Amazon | | ||
| Theo Truong | [nhtruong](https://github.com/nhtruong) | Amazon | | ||
|
||
[This document](https://github.com/opensearch-project/.github/blob/main/MAINTAINERS.md) | ||
explains what maintainers do in this repo, and how they should be doing it. | ||
If you're interested in contributing, see [CONTRIBUTING](CONTRIBUTING.md). |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added @nhtruong to the repo maintain permissions directly, FYI.