148
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 23 Oct 2023
148 points (96.8% liked)
Open Source
31028 readers
819 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
So all they have is a boilerplate script that doesn’t do anything yet?
I’d rather see this as a collaborative effort between upstream rather than a “layer” of scripts, not to mention their “phase 3” is forking upstream which we really don’t need.
I’d rather see this project’s team simply working with upstream and sending PRs / patches.
Am only one person :), but if anybody is interested in helping, I would love that, I can easily add you to be a member.
Fair, I wrote that quickly as a starting point.
Noted, am still thinking on the best way to approach this "interoperability" problem.
I love your passion but I think you published on GitHub a little too soon. Rather than pitch solutions, keep it to the problem space definition for now.
Then, reach out to the upstream developers and see what their thoughts are and how you can contribute. I’m sure there is definitely space for a interoperability library that makes it easy for any creative FOSS app to integrate and enter into this open ecosystem concept but rather than inventing it for upstream, you should invent it with upstream.
Good luck and stay this passionate - the FOSS community needs people like you!