<div dir="ltr"><div><br></div><div>+1000<br></div>very clearly. </div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 15, 2017 at 6:04 PM, Dmitry Tantsur <span dir="ltr"><<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 06/15/2017 11:56 AM, Neil Jerram wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just an immediate reaction: to me "OpenStack-Hosted projects" is not very distinct from "OpenStack projects". So with that terminology I think there will still be confusion (perhaps more).<br>
</blockquote>
<br></span>
This was my reaction as well. For people who misunderstood official vs unofficial, this is going to pose an even bigger challenge, I'm afraid.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
(Or did I misunderstand your new proposal?)<br>
<br>
Regards - Neil<br>
<br>
<br></span><div><div class="h5">
On Thu, Jun 15, 2017 at 10:16 AM Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a> <mailto:<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>><wbr>> wrote:<br>
<br>
Hi everyone,<br>
<br>
Back in 2014, OpenStack was facing a problem. Our project structure,<br>
inherited from days where Nova, Swift and friends were the only game in<br>
town, was not working anymore. The "integrated release" that we ended up<br>
producing was not really integrated, already too big to be installed by<br>
everyone, and yet too small to accommodate the growing interest in other<br>
forms of "open infrastructure". The incubation process (from stackforge<br>
to incubated, from incubated to integrated) created catch-22s that<br>
prevented projects from gathering enough interest to reach the upper<br>
layers. Something had to give.<br>
<br>
The project structure reform[1] that resulted from those discussions<br>
switched to a simpler model: project teams would be approved based on<br>
how well they fit the OpenStack overall mission and community<br>
principles, rather than based on a degree of maturity. It was nicknamed<br>
"the big tent" based on a blogpost[2] that Monty wrote -- mostly<br>
explaining that things produced by the OpenStack community should be<br>
considered OpenStack projects.<br>
<br>
So the reform removed the concept of incubated vs. integrated, in favor<br>
of a single "official" category. Tags[3] were introduced to better<br>
describe the degree of maturity of the various official things. "Being<br>
part of the big tent" was synonymous to "being an official project" (but<br>
people kept saying the former).<br>
<br>
At around the same time, mostly for technical reasons around the<br>
difficulty of renaming git repositories, the "stackforge/" git<br>
repository prefix was discontinued (all projects hosted on OpenStack<br>
infrastructure would be created under an "openstack/" git repository<br>
prefix).<br>
<br>
All those events combined, though, sent a mixed message, which we are<br>
still struggling with today. "Big tent" has a flea market connotation of<br>
"everyone can come in". Combined with the fact that all git repositories<br>
are under the same prefix, it created a lot of confusion. Some people<br>
even think the big tent is the openstack/ namespace, not the list of<br>
official projects. We tried to stop using the "big tent" meme, but (I<br>
blame Monty), the name is still sticking. I think it's time to more<br>
aggressively get rid of it. We tried using "unofficial" and "official"<br>
terminology, but that did not stick either.<br>
<br>
I'd like to propose that we introduce a new concept: "OpenStack-Hosted<br>
projects". There would be "OpenStack projects" on one side, and<br>
"Projects hosted on OpenStack infrastructure" on the other side (all<br>
still under the openstack/ git repo prefix). We'll stop saying "official<br>
OpenStack project" and "unofficial OpenStack project". The only<br>
"OpenStack projects" will be the official ones. We'll chase down the<br>
last mentions of "big tent" in documentation and remove it from our<br>
vocabulary.<br>
<br>
I think this new wording (replacing what was previously Stackforge,<br>
replacing what was previously called "unofficial OpenStack projects")<br>
will bring some clarity as to what is OpenStack and what is beyond it.<br>
<br>
Thoughts ?<br>
<br>
[1]<br>
<a href="https://governance.openstack.org/tc/resolutions/20141202-project-structure-reform-spec.html" rel="noreferrer" target="_blank">https://governance.openstack.o<wbr>rg/tc/resolutions/20141202-pro<wbr>ject-structure-reform-spec.htm<wbr>l</a><br>
[2] <a href="http://inaugust.com/posts/big-tent.html" rel="noreferrer" target="_blank">http://inaugust.com/posts/big-<wbr>tent.html</a><br>
[3] <a href="https://governance.openstack.org/tc/reference/tags/index.html" rel="noreferrer" target="_blank">https://governance.openstack.o<wbr>rg/tc/reference/tags/index.htm<wbr>l</a><br>
<br>
--<br>
Thierry Carrez (ttx)<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br></div></div>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><span class=""><br>
<br>
<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Shake Chen<br><br></div>
</div>