I'm wondering if we should rename the module in the Drupal 8 version. I initially chose the name "@font-your-face" as sort of a joke. I thought the CSS rule "@font-face" sounded like an insult a child would say, and I imagined another child saying "no, @font-YOUR-face." And that's amusing to me, but I don't think anyone else really gets value out of that. If I were doing it all over again, I'd pick a different name. And Drupal 8 might be a good opportunity to do it over again.

On the other hand, I think "@font-your-face" has proven a good brand. It's distinct enough that's it's easy to tell when someone's talking about the module (unlike more generic project names like "Features" or "Commerce" where there's often ambiguity), and it's direct enough that it's clearly about fonts. If we did pick a new name, I'd want it to be something more distinct than "Drupal Fonts."

Also, changing the name would require more than just code changes. There's the project URL on Drupal.org, the twitter account, a so-far-unused domain name, and a bunch of blog posts referencing the current name, all of which would need to change with a new name.

Now that I write all of this out, I'm leaning toward just leaving the name what it is, but I'd love to hear others' thoughts.

Comments

nevets’s picture

I would leave it named as it is. Easy to find.

btmash’s picture

I think the name is pretty fantastic (for all the reasons you laid out above) so I'm +1 for keeping it.

Drave Robber’s picture

+1 to keeping.

dolly nyc’s picture

+1 for keeping, for all the reasons above. Plus, changing the name could be exceptionally problematic to for those of us who are not as code-savvy.

sreynen’s picture

Status: Active » Fixed

Looks like we have a consensus to leave the name.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.