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

### Discussion

[comment]: # (What conversation would you like to facilitate?)

I have had a [Gitcoin Developer Grant ](https://gitcoin.co/grants/467/gitcoin-developer-grant-walid-mujahid) 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:

- A developer goes through the issues on their favourite project, finds the one they see themselves working on, starts a discussion, makes a claim on the issue, and anything else in line with general open source ettiqutte.
- Once the developer claims the issue, they go to their Gitcoin Tribe, on the "Suggest a Bounty" form, they select a checkbox to indicate that they would be working on the bounty themselves.
- Once the form is submitted, there should a new section on the Tribes page similar to Hackathon Projects that list each of the Suggested Bounties, and the developer who claimed the issue. This page would enable Tribe members to easily send funds/Tips and the first Tip would open up the Bounty with crowdfunding enabled, and each sequential tip is simply part of the crowdfund.

I am imagining here a progress bar for each of these listed bounties to show how far it has until it reaches the funding goal.

I am also imagining that for each of these bounties, it would be up to the developer to advertise and market as they might do for a Grant.

It is also here that I can also imagine the mini-CLR being repurposed. Where, instead of individual developers opening up Developer Grants for a project or multiple projects, a Tribe would each open up a Grant as the project itself, then the Tribe could decide to allocate funds to an in-Tribe mini-CLR in which for each round, the Tips given to each of these crowdfunding bounties would be matched.

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.