Let's say I fork Firefox. I can do that because it's open. I can't call my thing Firefox though (that's that's trademark owned by Mozilla).
It turns out, the brand name is actually the thing that matters, not the code. He who owns the name owns the users.
In terms of the code, he who owns the contributers owns the code. But it takes a LOT of work to switch people from one brand to another, even if the new brand is the old developers.
Witness the fact that MySql is still deployed more than MariaDb. The MySql brand is very strong, even if the MariaDb product is superior.
On the other hand, wikivoyage is more well known than wikitravel. LibreOffice is more well known than OpenOffice.
Ultimately though i think this is reasonable. If you go your own separate way you use a new name. If you give your project's name to someone else, that is your own stupid fault.
[1] - https://www.reddit.com/r/travel/comments/318v09/wikitravel_v...
See the 'wordpress' situation for a case study ...
Even the nicest and best people can change for the worse. One of the reasons to go for some foundation-like entity owning the name is that you can equalize out across multiple people in a meritocratic, democratic, demarchist, or whatever else process.
And even if you're incredibly sure you won't become a bad person: what happens if life hits you hard? A relative becomes disabled and you need money to care for them? Will you sell the trademark?
If it were ... but it isn't, quite to the contrary.
However look at Openoffice, where libreoffice clearly won.
I wouldn’t trust the data there very much.
Whether that would be enough to rank MariaDB higher, I can't say.
Even just looking at table design and schema management functionality, here's my increasingly-long rundown of subtle differences in features and syntax: https://www.skeema.io/blog/2023/05/10/mysql-vs-mariadb-schem...
AWS Aurora for MySQL is based on Oracle MySQL, without a MariaDB variant. Vitess only supports MySQL and not MariaDB. Between these two facts, you can ascertain a lot of companies are using MySQL under the hood.
Even in terms of "regular" managed DB hosted, only AWS RDS actively offers both MySQL and MariaDB variants; Azure had both but has chosen to drop their MariaDB product and focus only on MySQL. Google CloudSQL offers MySQL and has never supported MariaDB.
This is not to say MariaDB is bad! Quite the contrary. Just responding to the common incorrect HN refrain that Oracle MySQL is dead.
As for which product is "superior", in my experience they both have unique strengths and features that the other lacks. MariaDB has especially been adding some great FOSS features lately. MySQL is focusing more on enterprise/non-FOSS in the last couple years, but prior to that they added a ton of unique stuff to MySQL 8 as FOSS.
That's a sample size of one.
FRRouting forked from Quagga. Quagga is completely, utterly and unquestionably dead. So, with a sample size of two it's 50/50. What now?