Minetest-Mods team[Mod repository]

[BirgitLachner]

Hm ... seems to be more difficult ...

[BirgitLachner]

okay ... after enabling one mod after the other it seems to me, that "mg" causes all the problems.

[sofar]

okay ... after enabling one mod after the other it seems to me, that "mg" causes all the problems.

hmmmm, I can run with `mg` and `moretrees` and `biome_lib` and even `moreores`. Even `moreblocks` works on top of that. Can you post the full list of mods that causes the error, please? (world.mt content, basically, is what I need)

[BirgitLachner]

Oh ... I have got so many mods activated ... That will take so many time for you to check them all.

I'll have a look, if I find the same problem again and send world.mt then.

Thanks, Birgit

[Wuzzy]

The fact that this project depends on GitHub worries me.

I would like it more if the project would be independent from large megacorporations.

[Linuxdirk]

The fact that this project depends on GitHub worries me.

Absolutely. Self-hosting on maybe git.minetest.net was thrown out by the usual suspects ignoring all the benefits it would have due do it causes some work to set up and occasionally updating the user-facing software.

We have to wait until MICROS~1 fucks GitHub up (it's not "if", it is only "when", I think it will take the usual 2-3 years) before Minetest moves to (presumably) GitHub (wich is already used for some tasks GitHub is not capable of).

[texmex]

Well, at Mesehub we’d be glad to have them. Hosting web apps in 2019 is too painless for setup or maintenance to be the reason not doing it. I think I spent 15 minutes setting up Mesehub, and that’s including automatic updates, secure Docker environment, automatic certificate and automatic backups.

[rubenwardy]

Absolutely. Self-hosting on maybe git.minetest.net was thrown out by the usual suspects ignoring all the benefits it would have due do it causes some work to set up and occasionally updating the user-facing software.

I support switching to gitlab, as either a self-hosted instance or at gitlab.com

And there are other issues raised here, including the lack of network effect: https://github.com/minetest/minetest/issues/7412

[texmex]

Although Gitlab boasts some mighty features and pivoting toward that choice is understandable considering the Minetest engine build system, choosing Gitlab would be a setback for regular mod developers with need simpler than Gitlab’s massive feature set and slowness.

I recommend Gitea.

[sofar]

None of the alternatives are currently going to make an improvement - any move away from the current location will be massively disruptive.

For this reason I don't think minetest-mods should move at all, and if it becomes a necessity (e.g. actual policy changes to github's TOU that threaten the way that minetest-mods functions, not just people being paranoid) then I think the only correct solution is to self-host, and not to go from one possible pitfall to another possible pitfall.

gitlab is still nowhere near the adoption rate of github, keep that in mind, and almost everything in minetest-mods originated from github to begin with. Once you move it off, github will *redirect* users looking for minetest-mods *back to the outdated forks* on github, and not to gitlab or off-site hosting.

The best thing to do right now is to do what I've been doing:

- regularly backup and fetch copies of every minetest-mods mod
- continue working to fix bugs and help others get better mod code
- stay vigilant but not paranoid about github

[Wuzzy]

Good to know that the repos are backed up. This is a major relief. So GitHub is basically replacable if things go horribly wrong.

[twoelk]

Good to know that the repos are backed up. This is a major relief. So GitHub is basically replacable if things go horribly wrong.

... and create a more stable organization that is not prone to stumble over single places of failure.

see concerns in second post of this thread and the following discussion :-)