• melroy@kbin.melroy.org
    link
    fedilink
    arrow-up
    16
    ·
    edit-2
    1 year ago

    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

    • Odo@lemm.ee
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Wondering why a move from Codeberg (non-profit, free software, self-hostable) to Github (propietary software, Microsoft)? Seems like Codeberg would be more aligned to the project’s values.

      • melroy@kbin.melroy.org
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        I agree but the reason was simple. Codeberg.org had too many down time issues. I and the community was impacted by the codeberg issues on almost a weekly basis. Hence the reason to move. I could also go to gitlab, but to keep reusing the Forgejo runners, github has the same workflow syntax. Anyhow, it’s also not up to me anymore. If the community decides to move to another git server I’m also fine with that. But I doubt the community wants to move back to codeberg.

        • vintprox@kbin.melroy.org
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          In retrospective, it’s a practical decision to move away from downtimes, especially seeing as development is so rapid now.

          We might do a mirror to Codeberg to avoid a complete dependency on GitHub, while accepting PRs on the side. Priorities tell us to postpone this idea in favor of long-awaited changes and fixes, though! 😉

      • ISometimesAdmin@the.coolest.zone
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Speaking for myself, I greatly appreciate the fact that it was moved to Github because 99% of all open source projects I’ve ever wanted to contribute to in the past have all been on Github. Kbin (and alexapy, on gitlab) have been the only exceptions.

        And that’s not even mentioning my work also uses Github for our internal repos.

        Speaking purely selfishly, it’s simply more convenient to be able to manage and track my time and contributions all in a single place, and I can’t imagine I’m alone. I’m looking forward to seeing Codeberg’s long-term goals of federation see fruit, but for right now it was simply an obnoxious extra hurdle.