Adding @dreamer-89 to Opensearch maintainers.

[kartg]

Signed-off-by: Kartik Ganesh [email protected]

Description

I nominated Suraj Singh (@dreamer-89) to be a co-maintainer for Opensearch through our nomination process. The maintainers have agreed, and Suraj has kindly accepted.

Suraj has quickly become one of the top contributors to OpenSearch since the fork, authoring 70 PRs and reviewing numerous others from his peers. His major contributions include:

• Removal of mapping types, which was released with OpenSearch 2.0
• Key bugfixes and improvements for segment replication:
  • Update PrimaryShardAllocator to prefer replicas with higher replication checkpoint
  • Changes in the CCR plugin to be compatible with segment replication
  • Fix seg-rep diff logic to ignore missing files
  • Fix isAheadOf logic for ReplicationCheckpoint comparison

In his reviews of pull-requests, Suraj not only checks for correctness but also identifies opportunities to improve code style (example).

Check List

• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/2262/
• CommitID: 2551ac93aaa666b00f851556a8263b9ab9961189

[reta]

@kartg I believe we need to backport to 2.2 / 2.1 / 2.0 / 1.x / 1.3 so @dreamer-89 will be able to merge the pull requests to maintenance branches as well

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/2263/
• CommitID: 52f4aa0

[kartg]

@kartg I believe we need to backport to 2.2 / 2.1 / 2.0 / 1.x / 1.3 so @dreamer-89 will be able to merge the pull requests to maintenance branches as well

@reta My understanding is that granting @dreamer-89 the maintainer access role gives them the relevant access to all branches in the repo. If that's not accurate, please let me know.

That said, our existing documentation doesn't clarify how to backport updates to maintainers. I see that the maintainer list in our 2.* branches are largely in sync with main but the 1.* branches are pretty outdated. Do you think we should keep those lists up to date?

cc @dblock

[reta]

Thanks @kartg , I remember having issues initialy not able to merge to some maintance branches, it may be fixed though ... In any case, we could backport later on ... :-)