@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.
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.
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 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
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.
That is awesome to hear! Lemmy federating with the code forge it’s hosted on sounds awesome!
Im not talking about federation between Lemmy and Gitea. Not sure how that would work or if it would make sense.
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.