[palata]

For what it's worth, I'm not convinced by the change of name.

No matter if I write "postmarket", "PostMarket" or "posTmArkeTOs", the first result I get in my search engine is postmarketOS. In terms of how hard it is to pronounce, it feels like as soon as the context is there, one can say "pmOS". Kubernetes doesn't seem particularly easy to pronounce, but it doesn't seem like it's preventing it from being successful.

As a comparison, try to Google for /e/, or eos... I think it's getting better but a couple of years ago I was just not reading the /e/ changelogs because I just couldn't find the website. This, IMHO, is a bad name; and I have been a pretty satisfied user of /e/ for years, it's not like I don't like the project. But to be very honest, if CalyxOS had supported my phone I would have switched just because of the frustration with the name.

Also with every change of name comes confusion. For a very long time some people will keep calling it "postmarketOS", some will think it's a brand new project or a fork. Third-party documentation/blog posts will not get updated, ever. It takes time and energy to change a project name. And for what? Because it's "a bit too long" and "not so easy to pronounce"? I don't think it's worth it. It would be different if the project was called muskRocksOS.

[homebrewer]

I don't like renaming things as much as the next guy, but they're targeting an international audience. Ask a Chinese/Japanese/Arabic/whatever speaker if it's easy to pronounce (it is for me, but that's because I speak relatively passable English; judging from past experience, my friends would certainly find this name unpronounceable).

[palata]

I understand, and it happens to me that some project names are difficult to pronounce. Doesn't mean they are difficult to write or remember, though.

I still don't believe that it is a reason to change it and deal with the confusion that comes from that change.

[codetrotter]

> Third-party documentation/blog posts will not get updated, ever.

OTOH that could also be an advantage. For at least a year or so after they change the name, all info you can find about how to do something with it when you search with the new name is likely to be current. Instead of 7 year old guides that are completely out of date and don’t work with current versions.

[palata]

To see it as an advantage, you have to be sure that your community is active enough to write complete documentation with the new name.

It looks pretty bad when you look for documentation and people have to tell you to search for documentation with a different project name, because the name was changed.

For instance, whenever you want to do something with MapLibre, you have to think whether you should look at the Mapbox documentation or not. Many times it's confusing. But it is explained by the fact that there was an actual need for a fork, and hence a new name.

[worble]

Yeah, they could promote pmos (or maybe something like postos) to more prominently feature as a primary keyword, but in today's age of minimalism where it feels like every project is a single syllable word clashing with 100 others like it, I love a name that actually just says what it is on the tin.

[rglullis]

/e/ has changed to Murena, no?

[mnmalst]

No, the company selling smartphones with /e/OS is called Murena. https://murena.com/faq/

[yndoendo]

I recently switched to them as a step to help de-Google. Will not go back to standard Android and push for /e/OS at the moment. I don't mind the extra weight and size between the Fairphone 4 and Pixle 5a.

Waiting on a purchase from Furi Lab to see if I can move even further away.

Issue with most phone hardware with Linux is that they are all past products that don't have G5 support. Looks like all the push for Linux phones is coming from the EU and stale and stagnate in the USA, hardware wise.