Update Hours Dropdown in Funder Form

[PixelantDesign]

User Story

As a developer, I want to know how long a task will take so that I can determine whether I have bandwidth to work the bounty.

Description

Type: Enhancement to Bounty Creation screen

Summary: Currently 'Project Length' does not provide valuable insight to the developer taking on the work.

Actual behavior

Right now, the drop down shows Hours, Days, Weeks, Months - which is open and unclear to the developer.

Expected behavior

Change the drop-down to include the following values.

• < 4 Hours
• 5 - 8 Hours
• 8 - 20 Hours
• 21 - 40 Hours
• 40+ Hours

Solution

Summary: Implement above hours into the drop-down options.

Additional Information

Review with @PixelantDesign @vs77bb

[e-n-l]

I love this idea.

At some point, I think I'd really want an option for more granularity, that would allow for the following:

0. minutes as atomic unit
1. selected as [ number field ] [ unit select ]
2. maybe break time expected down per 'skill', 'tool' or field of expertise involved

Examples:

• '4 days' = 4 days x 8 hrs x 60 min = 1920
• '3 weeks' = 3 weeks x 5 days x 8 hrs x 60 min = 7200

This level of specificity might be better delegated to an integration with a 3rd party / internal tool for project planning, along with funnels for both repo-owners and contributors. Through a consistent, simple UX, everyone could iteratively improve project estimation accuracy. IMHO, opacity in that regard is a huge point of friction to the action <=> incentive correlation.

A plug-in ala Toggl comes to mind on the contributor side, so the contributor can track their actual time spent, and upon submission:
a) post what they believe a contributor of 'average' competency would have spent.
b) optionally, share with GitCoin and / or the repo-owner their actual time spent.

As an aside, I think it's clear that all of this is fairly subjective. Skill level, expectations, and time estimations are all very fuzzy, but I would assert that the more data we can surface and present in meaningful ways, the more concrete those subjective approximations become. At the very least, it's data that people find value in and makes the UX more valuable.

[frankchen07]

@PixelantDesign, some thoughts to consider:

The new change on the funder form ("Project Length" to "Time Commitment") grammatically makes it clearer as to the amount of dedication that a contributor might allocate for the task.

Adding an hours drop down in the funder form, especially one with predefined categories, would be redundant at this stage, as the time commitment drop down already has a categorical component to it. Furthermore, it has the potential to be confused with the time commitment dropdown (both are categorical and both are linked tightly to how many hours the task will take).

The implementation of an hours estimation for success pricing is akin to @e-n-l 's suggestion of having a custom input, with the added advantage that it's shuttled under the pricing section, which reduces confusion. As one who understands and likes having data to make decisions, having this type of estimated input helps Gitcoin see how people make their estimates - important information that may be abstracted away when using "hour categories".

[PixelantDesign]

Cool thanks for the feedback @frankchen07 ! Closing this issue then!