From aafabdcf6704a6b74dd607d158a45902e50aff5e Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Tue, 23 Jun 2015 10:38:52 -0700 Subject: [PATCH] Document startmeeting in our meetbot fork Change-Id: I08b474a60c688ff61bb931f3170a8699ba165b4f --- doc/source/irc.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/source/irc.rst b/doc/source/irc.rst index 62d8040ff2..c5b77e35fb 100644 --- a/doc/source/irc.rst +++ b/doc/source/irc.rst @@ -89,6 +89,21 @@ https://git.openstack.org/cgit/openstack-infra/meetbot. Manual installation of t plugin is straightforward and documented in that repository's README. OpenStack Infrastructure installs and configures Meetbot through Puppet. +Starting a Meeting +^^^^^^^^^^^^^^^^^^ + +To start a meeting, use the command ``#startmeeting`` followed by the +meeting name. For instance, if you are having a meeting of the +marketing committee use the command ``#startmeeting Marketing +Committee``. This will cause logs to automatically be placed in a +meeting-specific directory on the eavesdrop log server. The output +directory will be automatically lowercased and non-alphanumeric +characters translated to '_', so the above example will record to the +``marketing_committee`` directory. Be sure to use a consistent +meeting name to ensure logs are recorded to the same location. + +This feature is specific to the OpenStack Infrastructure Meetbot fork. + Voting ^^^^^^