Web: Beyond Blockchain: Hourly Rate Contracts On Gitcoin

Created on 9 Apr 2019  Â·  19Comments  Â·  Source: gitcoinco/web

User Story

As a bounty hunter, I would like to express an hourly wage which I'd like to be paid for my work on Gitcoin.

Why Is this Needed

To give hunters the ability to express their hourly rate expectations up front and get paid against that hourly wage, instead of a bounty amount.

Summary: The ability for a Gitcoin Hunter to state an hourly rate on their profile and to track hours spent on a bounty, finalizing with an invoice which a funder can use to pay out upon completion of work.

Description

Type: Feature

Current Behavior

Bounty hunters can only work for the bounty amount suggested.

Expected Behavior

Bounty hunters can express interest in working at a specific hourly rate.

Definition of Done

  • [ ] Bounty hunter hourly rate is shown on the Gitcoin profile
  • [ ] Bounty hunter can express interest in bounties against their hourly rate
  • [ ] Bounty hunter can provide an invoice against their hourly rate which can be paid out via Advanced Payout functionality by a Gitcoin Funder

Data Requirements

  • Number of hunters which use hourly rate vs. accept bounty terms

Additional Information

All 19 comments

Just a few concerns here

Pros
  • This would add more pressure for the funder to put more thought before bountying
  • The contributor would be forced to evaluate themselves

^ Both of the above would ensure better matching

Cons
  • How do we handle if hunter ends up spending more time than needed
    (cause we have a feedback cycle + reviews + etc). Would this lead to more disputes ?
  • Would this mean every bounty creation process as the funder would specify the hourly rate + time.
    They would not be able to set the bounty amount directly

@vs77bb / @owocki

How do we handle if hunter ends up spending more time than needed

I think we can make sure there is good communication between funder and coder by adding a feature that allows funders to 'approve' batches of hours?

Would it be possible to pre-fill this value based on the 'hours worked' value put into the submit work form for bounties already completed?
Being asked my hourly rate I might say e.g. $100, but it would help me to know what is the actual rate I've been working for on Gitcoin in the past.

This could work by the community accepting code changes and the time used. Hence a project is proposed at say 1000 hours at 50 dollars per hour. Then we have a bidding process to select the final developer, or people develop in parallel and the accepted solution gets the hourly rates. The acceptance is a community decision based on a forum viewing the changes. This is all global and hence India/China would be involved. That could affect rates too.

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


__This issue now has a funding of 1250.0 DAI (1250.0 USD @ $1.0/DAI) attached to it.__

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 12 months from now.
Please review their action plans below:

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

I find this idea very interesting to see how it plays out on the platform!

From what I see on the github issue the details are still under discussion, but I could start working on a funder contract which would start the countdown when a user is accepted up until he publishes his work.

Learn more on the Gitcoin Issue Details page.

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 months, 4 weeks from now.
Please review their action plans below:

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

I find this idea very interesting to see how it plays out on the platform!

From what I see on the github issue the details are still under discussion, but I could start working on a funder contract which would start the countdown when a user is accepted up until he publishes his work.
2) nionis has applied to start work _(Funders only: approve worker | reject worker)_.

I find this idea very interesting to see how it plays out on the platform!

From what I see on the github issue the details are still under discussion, but I could start working on a funder contract which would start the countdown when a user is accepted up until he publishes his work.
3) usmanmuhd has been approved to start work.

I'll discuss more about the flow with the core team and then implement the feature as required.

Learn more on the Gitcoin Issue Details page.

i see this was posted as a bounty for the hackathon. @thelostone-mc @danlipert just maknig sure you guys are CCed on engineering architecture input before anyone starts work!

@vs77bb i see that you made this part of the BB hackathon. do we have any further advice for hackathon participants? i think that having a dev team up with a designer might be super powerful for this.

The flow I was thinking of is:

  1. Every user has an hourly rate.
  2. They apply to work on a bounty.
  3. Any negotiations happen between the funder and hunter.
  4. Funder allocates a block of hours.
  5. Work done.
  6. Advanced payout.

If work is not done after 4.:
If the hours are exceeding the expectations then we have a negotiation window between the funder and hunter.
If there is no progress then kick out.

Already had a discussion with @owocki , looking for feedback from others.
@vs77bb It would be great if I can get a designer to work along with.

@usmanmuhd

  • would the negotiations happen on gitcoin /outside?
  • funder allocated block of hours ? the time to be spent on the task is usually filled during bounty creation. At what point would this happen? Also if additional funds are needed -> how would that be added to the bounty ? (via tip / crowdfund? )

would the negotiations happen on gitcoin /outside?

We can have a basic chat feature which will allow them to negotiate on gitcoin.

funder allocated block of hours ? the time to be spent on the task is usually filled during bounty creation

Funder has an expected time and the hunter might have another expected time. Sometimes the hunter thinks that the task needs more time and he can ask the funder for that. Funder decides as deemed fit. This can change at a later stage if both are in agreement.

Also if additional funds are needed -> how would that be added to the bounty ? (via tip / crowdfund? )

I hadn't thought about the crowdfund option, but now you have brought it up, it seems like a great idea to add additional funds via crowdfund to avoid later hassles.

@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

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


@usmanmuhd 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

@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

@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

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


__Work for 1250.0 DAI (1250.0 USD @ $1.0/DAI) has been submitted by__:

  1. @usmanmuhd

@ceresstation please take a look at the submitted work:

  • PR by @usmanmuhd

Submission for hackathon: #4747

Note: Needs a bit more of review and detail before it is ready for merge.

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


__The funding of 1250.0 DAI (1250.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @usmanmuhd.__

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Makondor2 picture Makondor2  Â·  3Comments

thelostone-mc picture thelostone-mc  Â·  4Comments

abitrolly picture abitrolly  Â·  4Comments

uluhonolulu picture uluhonolulu  Â·  3Comments

jasonrhaas picture jasonrhaas  Â·  4Comments