222
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Feb 2026
222 points (100.0% liked)
Open Source
44896 readers
508 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 6 years ago
MODERATORS
Ideally, you'd also first talk to the developers in charge of the project to see if your changes would be wanted in the first place.
(Or you'd start by reviewing existing bug reports and feature requests and addressing one of those.)
What I mean is, it's generally better to not just throw code at them and hope they'll like it. If you check first to see if they want it, you can save yourself from wasting effort on writing code that they'll decline.
I assume when people do that it's because they're going to be making the fork regardless, and they think they're being helpful by submitting a pull request with thier AI slop... But really they should just keep it on thier own fork if they don't understand the changes but want to use it regardless...