3 ms·
I think there are 2 dynamics that Andrew Kelley alluded to that Algora / Wasmer could have addressed better: 1. Consulting with the Ziglang leadership before c
by ayewo 3y ago
I think there are 2 dynamics that Andrew Kelley alluded to that Algora / Wasmer could have addressed better:
1. Consulting with the Ziglang leadership before creating the issue that kicked off the bounty. Doing it this way would have allowed them to provide some input on perhaps splitting the bounty, improving the acceptance criteria and other logistical stuff, rather than allow them find out later when the comments were devolving into personal attacks.
2. Splitting the bounty.
Offering three bounties: $2500, $1500 and $1000 increases the likelihood of producing different approaches and rewards skill as opposed to one $5000 bounty that rewards the fastest person, to the detriment of others working on it. The amount spent is the same but the outcome is less of a battle royale.
3. If splitting the bounty is not an option (because the intent is for the high-ticket $5000 on offer to fuel Wasmer’s marketing), then at least more thought should go into how the bounty is administered by working with Ziglang leadership so that it doesn’t create unhealthy competition or at least draw people with the right skills.
Zama runs a big-ticket bounty program that is worth emulating in how it is run https://github.com/zama-ai/bounty-program https://github.com/zama-ai/bounty-program
- zcesur 3y agoAgreed on all 3 points here, thanks for sharing your thoughts, super helpful Following your feedback, perhaps community bounties should be by default only shared with maintainers, and then the maintainers can choose whether to complete them themselves [1], or make them public, or disregard This approach would prevent situations like the above and hopefully also helps with FOSS sustainability [1]: https://twitter.com/algoraio/status/1703115434055082086 https://twitter.com/algoraio/status/1703115434055082086
- ayewo 3y agoYes, exactly. Courting the maintainers for their permission first could have avoided this scenario. So, assuming you did that but Ziglang leadership declined, for whatever reason, then the alternative would be to host the bounty on Wasmer’s repo as they have done now https://github.com/wasmerio/wasmer/issues/4218 https://github.com/wasmerio/wasmer/issues/4218.