Open Stack

Hello Everyone/PTL,

To improve the interaction/feedback between operators and developers, one of the efforts is to schedule
the 'operator-hour' in developers' events. We scheduled the 'operator-hour' in the last vPTG, which had mixed
productivity feedback[1]. The TC discussed it and thinks we should continue the 'operator-hour' in March
vPTG also. 

TC will not book the placeholder this time so that slots can be booked in the project room itself, and operators
can join developers to have a joint discussion. But at the same time, we need to avoid slot conflict for operators.
Every project needs to make sure its 'operator-hour' does not overlap with the related projects (integrated projects
which might have common operators, for example. nova, cinder, neutron etc needs to avoid conflict) 'operator-hour'.

Guidelines for the project team to book 'operator-hour' 
---------------------------------------------------------------------------------------
* Request in #openinfra-events IRC channel to register the new track 'operator-hour-<your project name>'.
For example, 'operator-hour-nova'

* Once the track is registered, find a spot in your project slots where no other project (which you think is related/integrated
project and might have common operators) has already booked their operator-hour. Accordingly, book with the newly
registered track 'operator-hour-<your project name>'. For example, #operator-hour-nova book essex-WedB1 . 

* Do not book more than one slot (1 hour) so that other projects will have enough slots open to book. If more discussion is
needed on anything, it can be continued in project-specific slots.

We request that every project book an 'operator hour' slot for operators to join your PTG session.
For any query/conflict, ping TC in #openstack-tc or #openinfra-events IRC channel.

[1] https://etherpad.opendev.org/p/Oct2022_PTGFeedback#L32

-gmann