Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
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. 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 hopefully 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 communication doesn't make it specially easy to see if such an approach is enough or not.
[1] https://github.com/wasmerio/wasmer/issues/4218#issuecomment-...
Looks like it's done through shared library
https://github.com/wasmerio/wasmer-ruby/blob/master/lib/wasm...