g.d.o or GDO or else?

I've noticed over the years that the "g.d.o" name is confusing to quite a few newcomers at our meetups. These days I just refer to groups.drupal.org as "groups.drupal.org" and sometimes as "Drupal Groups".

As a short name for sites in D.o documentation as well as issue queues, IRC - 'd.o' is used for Drupal.org, '*.d.o' to refer to all of the sub-sites. For individual sub-sites it's most of the time 'a.d.o', 'l.d.o', 'api.d.o' etc. Which makes perfect sense to me.
I personally would prefer 'g.d.o' to be used in the docs, GDO looks alien to me.

My impression is that "GDO" is how people outside the Drupal community would mostly abbreviate it, and the "g.d.o" format is somewhat unique to the Drupal community, who also say "dee dot oh" in verbal communication. For me personally, I'm more often communicating with people less familiar with the Drupal community, so I tend to use "GDO," and suspect I prompted this issue by doing that in wiki updates yesterday without really thinking about it.

Further complicating matters, both this project and the group were written "Groups.drupal.org" (with a capital G). That looks to me like an attempt to turn the domain name itself into a brand. Today, the site is clearly branded "Drupal Groups," which is short enough that we don't really need an abbreviation at all in many contexts.

Proposal: everyone keep doing whatever they want in casual conversation, but try to always use "Drupal Groups" in more permanent contexts, e.g. documentation and issue queues.

Proposal: everyone keep doing whatever they want in casual conversation, but try to always use "Drupal Groups" in more permanent contexts, e.g. documentation and issue queues.

Works for me. Thanks, sreynen!

No objections, marking as fixed.