Hi everyone,
In a few days some of us will meet in Denver for the 4th OpenStack PTG.
The event is made of several 'tracks' (organized around a specific
team/group 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:
http://ptg.openstack.org/ptg.html
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.
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>
Example:
#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'
commands:
#TRACK next <what will be discussed and when>
Example:
#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
Example:
#ironic clean
How to book reservable rooms
----------------------------
Like at every PTG, in Denver we will have additional reservable space
for extra un-scheduled discussions. In addition, 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 Chef OpenStack (#chef), LOCI (#loci), OpenStackClient (#osc),
Puppet OpenStack (#puppet), Release Management (#relmgt), Requirements
(#requirements), and Designate (#designate).
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>
Example:
#relmgt book Ballroom C-TueA2
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, infra...) 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:
https://git.openstack.org/cgit/openstack/ptgbot/tree/README.rst
--
Thierry Carrez (ttx)
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
In a few days some of us will meet in Denver for the 4th OpenStack PTG.
The event is made of several 'tracks' (organized around a specific
team/group 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:
http://ptg.openstack.org/ptg.html
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.
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>
Example:
#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'
commands:
#TRACK next <what will be discussed and when>
Example:
#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
Example:
#ironic clean
How to book reservable rooms
----------------------------
Like at every PTG, in Denver we will have additional reservable space
for extra un-scheduled discussions. In addition, 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 Chef OpenStack (#chef), LOCI (#loci), OpenStackClient (#osc),
Puppet OpenStack (#puppet), Release Management (#relmgt), Requirements
(#requirements), and Designate (#designate).
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>
Example:
#relmgt book Ballroom C-TueA2
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, infra...) 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:
https://git.openstack.org/cgit/openstack/ptgbot/tree/README.rst
--
Thierry Carrez (ttx)
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators