- what if the maintainer goes awol and the mod listing confuses and misleads more than anything else
I wasn’t referring to rogue users but more how to deal with a stale but original mod competing on old merit with newer alternatives.
Imo there has to be a better way than to do endless ”_redo” type of mod naming. Perhaps actively developed mods with feature parity sometimes can be recommended on the page of the stale one, if not take its place. I’m thinking of my experience with refreshing and improving adampilz’s item_drop as an example. If his original mod was present in CDB but abandoned, I would have to come up with a new name just for the sake of it, while also ”competing” with an inferior and stale mod.
I guess I want maintained mods to take precedence somehow.
- what if the maintainer goes awol and the mod listing confuses and misleads more than anything else
Here’s a fresh example:
How will ContentDB look a year or two down the road, when possible every other unmaintained game will get a refresh and repost by someone else than the original author? Or someone decides to do a ”Pixture Revival Redo”?
My point is that for the sake of the end user of the content CDB needs a way to deal with these sort of issues before they sprawl.
Attachments
B0005131-BE48-48C9-8B01-6882E78BBDBD.jpeg (125.16 KiB) Viewed 2067 times
Last edited by texmex on Fri Sep 13, 2019 17:03, edited 1 time in total.
To be fair, Pixture is not visible in Minetest 5.0.0.
I have not claimed the repository rights of the original Pixture yet. I'm not sure if I could or should. *shrug*
Version 1.0.0 is not released yet (but it's getting close!), so it's not too late for a rename or even a merger. :-)
I just posted it to make it easy for testers to download.
It probably would have been better to assume control of Pixture, but at the time of posting, I did not know whether kaadmy will ever want to pick Pixture up again. And then we'd have a nice collision and that would have been rude. :-/
Also, assuming control over the original repo is a huuuge responsibility as well. :-/
Also note that the goal of Pixture Revival is really just a revival, fix bugs, basically to make it work for MT 5.0.0. The goal was NOT to seriously extend the game feature-wise. Basically it's my way of preserving a piece of Minetest history, while still having a playable game. So that's another justification for the name. But yeah, I admit, it was only meant as a temporary name, and then it kind of stuck … I should probably discuss with kaadmy and others to clean up this little mess. It's not too late yet …
But another (possibly only theoretical) problem with a merger would be that there will no longer be a Pixture for MT 0.4 (at least not officially) … Idk how many players are able to get MT 5 yet.
Maybe pre-5.0.0 things should be hidden or at least marked in a special on the website? I know, it's not a real solution, but at least a start.
EDIT:
OK, I have a simple idea to help fixing situations like this one: Allow to mark certain things as “superceded”. This means that there is a newer iteration of the thing available and the thing is no longer developed. “Superceded” does not imply the thing itself is in any way broken, just that there's a different, improved version available that still closely resembles the original. Author endorsement might also be a criterion, but it gets difficult if the author already has vanished into a puff of smoke. “superseded” should not be used for the next thing in a game series (like, when each part of the series tells a story in an epic adventure).
I'm against allowing people to take over packages owned by someone else. But the ability to make packages as outdated and to recomend other packages would be good
From: Minetest ContentDB <youremail>
To: myemail
Subject: Verify email address
Date: Thu, 12 Sep 2019 20:21:55 +0000
This is a verification email!
That's all, the email address unchanged.
And if you try to upload an archive that isn't a .zip, the warning message uses both load and upload in the same line: e.g. "Please load upload a zip archive."
Well then. So “Pixture Revival” it is, I suppose? Because the name “Pixture” is already taken?
Rubenwardy, note that I specifically said “superceded”, not “outdated”. A superseded package might still be a fully functional game. “outdated” implies “kind of broken”. The choice of words is very important here.
Maybe I'm repeating myself but I'd be really handy if texture packs also had support for showing soft and hard dependencies as it would show what mods were supported texture-wise.
texmex wrote:Maybe I'm repeating myself but I'd be really handy if texture packs also had support for showing soft and hard dependencies as it would show what mods were supported texture-wise.
To be honest, if the mod is not enabled, it won't use the textures for it anyway.
It makes more sense for the TP creator to include a list of supported mods in the README file.
This way it will show up on the mod's page.
I want to add, it would be nice to be able to click on a project from the browse online page, and have it bring up the information on the CDB web page. Much like the behavior of the software managers for Linux distributions.
You know, it is possible to add version to the game name. So if author of Cool Game 0.0.1 will abandon development, then his authorship could be preserved. Anyone else could be able to make Cool Game 0.0.2.
More than that, with defined version it will be possible to keep mods consistent while they depend on other mods.
Other package managers already have versioning. I keep wondering, whether you will make third package manager for lua or give up and start using some existing.
WOW, that is impressive. Definitely a huge improvement. I honestly can't see anything wrong with the layout myself. It's very clean and professional looking.
My only feature suggestion would be to provide the ability to upload a custom banner (of the appropriate dimensions), rather than using one of the screenshots as a darkened background. Also having an option for a square PNG logo that could be placed immediately to the left of the title and short description. Basically I'm thinking something like how it is done on Facebook pages and subreddits.
Encouraging mod and game authors to include logos with their creations could have ancillary benefits as well, since once it gains enough traction then the in-menu installer could list the mods by their logos, which would probably make more sense from a GUI perspective than tiny screenshots. Also even the /mods commands on servers could eventually open a fancy formspec showing all of the installed mods by their logos, names, and authors. It opens a lot of possibilities for other applications.
Anyway, sorry for going a bit off on a tangent :) I just really like this new design so much!
1.25rem is the same padding as .card-header has. (You use that padding for .card-body in the other cards, too. But the card that holds the table does not use that body so the padding is missing and the 0.75rem coming from .table td are just too less in this case.)
ContentDB now has support for automatically creating releases. This can be done either by using the REST API, or by using webhooks with support for GitHub and GitLab. I decided not to use a polling approach to do this, because I wanted to keep the complexity of ContentDB low and avoid the explosion of state. The code for the webhooks is isolated, so I'm happy to accept contributions for the webhooks of other platforms.
ContentDB now has support for automatically creating releases. This can be done either by using the REST API, or by using webhooks with support for GitHub and GitLab. I decided not to use a polling approach to do this, because I wanted to keep the complexity of ContentDB low and avoid the explosion of state. The code for the webhooks is isolated, so I'm happy to accept contributions for the webhooks of other platforms.