[NEWS] kbin.run has completed migration to mbin codebase

all-knight-party, 7 months ago

logical change, haven't noticed any issues or incompatibilities on my end. is there a place where one could keep up with development of mbin from within the mbin system? for example, i follow Ernest for his general updates and discussions about kbin and its direction, as i don't otherwise ever look at github.

and does this mean that mbin forks here, forever? so if kbin receives large updates down the line mbin is now its own beast and will update and evolve independently?

melroy, 7 months ago

Yes, I created the Mbin fork. Expect this fork living forever, Kbin development WoW caused to stalled development. Mbin is community-focused. Despite I was the creator of the fork, various contributors do have owner rights on GitHub. It's build on trust and there will be no single maintainer. Development has been accelerated since. Due to Ernest inactivity and unresponsiveness in the past couple of months (year?), I didn't saw any other way then creating a fork.

all-knight-party, 7 months ago

Thank you for the info, I can definitely understand why you needed to fork at this point. I respect Ernest a lot, but he's one man with other responsibilities and things going on in his life.

melroy, 7 months ago

See my follow up post here: https://kbin.melroy.org/m/updates/t/55330/Mbin-is-born-Fork-of-kbin

debounced, 7 months ago

great questions! i think the good thing (or maybe bad, depends on who you ask i suppose...) is there isn't one person or owner of mbin. as of today, there are 10 owners/members of the project with merge privileges on the repo; however, we each need to get approval from at least 1 other project owner to "merge it" into the "main" branch.

github and the associated mbin matrix rooms are where most of the discussion about features and direction takes place among contributors, but i will try to make it a point to keep everyone here informed when a major change take place. right now we're trying to catch-up on the backlog of pull requests and enhancements that have been stagnating for months over in the kbin repo. @melroy is also pretty good about keeping the masses up-to-date on recent events if you want to follow him as well.

finally, one way to look at mbin is viewing it as a superset of kbin, that is, unless the kbin codebase changes dramatically or some other crazy thing happens like a change in license (which wouldn't be a good thing for kbin), it should be relatively easy to port over upstream changes from kbin that we want to see in mbin. my sneaking suspicion is that mbin will quickly surpass kbin in every way since we don't have a massive money pit like kbin.social holding us back, the focus is purely on the development of the code base and listening to community feedback/inputs. :-)