<div dir="ltr">Thanks Mark.<div><br></div><div>What do you think about the project selection for ATC designation? Is it the Technical Committee Approved set of projects? I don't think it's accurate just to delete the word "Core" there.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 19, 2014 at 10:32 AM, Radcliffe, Mark <span dir="ltr"><<a href="mailto:Mark.Radcliffe@dlapiper.com" target="_blank">Mark.Radcliffe@dlapiper.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I am fine with changing TC to Technical Committee and ATC to Active Technical Contributor.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a> [mailto:<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>]
<b>On Behalf Of </b>Anne Gentle<br>
<b>Sent:</b> Wednesday, November 19, 2014 6:16 AM<br>
<b>To:</b> Thierry Carrez; Radcliffe, Mark<br>
<b>Cc:</b> <a href="mailto:openstack-tc@lists.openstack.org" target="_blank">openstack-tc@lists.openstack.org</a><br>
<b>Subject:</b> Re: [openstack-tc] Fwd: Revised Bylaws<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi Mark, <u></u><u></u></p>
<div>
<p class="MsoNormal">Thanks for the summary, super helpful. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I'd like to request we don't use "TC" even in the draft. Using an acronym could cause confusion so let's spell out Technical Committee throughout. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Similarly, let's spell out ATC as Active Technical Contributor. One line I would like to clarify is "<span style="font-size:9.5pt;font-family:"Arial","sans-serif"">ATC must contribute to OpenStack Project" -- I would guess we mean that
to be "An Active Technical Contributor must contribute to a Technical Committee Approved OpenStack Project within the two six-month release cycles." [1]</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Arial","sans-serif"">Thanks,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Arial","sans-serif"">Anne</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">1. <a href="https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee" target="_blank">https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee</a></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Mon, Nov 17, 2014 at 6:59 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">FYI<br>
(forwarded at Mark Radcliffe's request)<br>
<br>
-------- Message transféré --------<br>
Sujet : Revised Bylaws<br>
Date : Sat, 15 Nov 2014 15:35:09 +0000<br>
De : Radcliffe, Mark <<a href="mailto:Mark.Radcliffe@dlapiper.com" target="_blank">Mark.Radcliffe@dlapiper.com</a>><br>
Pour : <a href="mailto:openstack-tc-owner@lists.openstack.org" target="_blank">openstack-tc-owner@lists.openstack.org</a><br>
<<a href="mailto:openstack-tc-owner@lists.openstack.org" target="_blank">openstack-tc-owner@lists.openstack.org</a>>, Stefano Maffulli<br>
<<a href="mailto:stefano@openstack.org" target="_blank">stefano@openstack.org</a>><br>
Copie à : Jonathan Bryce <<a href="mailto:jonathan@openstack.org" target="_blank">jonathan@openstack.org</a>>, Alan Clark<br>
<<a href="mailto:aclark@suse.com" target="_blank">aclark@suse.com</a>><br>
<br>
This email is a follow up to the discussion at the joint Technical<br>
Committee/Board meeting at the Paris Summit. I am enclosing the final<br>
draft of the revised bylaws. As you know, the DefCore process has<br>
developed a process for managing the application of trademarks to the<br>
OpenStack Project. The original bylaws provided for very detailed (and<br>
inflexible) approach to the use of trademarks and the modification of<br>
the Core OpenStack Project. The proposed revisions are meant to provide<br>
flexibility to adopt the Defcore procedures and any changes to those<br>
procedures in the future. These changes have included input from the<br>
Legal Affairs Committee, OpenStack Foundation management and the Defcore<br>
Committee. Please provide me with any comments by noon on Thursday,<br>
November 20. We will also be sending a similar email to the Board and<br>
the Defcore Committee. The drafts can be found at<br>
<br>
<a href="https://www.dropbox.com/sh/eztcbk8tvxouqfb/AABX8D6g8jns3Cp_4OGthc7Oa?dl=0" target="_blank">https://www.dropbox.com/sh/eztcbk8tvxouqfb/AABX8D6g8jns3Cp_4OGthc7Oa?dl=0</a><br>
<br>
After considering and incorporating any relevant comments, the<br>
Foundation is planning to have a Board meeting in the first week of<br>
December to approve the final draft. Then, such draft will be put on<br>
the Foundation website to prepare for approval by the Individual Members<br>
as part of their election of Individual Directors.<br>
<br>
1. Revisions for Determination Core and Trademark Policy.<br>
a. Shift from two to three categories of software<br>
i. Current bylaws<br>
A. OpenStack Project<br>
B. Core OpenStack Project<br>
ii.Revised bylaws<br>
A. OpenStack Project<br>
B. OpenStack TC Approved Release<br>
C. Trademark Designated OpenStack Software<br>
b. Change in determination of Trademark Designated OpenStack Software<br>
by the Board<br>
i. Current bylaws<br>
A. Modules: Block Storage, Compute, Dashboard, Identity<br>
Service, Image Service, Networking, and Object Storage<br>
B. Add/Remove Modules Process: Proposed by Technical Committee<br>
and approved by the Board of Directors ("Board")<br>
C. This provision can only be changed by a vote of the Board<br>
and the affirmative vote of (i) two-thirds of the Gold Members, (ii)<br>
two-thirds of the Platinum Members, and (iii) a majority of the<br>
Individual Members voting (but only if at least 25% of the Individual<br>
Members voting at an annual or special<br>
meeting).<br>
ii. Revised bylaws<br>
A. Trademark Designated OpenStack Software: Process for<br>
determining Trademark Designated OpenStack Software will be determined<br>
by the Board and does not need any vote by the members, but changes in<br>
process require Technical Committee approval (i.e. change from DefCore)<br>
B. OpenStack TC Approved Release (formerly Integrated<br>
Release): Determined by Technical Committee but "Trademark Designated<br>
OpenStack Software" can be deleted from OpenStack TC Approved Release<br>
only with permission of Board<br>
c. Change in management of trademarks<br>
i. Current bylaws<br>
A. Trademarks governed by detailed trademark policy in Appendix 8<br>
B. This provision can only be changed by a vote of the Board<br>
and the affirmative vote of (i) two-thirds of the Gold Members, (ii)<br>
two-thirds of the Platinum Members, and (iii) a majority of the<br>
Individual Members voting (but only if at least 25% of the Individual<br>
Members vote at an annual or special meeting).<br>
ii. Revised bylaws<br>
A. Trademarks will be governed by a trademark policy to be<br>
determined by the Board and does not need any vote by the members<br>
<br>
2. Determination of ATC<br>
a. Current bylaws: ATC must contribute to Core OpenStack Project.<br>
b. Revised bylaws: ATC must contribute to OpenStack Project .<br>
<br>
<br>
Separate Approval (at the request of DefCore)<br>
<br>
1. Legal Affairs Committee<br>
a. Current bylaws: Legal Affairs Committee currently is limited to<br>
five members (but eleven lawyers are attending).<br>
b. Revised bylaws: The Board can set the criteria for membership on<br>
the Legal Affairs Committee.<br>
<br>
2. Quorum for Individual Members to Amend the Bylaws<br>
a. Current bylaws: A majority of the Individual Members voting (but<br>
only if at least 25% of the Individual Members vote at an annual or<br>
special meeting). This vote was selected rather arbitrarily at the<br>
time the bylaws were drafted and did not anticipate the number of<br>
Individual Members which have joined the Foundation. The 2014 election<br>
for Individual Directors had participation of only [11%] of the<br>
Individual Members.<br>
b. Revised bylaws: A majority of the Individual Members voting (but<br>
only if at least 10% of the Individual Members vote at an annual or<br>
special meeting).<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" target="_blank">postmaster@dlapiper.com</a>. Thank you.<br>
---------------------------<br>
<br>
_______________________________________________<br>
OpenStack-TC mailing list<br>
<a href="mailto:OpenStack-TC@lists.openstack.org" target="_blank">OpenStack-TC@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div><div><div class="h5">
<span style="font-size:11px"><font style="font-size:11px" color="#008000">Please consider the environment before printing this email.</font></span><font style="font-size:11px" color="#008000">
<br>
<br>
<font color="#808080" size="1" face="Verdana">
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 <a href="mailto:postmaster@dlapiper.com" target="_blank">postmaster@dlapiper.com</a>. Thank you.
<br>
</font></font></div></div></div>
</blockquote></div><br></div>