Hello from Sweden! I followed this discussion but did not yet get: What shall be hosted at the codehouse project site? Just some few components? Or shall it be a growing, open collection of components? Or something completely different?
IMHO a wiki page is perfect for this task: Easy to collaborate & keep the overview. Listing & commenting proposals. Listing requirements. Reusable for later naming needs. > We could always go for ServiceReMix May IMHO confuse "outsiders": Is this a fork of the ServiceMix project? Or some kind of other re-use of SM? > Well, here are a few that spring to mind to get the creative process > rolling: > InTheMix IMHO great for components etc, as they will be used inside Servicemix > MixCentral > MixDepot IMHO great when a bigger bunch of related packages/projects/examples/... shall be hosted/linked. > MixBase > MixCore May be misunderstood as servicemix-core or other internals > BeyondServiceMix nice for things that complement ServiceMix To summarize the requirements: The name shall be * pronouncable (like distinction between acronym and abbreviation, e.g. VoIP and URL are speakable, whereas CSS and SVN are not) * showing clear separation from main project * somehow tying to the main project * search engine friendly (no command characters like " - + etc.) * easy to find (not too many other results, even with common spelling errors [e.g. space inbetween single words of a compound one]) * usable in professional contexts, so no similarity (written/spelled/spoken) with swearwords and the like (maybe even in other common languages than just English, so Spanish, Chinese, Arabian, Russian, French, German etc.) Did I miss something? Just add... Have a sunny saturday, Georg -- View this message in context: http://www.nabble.com/Changing-the-name-of-the-ServiceMix-project-at-the-Codehaus-tf2203136.html#a6339623 Sent from the ServiceMix - Dev forum at Nabble.com.
