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

Issue 898710 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Give *@chromium.org bug-editing privs by default

Project Member Reported by dpranke@chromium.org, Oct 24

Issue description

Per discussion in go/discouraging-chromium-accounts (and elsewhere), we've decided that it should be safe to give everyone who has a chromium.org account the ability to edit bugs.

Monorail recently added support for this sort of thing, so we should just make this happen.

There are two potential gotchas here:

1) someone with an account can't be trusted to edit bugs. The "workaround" here is to take away their account; we don't think there's a need for anyone who can't be trusted enough to have an account.

2) we think it's possible to create a "public GAIA" account foo@chromium.org directly, without going through the GSuite admin tools, as long as you control another @chromium.org account that can receive an email. This is confusing, but appears to add minimal additional risk, so it should be okay.
 
Owner: jrobbins@chromium.org
Status: Assigned (was: Untriaged)
@jrobbins - I've already forgotten how to do this. Can haz help plz?

Sign in to add a comment