[Fedora QA] #221: Reduce Blocker Bug Review Meeting Length

[Fedora QA]

#221: Reduce Blocker Bug Review Meeting Length
--------------------------+-------------------------------------------------
  Reporter:  tflink       |       Owner:           
      Type:  enhancement  |      Status:  new      
  Priority:  major        |   Milestone:  Fedora 16
 Component:  Trac         |     Version:           
Resolution:               |    Keywords:           
--------------------------+-------------------------------------------------
Comment (by tflink):

 Replying to [comment:8 adamwill]:
 > However, I'm not convinced the section discussed above belongs in the
 meeting SOP. The meeting SOP is supposed to be about _carrying out the
 meeting_, not about other tasks we might do to review blocker bugs. The
 blocker bug SOP just seems like the right place to put a task that's part
 of reviewing blocker bugs but is not part of the blocker bug review
 meetings, to me.

 I guess the question becomes "is poking people part of the meeting
 process?". I thought of it as part of the meeting prep but I don't really
 have strong feelings about it. If we want to detach the two parts, either
 putting it into the blocker SOP or creating a blocker review SOP would
 make more sense.

 Either way, I like the idea of linking to the review information from the
 meeting SOP.

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/221#comment:10>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance