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.
I don’t have a github account yet (only “lurked” there so far) but I’m going to create one in case I find something to contribute for bugs.
As for language, yeah English is not my first language, there’s a server dedicated to people from my country, no idea if they’re already contributing to localization but I’ll go check.
That directory has the English terms (look at strings.xml), and the one above has directories for each language. If your language doesn’t exist there, you can make a new directory for it.
If you don’t want to make a GitHub account or don’t feel comfortable contributing changes, you can always leave a post here with your translations and someone will get it contributed.
@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].
Uh reading your third link, no they are not reluctant to discuss it. That whole discussion sadly was about how the original “proposal” was framed, and I have to agree with that person that it wasn’t “proposed” but more stated as a demand.
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.
@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.
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.
God I appreciate these dudes. I don’t envy them one bit right now…
Yeah, very difficult situation, I truly hope they’ll find the help they need.
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.
Oh I’d love to do more but I’m not a developer :(
Only things I can do is donating and helping other people by answering questions (if I know the answers ofc, still learning myself).
Well, that’s super helpful by itself!
There are a couple other things you may be about to do as well, such as:
But honestly, just engaging with people here is super helpful.
Thanks for the advice!!
I don’t have a github account yet (only “lurked” there so far) but I’m going to create one in case I find something to contribute for bugs.
As for language, yeah English is not my first language, there’s a server dedicated to people from my country, no idea if they’re already contributing to localization but I’ll go check.
Well, if you get around to it, here’s where the translations are:
https://github.com/dessalines/jerboa/tree/main/app/src/main/res/values
That directory has the English terms (look at strings.xml), and the one above has directories for each language. If your language doesn’t exist there, you can make a new directory for it.
If you don’t want to make a GitHub account or don’t feel comfortable contributing changes, you can always leave a post here with your translations and someone will get it contributed.
@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
Uh reading your third link, no they are not reluctant to discuss it. That whole discussion sadly was about how the original “proposal” was framed, and I have to agree with that person that it wasn’t “proposed” but more stated as a demand.
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.
@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.
It’s really not that difficult. The things that need to be migrated are:
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.