[openstack-dev] [ptg] ptgbot HOWTO for track leads

Thierry Carrez thierry at openstack.org
Thu Feb 15 09:23:38 UTC 2018

Hi everyone,

In two weeks some of us will congregate in Dublin for the 3rd OpenStack
PTG. The event is made of several 'tracks' (organized around a specific
team or a specific theme).

Topics of discussions 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:


As a track lead, it is imperative that you make use of the PTG bot to
communicate what's happening. This is done by joining the #openstack-ptg
IRC channel on Freenode and speaking commands to the bot.

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 cross-project:

#nova now discussing #cinder interactions

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 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

For more information on the bot commands, please see:

Pro tip: designate someone tasked with updating the PTGbot with what's
currently being discussed, so that you can focus on keeping the
discussion on track.

You can play with the bot in the coming week, data will be reset on the
Sunday before the event starts.

Thierry Carrez (ttx)

More information about the OpenStack-dev mailing list