[Rust-VMM] [ptg] ptgbot HOWTO

Thierry Carrez thierry at openstack.org
Wed Apr 24 11:18:25 UTC 2019

Hi everyone,

In a few days, some contributor teams will meet in Denver for the 5th 
Project Teams Gathering. The event is organized around separate 'tracks' 
(generally tied to a specific team/group).

Topics of discussion are loosely scheduled in those tracks, based on the 
needs of the attendance. This allows to maximize attendee productivity, 
but the downside is that it can make the event a bit confusing to 
navigate. To mitigate that issue, we are using an IRC bot to expose 
what's happening currently at the event at the following page:


It is therefore useful to have a volunteer in each room who makes use of 
the PTG bot to communicate what's happening. This is done by joining the 
#openstack-ptg IRC channel on Freenode and voicing commands to the bot.

Usage of the bot is of course optional, but in past editions it was 
really useful to help attendees successfully navigate this dynamic event.

How to keep attendees informed of what's being discussed in your room

To indicate what's currently being discussed, you will use the track 
name hashtag (found in the "Scheduled tracks" section on the above 
page), with the 'now' command:

#TRACK now <what's currently being discussed>

#swift now brainstorming improvements to the ring

You can also mention other track names to make sure to get people 
attention when the topic is transverse:

#ops-meetup now discussing #cinder pain points

There can only be one 'now' entry for a given track at a time. To
indicate what will be discussed next, you can enter one or more 'next'

#TRACK next <what will be discussed and when>

#api-sig next at 2pm we'll be discussing pagination woes

Note that in order to keep content current, entering a new 'now' command
for a track will automatically erase any 'next' entry for that track.

Finally, if you want to clear all 'now' and 'next' entries for your
track, you can issue the 'clean' command:

#TRACK clean

#ironic clean

How to book reservable rooms

Like at every PTG, in Denver we will have additional reservable space 
for extra un-scheduled discussions. Two of those rooms (Ballroom 4 and 
Room 112) are equipped with a projector, so if your discussion would 
benefit from projection, you can also book time there. Finally, some of 
the smaller teams do not have any pre-scheduled space, and will solely 
be relying on this feature to book the time that makes the most sense 
for them. Those teams are the OpenStack release management team 
(#release-management) and requirements team (#requirements), the 
Extended Maintenance SIG (#extended-maint-sig), the Security SIG 
(#security-sig), the Bare Metal SIG (#baremetal-sig) and the 
Interoperability working group (#interop-wg).

The PTG bot page shows which track is allocated to which room, as well 
as available reservable space, with a slot code (room name - time slot) 
that you can use to issue a 'book' command to the PTG bot:

#TRACK book <slot code>

#release-management book Room 112-ThuA1

Any track can book additional space and time using this system. All
slots are 1h45-long. If your topic of discussion does not fall into an 
existing track, it is easy to add a track on the fly. Just ask PTG bot 
admins (ttx, diablo_rojo...) on the channel to create a track for you 
(which they can do by getting op rights and issuing a ~add <TRACK> command).

For more information on the bot commands, please see:

Let me know if you have any additional questions.

Thierry Carrez (ttx)

More information about the Rust-vmm mailing list