After thorough discussions where we weighted the pros and cons of profiting from the Great Git Migration, I think it's pretty clear that we have a great opportunity to migrate our source repositories back to Drupal.org. We will get:

• more visibility - people will find us through drupal.org easily
• more consistency - versions in the issue queue matching the real releases
• even more consistency - people will find the source better from drupal.org
• and then more consistency - usage stats will work again!

We will be able to:

• host our module and theme within the install profile - the major reason why we migrated away back then
• use whatever naming convention we want for tags and branches - although only some will be used for releases for now, see this issue for followup
• keep our history - the git team was nice enough to clone directly from our repositories (although see below, we're taking the opportunity of the migration to clean up our history)

What it means for you

This does have an impact on your existing repositories. When we migrate to git.drupal.org (which should happen by the end of the week, according to my precious sources), the repositories will change location. The other thing is that the commit IDs have changed, and you will need to refresh your local checkouts before you can work with them effectively.

So in short:

• repos will move to git.drupal.org
• you need to rebase or clone again
• make sure your identity is set correctly

See our migration documentation for all the gory details.