<div dir="ltr">
<p class="">About 4(1)(b)(iii):</p><p class="">===============</p><p class=""><a name="_cp_text_1_1"></a>After the OSP New Definition Date, the scope of the <font color="#0000ff"><u>Core</u></font>
OpenStack Project <font color="#0000ff"><u>which is an integrated
release</u></font> shall be determined as set forth in Section
4.13(c)(ii). The use of the OpenStack trademarks on the
<font color="#ff0000"><strike>OpentStack</strike></font><font color="#0000ff"><u>OpenStack</u></font>
Project shall be defined in the Trademark Policy in Section 7.3.</p><p class="">===============</p><p class="">The addition of "which is an integrated release" seems redundant to me, since "Core OpenStack Project" is defined in 4(1)(b)(iii) as "the software modules which are part of an integrated release". It might not be redundant if "which is an" is different from "which are part of", but if that is the case, then I think that distinction should be elaborated/made explicit - as it currently stands it is somewhat confusing.</p>
<p class="">Luis</p></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 8, 2014 at 12:48 PM, Mark McLoughlin <span dir="ltr"><<a href="mailto:markmc@redhat.com" target="_blank">markmc@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey<br>
<br>
I figure these proposed amendments are relevant to this list too.<br>
<br>
Thanks,<br>
Mark.<br>
<br>
-------- Forwarded Message --------<br>
> From: Radcliffe, Mark <<a href="mailto:Mark.Radcliffe@dlapiper.com">Mark.Radcliffe@dlapiper.com</a>><br>
> To: Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>><br>
> Cc: Eileen Evans Esq. (<a href="mailto:eileen.evans@hp.com">eileen.evans@hp.com</a>) <<a href="mailto:eileen.evans@hp.com">eileen.evans@hp.com</a>>,<br>
> <a href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a><br>
> <<a href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a>>, Roay, Leslie<br>
> <<a href="mailto:Leslie.Roay@dlapiper.com">Leslie.Roay@dlapiper.com</a>><br>
> Subject: [OpenStack-DefCore] Revised Bylaws<br>
> Date: Mon, 7 Apr 2014 19:03:01 +0000<br>
><br>
> I am enclosing the current version of the Bylaws marked to show<br>
> differences to the existing version (v15 to v.18) and marked to show<br>
> the changes to the initial revised draft (v.17 to v.18). This second<br>
> set of changes reflects comments raised at the last meeting of the<br>
> committee, particularly by Mark McLoughlin on behalf of the Technical<br>
> Committee. Version 18 has not yet been approved by the committee.<br>
> These changes are meant to reflect the need to move from a “module”<br>
> based method of determining when the trademark can be used to a more<br>
> flexible method which can be agreed upon by the Technical Committee<br>
> and the Board. As I said to Mark and I think that he passed on to the<br>
> Technical Committee, the reasons for the DefCore and these revisions<br>
> are as follows:<br>
><br>
><br>
><br>
> > I appreciate your comments at the Bylaws committee meeting. We<br>
> don’t want to have the TC misunderstand the reasons for the bylaws<br>
> change or<br>
><br>
> > their consequences. These changes are focused solely on determining<br>
> how and when the trademark can be used. We want to ensure that the<br>
> TC<br>
><br>
> > has an active role in the decisions. Consequently, we will shift<br>
> back to the use of “core” for these procedures being set up.<br>
> However, as<br>
><br>
> > I noted, a number of members of DefCore Committee have expressed a<br>
> desire to use a word other than “core” for this concept so we may<br>
> see<br>
><br>
> > an additional change in the name .<br>
><br>
><br>
><br>
><br>
> Please consider the environment before printing this email.<br>
><br>
> The information contained in this email may be confidential and/or<br>
> legally privileged. It has been sent for the sole use of the intended<br>
> recipient(s). If the reader of this message is not an intended<br>
> recipient, you are hereby notified that any unauthorized review, use,<br>
> disclosure, dissemination, distribution, or copying of this<br>
> communication, or any of its contents, is strictly prohibited. If you<br>
> have received this communication in error, please reply to the sender<br>
> and destroy all copies of the message. To contact us directly, send to<br>
> <a href="mailto:postmaster@dlapiper.com">postmaster@dlapiper.com</a>. Thank you.<br>
> _______________________________________________<br>
> Defcore-committee mailing list<br>
> <a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a><br>
<br>
<br>_______________________________________________<br>
legal-discuss mailing list<br>
<a href="mailto:legal-discuss@lists.openstack.org">legal-discuss@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Luis Villa<br>Deputy General Counsel<br>Wikimedia Foundation<br>415.839.6885 ext. 6810<br><div><a value="+14158820495"></a><br><div><span style="font-size:7.5pt;font-family:Tahoma"><font style="font-family:arial,helvetica,sans-serif" size="1">NOTICE: </font></span><font style="font-family:arial,helvetica,sans-serif" size="1"><i>This message may be confidential or legally privileged. If you have received it by accident, please delete it
and let us know about the mistake. As an attorney for
the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve
as a lawyer for, community members, volunteers, or staff members in their personal<b> </b>capacity.</i></font></div></div></div>
</div>