Taking a retrospective look on bounties at status from the start with Status Open Bounty and now using Gitcoin as our active tool, we need a way to allow permission-less bounty posting for core contributors that want to assign an issue to a bounty but also an understanding of what we’ve done so far and what has worked vs. what hasn’t.
- Gitcoin campaign recently worked very well in terms of active contribution with 19 bounties completed so far
- Defined issues with reasonable scope and well thought out funding scheme as well as marketing
- Growing list of developers contributing to embark outside of core team
- Using DAI as a stable-coin helped in terms of bounties taking much longer and fluctuations in bounty value.
- Pushing for 60 bounties over one month was a lofty goal and unreachable for a small team
- Bottleneck exists ad naesuem for managing and handling bounties eg. myself and @cryptowanderer
- Ad-hoc bounties get outdated or even worse sometimes don’t work
Based on learnings so far I’m proposing that each active team that would like to “bounty the world” take on a small working group of 2-4 dedicated members who define their responsibility (Bounty deployer, payout guy, etc.)to the cause to start a focused campaign on a set of issues they’d like to see bountied and scope out the issues for the particular set of problem / features they’d like implemented.
A really good piece of feedback that @iurimatias gave the other day is that we should consider bounties as a bit of a soft-introduction or even internship into the codebase that particular individual is working on. We should take all the feedback we get to make our code-bases easier for outside contribution through the learnings of bounties.
I believe that each new bounty campaign would require at least:
- Set of 4-5 issues max per initiative to exist with tags to define the bounty and proper scope for newcomer for each specific campaign, and completed before starting a new campaign with the existing bounty team.
- A spreadsheet like the funding scheme one above to define the scope of DAI / SNT involved
- Defined team members for each set of bounties to handle and confirming developer support is offered for the subset of issues.
- Work with finance to confirm address used for profile and funding for the specific agenda.
I’d be very happy to help anyone in getting setup with Gitcoin in terms of how it actually works for funding, deploying etc. and opening this up for further discussion and input on if everyone thinks this makes sense or any other comments; especially from @oskarth and others who have been interested in opening bounties on the desktop, nim team etc.