Documentation/BugTriageDay

Date: Wednesday, 17th December 2014

Time: Whenever you're awake!

Communications: #openstack-doc on the Freenode IRC Network

Goal: Triage at least 30 doc bugs in openstack-manuals and openstack-api-site.

How to Participate

 * 1) Before the day, try to become familiar with how to triage doc bugs by reading  about our bug triaging guidelines.
 * 2) Make sure you have joined the doc bugs group in Launchpad: [].
 * 3) Get to know the Cross-Project Liaison for Docs for each project by reading  the list of Docs liaisons.
 * 4) On the day join #openstack-doc on the Freenode IRC Network so you can communicate with everyone.
 * 5) Pick up one or more of the tasks below:

Understanding Doc Bugs

 * 1) The Launchpad bug area openstack-manuals is the default for doc bugs and should be used for docs sourced from these repositories:
 * 2) * clouddocs-maven-plugin
 * 3) * openstack-doc-tools
 * 4) * openstack-manuals,
 * 5) * operations-guide
 * 6) * security-doc
 * 7) Launchpad bug area openstack-api-site is used for all the API repositories:
 * 8) * api-site (includes the API Complete Reference)
 * 9) * compute-api (going to openstack-attic)
 * 10) * identity-api (going to openstack-attic)
 * 11) * image-api (going to openstack-attic)
 * 12) * netconn-api (going to openstack-attic)
 * 13) * object-api (going to openstack-attic)
 * 14) * volume-api (going to openstack-attic)

Triaging Doc Bugs
The best thing you can do on a bug triaging day is to write comments on a doc bug that are detailed enough for anyone to walk up and create a fix. Ask for docs team or liaison help all day on IRC.

The lists of bugs are here:
 * Bugs in OpenStack Manuals
 * Bugs in the API Site and API References


 * 1) If you sense the bug is fairly easy or straightforward to fix once it is triaged, tag it with "low-hanging-fruit" to indicate someone could pick it up easily.
 * 2) If a bug is marked Confirmed, look closely at it, research it to see if you can triage it, then set it to Triaged.
 * 3) Most of our bugs are tagged meaningfully, but do add tags if you think they are missing. Here are some tag ideas.

If you know a part of OpenStack well, write any suggested text or hints on how to doc something up on a particular bug. Here's a breakdown by category:
 * Nova
 * Swift
 * Xen-related
 * neutron
 * Cinder
 * Glance
 * Keystone

We also tag doc tooling bugs in these Launchpad projects with: doc-builds or doc-tools. These are not a priority for triaging. We want to focus on content doc bugs.

Close old fixed bugs
Old bugs are nasty. Even when they are long dead, they clog bug views and render the lists unusable. Just look at old bugs and check if they still apply ! If they don't, close them as FixReleased (if you can pinpoint when they were fixed) or Invalid (if you can't).

Getting Help
If you need assistance with knowing where something goes, fixing build failures, or approving reviews, please contact the following people on #openstack-doc during the allotted time.

Note that if you can't triage a doc bug, just move on to the next one! With nearly 600 doc bugs there are plenty to go around.

Time zone conversions