Open Stack

Thierry,

I think your 1) 2) 3) flow makes sense and aligns with my understanding, and of my reading of the draft.  I just wanted to emphasize that in #3, when you say “a trademark program”:

> 3/ a subset of (2) that the board actually includes in a trademark
> program  -- controlled by the Board

note that, for good reason, you did not say THE trademark program.  As there are currently multiple “trademark programs” (“openstack powered” etc) and that the trend is expected to continue in the future, and the bylaws don’t preclude that (in current form or in the new draft) as I read them.  

Your language doesn’t conflict with my point, I’m just emphasizing the “a” for folks that might think you meant THE (singular).  I find this is sometimes a point of confusion so wanted to cover it here.

Mark






> On Nov 20, 2014, at 3:29 AM, Thierry Carrez <thierry at openstack.org> wrote:
> 
> Richard Fontana wrote:
>> I have a question for the TC about the bylaws. This is really not
>> about a change. The latest Mark Radcliffe draft defines "OpenStack
>> Project" in this paragraph:
>> 
>> "4.13. The management of the technical matters for the OpenStack
>> Project is designed to be a technical meritocracy. The “OpenStack
>> Project” shall consist of the released projects to enable cloud
>> computing and the associated library projects, gating projects, and
>> supporting projects managed by the Technical Committee. The Technical
>> Committee shall designate a subset of the OpenStack Project an
>> “OpenStack TC Approved Release” from time to time. The Board of
>> Directors may determine "Trademark Designated OpenStack Software" from
>> time to time, which will be a subset of the "OpenStack TC Approved
>> Release" as provided in Section 4.1(b)(ii) and (iii)."
>> 
>> The existing definition of "OpenStack Project" is similar:
>> 
>> "The “OpenStack Project” shall consist of a “Core OpenStack Project,”
>> library projects, gating projects and supporting projects."
>> 
>> Is the TC comfortable with those definitions of "OpenStack Project"?
>> Does the whole 'big tent' issue affect that?
>> 
>> Consider that the CLA is implicitly tied to that definition.
> 
> My view is that there are three sets:
> 
> 1/ a superset of "OpenStack" code repositories (produced by the
> OpenStack Community, aligned with the OpenStack mission and adhering to
> the OpenStack way) -- controlled by the TC
> 
> 2/ a subset of (1) that we deem ready / mature / appropriate for the
> board to potentially include in a trademark program -- controlled by the TC
> 
> 3/ a subset of (2) that the board actually includes in a trademark
> program  -- controlled by the Board
> 
> The bylaws call (1) "The OpenStack Project", (2) An “OpenStack TC
> Approved Release”, and (3) "Trademark Designated OpenStack Software".
> 
> My interpretation is that the wording and definitions proposed are
> compatible with both the current structure and the proposed bigtent
> structures. They are definitely an improvement over the current wording,
> where usage of the "Core" word makes it incompatible with both structures.
> 
> Regards,
> 
> -- 
> Thierry Carrez (ttx)
> 
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc