| title | keywords | noratings |
|---|---|---|
Docker Docs Hackathon: April 17-21, 2017 |
hack, hackathon, dockercon, austin, 2017 |
true |
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 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!
Hackathon details{: class="button outline-btn" style="margin-bottom:20px;margin-right:20px"}Visit the rewards store{: class="button outline-btn" style="margin-bottom:20px"}
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:
- With the docs team's help in the fourth floor hack room at DockerCon on Tuesday, April 18th and Wednesday, April 19th, from 1-6pm.
- Online! Right here! During the whole week of DockerCon (April 17th - 21st).
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.
- Event page on DockerCon website
- View hackathon bugs on GitHub
- Report your hackathon work
- Browse prizes
- #docs on Slack, if you have questions
- Moby Mingle offer to mentor people to contribute to the Hackathon.
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!
- 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
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
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{: class="button primary-btn"}
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.
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.
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.
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{: class="button primary-btn"}
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>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.
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.