Hi Nevin, Thanks for jumping out. I am supportive of adding you to a Triage role. And I'm welcoming all the community members who volunteer to devote more to the community.
Regarding several questions you brought up, I can clarify one by one from my perspective. > 2. What responsibilities and expectations should accompany this role > in Gravitino? The role of triage is to help committers to work on the issue/PR management and triage, like labelling, assigning, reviewing, etc. 3. When my review is needed on a specific PR, should maintainers > formally assign me through GitHub’s Reviewers section and state the > expected scope? We encourage all the community members to jump into any issues/PRs you'd like to review and comment on. Reviewing is a way to understand the project and grow the visibility in the community. So I always encourage anyone to jump in and do anything they want to help grow the community. So, in short, it is not bound to any specific role or title. We don't have a mandatory assignment process for specifying reviewers. Besides, committers/PMC members will invite or ask the committers/contributors who work on the related parts to have a review. Two ways mutually co-existed. But, normally, we want all the community members to do such things voluntarily. > 4. Should the PR triage and reviewer-assignment workflow be documented > in CONTRIBUTING.md? As I mentioned above, we don't have a specific workflow/process for such things. The community always encourages doing such things voluntarily to maximize the bandwidth of the community, rather than sticking to the process of naming one by one. 5. Would the community prefer to continue this discussion on the > developer mailing list or in a dedicated GitHub Discussion thread? I think both are fine, because the GitHub one will also be synced to the dev mail list. But, for the community-related things like this, I would suggest we bring out here on the ASF mail list first. Best, Jerry Nevin Zheng <[email protected]> 于2026年7月15日周三 23:46写道： > Hello Gravitino community, > > I would like to request the GitHub Triage role for my account, @nevzheng. > > I’m happy to help triage and label issues and pull requests, route > contributions to the appropriate reviewers, apply milestones, and > request PR reviews. Recent coordination around PRs #10975 and #12011 > highlighted the need for clearer PR ownership and reviewer > assignments. > > The Triage role would allow me to help manage issues and pull requests > without granting write or merge access to the code repository. Apache > documents this role here: > > https://infra.apache.org/github-roles.html > > I have opened an issue describing the request and a corresponding draft PR: > > - Issue: https://github.com/apache/gravitino/issues/12027 > - Draft PR: https://github.com/apache/gravitino/pull/12028 > > The draft PR should remain unmerged until the community has discussed > the request and the required approval has been recorded. > > I would appreciate the community’s feedback on the following questions: > > 1. Does the community support granting me the GitHub Triage role? > 2. What responsibilities and expectations should accompany this role > in Gravitino? > 3. When my review is needed on a specific PR, should maintainers > formally assign me through GitHub’s Reviewers section and state the > expected scope? > 4. Should the PR triage and reviewer-assignment workflow be documented > in CONTRIBUTING.md? > 5. Would the community prefer to continue this discussion on the > developer mailing list or in a dedicated GitHub Discussion thread? > > If there is general support, could a committer or PMC member please > initiate or confirm the required vote and link the result to issue > #12027? > > Thank you, > > Nevin >
