This is part 3 of a series of posts about information Fedora produces about what going on in the project.

Up this time: meetings.

Various groups in Fedora meet (usually on IRC) weekly or bi-weekly and discuss issues around their area of the project. Whats the best way to follow all these meetings?

First you can simply have your IRC client idle and log -meeting, -meeting-1 and -meeting-2 on Almost all meetings take place in there. One notable exception is the QA groups blocker bug meetings, those take place in -qa (mostly because they tend to last a long time and they don’t want to block off the meeting channel for others the entire time).

What if you don’t have time to read through all those minutes? Most groups send a summary out to their groups mailing list after each meeting. If you are on each of those lists you can read the summaries there. If you don’t want to join a bunch of lists, there’s a handy meeting minutes list that all groups copy their meeting summaries to:¬† Simply subscribe there and you will get copies of all groups minutes delivered direct to your mailbox.

As with wiki changes or package commits you can also see these changes on the fedmsg bus:

  • #fedora-fedmsg on
  • The desktop/notify based fedmsg-notify applet ( yum install fedmsg-notify and configure/turn it on in settings)
  • The websocket based

You will see when meetings start, when they end, and a pointer to the summary and full logs of each.

IRC meetings are run with the help of the meetbot plugin, which also saves summaries and logs of meetings. If you would like to look at past meetings you can go directly to our meetbot site: Meetings are arranged by “team”, which is the name given to each meeting, or by irc channel and date the meeting took place in.