www.drupal.org uses multiple_email module for associating commits to user accounts. This is GitLab’s responsibility now, we are effectively just syncing over the confirmed email addresses.
multiple_email does have some other functionality, for example, password resets can be sent to confirmed secondary email addresses. Our new login/SSO solution doesn’t support any of this functionality, #3262372: Cloud IAM / Keycloak openid connect integration. multiple_email would also conflict with the SSO stack, as it would also try to set the primary account email address. So multiple_email will have to be removed.
Using the GitLab UI for this will make it possible for people to delete their {name}@{Drupal uid}.no-reply.drupal.org address for making commits with an anonymous email address. GitLab has its own version of this functionality, {GitLab ID}-{name}@users.noreply.drupalcode.org. We can switch to using that, and discontinue use of the Drupal.org-specific functionality.
Changes
- Any functionality that multiple_email provided will be gone. For example, if you’re in a situation where you needed a password reset sent to a secondary email, you can email help@drupal.org instead.
- The GitLab primary email address will be your real email address, not the no-reply address. You will get notifications from GitLab, they can be configured at https://git.drupalcode.org/-/profile/notifications. We should review what notifications are sent, for new accounts in particular.
Tasks
- #3300810: Use GitLab-managed anonymous commit emails in UI Update Drupal.org UI to replace
{name}@{Drupal uid}.no-reply.drupal.orgwith{GitLab ID}-{name}@users.noreply.drupalcode.org - #3300811: Bulk update GitLab users to adjust emails Update GitLab integration to set everyone’s:
- Primary email to their primary email on Drupal.org
- Commit email to the GitLab private email (we can not unblock editing this directly,
git.drupalcode.org/-/profilealso allows editing various fields that should stay in sync with Drupal.org; so we default to privacy)
- #3300812: Remove multiple email syncing Update GitLab integration to remove email syncing
Deployment
- Remove email integrity checks
- Adjust load balancer rules to allow updating email addresses on git.drupalcode.org
- drush pm-disable multiple_email
- Make a backup
- drush pm-uninstall multiple_email
Comments
Comment #2
drummComment #3
drummUpdating domain name to
users.noreply.drupalcode.org, which is configurable in GitLab.Comment #4
drummComment #5
drummThis is now all done.
Comment #6
drummmultiple_email has been disabled on Drupal.org for a few days now. The last blocker to removing it is #3266208: Reimplement issue commit comments to trigger on webhook invocation to replace the existing commit → user mappers that use multiple_email’s data.
Comment #7
drummComment #9
drummMultiple_email module is now fully scrubbed from Drupal.org.