this post was submitted on 30 Jun 2022
76 points (98.7% liked)
Open Source
31190 readers
251 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Does anyone have experience with Codeberg? It looks like a pretty good alternative.
Codeberg is based on Gitea, which closely resembles GitHub's interface. Contributing to projects hosted on Codeberg is just as easy as contributing to GitHub projects.
The good: familiar UI, nice community
The bad: much worse accessibility.
Conclusion: I'd recommend keeping a Gitea/Codeberg remote but not using it exclusively. Doing so should include more people without excluding people who use assistive technology.
So what forge should be used as the one with better acceddibility?
@opensource
We need better accessibility on FOSS projects. It has tu suck needing to use a cringe service like GitHub because of accessibility.
Also, one might look into Sourcehut (sr.ht)
I saw this the other day but couldn't really understand how it works:( Using mail list in 2022 seems a bit ... unintuitive?
also I'd love to be educated about equivalents to issues/PRs in sourcehut cuz I'm thinking about shifting away from github too:)
Mailing list is actually very accessable IMO. You do not have to sign up for any service (with another account or some hostile captcha) but just drop your changes via e-mail (which everyone on the internet has).
With that workflow you just do your changes locally and once done you create a patch from the diff and send it afterwards to the mailing list. It is super easy with git send-mail and you should check out git-send-mail.io for infos about the git mail workflow (the site is actually by the devs of sourcehut).
EDIT: Drew also made a nice video about PR vs mail workflow here.
I have to disagree from personal experience. There has only once in my life been a mailing list that it was useful to have been subscribed to, it was by a friend group. Every other mailing list that I was ever part of was a waste of time.
How does that contradict the usefulness of mailing lists in context of software development? It's not a chat for anything but specifically discussing contributions, thus not any worse than discussion boards below PRs.
maybe it doesn't.
https://git-send-email.io is very informative, thanks!
I use it, it's pretty nice. As someone already said: the interface it's practically the same.