What's a doc sprint and how can you run one of your own? I ran a three-day doc sprint for the Kubeflow open source community in July 2019. This short presentation describes the event and its outcomes, and gives some tips on running a successful doc sprint.

1. Sprinting for successThe story of an open source doc sprint | @sarahmaddox

2. Goals of doc sprint
● Create useful docs and fix bugs● Engage the Kubeflow community
○ Yes, we have docs
○ No, the docs are not perfect/complete
○ Yes, you can update the docs - here’s how

3. Lightning talks
People like to learn new stuff
People are interested in the patterns of effective tech writing
The lightning talks at the Kubeflow doc sprint:
● How to address the reader in technical documentation
● Passive resistance
● A short guide to writing well
● Kubeflow: a first impression
● Guiding users through a journey

4. Results of doc sprint
Stats:
● 31 pull requests (PRs) closed
● 32 issues fixed
● 6 more PRs under review
● 50 participants (out of 67 registrations)
● Participants already contributing to docs outside
the sprint
More:
● Gave colleagues the opportunity to show impact
● Generated buzz around Kubeflow and docs

5. Results of doc sprint
Kubeflow blog post: bit.ly/2H3Bw5g

6. Contributors to docs repository
Kubeflow Doc Sprint was July 10-12
Activity picked up from that date and has continued strong:
https://github.com/kubeflow/website/graphs/contributors

7. Commits to docs repository
Kubeflow Doc Sprint was July 10-12
Activity picked up from that date and has continued strong:
https://github.com/kubeflow/website/graphs/commit-activity

8. Want to run a doc sprint yourself?
Top tips:
● Start planning early
● Create and collaborate on a wish list / backlog
● Pay attention to the humdrum stuff
● Extra: Learning on the sprint
● Prizes and food
How to run a doc sprint: bit.ly/2H6lt6Z