I don't seem to have permission to access https://chromium-review.googlesource.com/#/admin/projects/linux-fpga-chameleon,access (even though i'm in chrome-git-admins).

It looks like smut created this repo: any ideas?

cychiang@: What is linux-platform-chameleon? It appears to be a chromeos project, so why is it not in the chromiumos/ namespace? Why do all of the normal devs have force-push permissions?

I believe the correct solution here is to make it inherit ACLs from the chromiumos/ project, rather than directly from All-Projects.

FWIW, the "push merge" permission has nothing to do with the existence of a "Merge" button in the UI; that button's existence is determined by the submit-strategy (merge, cherry-pick, or rebase) and whether or not you have permission to Submit.

Dave, assigning back to you as the current git admin, since I'm 90% sure that just changing the project inheritance is the right thing to do.

Hi agable@, linux-platform-chameleon is our fork of https://github.com/altera-opensource/linux-socfpga, which is the kernel for an FPGA board we use for ChromeOS testing: https://www.chromium.org/chromium-os/testing/chamelium.

History of the repo setup is in https://bugs.chromium.org/p/chromium/issues/detail?id=572809#c9.

"Why do all of the normal devs have force-push permissions?" --> I am not sure.
Ideally we would like to give force-push permission to only member of chromeos-chameleon.

Sorry I am not familiar with the ACL setting, but making linux-platform-chameleon inherit ACLs from chromiumos project seems right to me.
Thank you very much for the help!

Thanks Aaron!  I've changed linux-fpga-chameleon to inherit permissions from chromeos-chameleon.

> Ideally we would like to give force-push permission to only member of chromeos-chameleon.

Yep, that's how it's configured now - only chromeos-chameleon has force push permissions.

Great! Now I can see the submit button.
Thank you agable@ and dsansome@ !
Mark as verified!