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.
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
I've had a good experience doing a couple of bug fix bounties for urllib3 https://github.com/urllib3/urllib3/issues . I'd be interested in how the maintainers how found running the bug bounty and if it's given them more useful fixes or if it just adds more noise to deal with
I am testing a solution to the problem of funding open source through a custom license based off the AGPL, the Candid Public License: https://github.com/candiddev/cpl
The goal is to be ridiculously FOSS and require companies to do the same in order to use your project. If they don't want to embrace the copyleft aspect, they can purchase an exemption from it (see https://yaml8n.dev/pricing/ for an example).
In this model, the FOSS ecosystem can still thrive and build off of each other, and projects can negotiate license exemption to help sustain themselves.
I respectfully disagree with the take that Bounties damages Open Source Projefts, which I also respectfully communicated to the Zig leadership team.
After my communication they banned me from participating in their community (I quote from them "You're not welcome anymore on our GH repo nor any other community managed directly by us.").
For those interested, we moved the sponsorship work to the Wasmer repo, so those who want to work on it can do it freely.
https://github.com/wasmerio/wasmer/issues/4218
The contributors are expected to follow code of conduct: https://github.com/ziglang/zig/blob/master/.github/CODE_OF_C...
At least these lines sounds reasonable:
> Examples of behavior that contribute to creating a positive environment include:
> Using welcoming and inclusive language.