Lemmy

12540 readers

6 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago

MODERATORS

[email protected]

221

Update from Lemmy after the Reddit blackout (join-lemmy.org)

submitted 1 year ago by [email protected] to c/[email protected]

99 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] sugar_in_your_tea 2 points 1 year ago (1 children)

Well, I don't get to make that decision. If the maintainers choose to do that, I'll follow, but there's a good chance that a lot of the other contributors won't. For something in rapid development with a lot of community contributions, you want that barrier of entry to be as low as possible.

So if it was up to me (and it's not), I would say no. I would be open to an official mirror somewhere else, and perhaps moving to a separate feature/bug tracking system (esp. if it's easier for the community to report bugs), which imo is the biggest barrier to moving the repo.

I guess I'm not particularly worried about it since the project is FOSS and the difficulty in switching is pretty low.

[–] [email protected] 1 points 1 year ago (2 children)

@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] 4 points 1 year ago (1 children)

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] 2 points 1 year ago (1 children)

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] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 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 1 points 1 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.