Minetest → Luanti rename checklist

[Wuzzy2]

It has been decided to rename Minetest to Luanti. https://blog.minetest.net/2024/10/13/Introducing-Our-New-Name/

This issue is a checklist of all the places where the name needs updating.

Done

Luanti application

• Project name (Rename to Luanti #15294)
• menu_header.png (Rename to Luanti #15294)
• "ASCII" splash (Rename to Luanti #15294)
• README.md
• doc/lua_api.md
• All other files in doc/ (Rename to Luanti #15294)
• builtin/settingtypes.txt (Luanti rename: builtin #15324)
• builtin code (Luanti rename: builtin #15324)
• DevTest
• Devtest: minetest.* -> core.* (Rename minetest.* to core.* in devtest #15349)

Minetest Game

• Rename "Minetest" to "Luanti" in Minetest Game (luanti-org/minetest_game@312a67b)

Git / GitHub

• "About" section of https://github.com/minetest/minetest (Ctrl+F "Minetest is an open source voxel game-creation platform with easy modding and game creation")

Websites

• Website domain
• Website contents (Initial rename of Minetest to Luanti luanti-org.github.io#311)
• Blog domain
• API docs domain (api.minetest.net)
• Rename Minetest Blog to Luanti Blog ([no sq] Apply rename to Luanti blog#155)
• Update the pages of Minetest Wiki / Luanti Wiki (at least English)
• Update the pages of Minetest Developer Wiki / Luanti Developer Wiki (at least English)
• Mentions of "Minetest" in ContentDB

Social media

• Mastodon account
• Maybe edit the pinned posts of the Mastodon account
• Forums
• Subforum name: "Minetest-related projects" https://forum.minetest.net/viewforum.php?f=14
• Rename "Minetest" ContentDB user to "Luanti"
  • minetest game and sethome packages are being left under the minetest user, assuming that they will be left in the minetest org on github.

Semi-official

• Minetest Modding Book by @rubenwardy (included in checklist because it's mentioned in lua_api.md)
• Update Minetest luacheck standard to support core (Update Luanti (formerly Minetest) standard to 5.10.0 lunarmodules/luacheck#118)
  • This standard should be updated every release, but this one is particularly important since everything will start using core now.

To-Do

Edit by @appgurueu: Grouped into "Done" and "To-Do", ordered To-Dos roughly by estimated descending priority.

Package Sources

• Flathub: Resubmit as org.luanti.luanti, then do the EoL rebase
• Maybe: Create new luantidevs PPA, rename minetest to luanti as well, making sure to mark it as "provides minetest" so dependencies aren't broken

High-risk

• Maybe rename application directories (e.g. ~/.minetest, but it should probably be moved to ~/.local, ~/.config, etc. anyway in accordance with standards, e.g. XDG Move Linux user data to XDG directories #15382)

Social media

• Official IRC channels (#minetest, #minetest-dev, etc.)
  * [ ] Title and contents of sticky forum threads, see https://forum.luanti.org/viewtopic.php?p=440359#p440359 not happening, many sticky threads aren't updated, the renaming issue is just a part of the problem
• Rename "Minetest" forum user to "Luanti"

Git / GitHub

• Maybe: Git repo name
• Maybe: GitHub organization name

Websites

• Rename Minetest Wiki to Luanti Wiki
• Rename Minetest Developer Wiki to Luanti Developer Wiki
• Update the main page of Minetest Wiki / Luanti Wiki
• Update the main page of Minetest Developer Wiki / Luanti Developer Wiki
• Maybe project and component names on Weblate

---

Small warning about tools

Be careful when you mass-rename "Minetest" to "Luanti" with a tool that you don’t acidentally rename Minetest Game to Luanti Game.

---

(I've checked if a similar issue already exists but found none, so I decided to post it myself.)

(moderators: feel free to edit this list when you find new places or if you disagree with a particular point)

EDIT by SmallJoker: XDG directory issue reference.

[Wuzzy2]

Note: I've un-ticked "All other files in doc/" again because there are still files in there with "Minetest", for example minetest.6 (manpage), main_page.dox and others. Don't forget to search recursively.

[Wuzzy2]

After a few days of hard work, I'm very happy to announce that both wikis have pretty much all their content pages (excluding translated pages) updated to say "Luanti" instead of "Minetest", where appropriate. In places where a distinction between versions is important, I clarified that as well.

It's possible I've overlooked a small number of pages, but as I used page search extensively, so I'm positive all the important pages are now covered. I guess the missing instances will slowly get picked up by other wiki editors or me in the next years.

The only important page that is missing is the Main Page on both wikis, since I'm not allowed to edit them. Those pages still use the name "Minetest" in the text.

Also, the wikis themselves should be renamed as well to include "Luanti" in their name.

You can find more information about open wiki tasks that require admin intervention at the talk pages of both wiki Main Pages, and here: https://wiki.minetest.net/Minetest_Wiki:TODO

[sfence]

current latest dev build still writes screenshots to /Users/username/Library/Application Support/minetest/screenshots

(MacOS)

Paths for finding games, worlds, and store screenshots have not been changed to keep Luanti backward compatible with Minetest.

[okias]

website, github repos, would be cool to be aligned with new name... I'm not sure why to announce it, when lot of assets stay with old name.

Btw. high risk (following XDG standard). That's the best thing to do now, as after renaming it's kinda expected the default name will change, so changing path is easier.

if the game detects old path, it can use .minetest, otherwise proper XDG path, that's usually how it's done.

[appgurueu]

website, github repos, would be cool to be aligned with new name...

I agree, but one thing at a time. Right now the priority is to rename everything that's directly using-facing. The application has already largely been renamed, as well as the website (as of yesterday, https://luanti.org also works), which is good, now we have to rename the blog etc.

I'm not sure why to announce it, when lot of assets stay with old name.

The announcement lets us rename gradually in the open. Otherwise it would be rather confusing if we just started renaming things visibly and only then announced that we are going to rename (and what we are renaming to).
It is common for announcements to precede action.

[okias]

The website is great, that was one of the first thing I hit when I tried to rename the package (as I had to point to old website).

Usually the renaming (at least what I saw before) goes thou in one batch, so it's announcement and all the MR/PR got merged, so it's close to instantly flipped to avoid confusion. Anyway, thank you, with the website it's much better experience now :)

[appgurueu]

Many of the remaining points on the checklist require @celeron55 to resolve them:

• Blog domain
• API docs domain (api.minetest.net)
• Rename Minetest Wiki to Luanti Wiki
• Rename Minetest Developer Wiki to Luanti Developer Wiki
• Update the main page of Minetest Wiki / Luanti Wiki
• Update the main page of Minetest Developer Wiki / Luanti Developer Wiki

luckily these should all be pretty easy for celeron to resolve.

I'm not sure about the minetestdevs PPA anymore. It's possible to edit, but even just editing the description causes scary warnings (hence why I have reverted that).

The Flatpak should be possible to rename relatively smoothly at least.

[o1101o]

Hey what's up y'all. I was thinking about making a Luanti FB Page if that's ok? I've heard y'all don't really care about Social Media, but wanted to make sure it was Ok anyway.
Of course I'm a huge fan. I've got Luanti/ Minetest installed on Windows 10, 11, Androids and Linux Mint. Been playing it a couple years now. My 11 year old son builds his own games.

[appgurueu]

Hey what's up y'all. I was thinking about making a Luanti FB Page if that's ok? I've heard y'all don't really care about Social Media, but wanted to make sure it was Ok anyway. Of course I'm a huge fan. I've got Luanti/ Minetest installed on Windows 10, 11, Androids and Linux Mint. Been playing it a couple years now. My 11 year old son builds his own games.

We are present to some extent on some platforms, but not on Facebook. An unofficial Luanti Facebook page should certainly be fine. If it gains a certain amount of traction and aligns with our values, there even is a chance that it might eventually be made official (that's what happened with the Discord, for example).

[o1101o]

Awesome.
I created the Luanti FB page.
https://www.facebook.com/profile.php?id=61569556196555

[celeron55]

I added blog.luanti.org and api.luanti.org DNS now. They're the same as for the corresponding minetest.net ones, which is, CNAME to minetest.github.io. This obviously means someone has to configure the github pages for each accordingly.

EDIT: Those were set up now, and I also added redirects for them. https://irc.minetest.net/minetest-dev/2024-12-08#i_6225293

[celeron55]

I now set up a redirect for the wiki also, and renamed it (the title now has a different name).

However, it's not simple to fully rename it. For example, should I change the meta namespace which is currently Minetest_Wiki? This will affect links like https://wiki.luanti.org/Minetest_Wiki:About

[Wuzzy2]

Yes, please rename the "Minetest Wiki:" namespace, too. I will do the neccessary cleanup afterwards. There are not that many pages in that namespace anyway, so it should be fine.

Also, the main page and logo still needs updating. And all of that applies to the dev wiki as well.

[Wuzzy2]

The renaming/rewriting of sticky forum threads was rejected on the grounds of "many sticky threads are not updated".

Well, if these threads are outdated anyway, just unsticky them (any notify the author to give them a chance to update). It's not good when the forum is full of sticky but outdated forum threads. I also feel many sticky threads would work better as wiki pages.

Are sticky threads considered "holy"? I.e. once written, they must never be touched again?