Open source is a two edged sword.
New contributor submits heavy new PR, leaves after 90% review without response.
New contributor appears, submits most systematically and logically organized patch in history of FOSS project after reading 10 page contributing.MD and gets hired as first dev a month later.
As with anything there is upside, and downside.
💯
We could do better. Let's say a small dev community wants to protect itself from ghosting. Whenever a new contributor comes and takes on responsibility, he needs to pay a deposit of a size that corresponds to the size of the task he is committed to and the degree the team depends on finishing the contribution. If the contributor ghosts the team, the deposit is split among current and past contributors.
I see this can be a barrier of entry in the beginning, but if all open-source developers make such a deposit and it becomes the norm, the ghosting problem will be successfully mitigated.
Implementation details intentionally left out.
i think you need to try and contribute to any given FOSS project and see about how they percieve your intrusion, i mean contribution
i've tried to contribute to about 5 separate bitcoin, lightning and nostr related projects and the wall of silence or unnecessary hostility has been breathtaking
like, the nips repo... you know, that only applies to the JSON protocol implementations
there is NOTHING stopping anyone from forking to a new variant, the only limitation is making the canonical events for the IDs to sign on
fiatjaf thinks that is onerous but fiatjaf has a funny idea of what expensive computation is also
> i've tried to contribute to about 5 separate bitcoin, lightning and nostr related projects and the wall of silence or unnecessary hostility has been breathtaking
What happened - was there a common thread?
nostr:npub1elta7cneng3w8p9y4dw633qzdjr4kyvaparuyuttyrx6e8xp7xnq32cume your suggestion to require a buy-in would scare off all prospective contributors 😅. After all, FOSS devs volunteer their time, which at professional rates is not cheap. This is costly enough.
Rather maybe an easier to implement filter is start with small, consistent, reliable contributions. If it’s a good match for both sides, increasing responsibility is in order. Finding these type of long-term contributors is key to FOSS.
in the case of LND, they just completely failed to be timely about looking at the PR i made, and had to repeatedly update because they were merging other commits that required me to redo big parts of the changes, 4 times, and i was like, ok, nope this is never gonna happen
probably the PR is still sitting on the thing, nearly 2 years later
the purpose of the PR was to make it easier to pull in the protocol message code without the entire repository being compiled with it
