This section contains ideas for choosing names for projects and names for computers. Planning all these things in advance may seem excessively controlling to some people, but in my experience, deciding on this information once, before things are done differently by each person, will help project members communicate clearly.
Project names are usually chosen by engineering groups, with one name for each significantly different version of the products that they are working on. There should be no need to change a project's name once it has been chosen. Product names, on the other hand, are the names that customers see, and these names are usually chosen to help a product sell or to become popular. Product names can change at the whim of a market research poll or a new VP of Sales.
Some general guidelines for choosing names for projects are:
Since project names may appear in filenames or source code, shorter project names are preferable; four to six characters is common. Longer names will only be abbreviated anyway, and usually in two different ways.
Project names should sound different from each other when spoken aloud by people whose native language is not the one used by the rest of the group. Even if everyone speaks English, having two projects named "ctest" and "seebest" is too close for comfort.
It's much easier to be confident that all references to a project name can be ...