From: Robert Buchholz <rbu@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] Metting log bot
Date: Thu, 9 Jul 2009 14:08:16 +0200 [thread overview]
Message-ID: <200907091408.41535.rbu@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 426 bytes --]
Hi council,
I don't know if it has been discussed before (I have not found anything
in the archives), but Debian and Fedora use what seems to be a pretty
nice bot to log meetings, generate statistics and store todos and
decisions. I'm forwarding a Fedora announcement, you can see an example
output here:
http://meetbot.fedoraproject.org/fedora-meeting/2009-06-30/fedora-meeting.2009-06-30-14.59.html
Robert
[-- Attachment #1.2: Jon Stanley <jonstanley@gmail.com>: New meeting logging facility available --]
[-- Type: message/rfc822, Size: 6549 bytes --]
From: Jon Stanley <jonstanley@gmail.com>
To: fedora-announce-list@redhat.com
Subject: New meeting logging facility available
Date: Wed, 8 Jul 2009 21:34:38 -0400
Message-ID: <da159fda0907081834s1cde1601j68744c8765245ac2@mail.gmail.com>
This evening, Kevin Fenzi and I finished the integration of the
supybot plugin MeetBot into our beloved zodbot (for those that don't
know, zodbot is a very useful bot on the freenode IRC network, which
provides a number of services for Fedora contributors).
This plugin was developed by our friends over at Debian, who are using
it to record their meetings as well. We would like all Fedora
meetings to be recorded using this mechanism, such that there's one
format for all of the logs. Complete documentation can be found at
http://wiki.debian.org/MeetBot, and a summary of important commands is
below.
Some limitations right now are that it does not post to the wiki, it
only logs to flat files on the server hosting zodbot. These files are
available at http://meetbot.fedoraproject.org - the format (as of this
evening) for the layout of these files is <channel>/<date>/<time-based
filename>..
This plugin will work in any channel in which zodbot is present. If
your team would like zodbot in your channel (it should be in most
already), ping ricky, jds2001 (me), or nirik in #fedora-admin and
we'll get him right over there!
Some important commands:
#startmeeting <topic> - this starts a meeting about whatever topic
you provide. The person running this command is automatically given
chair powers.
#chair - provide a space separated list of chairs for the meeting.
These all have equal powers. You may not need more than one.
#topic - this sets the sub-topic for the meeting - i.e. what you're
talking about that moment. This is used to organize the minutes.
Only a chair can use this command.
#agreed - this command can be used by chairs in order to denote
something that was agreed upon during the meeting
#action - this records an action item from the meeting. If a nick is
present, it is assigned to that person in the minutes (note - it only
knows about nicks which have spoken to that point. For instance, if I
weren't at the meeting and you just assigned an action item to me, it
wouldn't come out that way in the minutes. The workaround for this
would be to use #nick to make the nick known).
#endmeeting - ends the meeting and prints URL's to the logs and
minutes of the meeting.
As always, feel free to let me know if you have questions or problems
using zodbot!
Thanks!
-Jon
--
fedora-announce-list mailing list
fedora-announce-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-announce-list
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2009-07-09 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 12:08 Robert Buchholz [this message]
2009-07-09 13:41 ` [gentoo-council] Metting log bot Luca Barbato
2009-07-09 13:54 ` Nirbheek Chauhan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200907091408.41535.rbu@gentoo.org \
--to=rbu@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox