Re:Bounties Damage Open Source Projects
by syrusakbary on Sunday September 17, 2023 @11:14AM
(#37545904)
This comment might be insightful: https://news.ycombinator.com/item?id=37545637
Tl;dr: The work was not required to be merged upstream
Re:Bounties Damage Open Source Projects
by guilhas on Sunday September 17, 2023 @06:55PM
(#37550151)
Don't understand the problem, can't the PRs just be ignored forever or closed?
No one can do any work unless the leadership green light seems a bit restrictive
But now the zig project are responsible for denying someone else $5,000. I think that's unfair pressure to put on them. It may also cause some of the potential bounty claimants to exert pressure on the zig team too.
Re:Bounties Damage Open Source Projects
by syrusakbary on Sunday September 17, 2023 @08:05PM
(#37550681)
This is not true.
The $5,000 reward did not required the work to be merged upstream. Please read the rest of the thread
You proposed a change to a repo you do not own. You offered an incentive to 3rd party developers to push PRs to that repo. You did not wait until the proposal was accepted. You thus required the community maintaining that repo to do extra review work on a feature they hadn't officially accepted yet. You were refused, and then offered the same incentives somewhere else, with the same drawbacks on the zig community.
Even in your new offer it's unclear whether people should make changes in zig (add support for your features in zig) or in wasmer (change the samples to work with the current zig compiler, or build libraries that work with zig) to support your features.
There's a time and place to offer incentives for someone else's project, but that shouldn't happen without their approval.