Skip to content

MAINTAINERS.md

Latest commit

 

History

History
91 lines (61 loc) · 3.75 KB

MAINTAINERS.md

File metadata and controls

91 lines (61 loc) · 3.75 KB
Raw

Maintainers

This document lists the maintainers of the Substrait Compliance Framework project.

Current Maintainers

Maintainers are responsible for the overall direction, health, and sustainability of the project. They review contributions, manage releases, and represent the project in the Substrait community.

Active Maintainers

Name GitHub Role Focus Areas Timezone
Ranjan Sinha @RanjanSinha-GH Project Lead / Release Maintainer Overall direction, releases, security triage coordination UTC-7

Current launch-state note: The project currently has a single named active maintainer. Additional maintainer seats may be added after open source launch, but no unnamed or placeholder maintainers are treated as active for governance, release approval, or security-response purposes.

Maintainer Responsibilities

Maintainers are expected to:

  1. Code Review: Review and provide feedback on pull requests
  2. Issue Triage: Label, prioritize, and respond to issues
  3. Release Management: Coordinate and execute releases
  4. Community Engagement: Participate in discussions and community calls
  5. Security: Respond to security vulnerabilities promptly
  6. Documentation: Ensure documentation stays current
  7. Mentorship: Guide new contributors and committers
  8. Governance: Participate in governance decisions

Maintainer Ownership and On-Call Expectations

  • Primary Maintainer of Record: Ranjan Sinha
  • Release Authority Owner: Ranjan Sinha
  • Security Triage Owner: Ranjan Sinha
  • Operational Coverage: Best-effort maintainer coverage during normal working hours in UTC-7
  • Current On-Call Status: No separate 24x7 production on-call rotation is claimed for this repository at pre-release stage

Until additional maintainers are formally added to the table above, release execution, security triage coordination, and final escalation decisions remain the responsibility of the Project Lead.

Maintainer Meetings

  • Frequency: To be announced post-launch
  • Format: Video call (recorded and shared publicly)
  • Agenda: Posted in GitHub Discussions 48 hours before meeting
  • Notes: Published in GitHub Discussions after meeting

Becoming a Maintainer

See GOVERNANCE.md for the process of becoming a maintainer.

Requirements:

  • Serve as a Committer for 6+ months
  • Demonstrate sustained, high-quality contributions
  • Show leadership in technical direction
  • Commitment to project sustainability
  • Nomination by existing Maintainer
  • Approval by majority of current Maintainers

Emeritus Maintainers

Maintainers who have stepped down but made significant contributions:

Name GitHub Period Contributions
No emeritus maintainers at this time - - -

Committers

Committers have write access to the repository and help with day-to-day maintenance:

Name GitHub Focus Areas Since
No committers at this time - - -

Contact

Acknowledgments

We thank all contributors who have helped make this project possible. See the Contributors page for a complete list.

Last Updated: June 26, 2026

To update this file, submit a pull request with the proposed changes.