Web: bounty: increase timeline + request increase of funds

[thelostone-mc]

Why Is this Needed?

Feature/Scope creep happens in every project. It’s unavoidable.

Would be nice if gitcoin would let me :

• request for an increase in timeline as a bounty hunter and provide the ability to ask for a raise of bounty to the owner with justification
• ability to increase the timeline as a bounty issuer ?

[mbeacom]

Scope creep... or progressive elaboration?! 🤔

Jokes aside, a formal action for requesting the funder to "add contribution" to the bounty could make sense and our ability to reflect changes to the scope of a bounty could be a good idea if we plan to aggregate bounty turnaround data.

[owocki]

request for an increase in timeline as a bounty hunter and provide the ability to ask for a raise of bounty to the owner with justification

We actually just released the ability for a funder to increase the amount of funds in an issue (the butotn will only appear if ur the funder though). Theres no current way for the bounty hunter to formally request more funds though.

ability to increase the timeline as a bounty issuer ?

We put in a fix so that the expiration date isn't a hard stop anymore.. Now people can pay out after the expiration date. Not sure if thats what you were looking for or not!?

Scope creep... or progressive elaboration?! 🤔

lol

[owocki]

if this is a priority, i think we should define a product spec for it.

[thelostone-mc]

I believe we should
We've already encounters where folks weren't able to submit expired bounties.

And increase payout is not something which everyone would be comfortable asking , having a button => sort of makes the user understand it's okay to request for more if they have a valid justification

[thelostone-mc]

I'll do a rough prototype via popup box ( like the start work ) to get things rolling ?

[mkosowsk]

This is an interesting topic and I've had some recent discussions about it with colleagues both at my company and outside.

Here's an article that addresses handling unplanned work during a sprint and various ways to deal with it which I actually think helps inform the discussion of scope creep for an issue on Gitcoin: https://baranoshnik.com/strategies-for-handling-unplanned-work-during-sprint/

Here are the quick patches for scope creep and how they relate to this topic:

1. Just absorb it- I think this is the method that is being advocated here, just absorb additional requests from the Funder into the ticket and increase the funding amount so the Contributor is being compensated for doing more than the initial contract. I agree with increasing the funding to account for more work but think this method can get a bit messy with issues. What if the original contributor doesn't want to do the additional work?
2. Break up and carry over- I like this one the best. If new work comes in for an issue that is significant enough to warrant additional compensation for a Contributor, I think it in most cases simply warrants a new issue. This is the cleanest to me, the previous Contributor could hop on the new issue or let it go to the crowd
3. Replace- replace some of the work on the ticket that hasn't been done with new scope without an adjustment in compensation. Would advocate use of this sparingly, it's altering the original contract.
4. Plan a buffer- the Funder hasn't fully scoped out the ticket but has enough for the Contributor to get started on and will add more details later. Would also say use this sparingly, think this often means that the Funder hasn't put enough thought into the ticket.

I think option no. 1 is far and away the cleanest but could see option no. 2 being used to good effect on the Gitcoin platform. I would caution against Funders using nos. 2 and 3.

[mkosowsk]

@thelostone-mc I definitely agree with the increase in timeline but am unsure about a button to ask for more funds, think it may introduce some wonkiness into the platform. Think it may have introduce some moral hazard into having the Funders being okay without fulling scoping their tickets to start 🤔

Will be interested to see the data on use of the button if/when it's added! 👍🏻

[kuhnchris]

@thelostone-mc did you ever come around to do the prototype?