Help Squash OpenStack Docs Bugs without Actually Writing OpenStack Docs

The OpenStack Docs team wants you to...kill some bugs. When are we going to do it? This Friday! How are we going to do it? Are you a stellar tech writer? Great! But, you don't have to write the actual documentation to help. If you know an OpenStack component like the back of your hand, take a look at a bug and suggest what should be written. Here's a breakdown of categories where the help is needed:

• Nova

• Swift

• Xen

• Neutron and Quantum

• Cinder

• Glance

• Keystone

The number of current OpenStack bugs is in the 300s and reflects all of the OpenStack projects. “So, for 10 projects, it's possible for the doc bug number to be 10 times as high as any given project,” says Rackspace Content Stacker and OpenStack Documentation PTL Anne Gentle.

“This is a good opportunity to triage doc bugs that have been stagnant for a while. We've done a lot of reorg lately and it would be nice to triage bugs so contributors know exactly where to fix a given doc bug,” says Anne. “Reviewing carefully will be as important as bug squashing, but we can certainly squish our numbers down.”

Please check out the Doc Bug Day wiki, where you can find all of the information. Let us know if you have any questions! Let’s make the OpenStack Docs the best they can be for the next cycle!