[all][tc] Moving PTL role to "Maintainers"

Ben Nemec openstack at nemebean.com
Thu Mar 5 20:24:54 UTC 2020



On 3/5/20 12:29 PM, Kendall Nelson wrote:
> 
> 
> On Thu, Mar 5, 2020 at 3:07 AM Graham Hayes <gr at ham.ie 
> <mailto:gr at ham.ie>> wrote:
> 
>     On 04/03/2020 22:43, Zane Bitter wrote:
>      > On 4/03/20 3:08 pm, Ben Nemec wrote:
>      >>
>      >>
>      >> On 3/4/20 12:57 PM, Zane Bitter wrote:
>      >>> One cannot help wondering if we might get more Nova cores
>     willing to
>      >>> sign up for a 1-week commitment to be the "PTL" than we're getting
>      >>> for a 6-months-and-maybe-indefinitely commitment.
>      >>
>      >> That's a really interesting idea. I'm not sure I'd want to go as
>     short
>      >> as one week for PTL, but shortening the term might make it
>     easier for
>      >> people to commit.
>      >
>      > The key would be to make it short enough that you can be 100%
>     confident
>      > the next person will take over and not leave you holding the bag
>      > forever. (Hi Rico!)
> 
>     And also that the person you hand it off too won't have to hand it back.
>     (Hi Tim!)
> 
>      > I've no idea where the magic number would fall, and it's probably
>      > different for every team. I'm reasonably confident it's somewhere
>      > between 1 week and 6 months though.
> 
>     Yeah - I am not sure the TC should mandate a number - some teams
>     might be OK with the 6 months, while others will need to do 1 or 2 weeks
> 
> 
> I would like to think elections would NOT get held every 1-2 weeks or 
> whatever the chosen PTL term is for a project? Its just a like...signup 
> sheet sort of thing? What if more than one person wants to sign up for 
> the same week( I can't think of why this would happen, just thinking 
> about all the details)?

Yeah, this logistical problem is one of the reasons I didn't want it to 
be a one week rotation. I guess maybe you could solve that by holding 
elections each cycle, but selecting a pool of PTLs who could then trade 
off as desired, but at that point I feel like you're back to not having 
a PTL and instead having a maintainer team. It also seems like a 
potentially complicated election system.

Plus it kind of introduces a problem with the PTL being the point of 
contact for the project. If it's changing weekly then you lose most of 
the benefits of having a single person other people know they can go to.

I'm also wondering if this actually solves the "Hi Rico!" case anyway. 
:-) If a PTL leaves the position because their focus has changed, they 
aren't likely to take it back even if the new person only technically 
signs up for a week. When your PTL candidate pool is exactly 1 then it 
doesn't matter if they're getting elected weekly or six monthly. I guess 
the idea is for this to increase the pool size, and whether that will 
work probably depends on the circumstances for each project.

Anyway, I still think it's an interesting idea, even if I have come up 
with a few new concerns after further consideration. Maybe it's 
something a few teams could experiment with initially and see if it 
works and what timeframes are appropriate?

> 
> -Kendall (diablo_rojo)



More information about the openstack-discuss mailing list