Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
### User Story
As a funder, I would like an updated variable pricing scheme on how to price my issue on Gitcoin based on a calculation of hourly rates and its derived success rate. In order for this to work, we need to add an input field for hours estimation to the pricing section of the [funder page](https://gitcoin.co/funding/new).
### Why Is this Needed
Currently, funders can price the issue based on the total price, but that doesn't give any other information on whether or not that hourly rate is sufficient for their issue to get completed. Adding an input field for hours estimation allows for an hourly rate calculation, which translates to a predicted bounty success rate.
### Current Behavior
Currently on the pricing section of the [funder page](https://gitcoin.co/funding/new), when the funder types in the total price paid out for the issue, a pop up below tells them what the bounty hunter would earn at a $40/$80/$120 rate, but that doesn't translate meaningfully to whether or not the funder should increase or decrease the price.
As an example to help you understand what this means, let's say I'm funding a beginner bounty on a feature improvement that would take several hours to complete. If I fund it with 1 ETH, it's about $300 bucks - the pop up rates tell me it's 7 hrs @ $40 (69% success rate), 4 hrs @ $80 (83% success rate),or 2 hrs @ $120 (95% success rate). If instead I fund it with 2 ETH, the success rates stay the same, but the hourly rates change(7 to 14, 4 to 7, 2 to 5, respectively). The problem is that changing the price changes the hourly rate estimations, not the success rates. The funder still has to do alot of mental math and read the [Medium article](https://medium.com/gitcoin/tutorial-how-to-price-work-on-gitcoin-49bafcdd201e) to get to a recommendation on whether they should increase or decrease the pricing bracket.
![screen shot 2018-08-28 at 09 51 52](https://user-images.githubusercontent.com/7516920/44744936-26b80300-aabb-11e8-80fb-b29007c5404e.png)
### Background & Analytics
Based on Gitcoin data, an analysis was done that yielded a relationship:
**(0.002 x Hourly Rate) + 0.65 = Predicted Success Rate**
This gives us the ability to estimate success percentages by the hourly rate, at the granularity of a dollar (for every $ increase, we have a 0.2% percentage point increase in success rate).
### Suggested Solution
We want to add an "estimated hours" input field to the funder page (example below):
![screen shot 2018-08-28 at 09 51 52 3](https://user-images.githubusercontent.com/7516920/44745569-efe2ec80-aabc-11e8-90c4-00c9188b03bb.png)
### Definition of Done
1. Add an "estimated hours" input field to the pricing section of the funder form.
2. Design an intuitive layout of the elements and how they appear to ensure that the relationship between the USD input and hours estimated input is clear (for example, make it obvious that 1 ETH = $289 USD divided by 6 estimated hours = an hourly rate of $48/hour, which correlates to a 75% success rate).
Elements to consider:
* Denominations input:
* Amount input:
* USD input and where it appears when the denominations input and the amount input are valid:
* Hours estimation input
* Pricing guideline input and where it appears when the denominations input, amount input, USD input, and hours estimation input are valid: