New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 603295 link

Starred by 4 users

Issue metadata

Status: Verified
Owner:
Last visit 21 days ago
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Create new group with access for ec-private-cr51

Project Member Reported by sosa@google.com, Apr 13 2016

Issue description

For chrome-internal.googlesource.com/chromeos/platform/ec-private-cr51, these are the ldaps who should have +2 review/commit rights:

ntaha@google.com
savagaon@google.com
vbendeb@google.com
wfrichar@google.com
serebrin@google.com
carlh@google.com

If possible, these ldaps should also be able to add/remove people from that list (note that it's not a pure subset):

resch@google.com
ntaha@google.com
serebrin@google.com

It's ok to keep the parent project (with its ACLs as chromeos)
 
Cc: autumn@chromium.org reinauer@chromium.org

Comment 2 by sosa@google.com, Apr 14 2016

Owner: sosa@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by sosa@google.com, Apr 14 2016

Owner: wfrichar@chromium.org
Can you please create an mdb group that honors what you have above. See mdb/
Owner: sosa@chromium.org

Comment 6 by sosa@chromium.org, Apr 15 2016

Status: Fixed (was: Assigned)

Comment 7 by benhenry@google.com, Apr 27 2016

Components: Infra>Git
Labels: -Infra-Git
Bulk verified
Status: Verified (was: Fixed)
bulk verified

Sign in to add a comment