Governance Policy

Introduction

Umpire is an application-focused API for memory management on NUMA & GPU architectures. This governance policy outlines the rules and processes that guide the development, contributions, and decision making of the Umpire project.

Team Roles

  • Project Leads: maintain the Umpire open source library and form the Technical Steering Committee of the Umpire Project.

  • Team Members: Regular contributors to Umpire

  • Collaborators: Irregular contributors to Umpire

Project Leads

  • Maintain the Umpire project

  • Determine project wide rules

  • Decide on subproject inclusion

  • Form the Technical Steering Committee

  • Reviewing and merging pull requests

  • Ensuring the project adheres to its code of conduct and contribution guidelines

  • Managing releases and ensuring high-quality standards

  • Facilitating discussions and resolving project issues

Technical Steering Committee

  • Setting the long-term technical and community goals of the project

  • Deciding on major feature inclusions and deprecations

  • Resolving escalated bug fix or feature request disputes

Current Roster

Team Members

  • Develop code, submit issues and Pull Requests

  • Review Pull Requests

  • Contribute documentation

  • Follow Collaborator rules

Collaborators

  • Individuals who contribute to the project, including code, documentation, and other assets

  • See the list of contributors for Umpire here

  • Following the contribution guidelines

  • Participating in discussions and code reviews

  • Reporting issues and suggesting improvements

Contribution Process

Pull Requests

  • Contributions are made via pull requests (PRs)

  • PRs must be reviewed by at least one project lead before merging

  • See the Contribution guide here

Issues

  • Contributors are encouraged to create issues for bugs, feature requests, and questions

  • Maintainers triage issues regularly and assign priorities

Code of Conduct

Release Management

Regular Releases

  • Umpire follows a regular release schedule with about 2 releases per year

  • Each release includes a summary of changes, new features, and bug fixes

  • Umpire project leads will coordinate project releases according to the release schedule

  • Once the release has been merged, it will be published in the Releases section of the repo

Communication Channels

  • The primary communication channel is the GitHub repository (issues, PR comments)

  • Other channels may include mailing lists and Slack (See the README for details)

Amendments

  • Changes to this governance policy require a formal proposal and approval by the Technical Steering Committee