After some consideration, we decided to stop the whole bounties program at this moment.
The reason is we are spending more time discussing the approach, giving advice, and fixing some results than we would spend without the bounty program.
Of course, we want to be fair and if you have been already assigned to some bounty and have already written the code for your bounty, let us know. But otherwise, if you haven't started, please don't.
We have experienced so many troubles with the bounties that we have to stop them at this moment for an unspecified amount of time. We are still open-source, open to contributions, and happy to promote E2B-related projects or include them in our Cookbook.
Thanks for understanding! 🙂
E2B Bounty Program
As an open-source product, we highly value community contributors who help us develop the best product. We provide financial rewards for the following bounties.
Disclaimer: Please try to only choose one bounty at a time and let us know if you gave up a bounty, so you don't block other users from choosing it.
:one: Choose a bounty.
:two: Fill in the application form.
:three: E2B team assigns you to the bounty. (If you want to first discuss your approach or have questions, we always offer a call or chat on Discord).
:four: Submit the bounty and receive financial reward, which is usually in a range of hundreds of $, depending on technical complexity of the solution.
Submissions rules
Disclaimer: We don't automatically accept every submitted bounty. We need to review the technical quality and that the bounty is completed without need to make big fixes on our side.
:one: The solution has sufficient technical complexity (is not trivial), the code is working and has no bugs
:two: Solution is submitted as a PR to the E2B Cookbook repo (this doesn't apply to integrations to other frameworks/platforms, where you should follow the corresponding guidelines)
:three: Submission contains complete code and a simple gif/demo video that shows how your program works
:four: Bounty is submitted within the deadline, which is 2 weeks by default, and can be adjusted after discussion.
⭐️ READ FIRST:
Hello contributors,
After some consideration, we decided to stop the whole bounties program at this moment.
The reason is we are spending more time discussing the approach, giving advice, and fixing some results than we would spend without the bounty program.
Of course, we want to be fair and if you have been already assigned to some bounty and have already written the code for your bounty, let us know. But otherwise, if you haven't started, please don't.
We have experienced so many troubles with the bounties that we have to stop them at this moment for an unspecified amount of time. We are still open-source, open to contributions, and happy to promote E2B-related projects or include them in our Cookbook.
Thanks for understanding! 🙂
E2B Bounty Program
As an open-source product, we highly value community contributors who help us develop the best product. We provide financial rewards for the following bounties.
Active bounties
Assigned bounties
Completed bounties
Steps to complete a bounty
Disclaimer: Please try to only choose one bounty at a time and let us know if you gave up a bounty, so you don't block other users from choosing it. :one: Choose a bounty. :two: Fill in the application form. :three: E2B team assigns you to the bounty. (If you want to first discuss your approach or have questions, we always offer a call or chat on Discord). :four: Submit the bounty and receive financial reward, which is usually in a range of hundreds of $, depending on technical complexity of the solution.
Submissions rules
Disclaimer: We don't automatically accept every submitted bounty. We need to review the technical quality and that the bounty is completed without need to make big fixes on our side. :one: The solution has sufficient technical complexity (is not trivial), the code is working and has no bugs :two: Solution is submitted as a PR to the E2B Cookbook repo (this doesn't apply to integrations to other frameworks/platforms, where you should follow the corresponding guidelines) :three: Submission contains complete code and a simple gif/demo video that shows how your program works :four: Bounty is submitted within the deadline, which is 2 weeks by default, and can be adjusted after discussion.
Want to suggest a bounty that isn't listed?
Submit your own idea for a bounty at hello@e2b.dev.