<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>Is the CFP going to open up this month? I had kinda heard that, but I’m secretly hoping it doesn’t open until after the holidays. :)</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div>Niki Acosta</div>
<div>Cloud Evangelist</div>
<div>Cisco Intercloud Services</div>
<div>(e) nikacost@cisco.com</div>
<div>(c) (+1) 512-912-6716</div>
<div>(t) @nikiacosta </div>
</div>
<br>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Lauren Sell <<a href="mailto:lauren@openstack.org">lauren@openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, December 13, 2015 at 8:29 PM<br>
<span style="font-weight:bold">To: </span>Kyle Mestery <<a href="mailto:mestery@mestery.com">mestery@mestery.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:openstack-track-chairs@lists.openstack.org">openstack-track-chairs@lists.openstack.org</a>" <<a href="mailto:openstack-track-chairs@lists.openstack.org">openstack-track-chairs@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-track-chairs] Call for Speakers Feedback, Next Steps<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi everyone,<br class="">
<br class="">
Thank you again for your input. To summarize the conversation last week, we are planning to implement the following changes to the call for speakers process:
<div class="">
<ul class="">
<li class="">Add stronger language to discourage product pitching in the proposal form</li><li class="">Limit the number of sessions each speaker can submit to 3 (we’ll need help communicating this to the community)</li><li class="">Make the speaker bio *required* (rather than optional) and provide the *option* to link to past Summit presentations or other speaking examples</li><li class="">Add the following questions to solicit more information about each proposed session:
<ul class="">
<li class="">What should attendees expect to learn in this session?</li><li class="">Why should this session be selected?</li><li class="">Please provide any relevant links to additional information, such as code repositories, case studies, papers, blog posts, etc.</li><li class="">(Note, we will have structured tags for audience and level of content, so these areas will also be addressed in the submission form, just not as free form questions)</li></ul>
</li></ul>
</div>
<div class="">For reference, you can see all of the etherpad notes here: <a href="https://etherpad.openstack.org/p/austin-call-for-speakers" class="">https://etherpad.openstack.org/p/austin-call-for-speakers</a></div>
<div class=""><br class="">
</div>
Additionally, we are planning to create a new landing page explaining the different tracks before you click through to submit a proposal. Hopefully this will help potential speakers align their presentation topics with our themes, as well as better communicate
the event and program to prospective attendees. Please note we attempted to create high level themes, which in effect group related tracks to better communicate which topics will be presented on which days ahead of the full agenda being released.
<div class=""><br class="">
</div>
<div class="">I’ve provided an early look at the high level schedule and tracks, and welcome any input on the specific themes or keywords you’d like to see related to your area of expertise. Please add any comments about themes and keywords in the google doc: <a href="https://docs.google.com/spreadsheets/d/1-33IWJL4d5g99aAGsm7bc7MC0EqVmVwUxUSfEsuTkDc/edit#gid=0" class="">https://docs.google.com/spreadsheets/d/1-33IWJL4d5g99aAGsm7bc7MC0EqVmVwUxUSfEsuTkDc/edit#gid=0</a><br class="">
<br class="">
Thanks for your help.<br class="">
<br class="">
Best,<br class="">
Lauren</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On Dec 10, 2015, at 2:04 PM, Kyle Mestery <<a href="mailto:mestery@mestery.com" class="">mestery@mestery.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Dec 10, 2015 at 12:33 PM, Lauren Sell <span dir="ltr" class="">
<<a href="mailto:lauren@openstack.org" target="_blank" class="">lauren@openstack.org</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">Thanks everyone for jumping on this thread and providing such great feedback! This makes me excited to raise the bar for content at the Austin Summit.
<div class=""><br class="">
</div>
<div class="">We’ve started an etherpad to summarize the feedback from the thread. Please jump in with anything we’ve missed, as well as to provide your thoughts next to the current proposals.</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://etherpad.openstack.org/p/austin-call-for-speakers" target="_blank" class="">https://etherpad.openstack.org/p/austin-call-for-speakers</a></div>
<div class=""><br class="">
</div>
<div class="">It seems like limiting the number of sessions each speaker can submit to 3 and adding additional questions to the submission form (such as links to resources, past speaking example videos, more questions about objectives & audience) have pretty
strong support from the group. </div>
<div class=""><br class="">
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">++, this is all good and will help track chairs in selecting appropriate sessions.<br class="">
<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">
<div class=""></div>
<div class="">One follow up question to Daniel’s point below — if we asked speakers to submit draft presentations a week before the Summit, do you think track chairs would be willing to scan through them for any obvious product pitches or deviations from the
original submission? I doubt we’d get 100% compliance from presenters, but it could be a good start. I put that proposal in the etherpad under Speaker Management if you want to comment there.</div>
<div class=""><br class="">
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">I'm not sure this would work, both because perpetrators of the product pitch sessions could just not upload their slides, and because track chairs are already heavily involved in the summit themselves. The gain for the amount of pain doesn't seem
to justify this IMHO.<br class="">
<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">
<div class=""></div>
<div class="">Ideally we can come up with a few concrete changes for this cycle, as well as plans we can start putting in place for Barcelona.</div>
<div class=""><br class="">
</div>
<div class="">Thank you again!</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class=""><span class="">
<div class="">On Dec 10, 2015, at 11:30 AM, Daniel Krook <<a href="mailto:krook@us.ibm.com" target="_blank" class="">krook@us.ibm.com</a>> wrote:</div>
<br class="">
</span>
<div class="">
<div class="">
<p class=""><span class="">There are a lot of great ideas in this thread and the parallel responses. Picking the best of these ideas is almost as much work as selecting presentations. :)<br class="">
<br class="">
I agree it's time to consolidate them into an Etherpad to see we can "vote" on the ideas by the end of the week before the Austin CfP goes out.<br class="">
<br class="">
<br class="">
My own take:<br class="">
<br class="">
- I like the idea to add the additional questions in Lauren's original email, and the idea of optional fields for "extra credit" highlighting speaking experience at previous Summits, meetups, recorded demos, etc. We recommend that submitters include much of
that information to create strong abstracts in the some of our guidance anyway: <a href="https://www.youtube.com/watch?v=CxFYNZ4jqik" target="_blank" class="">
https://www.youtube.com/watch?v=CxFYNZ4jqik</a><br class="">
<br class="">
- Moving talks or somehow autocategorizing talks between tracks could be smoother. I don't like seeing a whole new slew of talks that were moved in at the last minute after I've done an initial ranking. As a chair on the Related OSS track, I'm also not 100%
sure when a particular talk should be in my talk or Containers (e.g. Docker) or Operations (e.g. SaltStack). Maybe a co-vote between tracks and track chairs on content that sits in the gray areas? Maybe we add an "uncategorized/waivers bucket" and have track
chairs proactively "draft/categorize" the talks they think fit into their own track that may have been "cut/decategorized" from another talk?<br class="">
<br class="">
- We should require presenters to submit an early draft a week ahead of the event, like the Linux Foundation CfP site does. This forces speakers to at least submit a semi-complete outline (beneficial whether it's a weak talk at that point or they are procrastinators,
it could also tilt their hand on marketing content, and possibly give them a less stressful Summit attending experience (more time to attend
<i class="">other </i>talks rather than work on their own talk)). But this would still allow for up to-the-minute of the talk refinements, as the submitter controls the device used to do the actual presentation. This also somewhat mitigates the problem of biting
off more than they can chew if giving more than one presentation by forcing them to create content earlier.<br class="">
<br class="">
- While I think 2 presenters is an ideal limit for speakers per talk, I'm OK with allowing for up to 4, as this provides an opportunity for more experienced presenters to mentor younger co-speaking colleagues and to attribute talks to those who are shy or otherwise
can't attend the Summit (but contributed to talk content nonetheless).<br class="">
<br class="">
- For the same reason, I don't like the idea of limiting submissions per person (or number of talks for which they are an additional speaker). In some talks they may be the main presenter, others a minor co-presenter and possibly mentoring others, or they were
reached out with for their opinion to strengthen a panel submitted by someone else.
<br class="">
<br class="">
- For those two reasons and the logistical questions several already raised by others, I don't think we should limit submissions by company affiliation.
<br class="">
<br class="">
- I personally think there's some value in the community voting, and that should influence the initial ordering of what the track chairs see when they log in the very first time, but I understand it's not a common opinion. :)<br class="">
<br class="">
<font face="Arial" size="2" class=""><br class="">
</font><br class="">
<font face="Arial" size="2" class="">Thanks,</font><br class="">
<font face="Arial" size="2" class=""><br class="">
</font><br class="">
<b class=""><font face="Arial" color="#888888" size="4" class="">Daniel Krook</font></b><font face="Arial" size="2" class=""><br class="">
Senior Software Engineer, IBM Cloud<br class="">
Distinguished IT Specialist (The Open Group & IBM Senior Certified)</font></span></p>
<table border="0" cellpadding="0" cellspacing="0" class="">
<tbody class="">
<tr valign="top" class="">
<td colspan="2" valign="middle" width="650" class="">
<hr align="left" size="2" width="100%" class="">
</td>
</tr>
<tr valign="top" class="">
<td width="396" class=""><a href="http://www.linkedin.com/in/krook" target="_blank" class=""><span class=""><0E327443.jpg></span></a><font face="Arial" color="#5F5F5F" size="2" class=""></font><a href="http://twitter.com/danielkrook" target="_blank" class=""><span class=""><0E696251.jpg></span></a><font face="Arial" color="#5F5F5F" size="2" class=""></font><a href="http://github.com/krook" target="_blank" class=""><span class=""><0E483644.jpg></span></a><font face="Arial" color="#5F5F5F" size="2" class=""></font><a href="http://www.meetup.com/members/13919430/" target="_blank" class=""><span class=""><0E434558.jpg></span></a><font face="Arial" color="#5F5F5F" size="2" class=""></font><a href="http://www.slideshare.net/danielkrook" target="_blank" class=""><span class=""><0E317065.jpg></span></a><font face="Arial" color="#5F5F5F" size="2" class=""></font><u class=""><font face="Arial" color="#0000FF" size="2" class=""><br class="">
</font></u><a href="http://krook.info/" target="_blank" class=""><u class=""><font face="Arial" color="#5F5F5F" size="2" class="">krook.info</font></u></a><font face="Arial" color="#5F5F5F" size="2" class=""></font></td>
<td width="254" class="">
<div align="right" class=""><span class=""><0E100292.gif></span><font face="Arial" color="#5F5F5F" size="2" class=""><br class="">
</font></div>
</td>
</tr>
</tbody>
</table>
<br class="">
<br class="">
<br class="">
<span class=""><graycol.gif></span><font color="#424282" class="">Kendall Waters ---12/10/2015 11:46:24 AM---Hi Salvatore, The session feedback response rate from Tokyo was much lower than expected. This may b</font>
<div class="">
<div class="h5"><br class="">
<br class="">
<font color="#5F5F5F" size="2" class="">From: </font><font size="2" class="">Kendall Waters <<a href="mailto:kendall@openstack.org" target="_blank" class="">kendall@openstack.org</a>></font><br class="">
<font color="#5F5F5F" size="2" class="">To: </font><font size="2" class="">Salvatore Orlando <<a href="mailto:salv.orlando@gmail.com" target="_blank" class="">salv.orlando@gmail.com</a>></font><br class="">
<font color="#5F5F5F" size="2" class="">Cc: </font><font size="2" class="">"<a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank" class="">openstack-track-chairs@lists.openstack.org</a>" <<a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank" class="">openstack-track-chairs@lists.openstack.org</a>></font><br class="">
<font color="#5F5F5F" size="2" class="">Date: </font><font size="2" class="">12/10/2015 11:46 AM</font><br class="">
<font color="#5F5F5F" size="2" class="">Subject: </font><font size="2" class="">Re: [Openstack-track-chairs] Call for Speakers Feedback, Next Steps</font><br class="">
</div>
</div>
<div class=""><br class="webkit-block-placeholder">
</div>
<div class="">
<div class="h5">
<hr style="color:#8091a5" align="left" noshade="" size="2" width="100%" class="">
<br class="">
<br class="">
<br class="">
<font size="4" class="">Hi Salvatore,</font><br class="">
<br class="">
<font size="4" class="">The session feedback response rate from Tokyo was much lower than expected. This may be partly due to the wifi quality at the Summit as well as the unreliable mobile app. It could also be that attendees simply didn’t know about it. We
are hard at work building a new mobile app for the Austin Summit, which will have feedback forms for each session built into the app. We also plan to shorten the feedback survey to just 2 questions where the attendee can rate the session and then leave text
feedback if desired. We are hoping this will increase the response rate in Austin and help track chairs during the selection process in the future.
</font><br class="">
<br class="">
<font size="4" class="">Cheers,</font><br class="">
<font size="4" class="">Kendall</font><br class="">
<br class="">
<font size="4" class="">Kendall Waters<br class="">
OpenStack Marketing</font><u class=""><font color="#0000FF" size="4" class=""><br class="">
</font></u><a href="mailto:kendall@openstack.org" target="_blank" class=""><u class=""><font color="#0000FF" size="4" class="">kendall@openstack.org</font></u></a><font size="4" class=""><br class="">
</font><br class="">
<ul class="">
<ul class="">
<font size="4" class="">On Dec 9, 2015, at 3:42 PM, Salvatore Orlando <</font><a href="mailto:salv.orlando@gmail.com" target="_blank" class=""><u class=""><font color="#0000FF" size="4" class="">salv.orlando@gmail.com</font></u></a><font size="4" class="">>
wrote:</font><br class="">
<br class="">
<font size="4" class="">I think the huge number of submissions that we get is kind of reasonable, considering the importance of the Openstack summit event.</font><br class="">
<font size="4" class="">Nevertheless, it is more than fair to add some rigour to the submission process.</font><br class="">
<br class="">
<font size="4" class="">The three proposed additional questions are good in my opinion. They should actually be part of any talk abstract.</font><br class="">
<font size="4" class="">I think it could be worth trying to encourage submitters to add some evidence of the meat behind the abstract being reviewed.</font><br class="">
<font size="4" class="">Examples of such evidence could be:</font><br class="">
<font size="4" class="">- code repositories</font><br class="">
<font size="4" class="">- blog posts</font><br class="">
<font size="4" class="">- whitepapers, academic papers, or technical reports</font><br class="">
<font size="4" class="">- previous related work</font><br class="">
<font size="4" class="">- videos, slides, etc.</font><br class="">
<br class="">
<font size="4" class="">I don't think this will lead to less submission, but would help the track chairs team to "fast-reject" talks which appear to not have decent standards.</font><br class="">
<br class="">
<font size="4" class="">This could be achieved with an "additional material" section.</font><br class="">
<font size="4" class="">Obviously I don't want to force submitters to disclose any IP-protected material, though if that was the case a submission to the openstack summit shouldn't probably even be considered.</font><br class="">
<br class="">
<font size="4" class="">For the track chairs team going through a nomination and selection process each time sounds good to me. There are probably some open questions around criteria for selecting chairs and confirming people who did the chair duty in the previous
cycle, but I guess the foundation already has a process in place.</font><br class="">
<br class="">
<font size="4" class="">For the public voting system, I think it's useless at the moment. I second the idea of having an interface where one could rank the talks he/she is interested in and not rank at all the talks that are deemed not good enough to be presented.</font><br class="">
<br class="">
<font size="4" class="">For the selection process from track chairs, I'do instead for a process where talk proposal are evaluated first regardless of public voting (scoring could be "strong accept"/"weak accept"/"weak reject"/"strong reject"/"definitely meh").
And then accepted talks can be ranked to fill available slots taking also into account, if useful, the public voting outcome.</font><br class="">
<br class="">
<font size="4" class="">On another note... do we have the feedback from the Tokyo talks? I'd like to see what the audience thought of the talks that were selected.</font><br class="">
<br class="">
<font size="4" class="">Salvatore</font><br class="">
<br class="">
<br class="">
<font size="4" class="">On 9 December 2015 at 21:55, Niki Acosta (nikacost) <</font><a href="mailto:nikacost@cisco.com" target="_blank" class=""><u class=""><font color="#0000FF" size="4" class="">nikacost@cisco.com</font></u></a><font size="4" class="">> wrote:</font>
<ul class="">
<font face="Calibri" class="">My thoughts, for what its worth: </font><br class="">
<br class="">
<font face="Calibri" class="">Cap it at three submissions per person, including panels.
</font><br class="">
<font face="Calibri" class="">Strongly discourage straight up product-pitching sessions.
</font><br class="">
<font face="Calibri" class="">Would be cool to review sessions to take a first pass at what actually makes it to voting. There were far too many sessions to vote on.
</font><br class="">
<font face="Calibri" class="">The voting system is kinda painful. It would be useful to see a list of sessions for any given track and stack rank them, versus voting on them one by one.
</font><br class="">
<font face="Calibri" class="">Requirement to the submission form: allow someone to post a link to a previous recorded presentation. It would be helpful for trackchairs to review in the event there’s a tie.
</font><br class="">
<br class="">
<font face="Calibri" class="">Also— I’ve noticed that some track reassignments happened too late— in some cases, after final selections had been made. We should really press for a cutoff date for track re-assignments that is far enough in advance of the final
selections deadline to make sure track chairs are considering all of the sessions in the track.
</font><br class="">
<br class="">
<font face="Calibri" class="">:)</font><br class="">
<br class="">
<font face="Calibri" class="">Niki Acosta</font><br class="">
<font face="Calibri" class="">Cloud Evangelist</font><br class="">
<font face="Calibri" class="">Cisco Intercloud Services</font><br class="">
<font face="Calibri" class="">(e) </font><a href="mailto:nikacost@cisco.com" target="_blank" class=""><u class=""><font face="Calibri" color="#0000FF" class="">nikacost@cisco.com</font></u></a><br class="">
<font face="Calibri" class="">(c) </font><a href="tel:%28%2B1%29%20512-912-6716" target="_blank" class=""><u class=""><font face="Calibri" color="#0000FF" class="">(+1) 512-912-6716</font></u></a><br class="">
<font face="Calibri" class="">(t) @nikiacosta </font><br class="">
<br class="">
<br class="">
<b class=""><font face="Calibri" class="">From: </font></b><font face="Calibri" class="">Lauren Sell <</font><a href="mailto:lauren@openstack.org" target="_blank" class=""><u class=""><font face="Calibri" color="#0000FF" class="">lauren@openstack.org</font></u></a><font face="Calibri" class="">></font><b class=""><font face="Calibri" class=""><br class="">
Date: </font></b><font face="Calibri" class="">Wednesday, December 9, 2015 at 2:44 PM</font><b class=""><font face="Calibri" class=""><br class="">
To: </font></b><font face="Calibri" class="">"</font><a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank" class=""><u class=""><font face="Calibri" color="#0000FF" class="">openstack-track-chairs@lists.openstack.org</font></u></a><font face="Calibri" class="">"
<</font><a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank" class=""><u class=""><font face="Calibri" color="#0000FF" class="">openstack-track-chairs@lists.openstack.org</font></u></a><font face="Calibri" class="">></font><b class=""><font face="Calibri" class=""><br class="">
Subject: </font></b><font face="Calibri" class="">[Openstack-track-chairs] Call for Speakers Feedback, Next Steps</font><br class="">
<br class="">
<font face="Calibri" class="">Hello Tokyo Summit track chairs,<br class="">
<br class="">
We’re moving quickly to open the call for speakers for the Austin Summit next week and want to make sure we incorporate feedback from prior discussions on this list. Unfortunately, we didn’t have much turnout in Tokyo for the Summit tools & processes session,
where we were hoping to facilitate more discussion. We only had two people show up (outside of Foundation staff), so we primarily discussed the mobile app and reviewed the prototype.<br class="">
<br class="">
Based on earlier feedback in this thread, there is a desire to manage the growing number of submissions while increasing the quality. We have two levers we could pull for the submission process, but need to make decisions by the end of this week:<br class="">
1. Do we want to cap the number of sessions that each person can submit at 5?<br class="">
2. Do we want to add any questions or requirements to the submission form? See suggestions below.
<br class="">
<br class="">
For #2, we are already making a few minor changes this round to improve session tagging and ask speakers for “links to past presentations” and “areas of expertise.” For the session submission, we currently ask:
</font>
<ul class="">
<ul type="disc" class="">
<li class=""><font face="Calibri" class="">Session Title </font></li><li class=""><font face="Calibri" class="">Session level (beginner, intermediate, advanced)</font></li><li class=""><font face="Calibri" class="">Abstract</font></li><li class=""><font face="Calibri" class="">Short Description (450 characters max for YouTube and mobile app)</font></li><li class=""><font face="Calibri" class="">Select track from dropdown</font></li><li class=""><font face="Calibri" class="">Tags</font></li></ul>
</ul>
<font face="Calibri" class="">I would suggest consolidating the abstract and short description to be one question (because submitters often copy/paste it anyway), and then ask a few additional questions:</font>
<ul class="">
<ul type="disc" class="">
<li class=""><font face="Calibri" class="">Who is the intended audience for your session? Please be specific.</font></li><li class=""><font face="Calibri" class="">What is the problem or use case you’re addressing in this session?</font></li><li class=""><font face="Calibri" class="">What should attendees expect to learn?</font></li></ul>
</ul>
<font face="Calibri" class="">We are also making a few changes to the tracks, primarily grouping them into content categories to better promote and layout the content across the week.
<br class="">
<br class="">
Finally, we will very soon need to select the next round of track chairs. The Foundation has typically accepted nominations from the community and appointed track chairs based on subject matter expertise, contributions, working group involvement, etc. To help
bring in new perspectives, one proposal was to ask track chairs to decide two people from their team who would continue for the next cycle and nominate two new people from the community to keep things fresh. We’ve gotten a lot of feedback that another community
vote for track chairs is not desirable, but we could more broadly communicate the window for nominations. We’re accepting nominations now (email
</font><a href="mailto:summit@openstack.org" target="_blank" class=""><u class=""><font face="Calibri" color="#0000FF" class="">summit@openstack.org</font></u></a><font face="Calibri" class="">) and hope to have track chairs decided by mid-January. Any thoughts
on the process? <br class="">
<br class="">
Thanks,<br class="">
Lauren </font><br class="">
<font size="4" class=""><br class="">
_______________________________________________<br class="">
Openstack-track-chairs mailing list</font><u class=""><font color="#0000FF" size="4" class=""><br class="">
</font></u><a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank" class=""><u class=""><font color="#0000FF" size="4" class="">Openstack-track-chairs@lists.openstack.org</font></u></a><u class=""><font color="#0000FF" size="4" class=""><br class="">
</font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank" class=""><u class=""><font color="#0000FF" size="4" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</font></u></a><font size="4" class=""><br class="">
</font></ul>
<br class="">
<font size="4" class="">_______________________________________________<br class="">
Openstack-track-chairs mailing list</font><u class=""><font color="#0000FF" size="4" class=""><br class="">
</font></u><a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank" class=""><u class=""><font color="#0000FF" size="4" class="">Openstack-track-chairs@lists.openstack.org</font></u></a><font size="4" class=""><br class="">
</font><font size="4" class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a></font></ul>
</ul>
<tt class="">_______________________________________________<br class="">
Openstack-track-chairs mailing list<br class="">
<a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank" class="">Openstack-track-chairs@lists.openstack.org</a><br class="">
</tt><tt class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a></tt><tt class=""><br class="">
</tt><br class="">
<br class="">
<br class="">
</div>
</div>
</div>
<div class="">
<div class="h5">_______________________________________________<br class="">
Openstack-track-chairs mailing list<br class="">
<a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank" class="">Openstack-track-chairs@lists.openstack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br class="">
_______________________________________________<br class="">
Openstack-track-chairs mailing list<br class="">
<a href="mailto:Openstack-track-chairs@lists.openstack.org" class="">Openstack-track-chairs@lists.openstack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</span>
</body>
</html>