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-lead...
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.