-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated MAINTAINERS.md to match recommended opensearch-project format. (
#75) Signed-off-by: dblock <[email protected]>
- Loading branch information
Showing
1 changed file
with
4 additions
and
59 deletions.
There are no files selected for viewing
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,64 +1,9 @@ | ||
| - [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) | ||
| - [Be Responsive](#be-responsive) | ||
| - [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo) | ||
| - [Maintain OpenSearch Project Roadmap](#maintain-opensearch-project-roadmap) | ||
| - [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). | ||
| This document contains a list of maintainers in this repo. See [opensearch-project/.github/RESPONSIBILITIES.md](https://github.com/opensearch-project/.github/blob/main/RESPONSIBILITIES.md#maintainer-responsibilities) that explains what the role of maintainer means, what maintainers do in this and other repos, and how they should be doing it. If you're interested in contributing, and becoming a maintainer, see [CONTRIBUTING](CONTRIBUTING.md). | ||
|
|
||
| ## Current Maintainers | ||
|
|
||
| | Maintainer | GitHub ID | Affiliation | | ||
| | ------------------------ | --------------------------------------- | ----------- | | ||
| | Daniel "dB." Doubrovkine | [dblock](https://github.com/dblock) | 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`, `v2.0.0`, `patch`, 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. | ||
|
|
||
| ### 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. | ||
|
|
||
| ### Maintain OpenSearch Project Roadmap | ||
|
|
||
| Maintainers have access to manage the [OpenSearch project roadmap](https://github.com/orgs/opensearch-project/projects/1) and are responsible for working with individual repo maintainers to ensure the roadmap is up to date with new planned features. They ensure a high quality bar for cards that a placed in the roadmap. They are not responsible for determining what features are built and prioritized. | ||
|
|
||
| ### 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 | | ||
| | ------------------------ | ----------------------------------- | ----------- | | ||
| | Daniel "dB." Doubrovkine | [dblock](https://github.com/dblock) | Amazon | |