cacheson,
@cacheson@kbin.social avatar

It looks like they're still working out what they want their process to be:

https://github.com/MbinOrg/mbin/pull/34

Seems like your concern is addressed there:

Pull Requests require at least one (1) other maintainer approval before the PR gets merged (built-in peer review process).

The mbin fork happened when kbin development was looking a lot less active. In any case, it's not necessarily bad to have a diversity of approaches. Due to their differing organizational structures, mbin will likely tend to have more features and more rapid development, but also potentially more bugs, while kbin remains more stable.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fediverse@kbin.social
  • random
  • meta
  • Macbeth
  • All magazines