this post was submitted on 17 Jun 2023
24 points (96.2% liked)

Lemmy

12575 readers
1 users here now

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

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Kuvwert@lemm.ee 1 points 1 year ago (4 children)

God I appreciate these dudes. I don't envy them one bit right now...

[–] ulu_mulu@lemmy.world 1 points 1 year ago (3 children)

Yeah, very difficult situation, I truly hope they'll find the help they need.

[–] sugar_in_your_tea@sh.itjust.works 1 points 1 year ago (2 children)

Well, I'm lending a hand. I have some patches in production already, and I've only been contributing for a week or so.

If you have the means, please help out. There are tons of bugs, important features, etc, and it's a pretty stable base, so it's a good time to jump in.

[–] boud@framapiaf.org -1 points 1 year ago (1 children)

@sugar_in_your_tea About "good time to jump in": the small size of the lemmy dev community gives you a chance to shift off Microsoft to a community git forge e.g. #Codeberg [1] that aims at forge federation [2] *before* there's too much #TyrannyOfConvenience inertia. Mastodon devs are reluctant to even *discuss* giving up Microsoft [3].

@ulu_mulu @lemmy #GiveUpGitHub #forgefed #forgejo https://giveupgithub.org

[1] https://codeberg.org
[2] https://forgefed.org
[3] https://github.com/mastodon/mastodon/issues/22572

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.