Open Stack

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

On Tue, Mar 3, 2020 at 9:22 AM Herve Beraud <hberaud at redhat.com> wrote:
>
>
>
> Le mar. 3 mars 2020 à 18:13, Graham Hayes <gr at ham.ie> a écrit :
>>
>> On 02/03/2020 21:45, Mohammed Naser wrote:
>> > Hi everyone:
>> >
>> > We're now in a spot where we have an increasing amount of projects
>> > that don't end up with a volunteer as PTL, even if the project has
>> > contributors .. no one wants to hold that responsibility alone for
>> > many reasons.  With time, the PTL role has become far more overloaded
>> > with many extra responsibilities than what we define in our charter:
>> >
>> > https://governance.openstack.org/tc/reference/charter.html#project-team-leads
>> >
>> > I think it's time to re-evaluate the project leadership model that we
>> > have.  I am thinking that perhaps it would make a lot of sense to move
>> > from a single PTL model to multiple maintainers.  This would leave it
>> > up to the maintainers to decide how they want to sort the different
>> > requirements/liaisons/contact persons between them.
>> >
>> > The above is just a very basic idea, I don't intend to diving much
>> > more in depth for now as I'd like to hear about what the rest of the
>> > community thinks.
>> >
>> > Thanks,
>> > Mohammed
>> >
>>
>> Yeah, this is a tough spot.
>>
>> When we have talked about this in the past, we have theorized the role
>> could be stripped back to "Project Liaison to the TC". As noted in other
>> replies, the worry is that there is a lot of work that goes to the PTL
>> by default currently.
>>
>> We should look at this work, and if is it not bringing value, just
>> remove it.
>>
>> If it is bringing value, how do we ensure that someone does it?
>>
>> My consistent worry with the removal of the PTL single point
>> of contact, is that without it, this work will get missed.
>
>
> I agree the best way to miss something is to spread responsibility between members, everybody thinks that others are watchful.
>
>
> --
> Hervé Beraud
> Senior Software Engineer
> Red Hat - Openstack Oslo
> irc: hberaud
> -----BEGIN PGP SIGNATURE-----
>
> wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+
> Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+
> RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP
> F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G
> 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g
> glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw
> m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ
> hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0
> qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y
> F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3
> B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O
> v6rDpkeNksZ9fFSyoY2o
> =ECSj
> -----END PGP SIGNATURE-----
>