Volunteers to run official AsyncAPI Bounty program

[derberg]

So we did a trial of the program: https://github.com/orgs/asyncapi/discussions/541#discussioncomment-5462792
And it turned out to be a great success: https://www.asyncapi.com/blog/august-2023#asyncapi-bounty-program-trial

Some initial rules played well, and we also have some feedback for improvement.

Goal:

• To setup official AsyncAPI Bounty based on what we learned during trial
• Assign $20k annual budget, or a set of $5k quarter budgets (so we do not run out of credits in one run and make it a program that runs through out the whole year)

---

Is there anyone among @asyncapi/tsc_members or @asyncapi/ambassadors who'd like to help and run the program?

Duties:

• document the whole program (like rules, and stuff like that)
• communicate the status with the community
• run the program by announcing it, coordinating with maintainers and contributors that participate in it and completing it
• being a go-to-person that knows if bounty issue was completed and can be payed

So yeah, we need someone who will feel responsible for the program.

It is really hard to say how much time such role will require, for sure documenting the program and the process with take few hours
, but this is a one time commitment.

[imabp]

@derberg I can volunteer for this.
During the launch, I have already documented some sections, and created a video 5 months ago.

https://www.youtube.com/watch?v=bAfcoQKTHEQ&ab_channel=AbirPal

[aeworxet]

How many Bounty Issues of what types are planned to be kicked off every quarter?
Are there going to be changes in complexity levels and costs?

[derberg]

Are there going to be changes in complexity levels and costs

I think that what we had during trial should stay as it worked well

How many Bounty Issues of what types are planned to be kicked off every quarter?

$5k per quarter - hard to say how many issues, there are different values, and I don't think we should have hard requirement like 5 easy and 5 advanced or something like that

[aeworxet]

I think that what we had during trial should stay as it worked well
I don't think we should have hard requirement like 5 easy and 5 advanced or something like that

This implies from 13 to 25

((12 * 400) + (1 * 200)) || (25 * 200)

Bounty Issues per quarter?

[derberg]

which sounds good for starter I think, looking at the amount of maintainers we have that can do reviews, or tasks on their own. Of we get more sponsors, we can always increase

[Mayaleeeee]

I'd love to volunteer for this as well. However, I noticed that Abir has already shown interest. Please let me know how I can assist.

@derberg, could you please clarify what the "one-time commitment" entails?.

[derberg]

for sure documenting the program and the process with take few hours, but this is a one time commitment.

I mean that basing on my assumption the first and most consuming things, a one time commitment job, will be documenting the program and process. Then running the program should not be that time consuming I think

[aeworxet]

I will be third in line then.

[derberg]

@imabp @Mayaleeeee @aeworxet

what do you think folks, if instead of picking one person, and figuring what should be the decision process - we actually form a "bounty team" - so all 3 of you are involved, and share workload and responsibilities?

[imabp]

I agree on giving the program ownership to @aeworxet. As @aeworxet is quite active in the program.
I will be overviewing his decisions and ping in, when things are not going in right direction.

Thanks @derberg for pulling this up and also for understanding, on my bandwidth availability.

[Mayaleeeee]

Yes, please. @derberg
I agree with giving @aeworxet taking complete ownership of the project.
Thank you.

[derberg]

Thanks @imabp and @Mayaleeeee for clear statements.

For me it means that now @aeworxet is the Bounty Program lead just like Barbanio is leading of Ambassador Program. If in future program grows and gets more complicated, we can think on extending the group but for now looks like one person approach is best.

@thulieblack fyi

@aeworxet I guess we should remove @asyncapi/bounty_team ? or is it still valid?

[thulieblack]

Hey,

Yeah, I totally agree with @aeworxet being the Bounty Program Owner/Lead.

Since we are still in the early stages of the program, and there isn't much to delegate, it will be best if we have one person fully focus on the program.

[aeworxet]

I guess we should remove @asyncapi/bounty_team ? or is it still valid?

The @asyncapi/bounty_team turns 'user management' into 'group management' so it should be there for now.

[aeworxet]

We love 'ready-fire-aim' mode, so we are announcing 2023-Q4 Bounty Program Round while Bounty Program Rules are still in beta state as a PR.
They won't already change much, mostly only clarifications and paraphrases will be added, but perhaps you will have comments on topics that were overlooked or forgotten.

That said, let the production testing of the Bounty Program begin.

[ayushnau]

I would consider we need the following:

* a communication channel (something like 'XX_bounty_program' channel in Slack, and actually read it not only be a member of it)

* Bounty Issue tracking software (in future might be a part of website at `https://bounty.asyncapi.com` with gathering info on issues through GitHub API, and closing Bounty Issues on getting via webhook payload object for `pull_request` event with `action: closed`/`merged: true`, but for now a simple shared spreadsheet is fine)

* Git repository with Bounty Program rules in Markdown (with work going on in some 'dev' branch and 'main' containing only squashed commit with the ready doc, @thulieblack do you have something from Trial already?)

* maintain ban list to keep tracking of guys [like](https://github.com/asyncapi/website/issues/1425) [this](https://github.com/asyncapi/conference-website/issues/163) (who first ask to assign the issue to them and _only then_ start to think on the task, understand they can't do it and silently drop)

* kick off 13 to 25 Bounty Issues for Q4 and publish list in the communication channel

Do you have objections/proposals?

Please react fast to this message because @derberg most probably will not work tomorrow and Oct 1 is as soon as Sunday.

Hi @aeworxet I saw that we need to have a software for tracking bounties. I found that interesting and would like work on this. as a bounty program. I can dm you complete roadmap on how I would go about this. thnks.

[aeworxet]

Hey @ayushnau
Thank you for your desire to contribute to the Bounty Program.
Unfortunately there are no plans for dedicated software to track Bounty Issues for now, because the process is predicted (for now) to be kept gravely simple:

• indication of status with GitHub labels,
• filtering of issues by labels using GitHub's search tool,
• utilizing a GitHub bot to add/remove said labels with time trigger.

So all tracking process comes down to several GET requests in browser.

I hope you will be able to make full use of your experience during the Bounty Program rounds though.

[AyushNautiyalDeveloper]

@aeworxet how do we apply for bounty program.

[aeworxet]

When submitted GitHub issues receive label bounty it means they participate in the Bounty Program round. You look through them, choose one or two you are SURE you can complete, with respect to the schedule (you can check with the maintainer of the repo ahead of time, if your future approach is correct), after that ask in the issue's comments to assign the issue to you (for example with phrase 'I would like to work on this issue') and meet all milestones for the issue's complexity level.
After the issue is closed, apply for reward.
Future bugs related to your functionality you fix for free.

[derberg]

Closing as discussion is over and the bounty under @aeworxet coordination works like a charm