yeah. I agree.

I think it best if we determine who is doing the summary log at the beginning of a meeting (at least) and reminding them, and then require that it be done before the end of the day that the meeting is on.

I personally find it much easier to do them at the same time as the meeting is happening and send right after the meeting is over. Thats much easier than looking back on it later and trying to remember/look at everything.

Suggestion: The Board does this now using a Gobby session. Everyone is responsible for helping record the minutes, and then at the end of the meeting, a member leaving means they agree to the notes in their current or any subsequent form.

This is not without its pitfalls. It's possible for people to shirk recording minutes in favor of doing whatever it is they're doing on the other end of the phone, such as email or IRC. The idea is that someone out of the 10-11 people on the call should be able to capture what's going on correctly, or fix someone else's summary. In practice, I find I sometimes have to remind people mid-call that they need to help.

If I see a very multi-colored Gobby document I know things have gone very well in this regard. If it starts looking monochromatic, people need to step up and help.

The Board uses a private Gobby because we are sometimes recording sensitive issues which are expurgated from the public notes. Since FESCo doesn't suffer from that yoke, you could use gobby.fedoraproject.org effectively.

Anyway, this has been my experience with using Gobby, and FESCo's free to find whatever way works for them to get minutes published in an efficient and transparent manner.

I propose that we try what Paul suggested next week. For the release planning meetings, we do much the same thing, and it works well. The key to this working is that everyone needs to be connected to gobby BEFORE the meeting.

We can try that if folks like. I would also be willing to just do the minutes myself if folks prefer.

I have loaded the
http://wiki.debian.org/MeatBot
plugin into my irc bot 'fedbot'.

This plugin has a number of nice features for meetings, including generating the summary and logs and placing them in a local area on the end of the meeting.

You can test it out in #fedbot if you like.
We can also try it out for tomorrow's meeting if thats ok.

If it works out, we can add it to zodbot (or have a dedicated meeting bot) that uploads the logs/summary to a fedora machine (my bot only uploads to my personal machine here).

So have we decided to use MeatBot (fedbot) for this? I'll leave this open to track getting the plugin into Fedora/EPEL and part of my best friend zoddie :D

I have exchanged several emails with the upstream author of this plugin
(who is a debian developer, as they are going to be using this plugin there) and
have some things to report:

• He's not ready for a formal release yet and would prefer if I wait
  and package it when it's more mature.
• The name will be changed from MeatBot to MeetBot (the name of their
  current tcl plugin) as soon as it's more mature.
• He's looking into adding code to post to mediawiki, but is low on
  time. Patches welcome.

So, moving forward:

We can't really add this to zodbot currently as it's not yet packaged
(I don't think). So it would need to continue to just run on my server,
which is fine with me, but means logs are on my machine and not an
official fedora box. (Although I could rsync them easily).

It currently does not post to the wiki. Only logs locally.
(But it's being looked at).

Given those things, should we continue to use it?
I can rsync them up to my fedorapeople location or somewhere easily.

Thoughts?

MeetBot is now packaged in EPEL and running on zodbot. It seems to be working well as a way to record meetings, for various groups.

Closing this ticket, YAY!