[openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

Flavio Percoco flavio at redhat.com
Tue Aug 26 11:06:17 UTC 2014


On 08/26/2014 11:13 AM, Thierry Carrez wrote:
> OK, now that we have evacuated the terminology issue (we'll use liaison
> or janitor or secretary, not czar), and side-stepped the offtopic
> development (this is not about suppressing PTLs, just a framework to let
> them delegate along predetermined lines if they want to)... which of
> those unnamed roles do we need ?
> 
> In the thread were mentioned:
> - Bugs janitor (keep reported bugs under control)
> - Oslo liaison (already in place)
> - Security mule (VMT first point of contact)
> - Release secretary (communication with integrated release management)
> - Infrastructure contact (for gate and other infra issues)
> - Docs lieutenant (docs point of contact)

Sounds good to me.

> 
> Anita mentioned the "3rd party space" person, but I wonder if it would
> not be specific to some projects. Would it actually be separate from the
> "Infra contact" role ?
> 
> Do we need someone to cover the QA space ? Anything else missing ?

I think we do. We have someone assigned to QA in Zaqar and that has
worked pretty well for us. Malini has been taking care of tempest,
devstack patches and syncing with OpenStack's QA team.

Her efforts there have been a key on getting Zaqar in the gate and
making sure we're up-to-date with the latest changes happening in our QA.

> 
> At first glance I don't think we need a role for logistics (chairing
> meetings and organizing meetups), design summit planning, roadmapping,
> user point of contact, or spokesperson -- as I expect the PTL to retain
> those roles anyway...

+1 for letting the PTL take care of this.

Flavio

-- 
@flaper87
Flavio Percoco



More information about the OpenStack-dev mailing list