[all][foundation][ecosystem][tc] External projects under the foundation hat

Thierry Carrez thierry at openstack.org
Thu Jun 23 09:01:52 UTC 2022

Jeremy Stanley wrote:
> On 2022-06-22 16:30:47 -0500 (-0500), Ghanshyam Mann wrote:
> [...]
>> AFAIK, there is no governance requirement from OpenStack to have
>> the project be hosted on OpenDev, nor from OpenInfra
>> Foundation/Bylaws (that is why not all Open Infra projects are on
>> OpenDev). So I do not think we need any change in the governance
>> because we do not even have such restrictions.
> [...]
> If that's the consensus of the TC, then I recommend updating
> https://opendev.org/openstack/governance/src/branch/master/reference/new-projects-requirements.rst
> (particularly the parts where it says "The project uses public code
> reviews on the OpenStack infrastructure" and "The project has core
> reviewers and adopts a test-driven gate in the OpenStack
> infrastructure for changes").

Another thing to take into account is release management: I don't think 
the release team will support releases that bridge across different 
toolchains... one is plenty enough work for our small team.

That's not a "no" since we already have official openstack components 
that are released externally (openstack-puppet modules for example). The 
line we've been holding is that the center of the map[1] (OpenStack 
proper) is part of the "openstack" release, which has to be coordinated 
by the release team, and therefore has to all be on OpenDev. The other 
boxes (operations tooling, lifecycle management, operations tooling, 
client tools, integration enablers) don't necessarily have to. Those can 
be released independently (and off-cycle), and I guess could potentially 
be developed elsewhere, if the TC is comfortable with that.

[1] https://www.openstack.org/openstack-map

Thierry Carrez (ttx)

More information about the openstack-discuss mailing list