Rename project?

[aspino]

lcms-engine is a bit redundant, specially because it's effectively an engine and Rails generates an Engine module, but also an Engine class, which to me is a bit ugly/confusing.

@rsaksida How about renaming it to something like lcms-core, or simply lcms? Or perhaps we should come up with a better, less prosaic name for the project?

[rsaksida]

Looking at the kind of conventions that are used for engines (in task namespaces, route helpers, etc), a one word name would be ideal. lcms works fine and surprisingly there aren't many repos with that exact name in Github.

As for a less prosaic name, do you have any suggestions? Most (all) of our projects have boring names but it's not like that's a policy. 😄 I thought about "weaver lcms", weaver for the engine name, as a reference to the 'tapestry' in Learning Tapestry.

[aspino]

Looking at the kind of conventions that are used for engines (in task namespaces, route helpers, etc), a one word name would be ideal. lcms works fine and surprisingly there aren't many repos with that exact name in Github.

Yeah! I agree. One word is the way to go. Perhaps the problem with LCMS is that it's too generic? It's like a CMS that's named CMS, or a MVC framework named MVC. But who knows, perhaps we can set a new trend in naming 😄 lcms is definitely better than lcms_engine, so that's good.

As for a less prosaic name, do you have any suggestions? Most (all) of our projects have boring names but it's not like that's a policy. smile I thought about "weaver lcms", weaver for the engine name, as a reference to the 'tapestry' in Learning Tapestry.

I'm quite terrible with names, to be honest 😞 In a previous company I had a few years ago, we "kind of" had some commercial products and we decided to use latin verbs for the main feature of the software. So, for example, one of the projects was like a CMS for press, so we used novus as its name (which basically means news in english). I guess if we have some similar strategy for naming it will be easier to come up with cool & coherent names for projects. There's also the typical strategy of using a common theme, like Android using dessert names, Debian using Toy Story characters, etc. although perhaps that's more useful for internal codenames. Anyway, I think weaver sounds cool and makes total sense, so that could be our first candidate 😃

I suppose that, if the idea for LT is to make this project a future product in its own way, meaning that it has its own identity, then it probably makes sense to look for a more commercial/cool name. In any case, we can just decide to use an internal name for the time being and, should this project become a more mainstream product and someone comes up with a truly commercial name, we can decide whether we change it internally or not.