On Fri, Apr 20, 2007 at 12:21:43PM -0700, Garrett D'Amore wrote: > We have projects like "FireEngine", "Crossbow", "Clearview", "Brussels", > "Surya", and "Nemo" in the networking group. Some of these you probably > know, but some of them you probably don't. And figuring out what any of > them means (or even their existence) may be non-trivial without inside > knowledge. > > Much better, IMO, would have been names like: > > "TCP/IP Stack Rewrite", "Network Virtualization", "Network Softmac > Layer", "NIC Tunables API", "Route Lookup Optimization", and "GLDv3".
A short (preferably one-word) and unique whizzy name improves team spirit and makes it easy to refer to projects. A more descriptive phrase is useful to guide participants to the material they're looking for. We need both. FireEngine: TCP/IP Stack Rewrite is a fine formal name for a project (or, if you wish, formal name followed by synopsis). TCP/IP Stack Rewrite is descriptive (though not unique - it's likely to result in confusion when the second and third such projects come along - Surya II is likewise suboptimal but at least shorter) but uninspiring and clumsy to use as a reference. > (You then would have had acronyms or short forms like: "TISR" ... > pronounce "teaser"?... "NV" or "netvirt", "softmac", "nictune", "rlo"... > pronounce "rollo"?, and "GLDv3".) Some project names are given to this, some aren't. The ability to use whizzy names remains important. -- Keith M Wesolowski "Sir, we're surrounded!" FishWorks "Excellent; we can attack in any direction!"
