Web: Started work / Stop Work History

Created on 1 May 2018 · 28Comments · Source: gitcoinco/web

In https://github.com/ipld/js-cid/issues/38#issuecomment-378075363 I am pretty sure that the work was started by @dimkk 27 days ago, and I remember seeing it in gitcoin.co page too - https://gitcoin.co/issue/ipld/js-cid/38/121

But now @gitcoinbot edited its message to say that @rrandom is now working on the issue, although I don't see any activity from him. I also see that @gitcoinbot started to ping @rrandom in https://github.com/ipld/js-cid/issues/38#issuecomment-385448870 and it looks wrong, because there is no trace of history who started work on the issue, if he cancelled the work, no links to transactions - https://gitcoin.co/issue/ipld/js-cid/38/121

User Story

As a gitcoin.co user, I want to see history of changes on the bounty detail page, who worked on what, when started, when ended, so that I can reward people fairly.

Acceptance Criteria

The bounty detail page should show a history of who has started and stopped work

Source

abitrolly

Most helpful comment

thanks for letting us know @bohendo :)

how meta that this ticket is about start/stop work :)

owocki on 21 May 2018

😄3

All 28 comments

there is def a balance between providing the history of changes and clogging up the issue with a bunch of comments. we opted to avoid clogging up the issue with a bunch of comments..

perhaps we could have the gitcoin bounty show the start/stop work history.. would that suffcie @abitrolly

cc @mbeacom and @PixelantDesign on this

owocki on 1 May 2018

👍1

start/stop history will help. I expected to see it on bounty page, but if it is exposed through API then there should be no problem for the bot to update its message like it does right now with some concise history format. It can also generate some d3.js pictures.

abitrolly on 1 May 2018

But my biggest concern is that probably @dimkk never cancelled his work and @rrandom never started, so there is a bug on our side.

abitrolly on 1 May 2018

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

__This issue now has a funding of 0.07 ETH (51.87 USD @ $741.02/ETH) attached to it.__

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
Questions? Checkout Gitcoin Help or the Gitcoin Slack
$8,683.28 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 9 May 2018

👍1

What if somebody could complete this earlier than in 4 weeks?

abitrolly on 11 May 2018

@owocki as i undestand this will add a event model for record the activity of interested on each bounty right? I think the sunday send the PR with this functionality and one simple activity list on the bounty detail page

zoek1 on 12 May 2018

I just pushed a WIP PR using the Interested model instead of create a new model for events.

zoek1 on 13 May 2018

If two people show interest, should they both be shown under "Contributor" or only one at a time? I'm assuming we'll only display the first person to express interest who hasn't stopped working yet. Or maybe I don't need to touch that to solve this issue.

Also, why is there a many-to-many relationship between dashboard_interest and dashboard_bounty? Can one interest really be associated w more than one bounty?

bohendo on 14 May 2018

👍2

@owocki as i undestand this will add a event model for record the activity of interested on each bounty right? I think the sunday send the PR with this functionality and one simple activity list on the bounty detail page

seems like that'd be a good approach to me! we could actually consolidate a lot of the events associated with bounties into this model!

owocki on 15 May 2018

@owocki i've working on #925, this issue could take advantage of the activity model developed in such issue, we just need filtering the activity(start, work, stop work) on each given bounty. So I'll give priority to #925 and after i'll finish this, it's ok?

zoek1 on 16 May 2018

good call :)

owocki on 16 May 2018

@bohendo for the purposes of this ticket you can show all of the active interests that are in the DB on the frontend.

you can assume that someone else will handle the constraints on the number of of ppl who can express interest in https://github.com/gitcoinco/web/pull/1098

owocki on 17 May 2018

@owocki maybe just deploy https://github.com/fedora-infra/datanommer and fedmsg to avoid reinventing event flow?

abitrolly on 17 May 2018

@bohendo 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] warning (3 days)
[ ] escalation to mods (6 days)

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

gitcoinbot on 17 May 2018

Oops, I expected to have more time to work on this during weekdays but that hasn't been the case. I'll ether dig into this & finish it over the weekend or hand it off to the next code monkey.

bohendo on 19 May 2018

Apologies, I won't be able to give this issue the attention it deserves.

@zoek1 Sounds like you've got a solid battle plan though, rock on & best of luck. The gitcoin bounty is available now if you want to take it: https://gitcoin.co/issue/gitcoinco/web/1037/394

bohendo on 20 May 2018

This is why started/stopped is important. ;)

abitrolly on 21 May 2018

👍2

thanks for letting us know @bohendo :)

how meta that this ticket is about start/stop work :)

owocki on 21 May 2018

😄3

Whats the latest on this? I'd love to knock it out.