AsyncAPI Bounty Program Summary - 2024

Viacheslav Turovskyi

Viacheslav Turovskyi

·3 min read

AsyncAPI Bounty Program

Since ancient times, sponsors furiously wanted to support Open Source. AsyncAPI addressed that need by starting to quarterly publish for Middle and Senior engineers a set of tasks that are currently in demand among AsyncAPI Maintainers and rewarding their completion using accumulated donated funds.

During one year of existence of the AsyncAPI Bounty Program:

  • 32 GitHub issues were resolved, 16 of which had complexity level Advanced;

  • 50+ PRs were merged in total;

  • 8000+ USD were paid out as rewards.

Benefits for FOSS Community

  • At least one issue was closed in a third-party project due to a fixed bug in AsyncAPI's software.

Benefits for AsyncAPI GitHub Organization

Thanks to the Bounty Program Participants, AsyncAPI got:

Benefits for AsyncAPI Maintainers

The Bounty Program gives AsyncAPI Maintainers the possibility:

  • To announce a financial reward for GitHub issues that are currently in demand by the maintained project or the AsyncAPI Initiative as a whole, on which AsyncAPI Maintainers can either work and get rewarded themselves or delegate those issues to regular contributors who have more time and/or the necessary expertise.

Benefits for Bounty Program Participants

Typical benefits of the Bounty Program for its Participants who are in the early stages of their career are:

  • Development of a better approach to the evaluation of issues (it's fun reading messages from two months ago saying, '1-2 weeks left'.)

  • First/differing working experience (fully asynchronous distributed teams are still rare, unlike partially asynchronous distributed ones.)

  • Development of the possibility to showcase to the potential employer real-world work not obscured by an NDA.

With all that said, join a finally sure way to directly sponsor (and get rewarded for) FOSS development.

Giggly thing as a finishing touch: PR for a bug due to which several lines were output incorrectly to the front end.

Co-authored-by: Lukasz Gornicki