Web: Build V0 - Hackathon Experience in Gitcoin

Created on 6 Sep 2018 · 21Comments · Source: gitcoinco/web

User Story

As a remote contributor I'd like to not see hackathon issues in the issue explorer since I cannot participate on these issues.

As a hackathon participant I'd like to be able to see all of the prizes that are available on Gitcoin.

Description

Current Behavior

Expected Behavior

Separate experience.

Solution

V0 - hide hackathon bounties from the issue explorer and put hackathon bounties into a separate tab.
All issues created for hackathons should be tagged "hackathon name".
All hackathon users should be directed to a specific URL (basically filtered search with the name)
Nice to have: Add a hackathon link to that view from the issue explorer.

A core team member should be able to create a hackathon link in the admin panel.
Example: gitcoin.co/hackathons/hackathonname
There should be an area to upload a logo
3 fields to display prizes and value of each prize (1st, 2nd, 3rd)

Definition of Done

[ ] Hide hackathon bounties from the issue explorer
[ ] Put hackathon bounties into a new view based on the issue explorer (see mockup)
[ ] Create a custom url for hackathons that only core team members can see but are able to share.
[ ] create admin capabilities that allow:
A core team member should be able to create a hackathon link in the admin panel.
Example: gitcoin.co/hackathons/hackathonname
[ ] Add a hackathon logo
[ ] - 3 fields to display prizes and value of each prize (1st, 2nd, 3rd)
[ ] All of the above must be tested.

Additional Information

hackathon_v0

Source

PixelantDesign

Most helpful comment

this is a good idea, but i dont know if its the only thing we should be doing to better support hackathons or if it's the highest priority thing.. would be good to validate with our friends at ethberlin after the event, or maybe our ethdenver / MLH friends.

owocki on 7 Sep 2018

👍2

All 21 comments

@mbeacom

mark [2:22 PM]
If it's a priority, we could tackle it with some kind of Project/Event (read as group of bounties) designator object. We could allow Profile to create projects (and/or maybe let them pre-populate from GH projects) and allow them to associate an end date, whether or not the bounties should be displayed in the main explorer, and assets/images like displayed in the provided examples on the Github issue.

PixelantDesign on 6 Sep 2018

Opposed to that would it make sense to have another explorer endpoint for every hackathon
/explorer/ethindia , /explorer/ethberllin to show only those specific bounties

It would still need updating the schema and stuff but if it's really needed, we can do it!

cc @SaptakS

thelostone-mc on 6 Sep 2018

❤2

What's the effort for having a separate explorer? That experience would be ideal, but I was trying to think about easy ways to do this for Eth SF.

PixelantDesign on 6 Sep 2018

Opposed to that would it make sense to have another explorer endpoint for every hackathon /explorer/ethindia , /explorer/ethberllin to show only those specific bounties

This is compelling to me if it's easy enough to do. Each explorer endpoint could have the branding @PixelantDesign mentioned and referenced above (which I like!)

vs77bb on 7 Sep 2018

owocki on 7 Sep 2018

👍2

What's the effort for having a separate explorer? That experience would be ideal, but I was trying to think about easy ways to do this for Eth SF.

@mbeacom If we were to do this -> would it make sense to maintain this data in a separate table as opposed to adding an extra field at the existing schema to diff btwn normal bounties & event bounties ?

thelostone-mc on 7 Sep 2018

@PixelantDesign The convo above also could have bearing on our conversation about breaking out bug bounties from the main issue explorer.

Hackathons // bug bounties are a very different experience than a core Gitcoin bounty (getting paid for making a PR which is merged to an active repo).

@owocki @ceresstation also curious your learnings from ETHBerlin / if you agree this is helpful, now. I think ETHBerlin validated to me that it definitely needs to be broken out of the main explorer, if only to decrease confusion for our non-hackathon Gitcoiners (the majority).

vs77bb on 10 Sep 2018

👍1

i agree it would be helpful

owocki on 13 Sep 2018

@PixelantDesign

This is a concept, not to build for eth berlin.

Maybe lets built it for Status Hackathon or ETHDenver, since those are upcoming (not in the past)!

All issues created for hackathons should be tagged "hackathon name".
Nice to have: Add a hackathon link to that view from the issue explorer.

I think it'd be nice to have small designs done for each of these!

owocki on 20 Sep 2018

@owocki I don't think the logo matters that much? We can change it out. I'm more curious if there is enough definition here to bounty. I'll update the image if it helps.

PixelantDesign on 20 Sep 2018

Neat idea. What's the thing with the 'prices' on the left?

pinkiebell on 20 Sep 2018

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

__This issue now has a funding of 0.39 ETH (81.43 USD @ $208.8/ETH) attached to it.__

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin Slack
- $22,451.00 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 20 Sep 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, 2 weeks from now.
Please review their action plans below:

1) pinkiebell has been approved to start work.

Details already discussed via Slack. Turnaround probably this weekend.

Learn more on the Gitcoin Issue Details page.

gitcoinbot on 20 Sep 2018

💰 A crowdfund contribution worth 100.00000 DAI (100.0 USD @ $1.0/DAI) has been attached to this funded issue from @ceresstation.💰

Want to chip in also? Add your own contribution here.

gitcoinbot on 20 Sep 2018

@PixelantDesign
Explorer urls are like /explorer/ETHBerlin, so we reuse the explorer/dashboard code.
You can manage Hackathon events via /_administrationdashboard/hackathonevent/.

pinkiebell on 23 Sep 2018

@thelostone-mc I think it'd make sense to maintain the same Bounty objects we have now, but we could add a Project or Event model that relates back to the Bounty model.

Then we could simply exclude based on events or query on them to display appropriate results without manipulating the Bounty model directly.

This would give us the ability to add the branding for an event, timeframe, and potentially participants/enrollment/etc at some point.

mbeacom on 24 Sep 2018

@pinkiebell 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!