There are a few examples of using a company name in a project name and/or shortname.
- Acquia Marina - in project and short name.
- Pressflow Transaction - in project and short name, now deprecated for the generically named Transaction.
- Multimedia Element - in short name, but not the normal name.
I suggest that we figure out a policy here whether we want to try to limit company branding in the node title and "shortname" modules and/or themes. Projects have a way of outliving the original maintainer, and maintainers occasionally leave the company yet still maintain their modules. The "shortname" is the directory in CVS and the part of the URL after /project/ and is usually the internal name for the code that is used in hook names.
My initial feeling:
- Project shortnames should not be company specific. The shortname is the hardest thing to change (see http://drupal.org/node/631994 for example - not sure why the new name isn't getting magically generated).
- The project name can be company specific, but I'd prefer not in general.
- I feel like this is less important for themes than modules, perhaps because themes tend to have shorter lives than modules and because themes are more naturally tied to a specific company (the most popular themes from the 4.6 era are only very rarely used these days and our most popular themes for 5.x often were created for 6.x and backported as an afterthought)
Edited to clarify where I feel the branding should be limited.