this post was submitted on 20 May 2024
21 points (92.0% liked)
Open Source
31810 readers
586 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
I've yet to see a project that lives in github actually accept patches this way.
This is the main development path for most distros - Debian, Gentoo, etc.
Issues are tracked on bugzilla and then the patch is sent to the developer mailing list citing the bug ticket with
git send-email
. Not sure about Debian but in the case of Gentoo they accept contributions via their git mirror and email. The developers keep both in sync so that new contributors (who likely use github) are encouraged but more established users can stick to the mailing list.that is why I qualified the statement with "lives in github", i.e. the entire project relies on github issues, PRs etc. for all communication.
It has to be out of band… & you have to hope the maintainer a) checks there email & b) doesn’t turn their nose up to someone trying to contribute but getting the shaft in an horrible UX experience provided by their forge (I get heavy bandwidth throttle in my country & other countries are outright banned for US sanctions).