Time Nick Message 02:02 Blockhead256 !tell mistere_123 prior discussion about password resets here: https://irc.minetest.net/minetest/2024-11-24#i_6222168 02:03 Blockhead256 basically, I think you do want ruben for password resets. The system is intended to be self-service though. 02:03 Blockhead256 Remember that age-old advice "Never tell anyone, even customer support, your new password?" 02:03 Blockhead256 s/?"/"? 02:06 MTDiscord its already been fixed 02:09 Blockhead256 well, just on the off case, and for future reference 03:13 MTDiscord merging https://github.com/minetest/dev.luanti.org/pull/112 soon ™️ if no one hollers 03:17 MTDiscord @greenxenith going to make a follow up pr with mission statement + roadmap so that issue can be closed out. figured its been a week for anyone to scream, and the commented has been upvoted/aproval given here above somewhere by people 03:18 MTDiscord 👍 send pr link when done so I can take a gander 03:21 MTDiscord hmm, roadmap on the site seems counter intuitive, i think ill make a master issue for that, pin and lock it or some jazz and just link to that from the site? 03:22 MTDiscord seems like a pain to have to update it on the site all the time, and github issues have history 03:29 MTDiscord @greenxenith https://github.com/minetest/dev.luanti.org/pull/114 (note the linked issues it will close) merging once green is happy. 03:30 MTDiscord > can be found at this issue. 03:31 MTDiscord i cant lock out minetest-docs people from commenting on this: https://github.com/minetest/dev.luanti.org/issues/113, so honor system to just edit it to add stuff and not comment on it 03:32 MTDiscord done 03:33 MTDiscord anything else? 03:34 MTDiscord Im cool with it 03:35 MTDiscord thanks 03:53 MTDiscord went down a rabbit hole on https://github.com/minetest/dev.luanti.org/issues/85 there is https://github.com/CICDToolbox/markdown-lint ci action, which uses https://github.com/igorshubovych/markdownlint-cli which uses https://github.com/DavidAnson/markdownlint (seems to be popular at the core of a lot of things) but it doesnt have an option for what mark wants. it has an option for extensions 03:53 MTDiscord https://www.npmjs.com/search?q=keywords:markdownlint-rule of which none match what mark wants 03:54 MTDiscord so unless someone wants to write an extension for this, i kinda am leaning towards just closing the issue 07:02 MTDiscord wsor: Closing as "not planned" is OK by me, but maybe we add it to the style guide? It really feels do-able but I understand it's low ROI for now 07:24 Blockhead256 yeah it feels like something to ask of people in the creation of documents, even if it's not automated in the CI 21:09 MTDiscord still think githubs two closing options are kinda stupid 21:09 MTDiscord like i just want to close the thing damnit, dont care completed/not planned, etc 21:11 MTDiscord roller: did you want to rereview https://github.com/minetest/dev.luanti.org/pull/111 or is it good enough ™️ ? 21:18 MTDiscord I checked the changes and it looks good at a glance 21:19 MTDiscord thanks 21:19 MTDiscord ill merge in 10 if no one screams