• Boud
    link
    fedilink
    11 year ago

    @sugar_in_your_tea As a non-lemmy-dev, I don’t get to participate in that decision either, no matter how strong I think the arguments are.

    I’m not convinced that the difficulty in switching is low; as you say, bug/issue tracking is a big barrier, but other features are part of the #EEE strategy [4], and switching later when MS upsets the community like Musk or Huffman will be difficult.

    An official mirror would be a good start to make a future move easier.

    @lemmy

    [4] https://en.wikipedia.org/wiki/Embrace%2c_extend%2c_and_extinguish

    • @[email protected]OPM
      link
      fedilink
      41 year ago

      There are mirrors of the Lemmy code on Gitea and Gitlab. They are linked in the readme. We also hope to migrate development to Gitea once federation is implemented.

      • @[email protected]
        link
        fedilink
        21 year ago

        We also hope to migrate development to Gitea once federation is implemented.

        That is awesome to hear! Lemmy federating with the code forge it’s hosted on sounds awesome!

        • @[email protected]OPM
          link
          fedilink
          11 year ago

          Im not talking about federation between Lemmy and Gitea. Not sure how that would work or if it would make sense.

          • @[email protected]
            link
            fedilink
            11 year ago

            I get that but it still sounds awesome 😉 Of course Gitea federating with other Gitea (or Forgejo) instances would be awesome and make it a right candidate to host another fediverse project.

    • @sugar_in_your_tea
      link
      11 year ago

      It’s really not that difficult. The things that need to be migrated are:

      • links to repository - tedious, but the GH repo could be left up with links to the new repo and code mirroring could be configured; I’ve seen that done pretty often, and some projects go the opposite route (e.g. the Linux kernel has a GitHub mirror for… reasons)
      • issues - the GitHub CLI and API both offer a programmatic way to pull down issues, so those can be migrated with a script to whatever the new solution is; I could whip something up in an afternoon if needed
      • actual code hosting - just change remotes and push; this is like a 5-min thing
      • CI - the current CI situation is really simple and easy to port

      And, that’s it. If needed, the whole process could be done in a couple days.

      So I don’t see any kind of urgency here.