44
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 24 Dec 2024
44 points (97.8% liked)
Open Source
31733 readers
134 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
The general rule of thumb is, if a single PR changes lots of things then it won't be accepted.
I'd suggest breaking it into multiple PRs and possibly reaching out to someone on the core team to explain what you were trying to do and how you've done it kinda like RFC. Ideally this would've be done before you started with a major change but still.
I see you also mentioned original devs are no longer active. In that case you can send PRs but don't expect them to get merged but instead if you are still using it, try to update and fix other things as you see fit and people will see it and start using your repo and if at any time original devs comeback maybe they can official handover project to you or accept all your PRs. And this is totally OK as long as you are not breaking any license original devs had, that's what forks are for. If you want you can rename and do rebranding but that is not necessary unless original devs had trademarked the logs and stuff and that original repo is completely dead.