<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    i won't speak to whether this confirms/refutes the usefulness of the
    big tent. that said, probably as a by-product of being in non-stop
    meetings with sales/marketing/managers for last few days, i think
    there needs to be better definitions (or better publicised
    definitions) of what the goals of the big tent are. from my
    experience, they've heard of the big tent and they are, to varying
    degrees, critical of it. one common point is that they see it as
    greater fragmentation to a process that is already too slow.<br>
    <br>
    just giving my fly-on-the-wall view from the other side.<br>
    <br>
    <div class="moz-cite-prefix">On 15/06/2015 6:20 AM, Joe Gordon
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAHXdxOf+yiykW38B_FcYgyW4R_gQJHWqD_t60Y_8iOYfko3zQA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>One of the stated problems the 'big tent' is supposed to
          solve is:<br>
        </div>
        <div><br>
        </div>
        <div>'The binary nature of the integrated release results in
          projects outside the integrated release failing to get the
          recognition they deserve. "Non-official" projects are second-
          or third-class citizens which can't get development resources.
          Alternative solutions can't emerge in the shadow of the
          blessed approach. Becoming part of the integrated release,
          which was originally designed to be a technical decision,
          quickly became a life-or-death question for new projects, and
          a political/community minefield.' [0]</div>
        <div><br>
        </div>
        <div>Meaning projects should see an uptick in development once
          they drop their second-class citizenship and join OpenStack.
          Now that we have been living in the world of the big tent for
          several months now, we can see if this claim is true.</div>
        <div><br>
        </div>
        <div>Below is a list of the first few few projects to join
          OpenStack after the big tent, All of which have now been part
          of OpenStack for at least two months.[1]</div>
        <div><br>
        </div>
        <div>* Mangum -  Tue Mar 24 20:17:36 2015<br>
        </div>
        <div>* Murano - Tue Mar 24 20:48:25 2015</div>
        <div>* Congress - Tue Mar 31 20:24:04 2015</div>
        <div>* Rally - Tue Apr 7 21:25:53 2015 </div>
        <div><br>
        </div>
        <div>When looking at stackalytics [2] for each project, we don't
          see any noticeably change in number of reviews, contributors,
          or number of commits from before and after each project joined
          OpenStack.</div>
        <div><br>
        </div>
        <div>So what does this mean? At least in the short term moving
          from Stackforge to OpenStack does not result in an increase in
          development resources (too early to know about the long
          term).  One of the three reasons for the big tent appears to
          be unfounded, but the other two reasons hold.  The only thing
          I think this information changes is what peoples expectations
          should be when applying to join OpenStack.</div>
        <div><br>
        </div>
        <div>[0] <a moz-do-not-send="true"
href="https://github.com/openstack/governance/blob/master/resolutions/20141202-project-structure-reform-spec.rst"
            target="_blank">https://github.com/openstack/governance/blob/master/resolutions/20141202-project-structure-reform-spec.rst</a></div>
        <div>[1] Ignoring OpenStackClent since the repos were always in
          OpenStack it just didn't have a formal home in the governance
          repo.</div>
        <div>[2] <a moz-do-not-send="true"
href="http://stackalytics.com/?module=openstackclient-group&metric=commits"
            target="_blank">h</a><font color="#1155cc"><u><a
                moz-do-not-send="true"
                href="http://stackalytics.com/?module=magnum-group&metric=commits"><a class="moz-txt-link-freetext" href="http://stackalytics.com/?module=magnum-group&metric=commits">http://stackalytics.com/?module=magnum-group&metric=commits</a></a></u></font></div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
gord</pre>
  </body>
</html>