Open mkosowsk opened 6 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 0.15 ETH (84.18 USD @ $561.23/ETH) attached to it.
@oogetyboogety Just to confirm with @mkosowsk, looks like this one may be reserved for @jlas. Is that right, Mitch?
However, if you do decide to work this bounty and make a meaningful submission, Gitcoin Core will absolutely tip you for the .15ETH.
Thanks @vs77bb, I just saw that it's for @jlas. Definitely interested, once @jlas is completed, I may be able to help visualize the results. I'll let him get started first though and look for a couple other issues I can try
@vs77bb yep, that's correct I'm currently working closely with @jlas on this one :)
however, @oogetyboogety let's keep in touch! will ping you after initial results with @jlas
@jlas might snagging this one on Gitcoin by clicking 'Start Work'?
@mkosowsk is this issue still reserved, if it is not i will start working on it.
@nanspro thanks for your interest but goalposts shifted on this one a bit so cancelled the bounty :)
Issue Status: 1. Open 2. Cancelled
The funding of 0.15 ETH (69.8 USD @ $465.36/ETH) attached to this issue has been cancelled by the bounty submitter
Note: this issue is reserved for the excellent @jlas :)
User Story
As a PM managing ETHPrize bounties I want to perform data analysis on the current 82 (and counting!) developer interviews So that I can know with confidence the biggest developer pain points to focus efforts on the right areas for the next bounties.
Background
ETHPrize is a community research and bounty project that identifies the most critical issues facing the Ethereum ecosystem and organizes bounties to solve them. The current two bounties are $250,000 USD each and cover an Ethereum Package Manager and an Open Source Block Explorer.
82 (and counting!) interviews have been conducted in the space to determine where to focus efforts next. It would be great to perform data analysis on these interviews to help focus efforts.
Acceptance Criteria
Technical Details
Per @jlas: