Jump to: navigation, search


< Documentation
Revision as of 21:47, 9 September 2014 by Sdeaton2 (talk | contribs)

Date: Tuesday, 9th September 2014

Time: Whenever you're awake!

Communications: #openstack-doc on the Freenode IRC Network

Aim: Not yet set (the previous day exceeded a target of 100 bugs closed)

How to Participate

  1. Before the day, try to become familiar with How To Contribute to the Documentation
  2. On the day join #openstack-doc on the Freenode IRC Network so you can communicate with everyone
  3. Pick up one or more of the tasks below:

Fixing Bugs

The best thing you can do on a bug squashing day is to kill a live one. Just look at the list of Confirmed or Triaged and pick your target. Submit a change that fixes it. Ask for review help on the channel.

The lists of bugs are here:

  1. If you only feel comfortable making small changes, look for bugs with the tag low-hanging-fruit
    1. If you can't find low-hanging-fruit to fix, you can also try to complete tasks described at BugTriage
  2. Next, bugs marked "Triaged" have some helpful hints in them to assist
  3. However, most bugs are marked Confirmed

Providing information to the doc team

You don't have to edit documentation to assist on this bug day. 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:

We also tag doc tooling bugs in these Launchpad projects with: doc-builds or doc-tools.

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).

Triage bugs

If you are an OpenStack operator or developer, you might be able to provide helpful information about how to write up a particular topic. Just paste what you can in the bug and hit submit


  • Regenerate all configuration tables since many bugs can be marked as fixed after the regeneration and the regeneration patch might not mark all bugs as fixed.

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 get something to build - just submit it for review anyway! We can take a look at fix it.

UTC Mentors Timezone handover
2300 Loquacity, Sam-I-Am Australia
0000 Loquacity, Sam-I-Am
0100 Loquacity, Sam-I-Am Asia
0200 Loquacity, Sam-I-Am
0300 Loquacity, Sam-I-Am
0400 Loquacity, gpocentek India
0500 Loquacity, gpocentek
0600 AJaeger
0700 AJaeger
0800 AJaeger Europe
1400 annegentle, Sam-I-Am US-East
1500 annegentle, Sam-I-Am US-Central
1600 annegentle, Sam-I-Am
1700 annegentle, Sam-I-Am US-West
1800 annegentle, Sam-I-Am, gpocentek
1900 AJaeger, annegentle, Sam-I-Am, gpocentek
2000 annegentle, Sam-I-Am
2100 Loquacity, annegentle, Sam-I-Am
2200 Loquacity, annegentle, Sam-I-Am

Time zone conversions