How to become an OpenSearch Project repo maintainer
summary
OpenSearch has 113 opensearch-project repos and roughly 231 maintainers (March 2024); becoming one is concrete work: write a failing rest yaml test and run git bisect to find the commit, or start with doc fixes, README and CI badge updates, samples and meta-issues; bigger wins include RFCs or a full rewrite—example: a Go client rewrite changed 583 files in 78 commits and earned maintainer status; maintainers review PRs, triage issues, run releases and the nomination is a simple maintainer vote.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:10Artists vs Developers
- 3:38Dive in
- 7:41Start with docs
- 8:51Contribute to documentation
- 10:52Do GitHub repo
- 19:27Dont change everything
- 21:04Hurricane
- 21:57Consistency
- 22:24Scratch your own itch
- 24:28Have a strong reason
- 25:35Build things that are valuable
- 26:25Write the code
- 27:33Help others
- 28:32Learn what others are doing
- 30:27Say thanks
- 30:53Make something new
- 31:29Statistics
- 32:41How to become a maintainer
related talks
19mRoad To Maintainership: Shaping OpenSearch's Future
31mHow to contribute to the community & become an OpenSearch Maintainer
42mContribute to OpenSearch: Build Your Skills While Advancing Open Technolo...
22mYour Open Source Repo Needs A Project Manager
37mHow to Serve Open Source Maintainers Without Annoying Them?
45mGetting Started With OpenSearch Development
13mHow to Make Your First Open Source Contribution
46mClear Your Own Path to Open Source Maintainer