<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Megan –great idea. People are always surprised by how active WOO is and how they have made a big impact on each summit and in between through dev onboarding,
support systems, education and really increasing the participation of women to 12% of summit attendance. We have made It a mainstream topic and there are amazing contributions from WOO. There is also formal tracking of minutes and attendance so it would
lend itself to it. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank You,</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Nithya A. Ruff<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Director, SanDisk Open Source Strategy, Research
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">WIN Board Member</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:red">SanDisk
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:ZH-CN">|</span><span style="font-family:"Calibri",sans-serif;color:black">a Western Digital brand<b>
</b></span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#7F7F7F">951 SanDisk Drive, Milpitas, CA 95035<br>
T: + (408-801-7068)| M: + (510-378-3159)</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#7F7F7F"><a href="mailto:Nithya.Ruff@SanDisk.com"><span style="font-family:"Times New Roman",serif">Nithya.Ruff@SanDisk.com</span></a>
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0070C0">Twitter:</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#7F7F7F">
<a href="https://twitter.com/nithyaruff"><span style="font-family:"Times New Roman",serif">@nithyaruff</span></a>
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Megan Rossetti [mailto:rossetti.megan18@gmail.com]
<br>
<b>Sent:</b> Thursday, September 08, 2016 7:00 AM<br>
<b>To:</b> women-of-openstack@lists.openstack.org<br>
<b>Subject:</b> [Women-of-openstack] [Women-of-OpenStack]<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Hi team,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">In Austin, a sub-group was formed to help define a process for AUC (Active User Contributor) recognition. <span style="color:#333333">This working group was created to assist the </span><a href="https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee" title="Governance/Foundation/UserCommittee"><span style="color:#0088CC;text-decoration:none">User
Committee</span></a><span style="color:#333333"> (UC) define its constituency in a manner similar to how the </span><a href="https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee" title="Governance/Foundation/TechnicalCommittee"><span style="color:#0088CC;text-decoration:none">Technical
Committee</span></a><span style="color:#333333"> (TC) has defined the designation of </span><a href="http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc"><span style="color:#0088CC;text-decoration:none">Active Technical Contributors</span></a><span style="color:#333333"> (ATC)/</span><a href="http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc"><span style="color:#0088CC;text-decoration:none">Active
Project Contributors</span></a><span style="color:#333333"> (APC) and participants eligible to participate in the electoral process for </span><a href="http://governance.openstack.org/reference/charter.html#project-team-leads"><span style="color:#0088CC;text-decoration:none">Project
Team Leads</span></a><span style="color:#333333"> (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for
this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an </span><a href="https://governance.openstack.org/reference/projects/"><span style="color:#0088CC;text-decoration:none">OpenStack
TC sanctioned project</span></a><span style="color:#333333">. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. </span><a href="https://github.com/osops"><span style="color:#0088CC;text-decoration:none">OSOps</span></a><span style="color:#333333">, </span><a href="https://github.com/openstack/ops-tags-team"><span style="color:#0088CC;text-decoration:none">ops-tags</span></a><span style="color:#333333">,
etc.), active participation in any User Committee working group (e.g. </span><a href="https://wiki.openstack.org/wiki/API_Working_Group" title="API Working Group"><span style="color:#0088CC;text-decoration:none">API-WG</span></a><span style="color:#333333">, </span><a href="https://wiki.openstack.org/wiki/Enterprise_Working_Group" title="Enterprise Working Group"><span style="color:#0088CC;text-decoration:none">Enterprise-WG</span></a><span style="color:#333333">, </span><a href="https://wiki.openstack.org/wiki/ProductTeam" title="ProductTeam"><span style="color:#0088CC;text-decoration:none">Product-WG</span></a><span style="color:#333333">,
etc.), moderating sessions at OpenStack </span><a href="https://wiki.openstack.org/wiki/Operations/Meetups" title="Operations/Meetups"><span style="color:#0088CC;text-decoration:none">Ops-meetups</span></a><span style="color:#333333">, organizing OpenStack </span><a href="https://groups.openstack.org/"><span style="color:#0088CC;text-decoration:none">user
group meet-ups</span></a><span style="color:#333333"> across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">During the Mid-Cycle Operators meeting in NYC, we discussed adding the Women of OpenStack to the list of recognized groups. To recognize individuals for AUC status, we would need to track active participation
after each meeting, we are currently developing a form for that purpose. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">I would like to know what the team thinks about this endeavor, and if they are interested in AUC recognition.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Thank you.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> - Megan Rossetti<o:p></o:p></p>
</div>
</div>
PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this
message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy
any and all copies of this message in your possession (whether hard copies or electronically stored copies).
</body>
</html>