|
1 | 1 | - [Overview](#overview)
|
2 | 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 |
| - - [Backports](#backports) |
9 |
| - - [Be Responsive](#be-responsive) |
10 |
| - - [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo) |
11 |
| - - [Use Semver](#use-semver) |
12 |
| - - [Release Frequently](#release-frequently) |
13 |
| - - [Promote Other Maintainers](#promote-other-maintainers) |
14 |
| - |
| 3 | +- [Emeritus](#emeritus) |
| 4 | + |
15 | 5 | ## Overview
|
16 | 6 |
|
17 |
| -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). |
| 7 | +[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). |
18 | 8 |
|
19 | 9 | ## Current Maintainers
|
20 | 10 |
|
21 | 11 | | Maintainer | GitHub ID | Affiliation |
|
22 | 12 | | ------------------------ | ------------------------------------------------------ | ----------- |
|
23 |
| -| Bukhtawar Khan | [Bukhtawar](https://github.com/Bukhtawar) | Amazon | |
| 13 | +| Andriy Redko | [reta](https://github.com/reta) | Aiven | |
| 14 | +| Bukhtawar Khan | [Bukhtawar](https://github.com/Bukhtawar) | Amazon | |
| 15 | +| Daniel Doubrovkine | [dblock](https://github.com/dblock) | Amazon | |
24 | 16 | | Madhusudhan Konda | [madhusudhankonda](https://github.com/madhusudhankonda)| Chocolateminds|
|
| 17 | +| Sarat Vemulapalli | [saratvemulapalli](https://github.com/saratvemulapalli)| Amazon | |
| 18 | +| Vacha Shah | [VachaShah](https://github.com/VachaShah) | Amazon | |
| 19 | + |
| 20 | +## Emeritus |
| 21 | + |
| 22 | +| Maintainer | GitHub ID | Affiliation | |
| 23 | +| --------------- | --------------------------------------------------- | ----------- | |
25 | 24 | | Mital Awachat | [mitalawachat](https://github.com/mitalawachat) | Amazon |
|
26 | 25 | | Rishab Nahata | [imRishN](https://github.com/imRishN) | Amazon |
|
27 | 26 | | Vamshi Vijay Nakkirtha | [vamshin](https://github.com/vamshin) | 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 |
| -### Backports |
56 |
| - |
57 |
| -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. |
58 |
| - |
59 |
| -### Be Responsive |
60 |
| - |
61 |
| -Respond to enhancement requests, and forum posts. Allocate time to reviewing and commenting on issues and conversations as they come in. |
62 |
| - |
63 |
| -### Maintain Overall Health of the Repo |
64 |
| - |
65 |
| -Keep the `main` branch at production quality at all times. Backport features as needed. Cut release branches and tags to enable future patches. |
66 |
| - |
67 |
| -### Use Semver |
68 |
| - |
69 |
| -Use and enforce [semantic versioning](https://semver.org/) and do not let breaking changes be made outside of major releases. |
70 |
| - |
71 |
| -### Release Frequently |
72 |
| - |
73 |
| -Make frequent project releases to the community. |
74 |
| - |
75 |
| -### Promote Other Maintainers |
76 |
| - |
77 |
| -Assist, add, and remove [MAINTAINERS](MAINTAINERS.md). Exercise good judgement, and propose high quality contributors to become co-maintainers. |
0 commit comments