Maintainers¶
A maintainer is a contributor who has made sustained and valuable contributions to the Lance community. Maintainers are recognized for their work and granted various rights to support their ongoing contributions.
Rights¶
All maintainers have the following rights:
- GitHub triage permissions on all Lance repositories
- Publish preview/beta releases of all Lance projects at any time
- Propose stable releases of all Lance projects
- Execute stable releases after the vote has passed
Some maintainers may be granted GitHub write access to Lance repositories, which allows them to review and merge pull requests. Maintainers with write access may refer to themselves as "committers" when communicating outside the project, as this is a widely recognized term in the open source ecosystem, though "committer" is not part of the official Lance governance structure.
Maintainers with GitHub write access additionally have the following rights:
- GitHub write access to all Lance repositories
- Approve and merge code modifications in all Lance projects (except changes to format specifications)
Activities¶
Maintainers are encouraged to:
- Continue making valuable contributions to the Lance projects
- Help review PRs and provide feedback when possible
- Volunteer as release manager for stable releases when proposed
- Participate in community discussions and support other users
- Mentor and grow new maintainers
Maintainers with GitHub write access are additionally encouraged to:
- Actively review and merge PRs while maintaining project code quality
- Participate in technical discussions and decisions
- Maintain project code standards and best practices
Roster¶
| Name | GitHub Handle | Affiliation | GitHub Write Access | Ecosystem Roles |
|---|---|---|---|---|
| Matt Basta | mattbasta | RunwayML | ||
| Giuseppe Battista | giusedroid | AWS | ||
| Timothy Carambat | timothycarambat | Anything LLM | ||
| Ayush Chaurasia | AyushExel | LanceDB | ||
| Chongchen Chen | chenkovsky | MiraclePlus | ||
| Akela Drissner-Schmid | akelad | dltHub | ||
| Ty Dunn | TyDunn | Continue | ||
| Enwei Jiao | jiaoew1991 | Luma.ai | ✓ | Milvus Maintainer |
| Bryan Keller | bryanck | Netflix | Apache Iceberg Committer | |
| Aman Kishore | AmanKishore | Harvey.ai | ||
| Sangwu Lee | RE-N-Y | Krea.ai | ||
| Jeremy Leibs | jleibs | Rerun.io | ||
| Haocheng Liu | HaochengLIU | Seven Research | ✓ | |
| Nathan Ma | majin1102 | ByteDance | ✓ | Apache Amoro (incubating) PPMC Member |
| ChanChan Mao | ccmao1130 | LanceDB | ||
| Lu Qiu | LuQQiu | LanceDB | ✓ | Alluxio PMC Member |
| Rong Rong | walterddr | Google DeepMind | Apache Pinot PMC Member, Apache Flink Committer | |
| Nat Roth | nrothGIT | Meta AI | ||
| Kevin Shaffer-Morrison | kevinshaffermorrison | AWS | ||
| Noah Shpak | noahshpak | Thinking Machines | ||
| Ankit Vij | ankitvij-db | Databricks | ||
| Jiacheng Yang | jiachengdb | Google AI |
Becoming a Maintainer¶
To become a maintainer:
- Make sustained and valuable contributions
- Demonstrate active participation in the community
- Get nominated by a PMC member and approved through a passing vote
Here are some example areas of valuable contributions:
- Code Contributions:
- Submit pull requests implementing features or fixing bugs
- Review code and provide constructive feedback on PRs
- Tackle issues on GitHub, especially those marked "good first issue"
- Community Support:
- Help other users in Discord and GitHub discussions
- Answer questions and provide guidance to newcomers
- Host or participate in tech discussions and special interest groups
- Documentation and Content:
- Write or improve documentation, tutorials, and guides
- Create blog posts, demos, or case studies showcasing Lance
- Share your Lance journey through articles and technical content
- Advocacy and Outreach:
- Present Lance at meetups, conferences, or community events
- Spread awareness on social media and developer platforms
- Beta test new features and provide detailed feedback
- Champion Lance adoption in your organization or community
To be granted GitHub write access, the maintainer should:
- Demonstrate deep understanding of the Lance codebase
- Have a history of high-quality contributions
- Have earned trust from the community for code reviews
- Get nominated by a PMC member and approval through a passing vote
- Sign the Contributor License Agreement (CLA)