In general I am +1

The only question I have is about

You may only have 20 active collaborators at any given time per repository.

Not sure if this is a concern or not? I would assume not, but wanted to bring it to everyone's attention.

There is actually also a way to allow people to re-trigger Jenkins jobs: https://github.com/apache/kafka/pull/13578

Retriggering test is a little bit more sensitive as our resources are limited, and we should avoid overwhelming Jenkins even more.


-Matthias


On 4/27/23 11:45 AM, David Arthur wrote:
Hey folks,

I stumbled across this wiki page from the infra team that describes the
various features supported in the ".asf.yaml" file:
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features

One section that looked particularly interesting was
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub

github:
   collaborators:
     - userA
     - userB

This would allow us to define non-committers as collaborators on the Github
project. Concretely, this means they would receive the "triage" Github role
(defined here
https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role).
Practically, this means we could let non-committers do things like assign
labels and reviewers on Pull Requests.

I wanted to see what the committer group thought about this feature. I
think it could be useful.

Cheers,
David

Reply via email to