llama-stack-mirror/rfcs/RFC-0004-triage-role.md
Francisco Javier Arceo 9ba2e17032 Removing example section
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
2025-03-13 20:19:32 -04:00

2.1 KiB

The Llama Stack API

Author:

  • Red Hat: @franciscojavierarceo @nathan-weinberg

Summary

The Llama Stack project has grown substantially. To reduce maintainer burden, we propose creating a Triage-level role in Llama Stack.

Motivation

The project has had a large increase in the number of contributors, which has led to a growing backlog of requests. Contributors looking to help refine that backlog, unfortunately, need to get in touch with a maintainer to help, further adding to the maintainer's load.

By adding a Triage role, we hope to provide a way for established contributors to help the maintainers manage the requests from the community.

Permissions for the Triage-role

The incremental permissions a Triage role has above a Read only role are:

  1. Apply/dismiss labels
  2. Close, reopen, and assign all issues and pull requests
  3. Apply milestones
  4. Mark duplicate issues and pull requests
  5. Request pull request reviews
  6. Hide anyone's comments
  7. Move a discussion to a different category
  8. Lock and unlock discussions
  9. Individually convert issues to discussions
  10. Delete a discussion

Importantly, the Triage-role cannot:

  1. Approve or request changes to a pull request with required reviews
  2. Apply suggested changes to pull requests
  3. Edit wikis in private repositories
  4. Create, edit, run, re-run, and cancel GitHub Actions workflows
  5. Create and edit releases

And other important items outlined more in depth in the GitHub documentation.

Nomination Process for Triage-role

The process for nomination for the triage role should be simple and at the discretion of the maintainers.

Thank you

Thank you in advance for your feedback and support and we look forward to collaborating on this great project!

Cheers!