Web: BUILD Reserve Bounties Improvements

[thelostone-mc]

Description

As of now, a funder can come reserve a bounty for a user X while creating a bounty /new.
The created bounty is reserved for X for upto 72 hours during which only he can start work on it.
After that -> the issue is no longer reserved and is open to everyone to work on.

PR where it was built out: https://github.com/gitcoinco/web/pull/2950

Issues

• Right now, a reserved issue pops up into the /explorer for everyone even though they cannot start work on it.
• We have a simple check to determine if a reserved issue is open to the public, this means even after 72 hours expire -> we maintain who the issue was reserved for.
  If the grant owner edits the issue details -> the checks kick in and the issue is reserved again (which should not happen )
• There are instances where the funder may want the reserved issue to go beyond 72 hours (3 days) and that doesn't happen at the moment.

PR should Fix

• Introduce input on the same row as reserved for in /new which asks
  Release to the public after X with drop down with options after 3 days, after a week, keep reserved which map to corresponding hours
• Introduce a new state -> reserved.
• Any bounty created which is reserved for a user -> would be in this newly created state
• If the reserved bounty is started by user -> issue would transition to Work Started
• If the bounty is no longer reserved (aka reserved time elapses) remove the reserved for User from db & transition issue to Open State
• Add new state to the filter on the explorer to enable logged in user to see bounties reserved for them
• ensure reserved bounty appears on explorer only to the users who have an active reservation
• provide and button on the issue detail to force release the issue if needed. (Aka update dp to remove the reservedFor Data )

Discussions : https://github.com/gitcoinco/web/issues/3502

Note

This task would undergo PR reviews and feedback would have to be worked upon

[PixelantDesign]

If the funder has reserved it for a contributor, we would undo the reserved feature after 72 hours?

[thelostone-mc]

@PixelantDesign Yes, the code snippet which does that is mentioned in the description ^_^

[PixelantDesign]

My recommendation is to add a checkbox and let the user opt into the 72 hour realse.... instead of make assumptions that users would want it undone when they’ve clearly set it to reserve.

[thelostone-mc]

@PixelantDesign Updated the ticket. Freezing the scope for this ticket. 🙌

[gitcoinbot]

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

---

__This issue now has a funding of 0.45 ETH (53.86 USD @ $119.69/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  
  
  
  • Want to chip in? Add your own contribution here.
  
  
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  
  
  • $40,214.39 more funded OSS Work available on the Gitcoin Issue Explorer
  
  

[gitcoinbot]

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

---

__Workers have applied to start work__.

These users each claimed they can complete the work by 4 weeks, 1 day from now.
Please review their action plans below:

1) usmanmuhd has applied to start work _(Funders only: approve worker | reject worker)_.

WIll be doing this as discussed with @thelostone-mc before.

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[PixelantDesign]

Yes and contributors who cannot apply to work on this should not get notifications of this new issue.

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[thelostone-mc]

@usmanmuhd could we have the PR up for this / need help from my side ?

[gitcoinbot]

@usmanmuhd Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[thelostone-mc]

@usmanmuhd could we get a WIP PR opened up today ? I would like this in by this week

[usmanmuhd]

Yeah sure. Today evening it'll be done.

[thelostone-mc]

@usmanmuhd still waiting on the PR 😓

[gitcoinbot]

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

---

__Workers have applied to start work__.

These users each claimed they can complete the work by 2 weeks, 3 days from now.
Please review their action plans below:

1) satyamakgec has applied to start work _(Funders only: approve worker | reject worker)_.

1. Code setup
2. Understand the Code
3. Finding the pinpoint file
4. Implement the changes
5. Fix the test cases

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

@satyamakgec Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@satyamakgec Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[satyamakgec]

@gitcoinbot yes I am working on the issue.

[gitcoinbot]

@satyamakgec Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@satyamakgec Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

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

---

@satyamakgec due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

• [x] reminder (3 days)
• [x] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

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

---

@satyamakgec due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

• [x] reminder (3 days)
• [x] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

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

---

__The funding of this issue was increased to 0.7 ETH (178.87 USD @ $255.53/ETH) .__

• If you want to claim the bounty you can do so here
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $84,643.67 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@rafalkowalski Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[PixelantDesign]

@rafalkowalski could you provide an update on this?

[gitcoinbot]

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

---

__Work has been started__.

These users each claimed they can complete the work by 8 hours from now.
Please review their action plans below:

1) vince0656 has been approved to start work.

Hi there,

Having worked on Gitcoin before and added new bounty functionality, I feel like I could give this a good shot. I will aim to fix the issues listed in the description which includes:
-Release to public feature
-New state of reserved
-New bounties created with reservations are marked as reserved
-Transition to work started for reserved user that starts work
-Transition to open state if reserved user doesn't start working on issue after X time
-New filter to see bounties reserved for users

Any questions, let me know - thanks!

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

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

---

__The funding of this issue was increased to 0.98 ETH (180.54 USD @ $184.22/ETH) .__

• If you want to claim the bounty you can do so here
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $138,841.45 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

@vince0656 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[vince0656]

Hi there,

I'm still working on this.

Thanks very much,
Vincent

[vince0656]

Hi there,

I'm still working on this.

Thanks very much,
Vincent

[gitcoinbot]

@vince0656 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[vince0656]

Hi there,

I'm still working on this. Coming to the end now

Thanks very much,
Vincent

[gitcoinbot]

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

---

__Work for 0.98 ETH (166.4 USD @ $169.79/ETH) has been submitted by__:

1. @vince0656

@PixelantDesign please take a look at the submitted work:

• PR by @vince0656

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $133,098.99 more funded OSS Work available on the Gitcoin Issue Explorer

[thelostone-mc]

@PixelantDesign we are good for payout !

[vince0656]

@PixelantDesign @thelostone-mc @octavioamu Sorry to bug but any idea as to when this will be paid out? PR merged into master is: #5066

Thanks in advance

[owocki]

looks like @PixelantDesign owns this; and she just went out on maternity leave!

i can pay you out of my funds if you want ... then when @PixelantDesign gets back we can cancel the bounty

[vince0656]

@owocki yes please. Could you pay me and then cancel the bounty when @PixelantDesign is back. Thanks

[vince0656]

@owocki any update on the payout? Thanks in advance

[owocki]

sorry; devcon broke me inbox! paying out now

[gitcoinbot]

⚡️ A tip worth 0.98000 ETH (182.57 USD @ $186.3/ETH) has been granted to @vince0656 for this issue from @owocki. ⚡️

Nice work @vince0656! Your tip has automatically been deposited in the ETH address we have on file.

• $150189.58 in Funded OSS Work Available at: https://gitcoin.co/explorer
• Incentivize contributions to your repo: Send a Tip or Fund a PR
• No Email? Get help on the Gitcoin Slack

[owocki]

@PixelantDesign when ur back from leave; pls cancel the bounty (do not payout; i already paid!)