Hackathon results

_data/hackathon/hackathon-finalists.csv

@@ -0,0 +1,36 @@
+person,Pointsmain,Pointssecondary,subtotal,issuesfixed,bonuspoints,final
+shubheksha,1450,50,1500,31,1250,2750
+allejo,800,,800,3,1000,1800
+johnharris85,1325,,1325,7,250,1575
+jmaitrehenry,975,50,1025,9,,1025
+clocklear,975,,975,7,,975
+stevenhanna6,875,25,900,6,,900
+surajnarwade,800,,800,5,,800
+scjane,375,,375,11,250,625
+bdwill,300,,300,9,250,550
+gschaetz,500,,500,5,,500
+constanzekratel,500,,500,4,,500
+prashant171992,500,,500,7,,500
+ashishkamat2791,500,,500,1,,500
+jadametz,425,,425,6,,425
+NonCreature0714,400,,400,2,,400
+bhavin192,375,,375,3,,375
+jpooler,325,,325,4,,325
+michaelspets,275,,275,2,,275
+subodh-dharma,250,,250,1,,250
+alvin319,225,,225,3,,225
+vikstrous,200,,200,2,,200
+wcgcoder,200,,200,2,,200
+Rubab-Syed,175,,175,3,,175
+alfonso-cabrera,150,,150,3,,150
+tippexs,150,,150,2,,150
+audioboxer217,100,,100,1,,100
+frankgreco,100,,100,1,,100
+jaredestroud,75,,75,2,,75
+joaofernandes,50,,50,1,,50
+joeuo,50,,50,1,,50
+aboch,,50,50,2,,50
+jcberthon,,50,50,1,,50
+t3h2mas,50,,50,1,,50
+vishnu-narayanan,50,,50,2,,50
+jennylia,,25,25,1,,25

_data/hackathon/hackathonresults.csv

@@ -0,0 +1,157 @@
+issue,pr,fixer1,points1,fixer2,points2,comments
+"2232 (2002,  2403)",2860,allejo,500,stevenhanna6,25,"Originally assessed at 100 points, I up'ed this CSS issue to 250 points. Please review file changes in the PR. (25 bonus points to stevenhanna6 for duplicate attempted fix.)
+Issue #2403 had 750 points assigned. Please look at that PR also, should we consider awarding higher point value, e.g., 500 points for this at least?"
+1946,2894,ashishkamat2791,500,,,
+1168,2881,clocklear,500,,,
+218,2877,johnharris85,500,,,
+1978,2941,stevenhanna6,500,,,
+2619,N/A (see comments),allejo,250,,,Already fixed in other PR's. See 2619 for detail. Originally worth 250 points. Should we award anything to allejo for verifying?
+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,,,Misty reduced the points because the fix was much narrower in scope than the request
+2705,2944,surajnarwade,250,,,Not able to merge this yet because the upstream feature is not complete. Granting half the original 500 points.
+2098,2893,NonCreature0714,200,jcberthon,50,"Points value: 250, Fixer #1 PR was accepted, but Fixer #2 submitted some PR's with another approach:
+Correct Debian for ARMHF installation steps #2965
+Raspbian install corrections #2966 - this was closed without merge
+Please review thread on the issue #2098 - Misty awarded 50 of the 200 points for this"
+2868,2879,NonCreature0714,200,shubheksha,50,"NonCreature0714's PR was accepted, as fixes were more thorough, but shubheksha claimed it and started first. We should consider splitting the points, see discussion thread in issue, along with links to shubheksha's PRs. Misty split this 200 / 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,,,"Original points value was 250, but since applicable file is gone, and updates were relatively minimal for a 250 points issue, reduced points value to 100, to recognize work."
+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,"Original contributor created a commit, and second one put that commit on a PR to help with the submission"
+825,"2946, 2957, 2968",shubheksha,75,aboch,25,"aboch provided considerable guidance on these issues, points and mention as Fixer #2. Also this issue (825) is still open, and as it's fairly technical, request another review of it before closing"
+933,2968,shubheksha,75,aboch,25,"aboch provided considerable guidance on these issues, points and mention as Fixer #2"
+2012,2864,allejo,50,,,
+1476,"2857, 2971",bdwill,50,,,three issues addressed in one PR
+1673,N/A,clocklear,50,,,"Considerable research on ""host_integration: request to add script examples for Windows "". Misty awarded 50 points in issue."
+2237,2921,constanzekratel,50,,,
+1055,2828,jadametz,50,,,"After discussion, current plan is not to merge the PR, use one-off example  to illustrate general concepts. (PR is still open.) Points for research on the raised issue."
+1311,2843,jadametz,50,,,
+850,2845,jaredestroud,50,,,
+951,moby/moby 32831,jmaitrehenry,50,,,
+1694,"2790, 2880",joaofernandes,50,,,"Joao did the as far as I can tell, should we give any points to scjane?"
+2801,2854,joeuo,50,,,
+2555,2913,jpooler,50,,,
+2607,2832 (closed),jpooler,50,,,"Topic no longer exists, but full points awarded for thorough fix."
+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,,,"The issue was valued at 500 points, but the PR only changed a couple of instances of the warning style, and I'm still seing a huge amount of notes using the old style. I'm also not giving points to shubheksha, because it seems she didn't submit any PR about this."
+1030,N/A,alfonso-cabrera,25,,,"Verified, fix not needed. Points awarded."
+1665,N/A,alfonso-cabrera,25,,,"Verified, already fixed."
+2396,N/A,alvin319,25,,,
+2126,"2857, 2971",bdwill,25,jmaitrehenry,25,Fixer #2 addressed feedback and took the fix to 100%. Three issues addressed in one PR.
+1017,"2857, 2971",bdwill,25,,,three issues addressed in one PR
+1319,N/A,bdwill,25,,,"Verified only. Was 100 points, awarding 25. Please check thread to see if you agree."
+1977,N/A,bdwill,25,,,
+2067,N/A,bdwill,25,,,
+2239,N/A,bdwill,25,,,
+2510,N/A,bdwill,25,,,Verified fixed already.
+2130,2835,bhavin192,25,,,
+1499,N/A,clocklear,25,,,"Verified, already fixed."
+2587,N/A,gschaetz,25,,,"Verified as fixed only, worth 25 points to begin with, do we award points?"
+2782,N/A,gschaetz,25,,,verified fixed
+382,NOOP,jadametz,25,,,
+1539,N/A,jadametz,25,,,"Verified, already fixed."
+2077,2840,jadametz,25,,,
+1621,2847,jaredestroud,25,,,"PR not merged, as issue related to a superseded tutorial topic/file, 25 points awarded."
+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,,,"Verified, already fixed."
+1685,2923,prashant171992,25,,,
+1850,N/A,prashant171992,25,,,NOOP
+1990,2857,prashant171992,25,,,
+2772,N/A,Rubab-Syed,25,,,"Verified as already fixed. (gschaetz also verified as fixed, but 2 days later. I think those points should go to Fixer #1, Rubab-Syed)"
+811,N/A,scjane,25,,,"This was actually already addressed in PR 1096 by londoncalling, and no PR submitted by Hackathon participant, but awarding points for the review-and-verify step"
+998,N/A,scjane,25,,,"Verified, already fixed. Points awarded."
+1400,moby/moby#32684,scjane,25,,,
+1477,N/A,scjane,25,,,"Verified, already fixed."
+1548,N/A,scjane,25,,,"Verified, already fixed."
+1559,N/A,scjane,25,,,"Verified, already fixed."
+1680,N/A,scjane,25,,,"Verified, already fixed."
+2082,2850,scjane,25,,,
+2205,2852,scjane,25,,,
+205,2842,shubheksha,25,,,
+1525,2809,shubheksha,25,,,
+1625,2809,shubheksha,25,,,
+1844,2818,shubheksha,25,,,"Quite a bit of work done on the PR, which wasn't merged as it was a non-issue. Originally 100 points, what is right amount of points to award? (Awarded 25 pts, but please review)"
+1969,2822,shubheksha,25,,,
+1973,N/A,shubheksha,25,,,
+2108,N/A,shubheksha,25,,,
+2370,N/A,shubheksha,25,,,"Verified as fixed only, worth 25 points to begin with, do we award points?"
+2374,N/A,shubheksha,25,,,"Verified as fixed only, worth 25 points to begin with, do we award points?"
+2390,N/A,shubheksha,25,,,"Verified as fixed only, worth 25 points to begin with, do we award points?"
+2395,N/A,shubheksha,25,,,"Verified as fixed only, worth 25 points to begin with, do we award points?"
+2427,2876,shubheksha,25,,,
+2430,N/A,shubheksha,25,,,
+2433,N/A,shubheksha,25,,,
+2512,N/A,shubheksha,25,,,"Verified as fixed only, worth 25 points to begin with, do we award points?"
+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,,,,,

_data/toc.yaml

@@ -16,7 +16,7 @@ horizontalnav:
   node: samples
 
 guides:
-- title: "Docs hackathon: April 17-22nd, 2017"
+- title: Docs hackathon results
   path: /hackathon/
 - sectiontitle: Get Docker
   section:

hackathon/index.md

@@ -1,22 +1,145 @@
 ---
-title: "Docker Docs Hackathon: April 17-21, 2017"
+title: "Docker Docs Hackathon: Results for Austin, April 17-21, 2017"
 keywords: hack, hackathon, dockercon, austin, 2017
 noratings: true
 ---
 
-## Docs Hackathon: Results coming soon
+## 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!
-This week we will be wrapping up reviews on the remaining pull requests,
-tallying points, and sending out prizes. If you participated, make sure you
+If you participated, make sure you
 [fill out your report](/hackathon/#claiming-your-points) so you can [get your rewards](http://www.cafepress.com/dockerdocshackathon).
 
 We are so humbled and lucky to have a community like you working with us. From
 the bottom of our hearts: thank you!
 
-[Hackathon details](/hackathon/){: class="button outline-btn" style="margin-bottom:20px;margin-right:20px"}[Visit the rewards store](http://www.cafepress.com/dockerdocshackathon){: class="button outline-btn" style="margin-bottom:20px"}
+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](#raw-results).
+
+#### Largest change in a single fix
+
+This award goes to @allejo, for the site-shifting change in
+[pull request #2860](https://github.com/docker/docker.github.io/pull/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 @shubeksha who helped closed a stunning 31 bugs during our
+hackathon. For details of all of @shubeksha's contributions, see the
+[raw results](#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
+- @shubeksha
+- @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!
+
+An interesting note: these bonuses didn't actually change the top 3. Whether
+the bonuses were in play or not, they just added to the point total for these
+three amazing participants who fully earned the top spots.
+
+#### 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](https://9-volt.github.io/bug-life/?repo=docker/docker.github.io).
+
+![results graph](resultsgraph_austin.png)
+*Courtesy of [Bug Life](https://9-volt.github.io/)*
+
+#### 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](burndown.png)
+*Courtesy of [waffle.io](https://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 |
+| ----------- | ------------ | -------- | ----- | ----------- |{% for result in site.data.hackathon.hackathon-finalists %}
+| {{ result.person }} | {{ result.issuesfixed }} | {{ result.subtotal }} | {{ result.bonuspoints }} | {{ result.final }} | {% endfor %}
+
+#### By GitHub issue
+
+| Issue(s) | Pull Request(s) | Fixer #1 | Points to #1 | Fixer #2 (if split) | Points to #2 |
+| -------- | --------------- | -------- | ------------ | ------------------- | ------------ |{% for result in site.data.hackathon.hackathonresults %}
+| {{ result.issue }} | {{ result.pr }} | {{ result.fixer1 }} | {{ result.points1 }} | {{ result.fixer2 }} | {{ result.points2 }} |{% endfor %}
 
 ## Original Hackathon details
 
@@ -41,7 +164,7 @@ All participants who show up in the 4th floor hack room at DockerCon will get
 
 ![DockerCon Docs Hackathon logo](docs-hackathon-1.png)
 
-## Quick links
+### Quick links
 
 - [Event page on DockerCon website](https://dockercon.smarteventscloud.com/connect/sessionDetail.ww?SESSION_ID=116676)
 - [View hackathon bugs on GitHub](https://github.com/docker/docker.github.io/milestone/9)
@@ -50,7 +173,7 @@ All participants who show up in the 4th floor hack room at DockerCon will get
 - [#docs on Slack, if you have questions](https://dockercommunity.slack.com/messages/C2V58TASE)
 - [Moby Mingle offer](https://mobymingle.dockercon.com/offers/27855) to mentor people to contribute to the Hackathon.
 
-## How it works
+### 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
@@ -62,7 +185,7 @@ the points are redeemable for dollars in [our hackathon store](http://www.cafepr
 qualify you for valuable prizes like an Amazon gift card and a personally
 engraved trophy!
 
-## Prizes
+### Prizes
 
 - **All participants**: Points are redeemable for t-shirts, hoodies, sweatshirts,
   mugs, beer steins, pint glasses, flasks, hoodies, stickers, buttons, magnets,
@@ -73,7 +196,7 @@ engraved trophy!
 - **1st place**: A large trophy with a personal engraving, plus store credit,
   plus a $300 Amazon Gift Card
 
-### Bonuses
+#### Bonuses
 
 A select few will get bonuses for being extra special contributors:
 
@@ -81,7 +204,7 @@ A select few will get bonuses for being extra special contributors:
 - Most bugs closed (resolved as no-op or handled): 1000 points
 - Most participation (attended all days): 1000 points
 
-### Choosing a prize
+#### 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.
@@ -93,7 +216,7 @@ prizes.
 
 [View our available prizes](http://www.cafepress.com/dockerdocshackathon){: class="button primary-btn"}
 
-## When?
+### 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.
@@ -102,9 +225,9 @@ is the time when it's possible to claim and resolve bugs.
   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?
+### Where?
 
-### In-person
+#### 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.
@@ -114,13 +237,13 @@ Wednesday from 1pm to 6pm**. We'll be there to answer questions and help you.
   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
+#### Online
 
 Drop into [the community Slack channel for the docs](https://dockercommunity.slack.com/messages/C2V58TASE) and ask any questions
 you have. Otherwise, just go to GitHub and [look at our `hackathon` label](https://github.com/docker/docker.github.io/milestone/9)
 and come here to claim your points when you're done.
 
-## Claiming a bug
+### 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
@@ -128,29 +251,29 @@ saying you claim it. Respect it when you see other comments claiming a bug.
 
 [View available bugs](https://github.com/docker/docker.github.io/milestone/9){: class="button primary-btn"}
 
-## Claiming your points
+### Claiming your points
 
 Simply fill out this form when you're done participating. We'll take it from
 there.
 
 <iframe src="https://docs.google.com/forms/d/e/1FAIpQLSe-vXsZX_u8EoPanCGnBd5eudnaHdJ4dqTumOurt2smCC9gTg/viewform?embedded=true" width="760" height="500" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
 
-## Conversion rate
+### Conversion rate
 
-### Every 10 points is worth $1 USD in the swag store
+#### 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](http://www.cafepress.com/dockerdocshackathon).
 
-## Questions?
+### Questions?
 
 Ask us anything at docs@docker.com or in [the #docs channel on Slack](https://dockercommunity.slack.com/messages/C2V58TASE).
 
 Thank you for participating in the 2017 Docs Hackathon!
 
-## Legal
+### Legal
 
 Eligibility: Participants must be eighteen (18) years of age or older as of the date of your pull request.