V8 Committer status

[snek]

My commiter status seems to have been revoked some time in the last 4 days, and it has been far less than a year since my last gerrit activity. Why was it revoked? Could this be reinstated?

[Jakob Kummerow]

I've forwarded this question internally, will update when I hear back.

[Jakob Kummerow]

You need to set up a Security Key to secure your account. You should have received at least two reminder emails about this last year (Nov-Dec). Once you have set up a Security Key, your committer status can be reinstated.

FWIW, I see public documentation about this requirement on https://www.chromium.org/getting-involved/become-a-committer/#nomination-process. Since V8 is part of the Chromium ecosystem, this policy applies to us as well. We should probably put a note on https://v8.dev/docs/become-committer to reflect that.

[snek]

Thanks for checking. I've had a security key on my account since November though.

[Jakob Kummerow]

Ah, that might explain it: "Passkeys" are not "Security Keys". The latter is a device like this or this.

[snek]

What are you looking for exactly? Do you need the device to have attestation keys from yubico/titan specifically?

[snek]

Nevermind I see there are now two buttons for creating a "security key" and a "passkey", i've deleted and re-added my authenticator as a passkey. Really a shame that the webauthn spec was fucked up this badly but whatever, hopefully I fulfill the requirements now.

[Jakob Kummerow]

I'm not an expert on any of this, I'm just trying to help you. I don't think the manufacturer of the device matters, those were just examples to illustrate. I believe it needs to be "FIDO2 compliant", and you need to click the "+ Use a security key" button in your account settings. I'm not sure whether a phone is enough; personally I'm using dedicated hardware security keys.

[snek]

Yes I've done this now. Thanks for your guidance, I appreciate it.

[Jakob Kummerow]

To close out this thread: I've received confirmation from the admin team that the account is now configured correctly, and committer status has been restored.