Closed ahal closed 2 years ago
I like this proposal very much! I know the mobile teams would be pleased to let untrusted contributors run a subset of the jobs anyway.
The tiny nit I'd like to talk about is the name
mixed
. If someone new to TC reads a.taskcluster.yml
file, they have no way to guess what this policy does without reading the docs. How about something likepublic_restricted
ornon_collarborators_restricted
?
Good call, I like public_restricted
. More bikeshedding here welcome if anyone has other ideas.
Here's an example implementation of this RFC: https://github.com/taskcluster/taskcluster/pull/5569
(Got a little ahead of myself, but happy to change it if things come up here).
This will be landed on Friday this week during the Taskcluster Community meeting, unless there are any matters which come up that block it. Therefore please submit any final comments or raise objections before then.
Latest push doesn't change the content, I had just put the wrong RFC number in it (didn't realize it was supposed to match the PR, nor that there was a script to generate it).
I think it might good if new pushes didn't invalidate the reviews here :). The author can probably use their best judgement if a new change warrants a new review and re-request explicitly if it does.
Rendered
Issue: #173