Convert accepted Proposals to Bounties

[mktcode]

The idea is to create a workflow for discussing upcoming issues and converting them into an issue with a bounty attached in the end. If a project has "reserves" on Octobay, bounties could even be created automatically when a proposal gets accepted and fulfills certain criteria necessary for the process. Any other ideas?

[JasperTimm]

I really like this concept and I think it's the thing that will make Octobay really special. It'll be so cool to see it working in action, even on the testnet. I'm looking forward to implementing it.

If I understand right, at the moment there's no 'fixed amount' for the bounty on an issue right? It's simply the combined amount of donations at any point in time, until someone decides to pick it up? (Separately: do we have a system that somehow lists those user's that are currently considered to be working on an issue? Are we handling that via Github's issue assignment?)

So automatically creating an issue from a proposal seems like a no-brainer, at which point anyone can start depositing to it right? Making it an official bounty (presumably there's no limitation on what issues you can deposit to). I suppose the only difference now is that we would somehow automatically deposit funds onto the issue from the organisations coffers. That seems like a good plan too.

I think the sticking issue might be here that there's going to be an issue on the amount assigned to the bounty, as it's directly correlated with the amount of work it takes and developers will have different opinions on that. My first thought is back to scrum poker for estimates, hehe. But this should probably be resolved before proposal creation right? As it would be silly for people to knock down a proposal based on a disagreement for the estimate. Perhaps the frontend can somehow allow people to vote (without results) on the estimate for a discussion before it goes to proposal phase?

[mktcode]

It's simply the combined amount of donations at any point in time, until someone decides to pick it up?

Yes. But if that starts to make more trouble than it adds utility, we need to reconsider that. I can imagine it turns out that simply nobody except the project maintainers fund issues and outside supporters simply donate to a project and those donations can then maybe only be released through bounties.

do we have a system that somehow lists those user's that are currently considered to be working on an issue? Are we handling that via Github's issue assignment?

Nope, you can only assign people from your org to an issue, afaik. The connection is made through manual linking:

Or through a keyword in the pull request's comment: https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

We then list those pull requests here in the UI:

presumably there's no limitation on what issues you can deposit to

Exactly. Anyone can deposit on any issue at any time. I think you already implemented some logic for "locking" an issue after a bounty was withdrawn.

I suppose the only difference now is that we would somehow automatically deposit funds onto the issue from the organisations coffers.

Yes. One more thing we were thinking about was "Bounty Promises" where you can set up a bounty and set an amount without the need to actually deposit it.

developers will have different opinions on that. My first thought is back to scrum poker for estimates, hehe. But this should probably be resolved before proposal creation right?

That is exactly what we want to solve with this I'd say. Finding the "right" amount for a bounty by letting your already existing contributors, that hold your gov token, decide on it and then automatically setting up the bounty, from the project's reserves. Maybe there needs to be a special form of "proposal" or voting for that... a "Bounty Proposal" so to say. This thing definitely needs a lot of thinking and experimenting. :D

[mktcode]

I think we need to define what types of proposals and decision making we want to support here. Usually those governance system directly affect properties of the project, like Uniswap's fees. Not sure how exactly they are handling this but our governance system is for now completely decoupled from any project parameters. Maybe the best would be to really ONLY focus on bounty amounts.

[JasperTimm]

Nope, you can only assign people from your org to an issue, afaik. The connection is made through manual linking:

Or through a keyword in the pull request's comment: https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

I guess my thought then is when one person picks up the bounty, do we have a system to let people know that someone is already working on it?

That is exactly what we want to solve with this I'd say. Finding the "right" amount for a bounty by letting your already existing contributors, that hold your gov token, decide on it and then automatically setting up the bounty, from the project's reserves. Maybe there needs to be a special form of "proposal" or voting for that... a "Bounty Proposal" so to say. This thing definitely needs a lot of thinking and experimenting. :D

Yeah, I think a governance system for the effort estimates (i.e. bounty amounts) would be good. It's not really supported at the moment though as when people vote they can only say yay or nay, not give an amount. Maybe we can add an issue to implement this? So it grabs the vote weighted average of everyones given estimate?

[mktcode]

I guess my thought then is when one person picks up the bounty, do we have a system to let people know that someone is already working on it?

Maybe the pull request mechanic can be used for that as well. That was what I wanted to say. You can submit a draft PR right after the first commit. Depends a bit on the scope of the issue I guess. I also see this as a nice utility for our own Octobay token someday. Devs could pay a very tiny little fee to mark a bounty as "theirs". Maybe even something like "buying" a bounty or "bidding" on it.

Maybe we can add an issue to implement this? So it grabs the vote weighted average of everyones given estimate?

Absolutely. I'll think about this now and prepare an issue.

[mktcode]

I just read now that the "convert discussion to issue" feature was removed due to a bug.

community/community#2861 (reply in thread)

There's a "Reference in new issue" feature thogh.

But that is not really helpful... Doesn't create an actual connection between the two.

But the support for bringing back the Discussion -> Issue feature is there, so I hope it will be back soon.

[mktcode]

Idea for voting on the size of a bounty that emerges from a discussion:

Projects can have reserve funds on Octobay, from which bounties can be created automatically.
A proposal can have a budget, set by the maintainer (or anyone with the required permission/NFT), limited by the project's reserves.
This budget gets "locked" as long as the proposal is active. It get's "unlocked" if the proposal gets rejected.
Votes FOR the proposal can also suggest an amount <= the proposal's budget.
If the proposal gets accepted, an issue is created (from the discussion or through a bot) and the vote weighted average amount is being transferred to it. Any left over budget is unlocked and goes back to the project's reserves.

The step of assigning a budget to a proposal could be optional or maybe it's not necessary/helpful at all. The possible amount for the bounty could be just limited by the projects reserves.

A discussion can currently not be converted to an issue anymore due to a bug. (community/community#2861 (reply in thread))
Although it looks like this feature will come back, a fallback solution would be to create issues with a GitHub bot.

[gal1806]

good