Web: Need to be able to stop work bounties as the funder

Created on 18 Feb 2018 · 20Comments · Source: gitcoinco/web

Description

Either the issuer of the bounty, or the people who have submitted their intention to complete it, should be able to un-claim the bounty so it goes back to the open stage, for new people to know to start work.

bounties community member enhancement

Source

mbeylin

👍1

Most helpful comment

@owocki Gitcoin Bot running wild over here!

@thelostone-mc Sorry about this, appreciate your good humor 😂please work this as if it is yours while we get the issue resolved 👍

vs77bb on 21 Feb 2018

😄2

All 20 comments

@mbeylin Users that have Started work on a bounty can currently Stop Work on a bounty, but we don't provide the funder with any mechanism to remove interested parties. 👍 This makes sense!

mbeacom on 18 Feb 2018

__This issue now has a funding of 0.04 ETH (37.66 USD) attached to it.__

If you would like to work on this issue you can claim it here.
If you've completed this issue and want to claim the bounty you can do so here
Questions? Get help on the Gitcoin Slack
$10098.12 more Funded OSS Work Available at: https://gitcoin.co/explorer

gitcoinbot on 20 Feb 2018

@mbeacom My guess is the funder would be able to choose from a list of users that started working on the bounty and "un-start" them?

KennethAshley on 20 Feb 2018

@mbeacom @KennethAshley Yes. There should also be functionality to return the bounty to an 'Open' state, if the funder ends up.

@lazaridiscom I can see where you're coming from, but don't think the current state of the platform reflects your concerns. Funders (who are generally OSS developers / repo maintainers themselves) are implicitly incentivized to treat anyone working on their projects well. We have not seen any cases of malice in this to-date.

The 'Unstart' Work ("Stop Work"?) functionality is important because we've seen instances where developers go completely off the map, leaving the funder no easy way to return the bounty to an 'Open' state.

As the platform scales, I agree with your sentiment. We need to put barriers in place (probably to both 'Start Work' and 'Stop Work') to help ensure that the right developers are working on the right issues, and that the funders can only 'Stop Work' if it's clear that certain parameters are met (i.e. Developer has been MIA for 1 week, submission is clearly under quality).

vs77bb on 20 Feb 2018

👍2

@vs77bb @mbeacom
Did gitcoin bot just totally ignore my start work request and republish the bounty 😂
I'm a lil hurt to be honest :P

It happened when the title gets changed , the bot posted it just after @PixelantDesign renamed the issue. Might need to look into that

thelostone-mc on 21 Feb 2018

@owocki Gitcoin Bot running wild over here!

@thelostone-mc Sorry about this, appreciate your good humor 😂please work this as if it is yours while we get the issue resolved 👍

vs77bb on 21 Feb 2018

😄2

__Work has been started on the 0.04 ETH (34.22 USD) funding by__:

@thelostone-mc

__Please work together__ and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through.

On the above list? Please leave a comment to let the funder (@mbeacom) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.

Learn more on the gitcoin issue page
Questions? Get help on the Gitcoin Slack
$10211.09 more Funded OSS Work Available at: https://gitcoin.co/explorer

gitcoinbot on 21 Feb 2018

looking into the issues with gitcoin bot. sorry ya'll.. gimme a day or so to triage

owocki on 22 Feb 2018

__Work for 0.04 ETH (34.22 USD) has been submitted by__:

@sethmcleod

Submitters, please leave a comment to let the funder (@mbeacom) (and the other parties involved) that you've submitted you work. If you don't leave a comment, the funder may expire your submission at their discretion.

Learn more on the gitcoin issue page
Questions? Get help on the Gitcoin Slack
$10236.76 more Funded OSS Work Available at: https://gitcoin.co/explorer

gitcoinbot on 22 Feb 2018

😄1 👎1

just put in a fix for the gitcoinbot craziness. gonna monitor for the next few hours to make sure we're all good.

owocki on 22 Feb 2018

looking okay now.. thanks for your patience folks

owocki on 22 Feb 2018

Did gitcoin bot just totally ignore my start work request and republish the bounty 😂

sorry about this @thelostone-mc -- my bad

owocki on 22 Feb 2018

😄1

@mbeacom A few doubts

Looking at this -> the flow would be:

Bounty Issuer clicks reject on a submission -> 
update the list ( i’m assuming db update to ) -> refresh to show updated list. 
(Do we do the confirm action in a pop up box before triggering an rejection ? )

I’m assuming bounties network doesn’t have a reject API which needs to be invoked

Does that sound right ?

Digging into the code in kill_bounty.js -> towards I see

bounty.killBounty(bountyId, {gasPrice:web3.toHex($("#gasPrice").val()) * Math.pow( 10, 9 )}, final_callback);

Upon invoking the killBounty()-> then there is a final_callback -> redirects us back to the page upon successfully killing the bounty

Where do we update our db locally ?
I don’t see a UPDATE/DELETE db call happening anywhere
cause in this usecase I don’t have to invoke bounty.xyz(), instead I’d have to delete that submission (not a good idea cause if in the future we keep an audit ) / update the table to introduced a col (rejected) and set it to true

thelostone-mc on 24 Feb 2018

@thelostone-mc For this particular bounty, you'd only need to remove the specific user's Interest from the bounty and update the Started Work list in the current view. So, the funder could Stop Work for the specified user in the Started Work section of the bounty details page. Interest impressions aren't relayed to the actual bounty, but uses a relation to Interest from Bounty in our relational DB. Similarly to how the remove_interest view works for the bounty hunter.