| Time |
Nick |
Message |
| 00:38 |
|
Soni joined #minetest-dev |
| 03:42 |
|
AntumDeluge joined #minetest-dev |
| 04:00 |
|
MTDiscord joined #minetest-dev |
| 05:42 |
|
lhofhansl joined #minetest-dev |
| 05:58 |
|
tekakutli joined #minetest-dev |
| 06:08 |
|
fluxionary_ joined #minetest-dev |
| 06:29 |
|
calcul0n joined #minetest-dev |
| 08:22 |
|
Warr1024 joined #minetest-dev |
| 09:14 |
sfan5 |
sounds good |
| 09:15 |
sfan5 |
but dont forget that if the server sets custom values range_all needs to be disabled |
| 10:45 |
|
tekakutli joined #minetest-dev |
| 12:34 |
Zughy[m] |
Meeting reminder, in a few hours |
| 12:58 |
|
proller joined #minetest-dev |
| 16:57 |
|
Desour joined #minetest-dev |
| 17:33 |
rubenwardy |
#12614 updated |
| 17:33 |
ShadowBot |
https://github.com/minetest/minetest/issues/12614 -- Add ability to override item images using meta by rubenwardy |
| 17:33 |
rubenwardy |
and #12480 still waiting for review |
| 17:33 |
ShadowBot |
https://github.com/minetest/minetest/issues/12480 -- [Manual Squash] Redesign/unify mainmenu settings interface by rubenwardy |
| 17:49 |
|
Desour joined #minetest-dev |
| 18:00 |
Desour |
MEET_INGTIME |
| 18:04 |
Desour |
Zughy[m] Krock rubenwardy ping |
| 18:05 |
Zughy[m] |
hello hello |
| 18:07 |
Zughy[m] |
we could start hoping they come |
| 18:07 |
Zughy[m] |
> now that 5.7 has been released, we should write down a roadmap for 5.8 onwards (Zughy) |
| 18:08 |
Zughy[m] |
the summary of the 5.8 roadmap discussion was "Still need focus on UI/UX improvements, entities were not touched at all, dehardcoding shouldn't be a point" (2 meetings ago) |
| 18:11 |
Desour |
where did "dehardcoding shouldn't be a point" come from? dehardcoding would be a pretty neat direction / goal for the roadmap imo |
| 18:11 |
Desour |
(I can't find anything about dehardcoding here: <https://irc.minetest.net/minetest-dev/2023-03-19>) |
| 18:12 |
rubenwardy |
I think it was more like "maintenance/refractors shouldn't be a roadmap goal as it's an ongoing task like bug fixes" |
| 18:13 |
Zughy[m] |
yes, my bad, sorry |
| 18:14 |
Zughy[m] |
however, it tells external people what we're focusing on |
| 18:15 |
Zughy[m] |
I mean, it looks like we're gonna have the same roadmap that we've already got with 5.7? https://github.com/minetest/minetest/blob/master/doc/direction.md |
| 18:20 |
Desour |
we should add sscsm and dehardcoding to it, and remove or change internal code refactoring |
| 18:20 |
rubenwardy |
Who's going to work on sscsm? |
| 18:21 |
Desour |
I could adopt some parts of the big sscsm PR if I find time |
| 18:21 |
Krock |
reporting in! |
| 18:21 |
|
Jon[m] left #minetest-dev |
| 18:22 |
Krock |
the 5.7 roadmap seems good enough to me |
| 18:22 |
|
Wuzzy joined #minetest-dev |
| 18:22 |
Wuzzy |
Please update https://wiki.minetest.net/Template:Version |
| 18:22 |
Krock |
what is this used for? |
| 18:23 |
Krock |
wherever it is included, it might be better to keep it general |
| 18:23 |
Krock |
obviously that's already been forgotten at least twice in a row |
| 18:24 |
Desour |
if it always needs to be updated, the update steps need to include it |
| 18:28 |
Krock |
about sscsm: good question. If there was anyone willing to adopt it, it would most likely be seen as a reply in the PR |
| 18:29 |
Krock |
we already discussed that a few meetings ago and the main problem is its size |
| 18:29 |
Krock |
if a minimal implementation can be proposed, that would be great |
| 18:30 |
Wuzzy |
this template is used to include the version in various wiki pages without having to update it by hand everywhere |
| 18:31 |
Krock |
which pages need this information, for example? I cannot find a way to find references to this template |
| 18:32 |
MTDiscord |
<ROllerozxa> looks to be used for the minetest game wiki article |
| 18:32 |
MTDiscord |
<ROllerozxa> (and for obsolete translated main page articles, as well) |
| 18:32 |
MTDiscord |
<ROllerozxa> https://wiki.minetest.net/Special:WhatLinksHere/Template:Version |
| 18:32 |
Krock |
ah thanks |
| 18:39 |
Krock |
as for #13417 whereas swapping texture IDs for textures and re-triggering mapblock mesh generation to update them, the next feature that modders would ask for is per-node textuing |
| 18:39 |
Wuzzy |
I've added this to the release checklist |
| 18:39 |
ShadowBot |
https://github.com/minetest/minetest/issues/13417 -- Conditional textures for nodes, bulk texture changing |
| 18:39 |
Wuzzy |
https://dev.minetest.net/Releasing_Minetest#Update_wiki |
| 18:40 |
Krock |
okay thanks |
| 18:41 |
Krock |
sorry; I will be back later. |
| 18:45 |
Desour |
implementing, reviewing, and maintaining an implementation for 13417 would probably be too much work and complex, if I estimate it correctly. I'd therefore be for rejecting, before someone wastes much time and effort on it |
| 18:50 |
|
YuGiOhJCJ joined #minetest-dev |
| 18:59 |
|
PrairieWind joined #minetest-dev |
| 18:59 |
|
PrairieWind joined #minetest-dev |
| 19:05 |
|
tekakutli joined #minetest-dev |
| 19:07 |
Zughy[m] |
how about |
| 19:07 |
Zughy[m] |
>"Move code style guidelines into repo" |
| 19:07 |
Zughy[m] |
https://github.com/minetest/minetest/pull/12749 |
| 19:08 |
Zughy[m] |
(which is the last point) |
| 19:08 |
Zughy[m] |
and since we're at it |
| 19:08 |
Zughy[m] |
https://github.com/minetest/minetest/pull/12449 |
| 19:08 |
Desour |
#12449 |
| 19:08 |
ShadowBot |
https://github.com/minetest/minetest/issues/12449 -- [No Squash] Use .md extension for markdown files by rubenwardy |
| 19:09 |
rubenwardy |
this one was agreed upon on a previous meeting in September, just needs a review now |
| 19:11 |
sfan5 |
just merge it then |
| 19:12 |
Krock |
and update the wiki references |
| 19:13 |
Krock |
@ guidelines: I don't see much benefit in moving these since it's also a good rule of thumb for all minetest projects |
| 19:54 |
Desour |
closing #12749 then, (can be reopened if someone suddenly wants it) |
| 19:54 |
ShadowBot |
https://github.com/minetest/minetest/issues/12749 -- Move code style guidelines into repo by Desour |
| 19:57 |
Zughy[m] |
since we're here, what about Jude's PRs? Should we prioritise them and merge them with just one approval? |
| 19:59 |
Desour |
https://github.com/minetest/minetest/pulls/TurkeyMcMac |
| 19:59 |
nrz |
at work we are using more and more docsy for our internal docs, we embed in our repo. Wdyt about using a such thing in MT, embedding and versionning it, we can use github pages to expose it ? |
| 20:00 |
nrz |
it's just an idea because i see we are more and more using in repo docs |
| 20:00 |
nrz |
for #13017 for me it's more an experiment and FFI is clearly a bit rare to be used in MT context and outside |
| 20:01 |
ShadowBot |
https://github.com/minetest/minetest/issues/13017 -- Implement `minetest.get_node` and `minetest.get_node_or_nil` with LuaJIT FFI by TurkeyMcMac |
| 20:01 |
nrz |
#12972 needs rebase, why not i'd say |
| 20:01 |
ShadowBot |
https://github.com/minetest/minetest/issues/12972 -- Add option to silence HTTP errors by TurkeyMcMac |
| 20:07 |
Zughy[m] |
nrz is it an "okay, I'll adopt it"? |
| 20:08 |
nrz |
i don't have time currently, it's more the idea is ok |
| 20:18 |
|
tekakutli joined #minetest-dev |
| 20:39 |
sfan5 |
has anything tangible come from the "older versions load faster" claim? |
| 20:40 |
sfan5 |
rubenwardy: btw in the future we really need structued documentation that is generated from yaml or whatever else |
| 20:40 |
rubenwardy |
like, generated from code? |
| 20:41 |
Desour |
what "older versions load faster" claim are you referring to? |
| 20:41 |
rubenwardy |
the tech for doing this in lua is a bit clunky imo |
| 20:41 |
sfan5 |
not code, but the origin format should be machine-readable |
| 20:41 |
sfan5 |
because for every api version we should have the info: which version added, which version changed, which lua envs is it available |
| 20:41 |
sfan5 |
plus consistent cross links between structure definitions, types, etc. |
| 20:42 |
sfan5 |
Desour: was on discord and someone mentioned it in #minetest IIRC |
| 20:42 |
MTDiscord |
<GreenXenith> Isnt that the goal of the minetest-docs project |
| 20:43 |
sfan5 |
i dont know |
| 20:43 |
sfan5 |
if so, good |
| 20:43 |
MTDiscord |
<GreenXenith> Asciidoc is supposed to be able to export to other formats like XML and whatnot to make machine parsing easier |
| 20:43 |
Desour |
ah ok, I don't see the one, and don't read logs of the other. in case it was about client startup time: the texture alpha blitting takes much time |
| 20:44 |
Desour |
iirc, the goal of minetest-docs was to create more docs for examples and more useful information for the various api stuff. a bit like dev wiki |
| 20:45 |
MTDiscord |
<GreenXenith> It is intended to replace the lua_api.txt as well |
| 20:45 |
MTDiscord |
<GreenXenith> and be consistent in format |
| 20:46 |
MTDiscord |
<GreenXenith> I particularly care about being machine readable, as I generate code snippets from the API docs. And the replacement language server will probably do the same. |
| 20:46 |
sfan5 |
oh yeah also for language server/tab-complete purposes |
| 20:47 |
MTDiscord |
<GreenXenith> my script for parsing lua_api.txt is a nightmare |
| 20:49 |
sfan5 |
diceLibrarian: here, I quickly pasted it together https://0x0.st/H8ek.png |
| 20:49 |
sfan5 |
uhh |
| 20:49 |
sfan5 |
^ Desour |
| 20:50 |
sfan5 |
(why didn't I use copy-paste? it is a mystery) |
| 21:05 |
|
Desour_ joined #minetest-dev |
| 22:41 |
|
proller joined #minetest-dev |
