+craigb, from cros-test-infra team: To help test access setup as we go.
+bpastene: to advise on who we should be talking to for streamlining permissions here.

+ Nodir & Vadim to correct me where I'm wrong.

[1] Should be available to all googlers. Granting read-access to groups broader than that would probably be problematic.
[2] Should be controlled via the CIA group: https://chrome-infra-auth.appspot.com/auth/groups/project-infra-internal-committers. I think we've traditionally gated access to that group via a nomination process sent to chrome-infra@, but that seems a bit much for the configs of a single swarming server. We may want to make that more granular like we did for master-manager's config repo (which has its own group).
[3] This might be https://chrome-infra-auth.appspot.com/auth/groups/config-get-by-hash, but I'm not sure how that ties into the UI.
[4] This is https://chrome-infra-auth.appspot.com/auth/groups/config-admins, of which you're a direct member. That applies to all projects, which is unfortunate. Again we may want to make that more granular at the service-level.

[2] why do you need submit permissions in infradata/config, as opposed to upload CL permission? we can review stuff.

[3] is https://chrome-internal.googlesource.com/infradata/config/+/d45fd5e/configs/luci-config/services.cfg#220

I understand the permissions better here, and I agree with #3 that we don't need these premissions given the short roundtrip time I've seen so far with chops / trooper for reviews.