<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"HP Simplified";
panose-1:2 11 6 4 2 2 4 2 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"HP Simplified","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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">
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D">Hello WOO!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D">I have a panel proposal. Please read the abstract below and let me know if you are interested. It is still a little wordy but I intend to cut it down
and modify it for the panel representatives. I’d be open to any of your colleagues who may be interested in sharing community event experiences and techniques. Do you know someone who throws these OpenStack parties like me? Please feel free to forward…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D">I would also appreciate feedback on the proposal.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D">I look forward to hearing back from you!
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D">Thanks, Jeanne.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Verdana","sans-serif";color:#676767">When you host your next community event you will be glad you attended this session.
<br>
<br>
Imagine your team asks you to host a meetup or even better a mid-cycle meetup. What is the first panicked thought that comes to your mind? Is it the venue, cost, attendees, transportation, entertainment, wifi, food, drinks!? You take a deep breath, you can
handle this. Now imagine you are to host an OpenStack Summit event for the entire Summit, in Paris. You might experience event management stress disorder as you consider foreign culture, language, currency, environment, cuisine!? The deep breaths aren’t helping
with your hysteria. You know all issues associated with the event will be tied directly to you, this is a big deal, there’s a lot riding on this, there’s a lot riding on you. Keep breathing, the world isn’t coming to an end. The creators of the Pavillons
de Bercy event in Paris present an OpenStack event playbook. <br>
<br>
From this session you will know how to select a venue and vendors, balance your budget (even if it is zero), exceed attendee expectations and gain knowledge of community event culture. You will have processes, tools and resources that guide you to success
without panic. We will explore the best practices of initiation, planning, execution and closure related to the high pressures of organizing a superb event, whether it’s pizza and beer for 15 or the entire OpenStack Summit. You will hear funny anecdotes
and recommendations from your industry peers to assure your next event is unforgettable in the best way possible.
<br>
<br>
So friends, geeks, event planners, lend me your ears, for whether thou art a seasoned coordinator of events or a fresh face that hath only just cast thine eyes upon this world of management, all will learn from these words. OpenStack parties have a competitive
environment and although this competition is the fire at our heels keeping us up to snuff, we can simultaneously have a collaborative strategy ensuring unique attendee experiences at every Summit. We will discuss new strategies for event collaboration based
on challenges we all experience. Through this, new ideas will be conjured from the primordial goo that’s left in our brains, ideas we can use in future Summits.
<br>
<br>
Our open source environment encourages us to reach out as a community and meet up close and personal, face-to-face, eye to eye, heart to heart… okay maybe not that close. In this culture you can be a leader by gaining the knowledge that gives you identity.
You can go to your next community gathering riding upon a golden chariot of confidence, glimmering in the light of genius emanating off of you. As you step down, doves will soar out from behind you as your events coordinator garb radiates pure power from
within. When that day comes, it will be everyone else struggling to breathe.</span><span style="font-size:9.0pt;font-family:"HP Simplified","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>