Web: BUILD Action Plan Example for Start Work Dialog

Created on 10 Jul 2018 · 19Comments · Source: gitcoinco/web

As a contributor, I want an example of what is expected for an action plan.

Type: Feature

Current Behavior

No Example

Solution

Summary:

Provide an inline example for contributors to reference when writing an action plan.

Definition of Done

The designs are updated and built to spec.

[ ] Implement two scenarios for this dialog (permissionless and approval required)
Please pay attention to the copy details, the copy on the checkbox changes per scenario.
[ ] Update close dialog button with the new X icon.
[ ] Add copy as hint text
[ ] Clear the text when user clicks inside the input field
[ ] Experiment with a minimum character count and make a recommendation
[ ] Display action plan separate from questions in the github issue thread

Additional Information

Review with core team members @pixelantdesign

Mockups

Permissionless
screen shot 2018-07-10 at 2 26 32 am

Approval Required
screen shot 2018-07-10 at 2 26 42 am

ActionPlan_Example.zip

to bounty

Source

PixelantDesign

All 19 comments

i like this idea

owocki on 11 Jul 2018

What about contest & coop?
Should the behaviour be the same? (Additional checkboxes)

You can assign it to me, anytime, if you want ;)

pinkiebell on 11 Jul 2018

@PixelantDesign
We could pre-populate it with the template (like github issues template) instead of giving a placeholder

thelostone-mc on 11 Jul 2018

Or a dynamic todo-style form. That would also allow for more easy options to optimize the gitcoinbot

pinkiebell on 11 Jul 2018

👍1

What I have on my mind:

'Submit a Plan'

'What are the tasks for this issue?'
(Implement xyx. Needed for abc, takes approx. 1.2 hours)
(Writing tests, takes approx. 0.7 hours)
(writing documentation, 0.5 hours)

'Fine, you have 3 tasks with a total approximation of 2.4 hours of work.'
'That is round about 64 USD per hour for this bounty'

'Do you have any open question?'
(What are your recommend frameworks?)
(Are you fine with a turnaround time of 4 days?)

(checkbox)[x] .....

(submit)

That is easy to use, isn't it? ;)
bonus points:

easier upfront decision making for worker and funder.
^also metrics! Worker estimates upfront hours needed and the payment per hour.
The funder can also much better reason about the issue and maybe increase/decrease/split bounty
If the worker later submits work and gives his final estimate of hours worked,
we can easily derive statistics about (edit)upfront estimate -& real working hours and could
establish better guidelines based on this insights.
we now have a basic structure and can easily optimize the gitcoinbot.

How does that sound? ;)

pinkiebell on 11 Jul 2018

@pinkiebell these are all great points! I've thought about a progressive disclosure type experience.

We're trying to balance between asking too much and asking enough to be able to know that the contributor is really interested/committed to the project.

Not sure if we get so granular on the hours. We've heard from contributors that they tend to keep these short since folks that are writing short answers are first to apply for the tasks.

Open to hearing how you might simplify your proposal though.

What do you think @vs77bb ?

PixelantDesign on 13 Jul 2018

@pinkiebell I liked your ideas on making the fiels dynamic and progressive but thinking maybe we start with a simple update to see what the response is. Let me know if you're still interested in this one.

PixelantDesign on 16 Jul 2018

@PixelantDesign Sure. You can attach mockups anytime ;)

pinkiebell on 16 Jul 2018

I personally feel a dynamic to-do style form would be an overkill since most developers won't like the idea of filling up an entire form and rather want to jump to work. But that is just my opinion. @thelostone-mc @mbeacom what do you think?

SaptakS on 16 Jul 2018

👍1

@pinkiebell zip is attached.

PixelantDesign on 17 Jul 2018

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

__This issue now has a funding of 0.129 ETH (65.61 USD @ $508.62/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
$30,009.87 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 18 Jul 2018

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

__Work has been started__.

These users each claimed they can complete the work by 4 months, 3 weeks ago.
Please review their action plans below:

1) pinkiebell has been approved to start work.

Will submit PR today

Learn more on the Gitcoin Issue Details page.

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

Hi, I know already someone applied, but if you change your mind i have ready to work and implement this work with you! I have experience with js, html, css and React.js if you want to implement by component programming. Thank you!

Learn more on the Gitcoin Issue Details page.

gitcoinbot on 18 Jul 2018

@PixelantDesign

What about the other bounty types?

Contest
"I understand that this bounty is a contest and that other bounty hunters may be working in parallel with me."

Co-op
"I understand that this bounty is a multi-worker cooperative bounty. Other bounty hunters may be working in parallel with me, but the funder has indicated they will pay the bounty to multiple of us."

And regarding the minimum text length, I think a sentence (24?) characters are ok?

pinkiebell on 18 Jul 2018

👍1

Sounds good @pinkiebell

Let's do a 2 sentence minimum.

Thanks!

PixelantDesign on 19 Jul 2018

@bumanerdene I have another task you could help with you're interested!

PixelantDesign on 19 Jul 2018

@PixelantDesign I'm interested! Send me the details.