Startseite

New features on Drupal.org in preparation for The Great Git Migration

If you are a Drupal.org contributor with CVS access, please read this important announcement! We need you to make some changes to your user profile by February 13, 2011. This announcement also contains details about changes to how to edit e-mail addresses on Drupal.org that affect all users.

Commit statistics on Drupal.org are generated by the relationship between CVS usernames and Drupal.org usernames. In Git, there’s no direct equivalent. Instead, contributors identify themselves to Git on their local computer with their name and e-mail address. When their commits make it to Drupal.org, commit statistics are generated by linking those Git e-mails with Drupal.org account e-mails.

Therefore, to ensure all developers are properly credited for both their legacy contributions, as well as contributions post-Git migration, we’re deploying two new modules to Drupal.org:

  • Multiple E-mail Addresses, to allow more than one e-mail address (e.g. the one you use on GitHub, the one you use on Drupal.org) to be associated with your single Drupal user account. All users’ e-mail addresses are now editable on an “E-mail addresses” sub-tab, rather than the main user edit page.
  • CVS Migration Prefs, to specify to which e-mail address your legacy commits should be credited, once imported into Git. You can also choose a fake “no-reply” e-mail for all your legacy commits, in order to protect your privacy. If left untouched, this fake e-mail will be used. Your selection for legacy commit credit cannot be changed post-Git migration.

It’s important to consider the question of which e-mail address to associate with your Git commits. While your e-mail addresses won’t ever be visible to others on Drupal.org, they can be viewed with git log commands and similar. So it’s generally a good idea to specify an e-mail address that you would be comfortable giving out to untrusted people. At the same time, it is a generally accepted practice in the wider Git world to use a real e-mail address for this data.

Please see the following handbook pages for detailed instructions: