[openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs
Matthew Treinish
mtreinish at kortar.org
Tue Aug 26 15:28:13 UTC 2014
On Tue, Aug 26, 2014 at 10:04:41AM -0400, Doug Hellmann wrote:
>
> On Aug 26, 2014, at 5:13 AM, Thierry Carrez <thierry at openstack.org> 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)
> >
> > 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 ?
>
> It seems the QA team is also feeling pressure due to the growing community, so it seems wise to ensure every team has someone designated to help with coordinating work on QA projects.
>
Yes I agree, I was actually planning to start a liaison (I guess I'll have to
come up with a different name...) system similar to oslo at some point soon. We
discussed it during the QA meeting last week. [1] My plan was actually going
to be starting a thread on that this week before Thierry beat me to it.
-Matt Treinish
[1] http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-08-21-22.01.html
More information about the OpenStack-dev
mailing list