Gitcoin is a community of thousands of BUIDLers that are looking for projects to work on. Because of this strong community of Ethereum developers looking to build skills, develop relationships, and earn some ETH, there has never been a higher ROI time to delegate work in Open Source Software to the crowd.
Gitcoin is a community of thousands of BUIDLers that are looking for projects to work on.
Because of this strong community of Ethereum developers looking to build skills, develop relationships, and earn some ETH, there has never been a higher ROI time to delegate work in Open Source Software to the crowd.
But not every Github Issue is a good candidate for a bounty. If you are an OSS repo maintainer, and want to maximize our Return on Investment (ROI), you might spend some time thinking about:
Return — The value received for delegating work to someone else. This can be:
Investment — The resources put into delegating the work to someone else. This can be:
Using Gitcoin, We’ve seen OSS repo owners:
So how do we leverage incentivization mechanics to accelerate OSS?
In order to leverage Gitcoin’s crowd-sourced development incentivization tools, lets talk about some best practices for maximizing ROI of the tool:
In our experience, the following are great candidates for bounties:
In our experience, the following are not good candidates for bounties:
Here are some best practices we’ve seen from some of our 2018 Case Studies:
At surface level, you might think that bounties are a transaction. That might be true in some cases, but we’ve found that some of highest ROI bounties that we’ve seen thus far on Gitcoin are also the highest empathy bounties.
This means that, from the funder side, you can start off on the right foot if you:
It also means that from the development side, you can expect:
Some of this is Software Management 101, so if you’re got a background in Agile Stories, it might be worth skipping this part.
Here are some features we’ve seen of great specifications:
This is an Open Source Software Best Practice, and it also happens to be a OSS Incentivization Best Practice too.
We’ve found that all of the above really help:
For more inspiration in this area, check out this README.md template.
In the past, we’ve seen new features (especially those with qualitative aspects to them) go through a process like this:
If you’ve saved some budget for tipping a contributor or for follow-on bounties, that’s a great way to keep up momentum on your project.
If the above seems like a lot to remember, do not worry! Rome was not built in a day, and building an OSS community won’t happen in a day either.
Take the first step today and put a bounty on Gitcoin. If you start small, stay reasonable, and are responsive — thats a great place to begin.