Meetings/ChairaMeeting - OpenStack
All Wikimedia IRC channels on freenode are the responsibility of the IRC # wikipedia-bag · Bot Approvals Group for discussion / monitoring of bot No public logging – Meeting logs - posavski-obzor.info, 3. You can use the @meet bot to handle requests to schedule, modify and cancel meetings, as well as to look up your schedule. You can send a direct message. Slack-based AI assistant for scheduling, room booking and calendar management. Microsoft Exchange, Google G-Suite & Office compatible.
Take good notes One of the advantages of holding meetings in IRC is that notes come easy. Whether you're chairing a meeting or just participating, use the meetbot capabilities to help the auto-generation of high-quality meeting minutes: Use the topic command to set the current topic. The link command is useful to add clickable URLs to the meeting notes. Use the agreed command to mark that a consensus was reached on a particular point.
To assign work items to someone use the action command. For example, action reed to annotate the wiki pages will be rendered on the meeting minutes as a bullet point of things to do. Use the info command to summarise topics being discussed, for the benefit of the meeting minutes.
Sometimes a discussion evolves rapidly during the meeting so people should add a summary of the topic being discussed; for example info Jane summarized that the issues with the current setup are related to memory consumption.
This will make the minutes very informative at first glance and those that want to have more details will be able to read the full logs. Use the voting feature to enable participants to make decisions democratically. Full documentation of the upstream meetbot is on Debian's wikibut there is also documentation on OpenStack's fork of meetbot.
MeetBot, a supybot plugin for IRC meeting notetaking
You can look at the logs and minutes online. Commands All commands are case-insensitive, and use the prefix character. Not all commands have output. This might be confusing, because you don't know if it's been acted on or not. However, this is a conscious design decision to try to keep out of the way and not distract from the real people. If something goes wrong, you can adjust and have MeetBot re-process the logs later.
The calling nick becomes the chair. If any text is given on the rest of the line, this becomes the meeting topic, see meetingtopic above. You know the drill. MeetBot changes the topic in the channel saving the original topic to be restored at the end of the meeting. The rest of the line is the details. The nick which started the meeting is the owner and can't be de-chaired. The command replies with a list of the current chairs, for verification Chairs only. Provide irc nicks of people involved, and will be both a complete listing of action items, and a listing of action items sorted by nick at the end of the meeting.
This is very useful for making sure this gets done. If MrGreen has said something during the meeting, this will be automatically assigned to him. The URL must be the first thing on the line, separated by a space from the rest of the line, and it will be properly hyperlinked.
This command is automatically detected if the line starts with http: The first example below won't hyperlink properly, the second one won't be automatically detected: This will always appear in the topic in the channel, even as the topic changes. This is the actual "help" command.
MeetBot, a supybot plugin for IRC meeting notetaking
Confusingly, this does not give supybot help. This is only useful in order to make a list of action items be grouped by this nick at the end of the meeting. Only applies to commands which appear in the final output.
All spaces are removed from the rest of the line and the string is converted to lowercase. If meetingname is not provided, it defaults to channel.
Use the @meet bot
Hints on how to run an effective meeting Please contribute to this section! Think about the agenda beforehand, so that attendees are not tempted to jump ahead and discuss future items. This will make it very hard to follow. Liberally use the action command, making sure to include the nick of the person responsible.
It will produce an easy-to-scan list of things to do, as well as a sorted-by-nick version. This will make these things more likely to get done. In the same spirit, liberally use info on important pieces of data. If you think you'll want to refer to it again, info it. Assigning someone to watch the meeting to info other people's lines if they forget usually pays off.
Don't be afraid to tell attendees to wait for a future topic to discuss something. Delegate where possible and have those interested discuss the details after the meeting, where applicable.
- To one-up Slack, Google invites workers to hangout, chat in “Hangouts Chat”
- Hi, I'm Meeting Bot.
No need to take everyone's time if not everyone needs to decide. This only applies to some types of meetings Sometimes one chair to manage the topic at hand, and one chair to manage all people who are going off-topic, can help. Overview Unfortunately, MeetBot seems a bit complex to configure.
In order to keep things straight, keep this in mind: MeetBot has two distinct pieces.
MeetBot - Debian Wiki
This part can run independently, without the supybot plugin. The second part interfaces the core meeting. When reading about how to run MeetBot, keep this in mind, and if something is applicable to meeting. This design split greatly increases modularity a "good thing"and also allows the Replay functionality.
It should also allow other bot plugins to easily be written. Replay functionality Let's say you had a meeting which happened a while ago, and you would like to update the logs to a newer format. If supybot was the only way to use MeetBot, you'd be out of luck. Luckily, there is an independent way to replay meetings: It parses it and processes the meeting, and outputs all of the usual.
This is useful if you want to upgrade your output formats, MeetBot broke and you lost the realtime log and want to generate a summary using your own logfiles, remove or change something in the logs that was incorrect during the meeting.
As such, this is an important feature of MeetBot. However, this does make configuration changes harder. Since the replay function works independent of supybot, any configuration that is done in supybot will be invisible to the replay function.
Thus, we have to have a non-supybot mechanism of configuring MeetBot. There was a supybot way of configuring MeetBot added later, which can adjust most variables.
However, if something is configured here, it won't be seen if a file is replayed. This might be OK, or it might not be, depending on the variable. It works for configuring supybot, too, but requires shell access and a MeetBot reload to change.
Configuration is done by creating a file meetingLocalConfig. It works by automatically, not user-visible subclassing the Config class. Here is a minimal usage example. You need at least this much to make it run. Put this in meetingLocalConfig. It causes a subclass of the main Config object. Thus, you can do some advanced or just crazy things like add a new meeting command, meeting agenda item type, or more.
Some of these ideas are documented under the "Advanced configuration" section below. To reload a configuration in a running supybot, you can just reload the plugin in supybot the module is reloaded. Supybot-based config This is the system that configures MeetBot based on the supybot registry system.
Thus, it can be adjusted by anyone with the proper supybot capabilities. However, the configuration in the supybot registry won't be used if the replay functionality is used see above.
Thus, for example, if you configure the MediaWiki writer using supybot. To enable this system, first the supybot.