Bugzilla meetings: disappointment, disaster and chaos

[Benton, Kevin]

> "disappointment, disaster and chaos" Here are some of the words which
> appeared to summarize our last Bugzilla meeting which took place
> yesterday. And considering that all our meetings look similar (which
is
> quite true), here is how we could summarize all our meetings on IRC.

... much deleted ...

> This email is not about debating about the lack of a UI module owner.
> This will be in a separate email I plan to write in a few minutes, to
> separate threads. This email is about the way we should manage our IRC
> meetings. Here is an example of how a meeting could take place (thanks
> to vladd for pointing me to this URL):

... more deleted ...

I think it would be fair to say we ought to look at using Roberts Rules
of Order (or some derivative) for the meeting.  As an amateur radio
operator and SkyWarn network manager, we had a protocol for handling
emergency traffic.  It seems the same methodology could be used in our
meetings.  If a moderator were appointed for each meeting, that
moderator could take the lead on directing the conversation.  If someone
had something to say, the participant could simply do "/me raises hand"
in the channel, then politely wait for the moderator to recognize
him/her.  As long as the person recognized continued to speak, they
could pass the "speaker" role to others in the channel.

I know, it sounds like a lot of red tape, but I think it (or something
like it --- please!) would be better than what we have now.  One of the
challenges I've seen in the channel meetings is we get three or four
discussions going at the same time.  It's difficult to understand who is
speaking to whom after a while.

I like that we have a Wiki, but I think there are times when a blog
(Wordpress?) would make more sense. 

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
AMD - ECSD Software Validation and Tools
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.