Join the Kubeflow doc fixit at Write the Docs AU conference

Are you coming to the Write the Docs Australia 2019 conference on 14-15 November in Sydney? You’re invited to join us in a two-hour doc fixit on Thursday afternoon, as part of the conference.

Become a contributor to an open source project, learn a bit about how open source works, and help improve the experience of Kubeflow users. All in just two hours!

During the fixit, you’ll add a touch of tech writer shine to the Kubeflow docs. Docs are a super important part of the user experience of any product. Typos and grammatical inconsistencies can spoil that UX. Yet typos and odd syntax creep into any doc set so easily, especially when the doc set is largely written by non tech writers. You can help us set things right.

Where and when

The doc fixit is part of the Write the Docs Australia 2019 conference.

Date and time: Thursday, 14 November, at 1pm.
Location: Water Police Court, Sydney.

Registration

You don’t need to register separately for the doc fixit. Just register for the conference, then come along to the fixit on Thursday.

Your friendly doc fixit helpers

The doc fixit hosts are:

Sarah Maddox (that’s me: Kubeflow tech writer at Google)
Alec Glassford (Tech writer at Google)
Riona MacNamara (Tech writer manager at Google)

What happens at the fixit

Here’s how the fixit will work:

Before the fixit, I’ll create a spreadsheet with a list of doc bugs that need fixing. They’ll mostly be small things: typos, consistency in page structure, capitalisation, and so on.
At the start of the fixit, I’ll give a very short talk introducing the product (Kubeflow) and open source.
Then the group will look at the list of bugs and each person will choose what they want to do.
My assistants and I will help people create GitHub IDs if necessary.
Each person will create an issue in the GitHub issue tracker, describing the bug they’re about to fix.
Each person will then update the relevant doc on GitHub and send a pull request (PR) for review.
My assistants and I will help people sign the contributor licence agreement if necessary. (A bot will prompt them to do this when they send their first PR.)
My assistants and I will review the pull requests and approve each one when it’s ready.
The continuous merge/publish tools on the GitHub project will merge the change and publish the update in the docs.
The contributor will see their update appear in the docs!

I’ll also prepare a guide to for fixit participants, with the basics on how to work in GitHub and how to update the Kubeflow docs. The guides, in combination with the three of us helping during the fixit, should make the fixit fun and a useful learning experience for everyone.

Prerequisites

Here’s how you can prepare for the Kubeflow doc fixit:

Bring a laptop with WiFi capabilities.
If you don’t already have a GitHub account, sign up for one. If you have time to do this before the start of the sprint, that’s great. If not, you can do it during the sprint.
Sign the Google Contributor License Agreement (CLA). If you have time to do this before the start of the sprint, that’s great. If not, you can do it during the sprint.
It’s not mandatory to do any prework, but it will help if you know some Markdown.

References

Details of the Kubeflow doc fixit on the WtD AU site.
The Kubeflow documentation site.
The Kubeflow docs source on GitHub.