Comment on GitHub - MbinOrg/mbin: Mbin: a /kbin fork - By the community, for the community
QuazarOmega@lemy.lol 1 year ago
Is it me or the description leaves something to be desired? What is it that sets it mbin apart from kbin, wasn’t kbin developed by “the community” in the first place?
Blaze@discuss.tchncs.de 1 year ago
The general issue of Kbin is that most of the development has to be approved by the main contributor of the project.
This fork is meant to be easier to contribute to. Let’s see how it evolves.
nakal@kbin.social 1 year ago
It makes sense to approve things and keep navigating in one direction. What was the original problem?
ram@bookwormstory.social 1 year ago
The problem with kbin is that the project maintainer was leaving PRs to rot for months. Even things like PRs to update dependencies for security patches weren’t getting updated. The community-based one looks to resolve that by running by simple consensus.
I’m not sure I agree that’s a good idea, giving full governance to the community like that, but since Kbin’s development has slowed, and the app itself has proven itself to be less-than-desireable to maintain, this is a good chance at finding new direction.
nakal@kbin.social 1 year ago
Thanks for the explanation. Since KBin is more fragmented and does not build up enough steam for further development, it's maybe a better option to move to Lemmy at this point.
QuazarOmega@lemy.lol 1 year ago
Thanks, I understand now