Wasmer – Run, Publish and Deploy any code, anywhere

Re:Wasmer – Run, Publish and Deploy any code, anywhere by itishappy on Monday September 18, 2023 @12:39PM (#37558527)

The "different point of view" here seems like you're determined to interact with their community in a way they've explicitly asked you not to [0]:

> Please don’t use bounties to incentivize Zig development.

They explained their reasoning extensively:

  - Bounties foster competition at the expense of cooperation.
  - Bounties are an utterly simplistic way of dealing with the business management side of creating software:
    - Instead of scouting for a suitable candidate, you’re letting battle royale dynamics pick a winner for you, at the expense of everybody who’s going to lose the competition.
    - Instead of creating a clear contract where you take on some of the risk, you implicitly put the entirety of the risk on the contestants (eg partial solutions don’t get any payout).
    - Instead of allocating time and resources to proper due diligence, you instead penalize any form of thoughtfulness in favor of reckless action (eg a solution just needs to pass a test suite).
    - Instead of planning for the full lifecycle of software, which also includes maintenance, you end up with a quickly bitrotting artifact that is of no practical use to anybody.
    - Instead of spreading unease to all the people involved, it would be preferable you instead learned how to do business properly.
  - On projects less radical than Zig, you might also put pressure on the development team to accept the winning submission, which, given the above, will probably not be the most well-thought-out and maintainable solution.

You responded by moving the request to your own repo, with the following disclaimer [1]:

> Info: while ideally the PR should be merged into Zig master, is not a necessary requirement to receive the bounty. As long as a fork exists that fulfills the requirements laid out before, the bounty will be awarded

To an outsider, this looks like you slapped a new name on the exact thing the Zig team asked you to stop.

Do you feel your new request adaquately addresses the team's issues?

[0] https://ziglang.org/news/bounties-damage-open-source-project...

[1] https://github.com/wasmerio/wasmer/issues/4218

[ Parent | on HN ]

Re:Wasmer – Run, Publish and Deploy any code, anywhere by syrusakbary on Monday September 18, 2023 @01:01PM (#37558807)

While I respect their point of view, I do not agree that banning bounties in OSS projects is the right way of approaching it, and as such we haven't complied to it. Specially since this is a bounty for a real need that we have at Wasmer.

Furthermore, we also took their post constructively and added two more points on the bounty issue [1] that we believe should solve most of their concerns:

* Wasmer will manage the work and have at most one person or team working on it at a time. Anyone interested on the work should reply here and organization of the work will be done by the Wasmer team

* Partial work that actually works will be rewarded accordingly (for example, the libc layer, or the Zig layer itself)

Of course, the fact that they banned any further conversation from the disagreement doesn't make specially easy to see if such an approach will be sufficient for them or not.

[1] https://github.com/wasmerio/wasmer/issues/4218#issuecomment-...

[ Parent | on HN ]

Re:Wasmer – Run, Publish and Deploy any code, anywhere by rishav_sharan on Tuesday September 19, 2023 @02:12PM (#37573890)

Isn't that how oss works? You should be able to add bounties to your fork. Then zig team can choose not to merge these if they want.

[ Parent | on HN ]