Naming convention for new projects [closed]

Answer 1

Our SVN server has a flat folder of projects. So they look like so:

internal-<something>-system
client-<client name>

It works great, IMO. Directory structure on the servers is simply the domain name. For my development computer, I follow the naming convention of the SVN server. Don't try to stuff everything into different folders - a simple, consistent, prefix can do wonders for organization. For internal items, there isn't anything wrong with generic project names ("Time Manager" "Finance Manager") and such (so that the folders would be "internal-time-manager" and "internal-finance-manager" and so on).

Answer 2

We allocate a project number (P and then five digits) which is how the SVN, issue tracking, and document repositories are named; then the project has an informal name which is normally some humorous anagram or phrase arrived at by word association from the client name, what the project is for, etc.

This means that the names are hidden from the client (we just refer to the project number) but we have an easier way to refer to it internally that doesn't involve everyone remembering which project has which number!

There's usually an email round to the project team to get names suggested near the beginning, and the best suggestion is picked.

Some of my favourites included two Base Station projects which were named "Taoist Beans" and "Bonsai Teats".

Answer 3

Whats in the name? EVERYTHING. Make sure the name is interesting, unique and shows the worth of the product you are making. Names based on functionality is the way to go, but it should not define what are you doing rather a single word term that has somehow has a relation with what you are developing.

I often pick my project names in local language (urdu in my case).

Even if you have to insert client name, usually the product would be called ignoring the client name so it doesnt matter much if you pick strong name for your product.

Just to give an example, I named the chess engine I wrote "Shaatir". In urdu it means

1. Very Strong chess player
2. A Cunning/Clever person
3. Someone who lay down traps
4. Wicked.

Each one of the meaning somehow relates to my program.

Edit: You can also add a slogan to your product. Not sure why the idea is not so popular in the software industry. There are few examples though. Like "UBUNTU- Linux for human beings". Adds spice to your product.

Answer 4

I am in favour of the "codename-approach" but with added emphasis on including functionality and wittyness. Both for making it easy to remember what the project is about.

And then create additional hierarchical structures that sort by logic relations like "customer", "year", and such. You may want to introduce either some standard procedures for project creation or (considering that you are in the automation business) some automation.

(It might be that there are already systems existing out there to do so, I remember some presentation related to some envisioned filesystem in Longhorn that I attended years ago.)