Meeting minutes FESCo (2012-03-26)

[Adam Williamson]

On Fri, 2012-03-30 at 14:29 +0200, David Tardon wrote:
> On Tue, Mar 27, 2012 at 11:16:30AM -0700, Adam Williamson wrote:
> > On Mon, 2012-03-26 at 21:17 +0200, Marcela Mašláňová wrote:
> > 
> > Could I suggest that, if FESCo is going to have a different chair each
> > week, you at least have an SOP for arranging the meetings, so that this
> > kind of thing is done consistently?
> > 
> > Just in the last two weeks we've had a FESCo meeting announcement with
> > an empty topic, and now a minutes post with a different subject from all
> > the previous minutes posts (the 'standard' appears to be "Summary &
> > minutes for today's FESCo meeting (XXXX-XX-XX)") and with no text but an
> > *attachment* of the meetbot summary.
> 
> Sorry, but I really do not understand your problem. I have never had a
> problem recognizing the "meeting notes" email. The same for parsing its
> content. (Actually, I haven't even noticed that the subject is not
> always the same...)
> 
> If it is really so important that the structure of that email is always
> the same, without a sligthest variation, it should be sent directly by
> the bot, without any human intervention. Period.

If I want to quickly look through the results of all the FESCo meetings,
I just search for some word which should always show up in the topic of
those mails but rarely shows up in the topic of other mails. If there's
no process for sending the mail, I've no guarantee or reasonable
expectation I'll actually *find* all the mails this way. It's not about
'slightest variation(s)'. Remember one of the cases I cited was that an
announce got sent with no topic *at all*. How's anyone ever going to
find that one again?

Doing everything by bot is not always possible, if you want the summary
to have some kind of vaguely intelligent hand-editing. But if all you do
is copy/paste the bot summary, then sure, it would make sense just to
automate the process. Less chance of mistakes, saves everyone time.

> Or do we really need a policy/process/guideline for _everything_?

I tend to find it's a good idea. It has lots of benefits and virtually
no drawbacks, except that someone has to find time to write it.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net