Create a Triager-level role within Llama Stack #1561
Replies: 3 comments 8 replies
-
|
Totally agree with this, thanks for bringing this up Nathan! I think any way we can help out the existing group of maintainers with the amount of PRs and issues coming in would be ideal |
Beta Was this translation helpful? Give feedback.
-
|
Yes please. 🙏 Perhaps related, currently even an assignee of an issue cannot close it, nor a contributor can self-assign an existing issue. Maybe this can also be addressed in overall relaxing of github rules for this type of actions. |
Beta Was this translation helpful? Give feedback.
-
|
You should be able to close the issue via PR: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests |
Beta Was this translation helpful? Give feedback.
-
|
@nathan-weinberg we spoke with the maintainers today and they were definitely supportive of this! After reviewing the docs Triage makes a lot of sense. I'm not sure if Meta is on an GitHub Enterprise Cloud though so that's something we may have to consider, as I believe each triage seat (or outside collaborator?) will impact the cost. |
Beta Was this translation helpful? Give feedback.
-
|
So looks like maybe no concerns about Enterpise! Settings section: Adding an outside-collaborator: Settings permissions: I added you to Feast as Triage, can you share what you see? |
Beta Was this translation helpful? Give feedback.
-
|
Yes that worked!
(feel free to remove my newfound permissions 😄) |
Beta Was this translation helpful? Give feedback.
-
|
Cool, probably just submitting an RFC with these screenshots may be good enough 😂 |
Beta Was this translation helpful? Give feedback.
-
|
Would you like to @franciscojavierarceo or I can? Fine either way! |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I can of course. |
Beta Was this translation helpful? Give feedback.
-
I have noticed a dichotomy in this project over this last couple months, where the project has a limited number of Maintainers but a large number of Contributors. This has led to a growing backlog of Issues and Pull Requests. Contributors looking to help refine that backlog need to get in touch with a Maintainer to do things like assigning folks to an issue, closing an issue, etc.
I'm proposing the creation of a Triager-level group of folks within the project, as described here: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#repository-roles-for-organizations
The tl;dr for that link is that triagers have the ability to do some of the things I have described and more but crucially they cannot approve Pull Requests and cannot merge code - this gives the Maintainers confidence that they maintain technical control of the project while allowing community members to assist with more of the clerical work that currently only Maintainers can do, which may not be the best use of their time.
Happy to draw up an official RFC for this if folks generally consider it to be a good idea.
Beta Was this translation helpful? Give feedback.
All reactions