| Time |
Nick |
Message |
| 02:25 |
|
YuGiOhJCJ joined #minetest-dev |
| 04:00 |
|
MTDiscord joined #minetest-dev |
| 04:16 |
MTDiscord |
<cscscscscscscscscscscscscscscscs> So the minetest 5.10 feature freeze never happened right |
| 04:17 |
MTDiscord |
<cscscscscscscscscscscscscscscscs> since the name changed right |
| 06:24 |
MTDiscord |
<savilli> Congratulations on the successful renaming! |
| 06:35 |
|
hwpplayer1 joined #minetest-dev |
| 06:37 |
|
Topic for #minetest-dev is now FEATURE FREEZE IN EFFECT SINCE 2024-10-13. Luanti (fka Minetest) core development and maintenance. Chit chat goes to #minetest. https://dev.minetest.net/ https://irc.minetest.net/ https://github.com/minetest |
| 07:24 |
nore |
merging #15272 in 15 minutes |
| 07:24 |
ShadowBot |
https://github.com/minetest/minetest/issues/15272 -- Show warning in the settings menu when shaders are disabled by grorp |
| 07:44 |
nore |
merged |
| 08:02 |
|
whosit joined #minetest-dev |
| 08:45 |
|
\o` joined #minetest-dev |
| 08:46 |
|
Warr1024 joined #minetest-dev |
| 09:01 |
|
hwpplayer1 joined #minetest-dev |
| 10:48 |
|
\o` joined #minetest-dev |
| 11:20 |
pgimeno |
yay, we've got a new name! |
| 11:21 |
pgimeno |
if we move to #luanti-dev, would it be possible to also send the commit messages there instead of #luanti ? I don't think the commit messages make much sense out of a developers channel |
| 12:07 |
|
MTDiscord joined #minetest-dev |
| 14:07 |
|
hwpplayer1 joined #minetest-dev |
| 14:58 |
|
Desour joined #minetest-dev |
| 15:10 |
MTDiscord |
<warr1024> Has anyone considered renaming MTG back to the original "mesetint" name? It seems like now that the ball is rolling on renaming the engine, it would be nice to have a name for MTG that doesn't require the _game specifier. |
| 15:19 |
Desour |
mesetint is imo too nice of a name to be wasted for the boring modern mtg |
| 15:21 |
Desour |
better make an actual fun subgame that is mostly (e.g. doesn't need all the permafrost, kelp, or other boring mapgen stuff) compatible with mtg and call it mesetintng or something |
| 15:25 |
|
reinaldo joined #minetest-dev |
| 15:41 |
MTDiscord |
<warr1024> Whether we like MTG's content or not, it clearly occupies an important place in the ecosystem, any deviations from it are bikeshed hazards, and it still bears a name that's problematic for a couple reasons (its historical ambiguity, and that damn _game needed to disambiguate it). A better game wouldn't need a new name, but MTG might. |
| 15:41 |
|
SFENCE joined #minetest-dev |
| 16:30 |
Soni |
call it minetest? |
| 16:32 |
MTDiscord |
<warr1024> Yeah, that's what we're doing right now that remains a problem. The name Minetest will always remain as an alias for both game and engine, requiring disambiguation. Each one should have its own name that doesn't require further clarification. The engine has that from Luanti. The game could have it with Mesetint, but that name is so old and obscure that apparently few people remember it. |
| 16:33 |
MTDiscord |
<warr1024> The fact that the game HAS had the name before means that we can reevaluate the reasons why it stopped using that name and determine if they still make sense given the new context. |
| 16:33 |
|
ShadowNinja joined #minetest-dev |
| 16:33 |
|
ShadowBot joined #minetest-dev |
| 16:46 |
|
hwpplayer1 joined #minetest-dev |
| 19:18 |
|
fluxionary joined #minetest-dev |
| 19:59 |
|
SFENCE joined #minetest-dev |
| 20:05 |
sfan5 |
merging #15284, #15284 in a few minutes |
| 20:05 |
ShadowBot |
https://github.com/minetest/minetest/issues/15284 -- Disable SDL2 for 5.10.0 by sfan5 |
| 20:05 |
ShadowBot |
https://github.com/minetest/minetest/issues/15284 -- Disable SDL2 for 5.10.0 by sfan5 |
| 20:08 |
sfan5 |
#15260 i mean |
| 20:08 |
ShadowBot |
https://github.com/minetest/minetest/issues/15260 -- Trivial improvement to `get_item_group` by kno10 |
| 21:19 |
[MatrxMT] |
<Zughy> I'm taking care of renaming the "minetest" instances in the docs and I'll open a PR once I'm done. Telling you just to avoid that other people will waste their time |
| 21:19 |
ROllerozxa |
by the way, will the project name be renamed in time for 5.10.0's release or is that not within the scope of the feature freeze? |
| 21:21 |
sfan5 |
^ I think that needs deciding before we start |
| 21:25 |
[MatrxMT] |
<Zughy> I think it makes little sense to have announced the rename and then wait until end of January |
| 21:25 |
ROllerozxa |
it may cause some issues when binary names start changing, and translation filename changes may need some tweaks to the weblate pipeline setup potentially, which could drag on the freeze |
| 21:25 |
ROllerozxa |
but other than that it should be a simple change to the project name and some meta files in misc/ |
| 21:26 |
ROllerozxa |
(I would hope so at least) |
| 21:26 |
sfan5 |
changing program names is another can of works |
| 21:26 |
sfan5 |
maybe we can apply some light UI renaming just for this release? |
| 21:26 |
ROllerozxa |
yeah |
| 21:26 |
sfan5 |
can of worms* |
| 21:26 |
[MatrxMT] |
<Zughy> can I keep going with the docs though? |
| 21:28 |
sfan5 |
you plan to s/minetest\./core\./ the lua docs? |
| 21:28 |
[MatrxMT] |
<Zughy> yes, and also Minetest -> Luanti |
| 21:28 |
[MatrxMT] |
<Zughy> it's done manually, as there are exceptions like `minetest.conf` we don't want to touch |
| 21:28 |
[MatrxMT] |
<Zughy> (for now?) |
| 21:29 |
sfan5 |
hm |
| 21:29 |
[MatrxMT] |
<Zughy> the big one was lua_api.md (already done), the others are quite simple |
| 21:30 |
[MatrxMT] |
<Zughy> I'm not gonna touch things like `function check_if_minetestserver_up($host, $port)` in `protocol.txt` |
| 21:34 |
[MatrxMT] |
<grorp> in response to the original question: I think announcing a new name and doing a release with the old name a few weeks later would send the wrong message. It would look like we are not sure or not serious about the name change. |
| 21:35 |
[MatrxMT] |
<grorp> So I think we should definitely try to use the new name for 5.10 |
| 21:39 |
sfan5 |
intrusive or light rename? |
| 21:40 |
[MatrxMT] |
<Zughy> it depends on you, core devs. Do you think you can easily manage the remaining bugs way before the release date? If yes, maybe intrusive is the best option |
| 21:40 |
[MatrxMT] |
<Zughy> (we'll definitely miss something haha) |
| 21:44 |
|
dv^_^ joined #minetest-dev |
| 21:48 |
MTDiscord |
<luatic> hmm if i'm working on a PR should I use core.* or minetest.* there? |
| 21:50 |
sfan5 |
that's the least of our worries |
| 21:53 |
MTDiscord |
<luatic> btw i've got another commit which implements a consistent max depth of 1024 for json parsing and writing, feature or bugfix? our current max writing depth is 16 which i consider somewhat arbitrarily low. |
| 21:54 |
sfan5 |
bugfix imo |
| 21:55 |
MTDiscord |
<luatic> i'll add it to the PR then |
| 21:56 |
[MatrxMT] |
<Zughy> #15292 |
| 21:56 |
ShadowBot |
https://github.com/minetest/minetest/issues/15292 -- DOCS: replace Minetest -> Luanti, `minetest.` -> `core.` by Zughy |
| 22:16 |
ROllerozxa |
yay |
| 22:32 |
|
panwolfram joined #minetest-dev |
| 22:56 |
[MatrxMT] |
<Zughy> I must say, it feels good to be in the first day of feature freeze and see just 8 things left in the milestone |
| 23:05 |
|
Eragon joined #minetest-dev |
