Bugzilla Developer Meetings (was: RE: New Bugzilla Roadmap)

[Benton, Kevin]

> On Mon, 2006-01-30 at 13:49 -0500, David Miller wrote:
> > OK, this sounds like a good time...  Today is probably too soon to
> > expect people to make it on short notice though, since that's in
about
> > 10 minutes. :)  How about tomorrow?  or is that still too soon?
> 
> 	I think even tomorrow is too soon. :-) I think it would be best
to
> have
> a week's advance notice of the time.

I agree that advance notice is important.  I also think it's going to be
important to have an agenda for the meeting and to distribute that
agenda to potential attendees prior to the meeting.  I would much rather
attend a meeting that has stated goals than one without goals.  Meetings
with stated agendas give attendees time to prepare for what's planned to
be discussed.

Has anyone given thought yet to how the meeting will be run?  What
structure will be used?  How will order be maintained (preventing
communications break-down)?  Who will take notes?  Who will lead the
meeting?  Where will the meeting be held?  Should we have a special
channel for the meeting?  Will a Wiki be set up prior to the meeting for
document sharing?  Where will the meeting notes be posted for those who
are not able to attend?  How does one sign up for the meeting
notifications?

I ask these questions because I want to be able to justify to my boss
why I'm planning to spend a block of time on the IRC rather than working
on code that needs to be modified here.

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
 
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.