The Kbin developer wants to focus his work on deeper technical challenges, while the Mbin developers want development to be more fast-paced with greater community involvement. Both takes are valid, but difficult to combine in one development effort.
As quality control is more relaxed, there’s fewer safeguards against potentially bad code (bugs or harmful stuff, intentional or non-intentional).
When there was a bit of friction between kbin and mbin, this was the starting point: kbinwas criticized for being too slow and conservative, taking ages to implement features because everything needed to be thoroughly thought through and it’s just one man doing that. Meanwhile mbin went pretty far out in the opposite extreme. Both found the approach of the other potentially harmful (by either discouraging contributors or by not having enough checks in place).
I guess I missed it. Why there was a need to fork kbin? Are there issues with it?
The Kbin developer wants to focus his work on deeper technical challenges, while the Mbin developers want development to be more fast-paced with greater community involvement. Both takes are valid, but difficult to combine in one development effort.
deleted by creator
After I posted it, I found another discussion where it looks like mbin policy is that anyone can merge anyone else’s PR.
As a software developer, that actually sounds really scary.
how does it?
As quality control is more relaxed, there’s fewer safeguards against potentially bad code (bugs or harmful stuff, intentional or non-intentional).
When there was a bit of friction between kbin and mbin, this was the starting point: kbinwas criticized for being too slow and conservative, taking ages to implement features because everything needed to be thoroughly thought through and it’s just one man doing that. Meanwhile mbin went pretty far out in the opposite extreme. Both found the approach of the other potentially harmful (by either discouraging contributors or by not having enough checks in place).
A big advantage of more community involvement; more will get done in a shorter time
In the end it won’t matter for the end user, as both projects can choose to incorporate features from the other due to the open-source nature
So the question is, do you want it working now (Mbin) or do you want it working somewhere in the future (Kbin)