Blocker Bug Voting and Conversation

[Tim Flink]

I don't think that anyone is a huge fan of the current blocker bug
process. I realize that the people most affected by the process are
really busy right now but I also think that it wouldn't be a bad thing
to start a conversation while the process is active and at its most
painful. I don't really want this to devolve into a long flamewar about
how bad the process is (I probably spend more time with the process
than most people, I know it has issues) but I would like to start a
conversation about some of it.

This conversation affects both test@ and devel@, so please try to send
replies to both lists.

I'm trying to think through methods to improve the process but I
ended up with some questions that need more than just my input:
How useful is it to have the blocker votes and conversation in the bug?
I think that it needs to be public, archived and easily accessible from
affected bugs but I'm questioning the value of having conversations
about blocker status within bugzilla comments.

Affected Devs:
 - Do you find the blocker related conversations in bugzilla comments
   helpful? Annoying? Don't really care?

 - Do you want to be more involved in the blocker process? Less
   involved and just notified about status changes?

Affected Voters:
 - Do you vote on blocker status in bug comments?

 - Would you vote on blocker status more often if you could easily vote
   outside of meetings?

 - Do you want to receive status updates on the bugs you vote on, even
   if those status updates don't deal directly with blocker status?

Anyhow, helpful thoughts would be appreciated. Hopefully we can improve
the process so that it's less painful for everyone and maybe even more
useful (at the very least, less difficult to understand).

Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20121203/7dcf9b1e/attachment.sig>