[SOLVED] Help needed for finding an appropriate name for a project
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Help needed for finding an appropriate name for a project
Hi,
A few days ago, I've taken up work again on what used to be known as MLED and MLES, basically a software repository of a couple hundred extra packages for Slackware, with the ambition to provide an easy out-of-the-box desktop experience. The project is mostly for my personal use, which means installing it for clients here in South France. But it's more fun to publish it so others can benefit from it, and it's always good to have some feedback.
Funny thing, I'm currently struggling to decide on a final name for the project. I took some notes in a little notebook, but I'm still lost in indecision. So I thought a little input from you folks might help. The hard part can probably be formulated like this: I'll probably use all this in the years to come, so I'd better choose wisely. Here's the list of candidates first.
Keep "MLED" and "MLES", e. g. "Microlinux Enterprise Desktop" and "Microlinux Enterprise Server"
Or simply "Microlinux Desktop" and "Microlinux Server"
"Slick Linux Desktop", "Slick Linux Server"
"Linux From Slack"
"Beyond Linux From Slack"
LFSlack, BLFSlack?
Something entirely different?
I gave up the idea of finding an extra name for my CentOS-based desktop and server solutions, since there will be only relatively few use cases, and there's no need to find a special name for these configurations. "Custom configuration based on CentOS" will do the job.
I still like "MLED" and "MLES". Even though the "E" (Enteprise) might seem a little grand, it clearly outlines the target audience: professional users who need a reliable system, with more than 18 months of security updates. On the plus side, "MLED" and "MLES" have been in use for some time, so folks know what it's about.
Of course, I might leave out the "E" and go for "MLD" and "MLS". While the first may remind me vaguely of the (excellent) PLD distribution, I admit I don't really like them. "Microlinux Desktop" and "Microlinux Server" may sound nice, but there's no nice acronym for these.
The initial name for a Slackware+Xfce-based desktop back in 2005 or 2006 was "Slick Linux" or simply "Slick". Now I like that one, since aside from the obvious nod to the "mother" distribution, there's also the meaning of "slick" itself: "done or operating in a smooth, efficient and apparently effortless way", according to the dictionary. Unfortunately, most French people don't speak english, and the word "slick" only reminds them of racing car tyres.
"Linux From Slack" may best describe the project, though for obvious reasons it's a private joke for the geek community.
Since you are developing the distributions for your enterprise use I would just keep MLED/MLES, it falls more in line with RHEL and SLED/SLES, the most prominent enterprise distributions.
I would abstain from Slick Linux, since slick can also mean "deftly executed and having surface appeal or sophistication, but shallow or glib in content; polished but superficial; glib:" and, IMHO, it doesn't sound very professional (though that is, I would guess, more up to decide for your customers, I think this maybe a regional bias).
"Linux From Slack" is a funny one (but I do not think that this is a good project name)
MLED is already known, but for me it is impossible to say and I always read and think MELD, but thi is a merge tool
so Microlinux Deskto is not bad, you can replace the E with X, MLXD, MLXS
apropos merge, did you ever consider to check similarities between MLED and Salix, and if it would not be a good idea to build MLED or what ever it will be named upon Salix? For me as a user I think this could be a great Beyond Linux From Slack
I vote MLED/MLES. They are easy to say and they are already familiar in the community.
But if you want to shy away from the word "Enterprise", you could pick another word for the E. Maybe Embodies, Evolves, Exemplifies, Exquisite (although, I'd put an apostrophe after Microlinux, so it becomes Microlinux's Exquisite Desktop/Server), Extrapolates, and then there's any number of French words that start with E.
There are many article written about how to choose a business name that can also apply to naming a project. The number one thing to remember is do not limit your title. For example if you are in plumbing supply, choosing Jake's Plumbing is great if you plan to always do only plumbing. But what if the business grows and you start to also distributor supplies to other plumbers, well you original name (Jake's Plumbing) can still be a supply sourcer. But if you had originally name your business Jake's Plumbing Supply then you probably would not have much plumbers work so the business didn't grow and your only customers would have been other plumbers not people looking for a plumber. But also remember if you intend to only start with plumbing supplies and intend to grow to other commercial business products like mirrors and janitorial supplies then Jake's Plumbing doesn't really help the customer understand what they can expect from your business. The same is true of a product/project, name it what it is intended to supply or result in for the customer.
So in this case, you mention your audience is enterprise or small businesses and you offer both desktop and server versions based on Slackware Linux. In reality I don't think the customer is going to care if it is Slackware or RedHat or SUSE for base. Unless they have a Geek who insists that maintainability and sustainability if you or your business are hit by a car requires a widely supported base system. In your business plan perhaps you should have some backup technical support which a customer could use in case they need help when you are on vacation. So you are developing a GNU/Linux system based on Slackware, targeted for business and small business. Things to consider, what would a customer think of when looking for an desktop or server system? Will they want to check that DE or Server deployment numbers against some Internet or magazine, will they find MLED/MLES Slick or other name you might change to in those public reports? Perhaps it would be better to choose Microlinux Enterprise Slackware Desktop and Microlinux Enterprise Slackware Server, this covers a lot for the customer. I'm assuming the business name is Microlinux. Then the MLED/MLES titles become MLESD and MLESS, which you'd want to make sure doesn't become some acrimonious abbreviation which give the wrong meaning to the product whis Linux Enterprise Slackware Server=LESS would do ie I get less from this server than I should;-). Don't choose to change something that is already working well and seems to fit the situation. Remember you are a Slacker for Life, so let's not make extra work where done is needed.
So after that book, I like MLED/MLES just as they are.
What about "Microlinux" by itself? I don't think it has been used before, it's short, memorable, and doesn't need an acronym, and the server and desktop versions can just be descriptions rather than part of the name. Although, come to think of it, it vaguely reminds me of a Microsoft-Linux mashup. But I don't think that will be any more of a problem for you than it currently is.
What about "Microlinux" by itself? I don't think it has been used before, it's short, memorable, and doesn't need an acronym, and the server and desktop versions can just be descriptions rather than part of the name. Although, come to think of it, it vaguely reminds me of a Microsoft-Linux mashup. But I don't think that will be any more of a problem for you than it currently is.
I also thought about that, but "Microlinux" is the name of my small company.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.