search

gitcoinco / web

Grow Open Source
https://gitcoin.co
Other
1.78k stars 771 forks source link

As a developer I want to be able to crowdfund on an issue-per-issue bases through Bounties or Tips instead of Grants #7937

Open walidmujahid opened 3 years ago

walidmujahid commented 3 years ago

Discussion

I have had a Gitcoin Developer Grant in the last few Gitcoin Grant matching rounds and I have found that I have gained a lot of support, but the matching has consistantly been insignficant in comparison. Thus, this leads me to hypothesise that for the kind of Grant that I have, the crowdfunding aspects of Grants shows more success than the matching aspect.

Furthermore, I have found myself wanting a more straightforward way to show where the funds of my supporters are being used. So, I have to believe that crowdfunding on an issue-per-issue bases is something I would want. There were a couple initial solutions that I would be interested in discussing or testing and hopefully others would be interested in it as well.

Initially, one solution, I thought, was to ask for funding support through my Gitcoin profile and townsquare instead of a Grants page. In this method, I would claim an issue or multiple issues I would like to work on, then ask the Gitcoin community to send tips to help fund my work on them -of course, these would be big issues such involved feature requests that can take up to a week or more.

Then I thought to myself that there is already a system in place for this. Bounties. And in the past, Bounties used to have crowdfunding enabled. So, I have begun to take a liking to another solution which I would love to test that looks like the following:

Taking inspiration from the Gitcoin Requests idea at #671, we could perhaps design the process to not just incentivise developers to go out to find issues to report back to Gitcoin, but to find the issues and make them want to work on the issue themselves. The basic idea from #671 seems to already be intergated into Tribes at the moment, so we could work from there.

The flow I am seeing in my mind:

Finally, it would be interesting if each Tribe would have some kind of autonomous governance choices -not sure if that is the proper terminology- so that when these Suggested Crowdfunded Bounties are opened, the Tribe itself manages the bounties, and thus holds access to the fund, controls the release, becomes the arbitrators if an issue arrises, and could otherwise assign the funded bounty to someone else should the initial developer be incapable of completion -be it for a benign reason, or a bad actor.

I would very much love to start a discussion based on these ideas of mine. If the conclusion of such discussions is a feature spec, then I hereby declare that I wish to make claim to work on that myself.

walidmujahid commented 3 years ago

@PixelantDesign @owocki @vs77bb

gitcoinbot commented 3 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 1.2324 KSM (48.89 USD @ $39.67/KSM) attached to it as part of the sdsdfefd fund.

gitcoinbot commented 3 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 1.2324 KSM (48.79 USD @ $39.67/KSM) attached to this issue has been cancelled by the bounty submitter

owocki commented 3 years ago

And in the past, Bounties used to have crowdfunding enabled.

im a big fan of this idea, the big wrinkle in crowdfunding is custody of funds. we've ripped out standrardbounties (where funds used to be custodied) for simplicity reasons, so that kind of leaves a bit of a hole in the custody of funds for each particular bounty. if we can solve that (maybe the simple answer is just to have people commit the funds at the start, then follow up to payout later) then i think this is viable

walidmujahid commented 3 years ago

we've ripped out standrardbounties (where funds used to be custodied) for simplicity reasons

@owocki Gitcoin is not using standardbounties anymore? Or did I misunderstand? Could refer me to the parent issue or PR that you are referrring to?

owocki commented 3 years ago

thats right, we've removed standard bounties for all go-forward bounties (well eventually retire the legacy bounty support).

i dont have a PR link, sorry.

walidmujahid commented 3 years ago

thats right, we've removed standard bounties for all go-forward bounties

Okay, then I will start by reviewing the bounties section. I am out of date on that section of the codebase. I will try to come up with some kind of proposed solution for discussion.

owocki commented 3 years ago

I think allowing people to attest that they'll help fund the bounty (without actually staking) is the simplest solution to start with. Would love to collab on that.

‪On Mon, Nov 30, 2020 at 5:25 PM ‫Walid Mujahid وليد مجاهد‬‎ < notifications@github.com> wrote:‬

thats right, we've removed standard bounties for all go-forward bounties

Okay, then I will start by reviewing the bounties. I am out of date on that section of the codebase. I will try to come up with some kind of proposed solution for discussion.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gitcoinco/web/issues/7937#issuecomment-736136252, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD5PCNUI4SUVYU3XQ2OLUDSSQZXZANCNFSM4UB37RZA .

--

@owocki http://www.twitter.com/owocki

gitcoin is live and has generated over $7.3mm for Open Source Software - see our results https://gitcoin.co/results

walidmujahid commented 3 years ago

@owocki That does sound like a simple solution to start out with. Could this work as the following?

  1. User suggests a bounty through a tribe and selects checkbox to indicate they have claimed the issue.
  2. A list of bounty suggestions is shown publicly on the tribe and perhaps a user's suggestion is shown on their own profiles as well.
  3. Funders click a button to indicate they have funds that they wish to pay forth upon a bounty's completion or another signal.
  4. Bounty is complete or another signal goes off. 4.5. Funders are essentially directed through the Tip flow -possibly modified- where they send the money to the person who finished the bounty.

Thus the funds never left the hands of the people who attested they had said funds.

owocki commented 3 years ago

what i was envisioning is something more like this

  1. when a bounty is open or started, anyone can click 'add funds' and add a funding committment. funds never change hands, but the funding total is adjusted up top + a new activity feed item is added.
  2. once the work is submitted, those ppl get an email saying the bounty was submitted - just like the funder does.
  3. they can 'payout bounty' just like the funder can.
walidmujahid commented 3 years ago

So, I will be working on making this possible @owocki. Getting a crowdfunding mechanism working for grants again would really help for the kind of experimentation I want to do by moving my specific grant I mentioned away from grants. and making crowdfunding an issue-per-issue matter.

I've been having some local machine troubles over the past week or, but I have settled the matters. Over the next few days, I want go over and write a small spec for myself to share here for any feedback. How you envision it is straightforward and simple.

As part of the funding process, should there be a way to verify that the funders 'currently' have the funds they are contributing to the bounty?

owocki commented 3 years ago

As part of the funding process, should there be a way to verify that the funders 'currently' have the funds they are contributing to the bounty?

i think id err on the side of simplicity here.

also cc @Kweiss who im working with to help figure out how to harness community enthusiasm + talent to advance the product

walidmujahid commented 3 years ago

i think id err on the side of simplicity here.

Makes sense.