|
|
|
|
@ -3,12 +3,11 @@
|
|
|
|
|
.. _irc:
|
|
|
|
|
|
|
|
|
|
..
|
|
|
|
|
TODO this entire doc shoudl be reevaluated in light of IRC changes
|
|
|
|
|
|
|
|
|
|
IRC Services
|
|
|
|
|
############
|
|
|
|
|
|
|
|
|
|
The infrastructure team runs a number of IRC bots that are active on
|
|
|
|
|
The OpenDev team runs a number of IRC bots that are active on
|
|
|
|
|
OpenDev and OpenStack related channels.
|
|
|
|
|
|
|
|
|
|
At a Glance
|
|
|
|
|
@ -48,12 +47,11 @@ Access
|
|
|
|
|
------
|
|
|
|
|
|
|
|
|
|
`Register the channel with ChanServ
|
|
|
|
|
<https://freenode.net/news/registering-a-channel-on-freenode>`_ and give the
|
|
|
|
|
infrastructure team account founder access to the channel with::
|
|
|
|
|
<https://www.oftc.net/Services/>`_ and give the
|
|
|
|
|
infrastructure team account master access to the channel with::
|
|
|
|
|
|
|
|
|
|
/msg chanserv register #channel
|
|
|
|
|
/msg chanserv set #channel guard on
|
|
|
|
|
/msg chanserv access #channel add openstackinfra +AFRefiorstv
|
|
|
|
|
/msg chanserv access #channel add opendevaccess master
|
|
|
|
|
|
|
|
|
|
This is good practice project-wide to make sure we keep channels under
|
|
|
|
|
control and is a requirement if you want any of the project bots in
|
|
|
|
|
@ -68,7 +66,7 @@ channel to gerritbot and accessbot, otherwise Zuul will fail tests.
|
|
|
|
|
Meetbot
|
|
|
|
|
=======
|
|
|
|
|
|
|
|
|
|
The OpenStack Infrastructure team runs a slightly modified
|
|
|
|
|
The OpenDev team runs a slightly modified
|
|
|
|
|
`Meetbot <https://wiki.debian.org/MeetBot>`_ to log IRC channel activity and
|
|
|
|
|
meeting minutes. Meetbot is a plugin for
|
|
|
|
|
`Supybot <https://sourceforge.net/projects/supybot/>`_ which adds meeting
|
|
|
|
|
@ -95,10 +93,10 @@ if you don't want a prefix character).
|
|
|
|
|
Meetbot
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
The OpenStack Infrastructure Meetbot fork can be found at
|
|
|
|
|
The OpenDev Meetbot fork can be found at
|
|
|
|
|
https://opendev.org/opendev/meetbot. Manual installation of the Meetbot
|
|
|
|
|
plugin is straightforward and documented in that repository's README.
|
|
|
|
|
OpenStack Infrastructure installs and configures Meetbot through Puppet.
|
|
|
|
|
OpenDev installs and configures Meetbot through Puppet.
|
|
|
|
|
|
|
|
|
|
Starting a Meeting
|
|
|
|
|
^^^^^^^^^^^^^^^^^^
|
|
|
|
|
@ -113,12 +111,12 @@ 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.
|
|
|
|
|
This feature is specific to the OpenDev Meetbot fork.
|
|
|
|
|
|
|
|
|
|
Voting
|
|
|
|
|
^^^^^^
|
|
|
|
|
|
|
|
|
|
The OpenStack Infrastructure Meetbot fork adds simple voting features. After
|
|
|
|
|
The OpenDev Meetbot fork adds simple voting features. After
|
|
|
|
|
a meeting has been started a meeting chair can begin a voting block with the
|
|
|
|
|
``#startvote`` command. The command takes two arguments, a question posed to
|
|
|
|
|
voters (ending with a ``?``), and the valid voting options. If the second
|
|
|
|
|
@ -195,11 +193,12 @@ listening to, including #opendev:
|
|
|
|
|
Log a message to the wiki page.
|
|
|
|
|
|
|
|
|
|
#status notice MESSAGE
|
|
|
|
|
Broadcast a message to all OpenStack channels, and log to the wiki
|
|
|
|
|
page.
|
|
|
|
|
Broadcast a message to all OpenDev and OpenStack channels, and
|
|
|
|
|
log to the wiki page.
|
|
|
|
|
|
|
|
|
|
#status alert MESSAGE
|
|
|
|
|
Broadcast a message to all OpenStack channels and change their
|
|
|
|
|
Broadcast a message to all OpenDev and OpenStack channels and
|
|
|
|
|
change their
|
|
|
|
|
topics, log to the wiki page, and set an alert box on the wiki
|
|
|
|
|
page (eventually include this alert box on status.openstack.org
|
|
|
|
|
pages).
|
|
|
|
|
|
Zuul
2 years ago
committed by