Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DESIGN - As a funder, I want example bounties that I can copy, so I know I'm scoping my bounty correctly. #2211

Closed
owocki opened this issue Sep 13, 2018 · 22 comments

Comments

@owocki
Copy link
Contributor

owocki commented Sep 13, 2018

User Story

As a funder, I want example bounties that I can copy, so I know I'm scoping my bounty correctly.

Why Is this Needed

Summary:
People don't already read the documentation about what makes a great bounty. By giving them examples we can just copy, they are able to just follow in the foot steps of those bounty hunters

Description

Type:
Feature

Current Behavior

No Examples Listed

Expected Behavior

a DESIGN that shows off 3 Example bounties in each of the following categories:

  1. Feature Request
  2. Bug Bounty
  3. Design Request
  4. Security Bounty
@vs77bb
Copy link
Contributor

vs77bb commented Sep 14, 2018

This is a good idea... my only question: how do we natively give them our 'bounty templates' on Github (the place where the issue is going to live)?

Somehow in markdown format?

@PixelantDesign
Copy link
Contributor

Linking to good examples might just do the trick.

@thelostone-mc
Copy link
Member

@vs77bb if we host the examples -> it's easy (but it might be an overkill) but markdown languages are fairly common and easy to derive just looking at the text

@owocki
Copy link
Contributor Author

owocki commented Sep 14, 2018

Linking to good examples might just do the trick.

@PixelantDesign i'm trying to decide if this is more of a design task or a coding task... probably we need to decide exactly where these example links are going to live? at first i was thinking it should go on the 'before you post a bounty' interstitial, but now i'm thinking the form itself might be a good idea (since most people move past that interstitial). what do you think?

if we host the examples

I like the idea of using live examples instead of just stock examples.. feels more real

@owocki owocki changed the title As a funder, I want example bounties that I can copy, so I know I'm scoping my bounty correctly. DESIGN - As a funder, I want example bounties that I can copy, so I know I'm scoping my bounty correctly. Sep 17, 2018
@gitcoinbot
Copy link
Member

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


This issue now has a funding of 0.4 ETH (82.46 USD @ $206.16/ETH) attached to it.

@gitcoinbot
Copy link
Member

gitcoinbot commented Sep 18, 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 6 months, 1 week from now.
Please review their action plans below:

1) anish-agnihotri has been approved to start work.

Hey,

Just saw this issue on Gitcoin and would love to help out with it. I've been looking at various types of bounty submissions for the last few days, and some of them certainly shine with their content. I've read up on the past discussion, and it seems that the general consensus seems to be towards multiple markdown files with the content (with possible links to example past bounties). I'd be glad to help out with those in terms of actual content generation, markup design, and additional research into what makes a successful bounty.

Other than that, hosting directly on Gitcoin could also be a viable option. Hosting this content in a convenient location like the Help page could easily be done as well (in this case, opting for HTML-formatted content instead of Markdown).

Let me know if that sounds aligned to what you were thinking of.

Thanks,

Anish

Learn more on the Gitcoin Issue Details page.

@vs77bb
Copy link
Contributor

vs77bb commented Sep 18, 2018

Hi @Anish-Agnihotri - just approved you to work on this one! I think you're on the right track with the below.

I've read up on the past discussion, and it seems that the general consensus seems to be towards multiple markdown files with the content (with possible links to example past bounties). I'd be glad to help out with those in terms of actual content generation, markup design, and additional research into what makes a successful bounty.

MARKET Protocol does a phenomenal job with their template, I'd recommend checking out some of their bounties here!

@Anish-Agnihotri
Copy link
Contributor

Hey there! Just wanted to chip in and drop an update (since it's been nearly a day since I was approved to work on this bounty, thanks again too).

I've started work for the bounty over at gitcoin-exemplars. Feel free to check out the progress, provide feedback, or inform me of any concerns if you have input. .

Other than that, I've taken a look at what MARKET Protocol does as well, and it really does look incredible. I'll be sure to take that into consideration, thanks!

@Anish-Agnihotri
Copy link
Contributor

Anish-Agnihotri commented Sep 19, 2018

Just finished off a complete section for bug bounties (one of the four required bounties for successful bounty completion). It has one general file regarding what makes a successful bug bounty, and three specific examples (in the form of a traditional, contest, and cooperative project type).

You can take a look at them here:

  1. Bug Bounty Exemplars

Let me know if this is aligned to your scope and what you had in mind. Otherwise, I'd be glad to alter them as you see fit.

In addition, after writing these up, I realized that a madlibs sort of tool where users can select their inputs and the description file is auto generated would be fantastic for this case. After bounty completion, I'd be glad to help make a Gitcoin tool for the toolbox integrating this functionality if there is interest.

@owocki
Copy link
Contributor Author

owocki commented Sep 19, 2018

@Anish-Agnihotri reviewing now!

@owocki
Copy link
Contributor Author

owocki commented Sep 19, 2018

@Anish-Agnihotri this seems like a good start -- id love to see the design/feature/security bounty ones filled out!

@Anish-Agnihotri
Copy link
Contributor

@owocki Perfect! That sounds good. I'm looking to get these knocked out in the next two days to three days after I write and review the content.

I'll keep you updated as I complete more.

@Anish-Agnihotri
Copy link
Contributor

Just finished another set of bounty write-ups. Here are the ReadME's for design request bounties:

  1. Design Request Bounty Exemplars

Looking to get the other two sets knocked out tomorrow and finish editing to get them prepped for submission. Let me know if you have any concerns as always.

@Anish-Agnihotri
Copy link
Contributor

Hey there,

I've completed the work now over at gitcoin-exemplars. Feel free to take a look and let me know. For some of these bounties, the live examples were very rudimentary, so I've designed my own appropriate descriptions.

I'd love to make this into an automated Gitcoin tool in the future, but for the meantime, please do let me know if you have any concerns - or, if this appropriately fulfills the bounty (in which case I will submit my work through the platform).

@PixelantDesign
Copy link
Contributor

PixelantDesign commented Sep 24, 2018

The templates are great @Anish-Agnihotri ! This would also be great to have on the funder/contributor guides once that is out.

@Anish-Agnihotri
Copy link
Contributor

Perfect! Thanks @PixelantDesign . In that case, I'll submit the bounty as soon as my gas faucet request goes through.

@gitcoinbot
Copy link
Member

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


Work for 0.4 ETH (93.58 USD @ $233.96/ETH) has been submitted by:

  1. @Anish-Agnihotri

@owocki please take a look at the submitted work:


@owocki
Copy link
Contributor Author

owocki commented Sep 24, 2018

paying out now!

@gitcoinbot
Copy link
Member

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


The funding of 0.4 ETH (93.76 USD @ $234.41/ETH) attached to this issue has been approved & issued to @Anish-Agnihotri.

@Anish-Agnihotri
Copy link
Contributor

Perfect, thanks! Feel free to let me know if anything else is needed in the future, and I'd be glad to help out in regards to these templates.

Thanks,

Anish

@thelostone-mc
Copy link
Member

@PixelantDesign do we wanna reuse this ticket for wiring it to guide / should we close this out and create a new one ?

@ali8889
Copy link

ali8889 commented Jun 1, 2019

Oky

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants