New Format for QA Devel Meetings

[Tim Flink]

After some discussion at devconf and farther discussion at this weeks
qadevel meeting, we're going to try changing a few things about the
meetings to make them faster and a bit more useful.

 - Start holding meetings every week, on Mondays one hour before the QA
   meetings

 - Discuss status and open floor every week, task assignments and
   planning every other week

 - Ask folks to have status #info messages ahead of time instead of
   writing them on-demand during the meeting

The idea behind the last item is to spend less time waiting for folks
to type since that's dead time for everyone else. You don't need to
write a 1000 word essay on what you've been up to for the last week,
just enough to keep everyone aware of what you're working on and the
problems you may have hit.

For some example status statements:

Person 1
  #info finished coding for woozles, review is underway and should be
        done in the next day or two
  #link https://phab.example.org/D125
  #info after the woozle review is done, will start working on
        de-fraggling the stembasins
  #link https://phab.example.org/T421

Person 2
  #info still working to get libcloudmagic to always use the right
        image, ran into some problems with having a consistent path on
        all clients. Will hopefully be ready for review later this week
  #link https://phab.example.org/T395

These are just examples, feel free to expand on them but try to include
relevant links and enough detail for other folks to know what you're
talking.

We'll try this for a couple weeks to see if it works well for us. If it
ends up not working so well, we'll try something else - probably some
form of a shared document that's updated before the meeting.

If you have any concerns or suggestions, this thread would be a great
place to bring them up.

Tim