<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 16, 2015 at 9:16 PM, Georgy Okrokvertskhov <span dir="ltr"><<a href="mailto:gokrokvertskhov@mirantis.com" target="_blank">gokrokvertskhov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">In Murano project we do see a positive impact of BigTent model. Since Murano was accepted as a part of BigTent community we had a lot of conversations with potential users. They were driven exactly by the fact that Murano is now "officially" recognized in OpenStack community. It might be a wrong perception, but this is a perception they have.<div>Most of the guys we met are enterprises for whom catalog functionality is interesting. The problem with enterprises is that their thinking periods are often more than 6-9 months. They are not individuals who can start contributing over a night. They need some time to create proper org structure changes to organize development process. The benefits of that is more stable and predictable development over time as soon as they start contributing.</div></div></blockquote><div><br></div><div>Sure, I was ignoring the question about potential users, and only looking at 'development resources'. Although I am interested in seeing how the user's view of being official changes now that it means something very different (governance wise) in the big tent. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><br></div><div>Thanks</div><div>Gosha<br><div><br></div><div> </div></div></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Tue, Jun 16, 2015 at 4:44 AM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You may also find my explanation about the Big Tent helpful in this interview with Niki Acosta and Jeff Dickey:<br>
<br>
<a href="http://blogs.cisco.com/cloud/ospod-29-jay-pipes" rel="noreferrer" target="_blank">http://blogs.cisco.com/cloud/ospod-29-jay-pipes</a><br>
<br>
Best,<br>
-jay<div><div><br>
<br>
On 06/16/2015 06:09 AM, Flavio Percoco wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 16/06/15 04:39 -0400, gordon chung wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
i won't speak to whether this confirms/refutes the usefulness of the<br>
big tent.<br>
that said, probably as a by-product of being in non-stop meetings with<br>
sales/<br>
marketing/managers for last few days, i think there needs to be better<br>
definitions (or better publicised definitions) of what the goals of<br>
the big<br>
tent are. from my experience, they've heard of the big tent and they<br>
are, to<br>
varying degrees, critical of it. one common point is that they see it as<br>
greater fragmentation to a process that is already too slow.<br>
</blockquote>
<br>
Not saying this is the final answer to all the questions but at least<br>
it's a good place to start from:<br>
<br>
<a href="https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/the-big-tent-a-look-at-the-new-openstack-projects-governance" rel="noreferrer" target="_blank">https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/the-big-tent-a-look-at-the-new-openstack-projects-governance</a><br>
<br>
<br>
<br>
That said, this is great feedback and we may indeed need to do a<br>
better job to explain the big tent. That presentation, I believe, was<br>
an attempt to do so.<br>
<br>
Flavio<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
just giving my fly-on-the-wall view from the other side.<br>
<br>
On 15/06/2015 6:20 AM, Joe Gordon wrote:<br>
<br>
One of the stated problems the 'big tent' is supposed to solve is:<br>
<br>
'The binary nature of the integrated release results in projects<br>
outside<br>
the integrated release failing to get the recognition they deserve.<br>
"Non-official" projects are second- or third-class citizens which<br>
can't get<br>
development resources. Alternative solutions can't emerge in the<br>
shadow of<br>
the blessed approach. Becoming part of the integrated release,<br>
which was<br>
originally designed to be a technical decision, quickly became a<br>
life-or-death question for new projects, and a political/community<br>
minefield.' [0]<br>
<br>
Meaning projects should see an uptick in development once they drop<br>
their<br>
second-class citizenship and join OpenStack. Now that we have been<br>
living<br>
in the world of the big tent for several months now, we can see if<br>
this<br>
claim is true.<br>
<br>
Below is a list of the first few few projects to join OpenStack<br>
after the<br>
big tent, All of which have now been part of OpenStack for at least<br>
two<br>
months.[1]<br>
<br>
* Mangum - Tue Mar 24 20:17:36 2015<br>
* Murano - Tue Mar 24 20:48:25 2015<br>
* Congress - Tue Mar 31 20:24:04 2015<br>
* Rally - Tue Apr 7 21:25:53 2015<br>
<br>
When looking at stackalytics [2] for each project, we don't see any<br>
noticeably change in number of reviews, contributors, or number of<br>
commits<br>
from before and after each project joined OpenStack.<br>
<br>
So what does this mean? At least in the short term moving from<br>
Stackforge<br>
to OpenStack does not result in an increase in development<br>
resources (too<br>
early to know about the long term). One of the three reasons for<br>
the big<br>
tent appears to be unfounded, but the other two reasons hold. The<br>
only<br>
thing I think this information changes is what peoples expectations<br>
should<br>
be when applying to join OpenStack.<br>
<br>
[0] <a href="https://github.com/openstack/governance/blob/master/resolutions/" rel="noreferrer" target="_blank">https://github.com/openstack/governance/blob/master/resolutions/</a><br>
20141202-project-structure-reform-spec.rst<br>
[1] Ignoring OpenStackClent since the repos were always in<br>
OpenStack it<br>
just didn't have a formal home in the governance repo.<br>
[2] h <a href="http://stackalytics.com/?module=magnum-group&metric=commits" rel="noreferrer" target="_blank">http://stackalytics.com/?module=magnum-group&metric=commits</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
--<br>
gord<br>
<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
__________________________________________________________________________<br>
<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
<br>
<br>
<br>
<br>
__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
<br>
__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr"><font color="#999999"><span style="background-color:rgb(255,255,255)">Georgy Okrokvertskhov<br>
Architect,<br><span style="font-family:arial;font-size:small">OpenStack Platform Products,</span><br>
Mirantis</span><br>
<a href="http://www.mirantis.com/" target="_blank">http://www.mirantis.com</a><br>
Tel. <a href="tel:%2B1%20650%20963%209828" value="+16509639828" target="_blank">+1 650 963 9828</a><br>
Mob. <a href="tel:%2B1%20650%20996%203284" value="+16509963284" target="_blank">+1 650 996 3284</a></font><br></div></div>
</font></span></div>
<br>__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>