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.

[–] Schola@lemmings.world 10 points 10 months ago (1 children)

they

Am only one person :), but if anybody is interested in helping, I would love that, I can easily add you to be a member.

so all they have is a boilerplate script that doesn’t do anything yet?

Fair, I wrote that quickly as a starting point.

I’d rather see this project’s team simply working with upstream and sending PRs / patches.

Noted, am still thinking on the best way to approach this "interoperability" problem.

[–] fartsparkles@sh.itjust.works 20 points 10 months ago* (last edited 10 months ago)

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!