this post was submitted on 30 Oct 2023
50 points (83.8% liked)
Fediverse
17698 readers
2 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ernest has some big life stuff going on right now (you can check out his posts if you really need to know), and hasn't been able to review/merge in PRs for kbin lately. Furthermore, kbin.social doesn't even have the latest changes that are merged in, so the community fork mbin was made by @melroy, one of the most prolific contributors to kbin.
Thank you for providing some context for this. It kind of sounds like a fork might not have been necessary if Ernest was willing to make @melroy a maintainer. Do you know if there's any philosophical reason he wasn't willing to do that? Real life stuff comes and goes, but it seems silly to halt the "official" project that others are relying on and still wanting to improve upon and thereby force a fork. As it stands right now, it sounds like it will be awkward for Ernest to come back in and try to restart work on kbin and will be increasingly awkward the more that mbin progresses, becomes the standard, and the code bases diverge.
Despite being maintainer of Kbin (incl. several others), we wasn't allowed to merge other PR changes except my own or changes that Ernest didn't like (eg. GUI pull requests were reverted again). Then when development slowly became to a halt, I didn't want the project to die. I didn't saw any other solution than to fork the project. Not only that, we also didn't like some changes from the past, which Mbin also rolled-back (like only show local magazines in the random sectors in the sidebar).
The fork by the community for the community also allows us to do multiple things from the start: 1. No single maintainer anymore. 2. Introducing a C4 contract: https://rfc.zeromq.org/spec/44/ 3. More transparency and giving all contributors owner rights on all platforms incl but not limited by GitHub, Weblate and Matrix. Allowing multiple people to become fully responsible for the project. Having discussions about contents, when we as a community agree on changes PRs can be merged after 1 owner approval. Various instances now moved to Mbin (like https://fedia.io/ ), because they saw hope again. As stated earlier, we also moved to GitHub now and to the hosted weblate.org instance. Currently the development is booming, because it's not getting reversed and slowed down.
We had ~150 PRs in a only 2 weeks time (Kbin has this number over a year not a week or two). The amount of improvements in the code, bug fixes, GUI, docker setup, documentation and security fixes as well as various features are impressive. Mbin is not about me, it's about the community now.
See also: https://kbin.melroy.org/m/updates/t/55330/Mbin-is-born-Fork-of-kbin
Thank you for laying it all out there. It sounds like you're doing it the right way 🙂