As our repos grow in activity, it takes more and more effort to maintain them and ensure code and issues are being actively triaged for consideration and review. This document outlines the responsibilities of the on-duty maintainer.
- Every business day, the on-duty maintainer is expected to make a pass over all open PRs and new issues in all
UMA repositories.
- On-duty maintainers rotate each week in a round robin fashion
- For each PR, the on-duty maintainer should make sure the PR is moving forward:
- Check the title and description according to the template. If either of these are incorrect, edit them and add a comment explaining your edits.
- Make sure reviews are requested. If not, request them (if the PR is very small, feel free to just review it yourself).
- If the PR has stalled, determine whose action is needed and tag them in a comment (or re-request a review if it's the reviewer). If a 3rd party's PR is ready and passing tests, merge it.
- DCO is a common problem for many users, please help them by pointing them to the DCO docs. Note: DCO checks can be overriden for UMA org members because DCO is covered by other agreements, but 3rd party developers must sign off on their commits.
- For the full PR process, see the contributing guidelines.
- For each new issue:
- If it's a 3rd party issue, traige by assigning or tagging a relevant UMA team member.
- If it was posted by an UMA org member, no action is required.