nevzheng opened a new issue, #12027: URL: https://github.com/apache/gravitino/issues/12027
### What would you like to be improved? Pull-request responsibilities should be clearer and managed through GitHub. I would be happy to help triage, label, and route issues and pull requests, but I currently do not have the repository permissions required to perform those actions. I can comment and provide reviews, but I cannot apply labels, assign work, manage milestones, or help organize the PR queue. Recent coordination around #10975 and #12011 also highlighted the need to make review responsibilities explicit. When my help is needed on a PR, I should be formally assigned through GitHub's Reviewers section so that both the author and I understand what is expected. Apache provides a GitHub Triage role specifically for contributors who help manage issues and pull requests without receiving code write access: https://infra.apache.org/github-roles.html ### How should we improve? Grant `nevzheng` GitHub Triage access after the required project approval is recorded. The implementation would add `nevzheng` to the `github.collaborators` section of `.asf.yaml`. This would allow me to: - Apply labels to issues and pull requests. - Assign and help route issues and pull requests. - Apply milestones. - Close or reopen issues and pull requests when appropriate. - Request pull-request reviews. - Help maintain a clear and organized contribution queue. This role would not grant write access to the code repository. For individual PRs, maintainers should continue to assign me through GitHub's Reviewers section when my review is expected. Once my role in a PR or discussion is clear, I am happy to engage the contributors and help move it forward. A corresponding draft PR will remain open while the project discusses and records the required approval. It should only be merged after that process is complete. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
