<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 31, 2018 at 2:25 AM, James E. Blair <span dir="ltr"><<a href="mailto:corvus@inaugust.com" target="_blank">corvus@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
With recent changes implemented by the OpenStack Foundation to include<br>
projects other than "OpenStack" under its umbrella, it has become clear<br>
that the "Project Infrastructure Team" needs to change.<br>
<br>
The infrastructure that is run for the OpenStack project is valued by<br>
other OpenStack Foundation projects (and beyond). Our community has not<br>
only produced an amazing cloud infrastructure system, but it has also<br>
pioneered new tools and techniques for software development and<br>
collaboration.<br>
<br>
For some time it's been apparent that we need to alter the way we run<br>
services in order to accommodate other Foundation projects. We've been<br>
talking about this informally for at least the last several months. One<br>
of the biggest sticking points has been a name for the effort. It seems<br>
very likely that we will want a new top-level domain for hosting<br>
multiple projects in a neutral environment (so that people don't have to<br>
say "hosted on OpenStack's infrastructure"). But finding such a name is<br>
difficult, and even before we do, we need to talk about it.<br>
<br>
I propose we call the overall effort "winterscale". In the best<br>
tradition of code names, it means nothing; look for no hidden meaning<br>
here. We won't use it for any actual services we provide. We'll use it<br>
to refer to the overall effort of restructuring our team and<br>
infrastructure to provide services to projects beyond OpenStack itself.<br>
And we'll stop using it when the restructuring effort is concluded.<br>
<br>
This is my first proposal: that we acknowledge this effort is underway<br>
and name it as such.<br>
<br>
My second proposal is an organizational structure for this effort.<br>
First, some goals:<br>
<br>
* The infrastructure should be collaboratively run as it is now, and<br>
the operational decisions should be made by the core reviewers as<br>
they are now.<br>
<br>
* Issues of service definition (i.e., what services we offer and how<br>
they are used) should be made via a collaborative process including<br>
the infrastructure operators and the projects which use it.<br>
<br>
To that end, I propose that we:<br>
<br>
* Work with the Foundation to create a new effort independent of the<br>
OpenStack project with the goal of operating infrastructure for the<br>
wider OpenStack Foundation community.<br>
<br>
* Work with the Foundation marketing team to help us with the branding<br>
and marketing of this effort.<br>
<br>
* Establish a "winterscale infrastructure team" (to be renamed)<br>
consisting of the current infra-core team members to operate this<br>
effort.<br>
<br>
* Move many of the git repos currently under the OpenStack project<br>
infrastructure team's governance to this new team.<br>
<br>
* Establish a "winterscale infrastructure council" (to be renamed) which<br>
will govern the services that the team provides by vote. The council<br>
will consist of the PTL of the winterscale infrastructure team and one<br>
member from each official OpenStack Foundation project. Currently, as<br>
I understand it, there's only one: OpenStack. But we expect kata,<br>
zuul, and others to be declared official in the not too distant<br>
future. The winterscale representative (the PTL) will have<br>
tiebreaking and veto power over council decisions.<br></blockquote><div><br></div><div><br></div><div>So the "winterscale infrastructure council"'s purview is quite limited in scope to just govern the services provided?</div><div><br></div><div>If so, would you foresee a need to maintain some kind of "Infrastructure council" as it exists at the moment to be the technical design body?</div><div><br></div><div>Specifically, wouldn't we still want somewhere for the "winterscale infrastructure team" to be represented and would that expand to any infrastructure-related core teams?</div><div><br></div><div>Cheers,<br></div><div>Josh<br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
(This is structured loosely based on the current Infrastructure<br>
Council used by the OpenStack Project Infrastructure Team.)<br>
<br>
None of this is obviously final. My goal here is to give this effort a<br>
name and a starting point so that we can discuss it and make progress.<br>
<br>
-Jim<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br></div></div>