smart_contracts
smart_contracts copied to clipboard
gitcoinco
more than one bounty per github issue
Requirements
- right now, gitcoin bounties have a 1:1 relationship with a github issue
- update so that gitcoin bounties have a n:1 relationship with a github issue
- submit a PR against web repo
- submit a PR against smart_contracts repo
IMO instead of binding bounties to one github issue, it's more about how the submitter to properly separate issues for bounty.
Ex: to introduce a new UI or a new mechanism, it could be separated to UX bug and Eng bug and submit separate bounties for them. A smaller and concrete issue also helps estimate the required time and the difficulty.
Things I see missing from gitcoin now is ability for many people to pool fund for an issue, which will promote a project to develop faster to where its community/user wants.
Does n:1 relation mean if someone merge the PR, they will get all n of the bounties? If so then it will solve the pooling problem.
@mbeylin has done some thought on this. it is likely ill integrate his work ( https://github.com/ConsenSys/StandardBounties/ ) soon.
@owocki Hi Kevin, I picked this one up from gitcoin.co and I'm curious if you wanted to keep this a simple enhancement (n:1 contracts/issues), or if you want to overhaul the bounty system by integrating ConsenSys/StandardBounties? Perhaps we should chunk this out into phases, phase 1 being the small change to add functionality in the short term, then a separate phase or phases to refactor the bounty system to implement StandardBounties.
you want to overhaul the bounty system by integrating ConsenSys/StandardBounties?
This, please. Youll probably want to coordinate with the claimee of https://github.com/gitcoinco/web/pull/48
Gotcha. If the claimee doesn't get back to you, I'd be glad to pick that one up and knock them both out at the same time.
no word from him. hit me up on gitcoin.co/slack and lets chat more about this
The funding of 0.06 ETH (47.81 USD) attached has been claimed by @maxwolff.
@maxwolff, please leave a comment to let the funder (@owocki) and the other parties involved your implementation plan. If you don't leave a comment, the funder may expire your claim at their discretion.
- Learn more on the gitcoin issue page
- Questions? Get help on the Gitcoin Slack
- $12364.02 more Funded OSS Work Available at: https://gitcoin.co/explorer
Good to see this work on StandardBounty. Apart from this, shouldn't multiple bounties per issue just 'increase' the bounty? Otherwise I think it is preferable to have a new issue for this. If the question is who would decide on payout, maybe there could be voting so that all bounty creators have a vote and depending on that the claimant can claim all or at least some of the bounty depending on how voting works. Or maybe these would be kept on-chain as multiple bounties, but at least for the user I think it is preferable to see them as one. (esp as seeing that with StandardBounty this or maybe even generally chain-code it is necessary so that bounties can be tied to issuers)
