Open Stack

I agree with folks before me.

As my predecessors have stated, throwing all folks into "maintainers"
group/team would kill the responsibility relation.
I believe we could get away with splitting the PTL role into multiple
subroles and actually let each project decide on what these would be
to satisfy that project's needs (but give some guidelines too maybe?).
Also, it would make sense to allow assigning these on primary and
secondary terms.
Both would get "privileges", everyone is obviously responsible for
itself, but primary is responsible if they are currently available and
the role is POC-like.
This way we could both lessen the load on PTL and officially allow vices.
That said, these would need to get assigned and /me not sure how to
best approach this atm.


PS: Deprecate ask.o.o all the way. :-)

-yoctozepto

wt., 3 mar 2020 o 19:42 Michael Johnson <johnsomor at gmail.com> napisał(a):
>
> Putting my former PTL hat on:
>
> I agree with Slawek. I think the PTL role is still important.
>
> That said, the list of responsibilities can get daunting.
>
> I would lean toward re-affirming the "Project Team Leads" statement
> you linked and highlight, in the new contributor guides, that the
> other tasks can be delegated. Maybe we should also re-word that
> statement to clarify or soften the "manage day-to-day operations"
> part.
>
> I think over the history of OpenStack we have had "hands on" PTLs and
> more "delegate" PTLs, both supporting healthy projects.
>
> The lack of a clear "boundary" for the PTL role has probably lead to
> Fear-Uncertainty-and-Doubt. My hope is that the new contributor guide
> goal will help clarify the role.
> This may also highlight tasks that we can remove (deprecate
> ask.openstack.org anyone?).
>
> Michael