Open Stack

Tony Breeds wrote:
> On Tue, Apr 09, 2019 at 09:22:43PM -0500, Eric Fried wrote:
>   
>>> core-team sure, but what is it that a PTL does/can do that a SIG chair
>>> can't?
>>
>> Ack patches in other repositories like release, governance, etc.? But
>> yeah, no reason a SIG chair couldn't also do those things, as long as
>> the vote is recognized the same way.
> 
> I can't speak to the TC but I think that a SIG chair would basically be
> a Liaison in the releases repo and we already know how to handle that.

So.. switching to my release management hat... that actually brings up 
an interesting point, and a good reason to keep PowerVMStackers and 
Winstackers the same.

Project teams basically produce "OpenStack" the software release, while 
SIGs work to make "OpenStack" more relevant for specific cases. While 
SIGs can produce code and can own git repositories, we currently have no 
SIG that owns *deliverables* being made part of the regular OpenStack 
release.

The release team only tracks project teams, and it's simpler if it stays 
that way. It's also a really good delineation as to what is project team 
territory and what is SIG territory.

Both PowerVMStackers or WinStackers currently produce deliverables that 
are released under a cycle-based model and are included in the final 
"OpenStack" release. Switching those teams to become SIGs would have an 
additional consequence: it would remove those deliverables from the 
"OpenStack" release.

So unless those teams actually want that, or the TC decides to do that, 
I don't think we should switch those teams to SIGs.

-- 
Thierry Carrez (ttx)