I am not sure I understand Steven's statement about "so". The intention of the bylaws is clear, the Technical Committee Approved Release (which is defined in Section 4.1(b)) needs to be licensed under ASL2.0.  The definitions are below:
 
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 Technical Committee 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 Technical Committee Approved Release" as provided in Section 4.1(b)(ii) and (iii).
 
-----Original Message-----
From: Doug Hellmann [mailto:doug@doughellmann.com]
Sent: Thursday, July 09, 2015 12:50 PM
To: legal-discuss
Subject: Re: [legal-discuss] Licensing options for new project (Kolla) entering big tent
 
Excerpts from Richard Fontana's message of 2015-07-09 15:43:55 -0400:
> On Thu, Jul 09, 2015 at 07:24:36PM +0000, Steven Dake (stdake) wrote:
> > Technically the technical committee doesn¹t have a TC release
> > anymore either, as far as I understand.  But IANAL :)
>
> I've been wondering about that. What if anything does "Technical
> Committee Approved Release" mean now?
 
The term is defined in the bylaws as the subset of all OpenStack projects the TC has proposed be included in DefCore's trademark considerations. We have a tag indicating the current list of projects:
http://governance.openstack.org/reference/tags/tc-approved-release.html
 
Doug
 
_______________________________________________
legal-discuss mailing list
legal-discuss@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
 
 Please consider the environment before printing this email.

The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster@dlapiper.com. Thank you.