|
| 1 | +# Maintainers |
| 2 | + |
| 3 | +This document describes who maintains this project and how maintenance decisions are made. |
| 4 | + |
| 5 | +## Current Maintainers |
| 6 | + |
| 7 | +- @ecwireless |
| 8 | +- @Jipperism |
| 9 | +- @rickstaa |
| 10 | + |
| 11 | +## Responsibilities |
| 12 | + |
| 13 | +Maintainers are responsible for: |
| 14 | + |
| 15 | +- Reviewing and merging pull requests |
| 16 | +- Maintaining overall code quality and project direction |
| 17 | +- Managing releases and versioning |
| 18 | +- Triaging issues and feature requests |
| 19 | +- Ensuring CI and core workflows remain healthy |
| 20 | + |
| 21 | +## Project Planning & Tracking |
| 22 | + |
| 23 | +Active work, priorities, and longer-term plans are tracked on the maintenance project board: |
| 24 | + |
| 25 | +👉 **Project Board:** https://github.com/orgs/livepeer/projects/18 |
| 26 | + |
| 27 | +The board is the source of truth for: |
| 28 | + |
| 29 | +- Planned work and priorities |
| 30 | +- In-progress tasks |
| 31 | +- Known issues and follow-ups |
| 32 | + |
| 33 | +Not all work is guaranteed to be scheduled, but the board reflects current focus. |
| 34 | + |
| 35 | +## Pull Request Review |
| 36 | + |
| 37 | +- All PRs require at least one maintainer review before merging |
| 38 | +- Larger changes should include appropriate tests and documentation where applicable |
| 39 | +- Larger features require oversight from appropriate stakeholders (such as the Livepeer Foundation) |
| 40 | +- Breaking changes should be clearly called out in the PR description |
| 41 | + |
| 42 | +## Decision-Making Process |
| 43 | + |
| 44 | +Maintenance decisions are made by the maintainers, aiming for consensus whenever possible. For controversial changes or those with broad impact, maintainers discuss options in the relevant issue or pull request. If consensus cannot be reached in a reasonable time, @rickstaa has the final say. The Livepeer Foundation, or other stakeholders, may also be called upon to provide direction. |
| 45 | + |
| 46 | +## Releases |
| 47 | + |
| 48 | +- Releases are made on an as-needed basis |
| 49 | +- Patch releases may be issued for critical fixes |
| 50 | +- Breaking changes are documented clearly in GitHub release notes |
| 51 | + |
| 52 | +## Project Status |
| 53 | + |
| 54 | +This project is actively maintained. |
0 commit comments