Recently a very interesting project came my way and making headway thru its architecture and design now. The project is making me think more than ever, surprisingly not about the use cases as much as name for the project. We picked the concept several times before but was dropped due to politics, financials etc etc. Somehow I feel this is it… we are making it.
Here now comes the important question, what do we name it?
- Microsoft has very exciting tradition for naming their pre-production releases with a codename based on places
- Apple names their OS as cats
- Firefox as Nature parks
- Open source projects have weirdest traditions of naming the projects, not yet figured out yet.
- O’Reilly has chosen their book covers as animal kingdom
- Microsoft press chose the toolbox.
- webMethods uses product line major versions by alphabetically.
Longhorn, Leopard, Indigo, Poseidon, Gran Paradiso, Yukon, SharpFreedom, Supertanga, Revolution, Lightning, Lambrate, Orcas, Q98, Fiji, Pendolino, McKinley, there is absolutely nothing in common.
We need to have some fun with the project, pick a mythology and name the components. It is very monotonous to use very overused acronyms that make you feel geeky. Nothing makes sense anymore, use of boring version numbers is monotonous and dry. There may be a need to use these names in pre-release discussions, can be used in namespaces where needed in codebase, naming the codebase with the mythical project name. There are several reasons to name the project with the name that attracts the team.
Still wondering what should be the name of my project?