Docker Docs Hackathon: Results for Austin, April 17-21, 2017

Estimated reading time: 17 minutes

Docs Hackathon: Winners

Well, it’s over. We had an amazing hackathon on the documentation last week, with over 140 bugs closed and counting. We couldn’t be more thankful for your participation! If you participated, make sure you fill out your report so you can get your rewards.

We are so humbled and lucky to have a community like you working with us. From the bottom of our hearts: thank you!

Let’s dive into the results. First up, the point bonus winners:

Bonuses

There were three bonus categories. You can see the point values from these bonuses reflected in the participant report.

Largest change in a single fix

This award goes to @allejo, for the site-shifting change in pull request #2860. A revamp of many aspects of the site’s responsive behavior that affected our CSS, JS, and include/header structure, you can thank @allejo for the site operating so well in various resolutions now, and keeping the menus working regardless of viewport size and footer position.

Most bugs closed

This award goes to @shubheksha who helped closed a stunning 31 bugs during our hackathon. For details of all of @shubheksha’s contributions, see the raw results. Excellent work!

Most participation (active every day)

This is tough because we actually had several people who spent time on the hackathon every single day it was active. So we’re going to split this award four ways:

  • @johnharris85
  • @shubheksha
  • @scjane
  • @bdwill

We saw you all, in person, in Slack, or on GitHub, and worked with you the whole hackathon. 250 points to each of you, and our sincere thanks.

Overall winners

And now, the moment we’ve all been waiting for. The top three of the Docs Hackathon!

3rd place: @johnharris85

Congratulations to @johnharris85, our second runner-up! For your efforts you get:

  • $157.50 in the hackathon swag store
  • A trophy with a personal engraving

2nd place: @allejo

Congratulations to @allejo, our runner-up! For your efforts, you get:

  • $180 in the hackathon swag store
  • A $150 Amazon Gift card
  • A trophy with a personal engraving

1st place: @shubeksha

Last but not least, a round of applause for our first-place winner!

Congratulations to @shubeksha! With an amazing 31 bugs closed, Docker thanks you from the bottom of our hearts. For your efforts you get:

  • $275 in the hackathon swag store
  • A $300 Amazon gift card
  • A large trophy with a personal engraving

Amazing work, @shubeksha, and once again, many thanks to our participants. We’re already planning the next one, so get ready!

Hackathon impact and results

Stats

Just a few bits of trivia.

  • Total points awarded: 16750
  • Total issues closed: 158
  • Total participants (not counting Docker employees): 35
  • Average points per issue: 106.01
  • Average points per participant: 478.57
  • Average participation time: 52.2 minutes (based on our estimate that 100 points = 1 hour of work)

Visuals

Bug count graph

In this graph you can see the pile-up of bugs we were experiencing in the docs, and the dramatic flurry of activity that closed many of these bugs during the hackathon. This is actually a graph of the labels attached to bugs; interact with these results here.

results graph Courtesy of Bug Life

Bug burndown graph

In this graph you see the ideal line for reaching zero bugs during the hackathon. Unfortunately it took us a bit longer to reach zero while we graded and closed lingering PRs. But we did indeed get there!

burndown graph Courtesy of waffle.io

Raw results

You can audit our work on GitHub, or with these handy tables.

By participant

Participant Issues Fixed Subtotal Bonus Final Score
shubheksha 31 1500 1250 2750
allejo 3 800 1000 1800
johnharris85 7 1325 250 1575
jmaitrehenry 9 1025   1025
clocklear 7 975   975
stevenhanna6 6 900   900
surajnarwade 5 800   800
scjane 11 375 250 625
bdwill 9 300 250 550
gschaetz 5 500   500
constanzekratel 4 500   500
prashant171992 7 500   500
ashishkamat2791 1 500   500
jadametz 6 425   425
NonCreature0714 2 400   400
bhavin192 3 375   375
jpooler 4 325   325
michaelspets 2 275   275
subodh-dharma 1 250   250
alvin319 3 225   225
vikstrous 2 200   200
wcgcoder 2 200   200
Rubab-Syed 3 175   175
alfonso-cabrera 3 150   150
tippexs 2 150   150
audioboxer217 1 100   100
frankgreco 1 100   100
jaredestroud 2 75   75
joaofernandes 1 50   50
joeuo 1 50   50
aboch 2 50   50
jcberthon 1 50   50
t3h2mas 1 50   50
vishnu-narayanan 2 50   50
jennylia 1 25   25

By GitHub issue

Issue(s) Pull Request(s) Fixer #1 Points to #1 Fixer #2 (if split) Points to #2
2232 (2002, 2403) 2860 allejo 500 stevenhanna6 25
1946 2894 ashishkamat2791 500    
1168 2881 clocklear 500    
218 2877 johnharris85 500    
1978 2941 stevenhanna6 500    
2619 N/A (see comments) allejo 250    
2748 2824 bhavin192 250    
1809 2866 constanzekratel 250    
1456 moby/moby 32701 gschaetz 250    
2277 2871 jadametz 250    
777 2940 jmaitrehenry 250    
1580 2964 jmaitrehenry 250    
1742 3036 jmaitrehenry 250    
1667 2824 johnharris85 250    
2036 2827 johnharris85 250    
2025 moby/moby 32751 michaelspets 250    
786 2833 prashant171992 250    
2407 2976 subodh-dharma 250    
344 2961 surajnarwade 250    
2705 2944 surajnarwade 250    
2098 2893 NonCreature0714 200 jcberthon 50
2868 2879 NonCreature0714 200 shubheksha 50
2096 2888 alfonso-cabrera 100    
967 moby/moby 32723 alvin319 100    
2398 2922 alvin319 100    
974 2863 audioboxer217 100    
2589 moby/pull/32735 bhavin192 100    
995 2920 clocklear 100    
1097 2886 clocklear 100    
1683 2884 clocklear 100    
2167 2890 clocklear 100    
1465 2885 constanzekratel 100    
1465 2885 constanzekratel 100    
847 2861 frankgreco 100    
443 2875 gschaetz 100    
2005 moby/moby 1456 gschaetz 100    
2478 2919 jmaitrehenry 100    
176 2972 johnharris85 100    
1417 3008 johnharris85 100    
2116 2837 johnharris85 100    
2423 2910 jpooler 100    
2659 2918 jpooler 100    
2192 2988 Rubab-Syed 100    
1448 2817 shubheksha 100    
1448 2817 shubheksha 100    
2125 2949, 2959 shubheksha 100    
2435 2814 shubheksha 100    
2732 2831 (2810) shubheksha 100    
1316 2841 stevenhanna6 100    
1805 2993 stevenhanna6 100    
2592 2990 stevenhanna6 100    
1353 2912 surajnarwade 100    
1678 2905 surajnarwade 100    
357 2909, 2911 tippexs 100    
1904 2794 vikstrous 100    
1904 2794 vikstrous 100    
2637 2878 wcgcoder 100    
2637 2878 wcgcoder 100    
2088 2971 bdwill 75 jmaitrehenry 25
825 2946, 2957, 2968 shubheksha 75 aboch 25
933 2968 shubheksha 75 aboch 25
2012 2864 allejo 50    
1476 2857, 2971 bdwill 50    
1673 N/A clocklear 50    
2237 2921 constanzekratel 50    
1055 2828 jadametz 50    
1311 2843 jadametz 50    
850 2845 jaredestroud 50    
951 moby/moby 32831 jmaitrehenry 50    
1694 2790, 2880 joaofernandes 50    
2801 2854 joeuo 50    
2555 2913 jpooler 50    
2607 2832 (closed) jpooler 50    
926 2849 prashant171992 50    
2580 2943 prashant171992 50    
2783 2838 prashant171992 50    
1528 2858 Rubab-Syed 50    
1054 moby/moby 32803 scjane 50    
1759 moby/moby 32682 scjane 50    
2575 2807 scjane 50    
1670 2816 shubheksha 50    
2017 2819 shubheksha 50    
2151 2820 shubheksha 50    
2281 2821 shubheksha 50    
2300 2815 shubheksha 50    
2535 2813 shubheksha 50    
2724 2812 shubheksha 50    
2803 2808 shubheksha 50    
2751 2839 stevenhanna6 50    
1312 2903 surajnarwade 50    
2468 2914 surajnarwade 50    
1840 2939 t3h2mas 50    
2781 2937 tippexs 50    
1030 N/A alfonso-cabrera 25    
1665 N/A alfonso-cabrera 25    
2396 N/A alvin319 25    
2126 2857, 2971 bdwill 25 jmaitrehenry 25
1017 2857, 2971 bdwill 25    
1319 N/A bdwill 25    
1977 N/A bdwill 25    
2067 N/A bdwill 25    
2239 N/A bdwill 25    
2510 N/A bdwill 25    
2130 2835 bhavin192 25    
1499 N/A clocklear 25    
2587 N/A gschaetz 25    
2782 N/A gschaetz 25    
382 NOOP jadametz 25    
1539 N/A jadametz 25    
2077 2840 jadametz 25    
1621 2847 jaredestroud 25    
2285 2974 (2869) jmaitrehenry 25 jennylia 25
2113 N/A jmaitrehenry 25    
2643 moby/pull/32722 jmaitrehenry 25    
1622 N/A johnharris85 25    
2675 2916 jpooler 25    
2862 2870 michaelspets 25    
1610 N/A prashant171992 25    
1685 2923 prashant171992 25    
1850 N/A prashant171992 25    
1990 2857 prashant171992 25    
2772 N/A Rubab-Syed 25    
811 N/A scjane 25    
998 N/A scjane 25    
1400 moby/moby#32684 scjane 25    
1477 N/A scjane 25    
1548 N/A scjane 25    
1559 N/A scjane 25    
1680 N/A scjane 25    
2082 2850 scjane 25    
2205 2852 scjane 25    
205 2842 shubheksha 25    
1525 2809 shubheksha 25    
1625 2809 shubheksha 25    
1844 2818 shubheksha 25    
1969 2822 shubheksha 25    
1973 N/A shubheksha 25    
2108 N/A shubheksha 25    
2370 N/A shubheksha 25    
2374 N/A shubheksha 25    
2390 N/A shubheksha 25    
2395 N/A shubheksha 25    
2427 2876 shubheksha 25    
2430 N/A shubheksha 25    
2433 N/A shubheksha 25    
2512 N/A shubheksha 25    
2734 2811 shubheksha 25    
2634 2846 stevenhanna6 25    
2223 N/A vishnu-narayanan 25    
2223 N/A vishnu-narayanan 25    
2202 See Issue #2232        
2403 See Issue #2232        

Original Hackathon details

During DockerCon 2017, Docker’s docs team will be running our first-ever hackathon, and you’re invited to participate and win prizes – whether you attend DockerCon or are just watching the proceedings online.

Essentially, it’s a bug-bash! We have a number of bugs filed against our docs up on GitHub for you to grab.

You can participate in one of two ways:

Or, both – if you want to have the best shot. After all, we won’t be in the hack room 24/7 that whole week.

All participants who show up in the 4th floor hack room at DockerCon will get this way-cool magnet just for stopping by.

DockerCon Docs Hackathon logo

How it works

We have a number of bugs that have built up in our docs queue on GitHub, and we have labeled a whole slew of them with the tag hackathon, which you can see here.

Submit fixes for these bugs, or close them if you do a bit of research it turns out they aren’t actually valid. Every action you take gets you more points, and the points are redeemable for dollars in our hackathon store. These points also qualify you for valuable prizes like an Amazon gift card and a personally engraved trophy!

Prizes

  • All participants: Points are redeemable for t-shirts, hoodies, sweatshirts, mugs, beer steins, pint glasses, flasks, hoodies, stickers, buttons, magnets, wall clocks, post-cards, and even doggie t-shirts.
  • 3rd place: A small trophy with a personal engraving, plus store credit
  • 2nd place: A small trophy with a personal engraving, plus store credit, plus a $150 Amazon Gift Card
  • 1st place: A large trophy with a personal engraving, plus store credit, plus a $300 Amazon Gift Card

Bonuses

A select few will get bonuses for being extra special contributors:

  • Largest single change introduced in a fix (files changed/lines of delta): 1000 points
  • Most bugs closed (resolved as no-op or handled): 1000 points
  • Most participation (attended all days): 1000 points

Choosing a prize

You can see the point values for the bugs in the GitHub queue. Those are worth cash in our rewards store at http://www.cafepress.com/dockerdocshackathon.

Our points-to-cash conversion rate will be figured out at the end of the hackathon, and will essentially be a function of the number of points that hackathon participants logged, and the number of dollars we have to spend on prizes.

View our available prizes

When?

The docs hackathon is going on from April 17th thru April 21st, 2017. This is the time when it’s possible to claim and resolve bugs.

Note: Okay, technically, we won’t be tallying until the following Monday, April 24th. Just be sure you’ve submitted your claim form by then. If we don’t see your work on Monday morning, it won’t be counted.

Where?

In-person

Attending DockerCon? Come to the fourth floor hack room on Tuesday and Wednesday from 1pm to 6pm. We’ll be there to answer questions and help you.

Note: While the hackathon is officially ongoing all week online, working in the hack room with us for these two days is by far the best way to participate; the docs team will be on-hand to get you started, get you unstuck, and guide you.

Online

Drop into the community Slack channel for the docs and ask any questions you have. Otherwise, just go to GitHub and look at our hackathon label and come here to claim your points when you’re done.

Claiming a bug

Whether attending in-person or online, to claim a bug as one that you are working on (so nobody else grabs it out from under you) you must type a comment saying you claim it. Respect it when you see other comments claiming a bug.

View available bugs

Claiming your points

Simply fill out this form when you’re done participating. We’ll take it from there.

Conversion rate

Every 10 points is worth $1 USD in the swag store

You’ll see point values for each of the bugs, such as points/100 and points/250. Opening an accepted PR that fixes these bugs by the end of the hackathon earns you that number of points.

So if you fix a 100-point bug, that’s $10 you have to spend in the swag store.

Questions?

Ask us anything at docs@docker.com or in the #docs channel on Slack.

Thank you for participating in the 2017 Docs Hackathon!

Eligibility: Participants must be eighteen (18) years of age or older as of the date of your pull request.

To participate in the Docs Hackathon you must submit a pull request that handles a GitHub issue in the docker/docker.github.io repo that has the label “hackathon” sometime between April 17th thru 22nd.

Multiple entries per person allowed and encouraged.

Participation in the Docs Hackathon and submission of content therein gives Docker rights to use submitted content (e.g., text, code, and images) for potential future promotional marketing activities.

For the purposes of copyright all content submitted to Docker for the Docs Hackathon belongs to Docker.

Winners will be announced the week of April 22nd on https://docs.docker.com/hackathon. The winners will be named by GitHub username and contacted via email.

hack, hackathon, dockercon, austin, 2017