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

ParticipantIssues FixedSubtotalBonusFinal Score
shubheksha31150012502750
allejo380010001800
johnharris85713252501575
jmaitrehenry91025 1025
clocklear7975 975
stevenhanna66900 900
surajnarwade5800 800
scjane11375250625
bdwill9300250550
gschaetz5500 500
constanzekratel4500 500
prashant1719927500 500
ashishkamat27911500 500
jadametz6425 425
NonCreature07142400 400
bhavin1923375 375
jpooler4325 325
michaelspets2275 275
subodh-dharma1250 250
alvin3193225 225
vikstrous2200 200
wcgcoder2200 200
Rubab-Syed3175 175
alfonso-cabrera3150 150
tippexs2150 150
audioboxer2171100 100
frankgreco1100 100
jaredestroud275 75
joaofernandes150 50
joeuo150 50
aboch250 50
jcberthon150 50
t3h2mas150 50
vishnu-narayanan250 50
jennylia125 25

By GitHub issue

Issue(s)Pull Request(s)Fixer #1Points to #1Fixer #2 (if split)Points to #2
2232 (2002, 2403)2860allejo500stevenhanna625
19462894ashishkamat2791500  
11682881clocklear500  
2182877johnharris85500  
19782941stevenhanna6500  
2619N/A (see comments)allejo250  
27482824bhavin192250  
18092866constanzekratel250  
1456moby/moby 32701gschaetz250  
22772871jadametz250  
7772940jmaitrehenry250  
15802964jmaitrehenry250  
17423036jmaitrehenry250  
16672824johnharris85250  
20362827johnharris85250  
2025moby/moby 32751michaelspets250  
7862833prashant171992250  
24072976subodh-dharma250  
3442961surajnarwade250  
27052944surajnarwade250  
20982893NonCreature0714200jcberthon50
28682879NonCreature0714200shubheksha50
20962888alfonso-cabrera100  
967moby/moby 32723alvin319100  
23982922alvin319100  
9742863audioboxer217100  
2589moby/pull/32735bhavin192100  
9952920clocklear100  
10972886clocklear100  
16832884clocklear100  
21672890clocklear100  
14652885constanzekratel100  
14652885constanzekratel100  
8472861frankgreco100  
4432875gschaetz100  
2005moby/moby 1456gschaetz100  
24782919jmaitrehenry100  
1762972johnharris85100  
14173008johnharris85100  
21162837johnharris85100  
24232910jpooler100  
26592918jpooler100  
21922988Rubab-Syed100  
14482817shubheksha100  
14482817shubheksha100  
21252949, 2959shubheksha100  
24352814shubheksha100  
27322831 (2810)shubheksha100  
13162841stevenhanna6100  
18052993stevenhanna6100  
25922990stevenhanna6100  
13532912surajnarwade100  
16782905surajnarwade100  
3572909, 2911tippexs100  
19042794vikstrous100  
19042794vikstrous100  
26372878wcgcoder100  
26372878wcgcoder100  
20882971bdwill75jmaitrehenry25
8252946, 2957, 2968shubheksha75aboch25
9332968shubheksha75aboch25
20122864allejo50  
14762857, 2971bdwill50  
1673N/Aclocklear50  
22372921constanzekratel50  
10552828jadametz50  
13112843jadametz50  
8502845jaredestroud50  
951moby/moby 32831jmaitrehenry50  
16942790, 2880joaofernandes50  
28012854joeuo50  
25552913jpooler50  
26072832 (closed)jpooler50  
9262849prashant17199250  
25802943prashant17199250  
27832838prashant17199250  
15282858Rubab-Syed50  
1054moby/moby 32803scjane50  
1759moby/moby 32682scjane50  
25752807scjane50  
16702816shubheksha50  
20172819shubheksha50  
21512820shubheksha50  
22812821shubheksha50  
23002815shubheksha50  
25352813shubheksha50  
27242812shubheksha50  
28032808shubheksha50  
27512839stevenhanna650  
13122903surajnarwade50  
24682914surajnarwade50  
18402939t3h2mas50  
27812937tippexs50  
1030N/Aalfonso-cabrera25  
1665N/Aalfonso-cabrera25  
2396N/Aalvin31925  
21262857, 2971bdwill25jmaitrehenry25
10172857, 2971bdwill25  
1319N/Abdwill25  
1977N/Abdwill25  
2067N/Abdwill25  
2239N/Abdwill25  
2510N/Abdwill25  
21302835bhavin19225  
1499N/Aclocklear25  
2587N/Agschaetz25  
2782N/Agschaetz25  
382NOOPjadametz25  
1539N/Ajadametz25  
20772840jadametz25  
16212847jaredestroud25  
22852974 (2869)jmaitrehenry25jennylia25
2113N/Ajmaitrehenry25  
2643moby/pull/32722jmaitrehenry25  
1622N/Ajohnharris8525  
26752916jpooler25  
28622870michaelspets25  
1610N/Aprashant17199225  
16852923prashant17199225  
1850N/Aprashant17199225  
19902857prashant17199225  
2772N/ARubab-Syed25  
811N/Ascjane25  
998N/Ascjane25  
1400moby/moby#32684scjane25  
1477N/Ascjane25  
1548N/Ascjane25  
1559N/Ascjane25  
1680N/Ascjane25  
20822850scjane25  
22052852scjane25  
2052842shubheksha25  
15252809shubheksha25  
16252809shubheksha25  
18442818shubheksha25  
19692822shubheksha25  
1973N/Ashubheksha25  
2108N/Ashubheksha25  
2370N/Ashubheksha25  
2374N/Ashubheksha25  
2390N/Ashubheksha25  
2395N/Ashubheksha25  
24272876shubheksha25  
2430N/Ashubheksha25  
2433N/Ashubheksha25  
2512N/Ashubheksha25  
27342811shubheksha25  
26342846stevenhanna625  
2223N/Avishnu-narayanan25  
2223N/Avishnu-narayanan25  
2202See Issue #2232    
2403See 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