Skip to content

Commit c574532

Browse files
authored
Updated MAINTAINERS.md to match recommended opensearch-project format. (#185)
Signed-off-by: dblock <dblock@amazon.com>
1 parent ae33b80 commit c574532

File tree

1 file changed

+9
-69
lines changed

1 file changed

+9
-69
lines changed

MAINTAINERS.md

Lines changed: 9 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -1,74 +1,14 @@
1-
- [Overview](#overview)
2-
- [Current Maintainers](#current-maintainers)
3-
- [Maintainer Responsibilities](#maintainer-responsibilities)
4-
- [Uphold Code of Conduct](#uphold-code-of-conduct)
5-
- [Prioritize Security](#prioritize-security)
6-
- [Review Pull Requests](#review-pull-requests)
7-
- [Triage Open Issues](#triage-open-issues)
8-
- [Be Responsive](#be-responsive)
9-
- [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo)
10-
- [Use Semver](#use-semver)
11-
- [Release Frequently](#release-frequently)
12-
- [Promote Other Maintainers](#promote-other-maintainers)
13-
141
## Overview
152

16-
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).
3+
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).
174

185
## Current Maintainers
196

20-
| Maintainer | GitHub ID | Affiliation |
21-
| ------------------------ | --------------------------------------- | ----------- |
22-
| Jack Mazanec | [jmazanec15](https://github.com/jmazanec15) | Amazon |
23-
| Vamshi Vijay Nakkirtha | [vamshin](https://github.com/vamshin) | Amazon |
24-
| Vijayan Balasubramanian | [VijayanB](https://github.com/VijayanB) | Amazon |
25-
| Deep Datta | [deepdatta](https://github.com/deepdatta) | Amazon |
26-
| David Venable | [dlvenable](https://github.com/dlvenable) | Amazon |
27-
| Shivani Shukla | [sshivanii](https://github.com/sshivanii) | Amazon |
28-
29-
## Maintainer Responsibilities
30-
31-
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.
32-
33-
### Uphold Code of Conduct
34-
35-
Model the behavior set forward by the [Code of Conduct](CODE_OF_CONDUCT.md) and raise any violations to other maintainers and admins.
36-
37-
### Prioritize Security
38-
39-
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.
40-
41-
Note that this repository is monitored and supported 24/7 by Amazon Security, see [Reporting a Vulnerability](SECURITY.md) for details.
42-
43-
### Review Pull Requests
44-
45-
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.
46-
47-
### Triage Open Issues
48-
49-
Manage labels, review issues regularly, and triage by labelling them.
50-
51-
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`.
52-
53-
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.
54-
55-
### Be Responsive
56-
57-
Respond to enhancement requests, and forum posts. Allocate time to reviewing and commenting on issues and conversations as they come in.
58-
59-
### Maintain Overall Health of the Repo
60-
61-
Keep the `main` branch at production quality at all times. Backport features as needed. Cut release branches and tags to enable future patches.
62-
63-
### Use Semver
64-
65-
Use and enforce [semantic versioning](https://semver.org/) and do not let breaking changes be made outside of major releases.
66-
67-
### Release Frequently
68-
69-
Make frequent project releases to the community.
70-
71-
### Promote Other Maintainers
72-
73-
Assist, add, and remove [MAINTAINERS](MAINTAINERS.md). Exercise good judgement, and propose high quality contributors to become co-maintainers.
74-
7+
| Maintainer | GitHub ID | Affiliation |
8+
| ----------------------- | ------------------------------------------- | ----------- |
9+
| Jack Mazanec | [jmazanec15](https://github.com/jmazanec15) | Amazon |
10+
| Vamshi Vijay Nakkirtha | [vamshin](https://github.com/vamshin) | Amazon |
11+
| Vijayan Balasubramanian | [VijayanB](https://github.com/VijayanB) | Amazon |
12+
| Deep Datta | [deepdatta](https://github.com/deepdatta) | Amazon |
13+
| David Venable | [dlvenable](https://github.com/dlvenable) | Amazon |
14+
| Shivani Shukla | [sshivanii](https://github.com/sshivanii) | Amazon |

0 commit comments

Comments
 (0)