Yicong-Huang commented on issue #4071: URL: https://github.com/apache/texera/issues/4071#issuecomment-3560642743
Yes I aware of this option, and usually it is a good way to become a "triager" before officially become a "committer". A few points, though: 1. Apache does not allow GitHub "Triage Access" explicitly. It only gives "Write Access" to committers. 2. The above workaround can only allow up to 10 external collaborators (see example [Apache Iceberg yaml](https://github.com/apache/iceberg/blob/0d4d3a562ffd339faae7e1db41c2068dc77920e8/.asf.yaml#L49). Deciding who to support or not is also a procedure, i.e., contributors typically need to "earn" the role through a process. 3. This is now incubating for Apache project, so we should not only consider "students". So I tend to not go with this temporary workaround, at least for this purpose. We could promote 1~2 good candidates to be granted as "triager role" to help out. We should have a way for all external contributors (none committers) to be able to "triage", such as assign issues, request reviews, etc., possibly through GitHub Actions and comments as commands. In this direction I am setting up some automations such as - #4060. -- 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]
