Giters

mt-mods / mt-mods

mt-mods meta repository for management and issues

Home Page:https://discord.gg/8k3K5nyj7x

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Request to transfer control of all of my Minetest-related repositories

VanessaE opened this issue · comments

commented

I have decided to basically retire from most Minetest-related activities, which includes modding.

Since a lot of people rely on them, I'd like to hand-over ownership and maintenance of any or all of my Minetest-related projects hosted on my Gitlab account to someone else. Obviously that'll require cloning them all from there to here.

This issue has been crossposted to minetest-mods and mt-mods -- the idea here is that I'm perfectly happy for either of these organizations to get my mods, just whoever wants to take on which ones. In fact, if others outside these groups wish to take over some projects, I'm okay with that, too.

All of my projects are located at https://gitlab.com/users/VanessaE/projects

Although it's conceivable that I'll randomly find a reason to add/change something in one of my projects, I do not require commit access or anything of the kind. That stuff can be done with ordinary pull requests.

All of the following projects need to be transferred somewhere:

Mods

Texture packs

Mod forks where I eventually became the maintainer

RBA's old shader projects
These shaders are unmodified from RBA's last changes, as far as I know, and probably don't work anymore, but they should still be copied over, for posterity:

Any open issues on the above repositories should be copied-over as well, though I don't know if there's any automated way to do that.

Any other projects found on my Gitlab profile are either outdated, or are just forks of other peoples' projects where I probably contributed something, or are unrelated to Minetest, and may be ignored.

All projects transferred to someone else will be deleted from my Gitlab account.

commented

I guess at least basic_materials could fit well because of pipeworks and technic plus.
@BuckarooBanzay what do you think? Or was there some bigger plans...?

However that mod should stay as stable as possible but I guess ensuring that is something to discuss somewhere else (or separate issues for mods, I guess there's some work to do with adopted stuff anyway).

commented

Well, I've pulled basic_materials to mt-mods/basic_materials with complete history, so waiting there for "semi-official" decision 😄

commented

Or was there some bigger plans...?

There is no "great plan" for all of this, but i'm writing an official "guideline" of the mt-mods org soon(-ish)
The main theme should be along the lines of "innovation, not mod-graveyard"

commented

Out of the 26 mods (not counting the textures and old shaders), 13 of them are on pandorabox, so it would be in our interest to have them easily maintainable.

So if we're going to "take" half of them already, I see no reason not to take the other half too :)

The textures and old shaders probably don't fit in mt-mods, as those likely won't need much (or any) maintenance.

commented

texturepacks could go to https://github.com/minetest-texture-packs

@Panquesito7 thoughts?

commented

texturepacks could go to https://github.com/minetest-texture-packs

@Panquesito7 thoughts?

Sounds good 👍 CC: @tacotexmex.

commented

I've pulled following repos to mt-mods (everything under Mods header):
Check marks indicate that issues and merge requests have been added from original repo.

  • signs_lib
  • basic_signs
  • street_signs
  • biome_lib
  • plantlife_modpack
  • moretrees
  • minislots
  • unifieddyes
  • autoclose_doors
  • reboot_warner
  • coloredwood
  • led_marquee
  • nixie_tubes
  • round_trunks

Issues and merge requests have not been copied but I could take a look if those could also be copied all at once using API.
edit. Issues and merge requests have been copied for checked repos.

commented

Mod forks where I eventually became the maintainer

Some mods do contain questionable licenses:

  • steel does not include any license at all.
  • others do have licenses added (and/or changed) later but licensing/relicensing is apparently not done by copyright holder.

If there's original sources for licenses / mentions of intended license by copyright owner it could be good to add notes about license sources to repositories.

Other than that I guess it could be assumed that licenses (where license exists) are valid, possibly released in some forum or otherwise authorized by copyright owner?
(also I did not go through all repos, just ones under mentioned header after I noticed that steel did not have license)

commented

steel has the license in its readme, reboot_warner and autoclose_doors don't have a license though.

commented

reboot_warner and autoclose_doors were one-offs for my servers, originally. Consider them public domain , or WTFPL or CC0 if you like.

For the sake of being official, I've just pushed the CC0 license to those two.

As for licenses of the ones I "took over", your guesses are as good as mine. 😉

ilights and currency were originally by Dan Duncombe. Near as I can tell, he only ever uploaded his originals as ZIPs to his forum posts. Those ZIPs can be found on these pages:

https://forum.minetest.net/viewtopic.php?f=16&t=7422
https://forum.minetest.net/viewtopic.php?f=13&t=7002

I'm 99% certain that the licenses declared on those posts are correct.

Gloopblocks was originally by Gloopmaster/Nekogloop. The original repo for THAT one appears to be here: https://github.com/GloopMaster/gloopblocks

commented

Issues and merge requests have not been copied

Ok, let me know when I can delete my repos.

commented

ok, all of the "Mod forks where I eventually became the maintainer" have been moved and issues for just that section moved

commented

pipeworks and basic_materials were done among first mods.

I've moved/checked issues for some mods, check marks in comment: #1 (comment)

@wsor4035 you've handled these too?
homedecor_modpack, home_workshop_modpack and simple_streetlights

If so then I think only things that still need some work would be:

  • unifieddyes issues and merge requests
  • moretrees issues and merge requests
  • Texture packs not for mt-mods
  • RBA's old shader projects not for mt-mods
commented

"Mod forks where I eventually became the maintainer" and "homedecor_modpack, home_workshop_modpack and simple_streetlights" have all had there issues and pull requests moved

commented

pipeworks and basic_materials were done among first mods.

I've moved/checked issues for some mods, check marks in comment: #1 (comment)

@wsor4035 you've handled these too? homedecor_modpack, home_workshop_modpack and simple_streetlights

If so then I think only things that still need some work would be:

  • unifieddyes issues and merge requests
  • moretrees issues and merge requests
  • Texture packs not for mt-mods
  • RBA's old shader projects not for mt-mods

issues (no prs) moved

commented

Oh, I also have a fork of Sanchez' blox mod on my repo:
https://gitlab.com/VanessaE/blox
https://forum.minetest.net/viewtopic.php?t=1960

Something should be done with it also. I do not consider myself to be the maintainer, but apparently my fork is the one people normally use, probably because I converted it to use hardware coloring through Unified Dyes.

commented

@VanessaE https://github.com/mt-mods/blox done

Anything useful in colored-itemstacks branch? 3 years ago updated, no conflicts with master.

commented

its one commit ahead, 6 behind, anyways its on github if we want it, dont have time to read it over atm

commented

I am not sure what that branch is actually for -- I could swear itemstacks already had color.

commented

Ok, by my count, all issues/PRs that needed moved have been moved. All mod repos have been deleted.

All that leaves is the texture packs and the shaders.