<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=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Lucida Handwriting";
panose-1:3 1 1 1 1 1 1 1 1 1;}
/* 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.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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","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-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1033581074;
mso-list-template-ids:766044838;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1562248890;
mso-list-template-ids:-2051514308;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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" style="word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="Section1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I agree with Niki's view. In addition, I'd like to add the following suggestions -<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">1. We should make our summit not just a place for OpenStack veterans to share their insights and experiences, but also a welcoming place for newbies to share
their new ideas without feeling being judged or the barrier to entry. So, I'd like to suggest we allocate a portion of the sessions for speakers who never spoke before and topics that were never discussed before.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">2. Panels are really fun and informative. It looks like we generally have good attendance for panel sessions. Maybe we should require minimum 2 panels/track
and invite folks who submitted but didn't get selected as speakers to join the panels. In that case, more people can have stage time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">3. Definitely "yes" on maximum 3 submissions/person (including panels). In this case, we can give stage time to more people. Again, my view is that our events
should be more open, more inclusive, and not just limit them to veterans. This is the only way we can generate new ideas, new innovations.
<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">Also, this is not really track-chair related; it has more to do with event management. I noticed that in Tokyo, some popular sessions were assigned to a small
room with a huge overflow, and some sessions were given a big room with no more than 30% occupancy. I guess people generally didn't RSVP ahead of time and decided to check out sessions in the last minute. I suggest maybe we should enforce that people who
RSVP'ed will be guaranteed to get in, and people who didn't RSVP will have to wait in line at the door. This means we will need to scan badge and check at the door. This might help us with more accurate room assignment. In addition, it will give us data points
on who attended what sessions, what topics are popular, etc. for future reference.<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">Just my $0.02,<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">Anni<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>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><img width="102" height="32" id="Picture_x0020_8" src="cid:image001.png@01D13285.B56CCA60" alt="cid:image001.png@01CBC2CC.A2FB0D70"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Lucida Handwriting";
color:#1F497D">Anni Lai<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial","sans-serif";
color:#1F497D">Email:
<a href="mailto:cathy.wu@huawei.com">anni.lai@huawei.com</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> Niki Acosta (nikacost) [mailto:nikacost@cisco.com]
<br>
<b>Sent:</b> Wednesday, December 09, 2015 12:55 PM<br>
<b>To:</b> Lauren Sell; openstack-track-chairs@lists.openstack.org<br>
<b>Subject:</b> Re: [Openstack-track-chairs] Call for Speakers Feedback, Next Steps<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">My thoughts, for what its worth: <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">Cap it at three submissions per person, including panels. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">Strongly discourage straight up product-pitching sessions. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">:)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">Niki Acosta<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">Cloud Evangelist<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">Cisco Intercloud Services<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">(e) nikacost@cisco.com<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">(c) (+1) 512-912-6716<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">(t) @nikiacosta <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black">Lauren Sell <<a href="mailto:lauren@openstack.org">lauren@openstack.org</a>><br>
<b>Date: </b>Wednesday, December 9, 2015 at 2:44 PM<br>
<b>To: </b>"<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>
<b>Subject: </b>[Openstack-track-chairs] Call for Speakers Feedback, Next Steps<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">Hello Tokyo Summit track chairs,<br>
<br>
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>
<br>
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>
1. Do we want to cap the number of sessions that each person can submit at 5?<br>
2. Do we want to add any questions or requirements to the submission form? See suggestions below. <br>
<br>
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:
<o:p></o:p></span></p>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Session Title <o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Session level (beginner, intermediate, advanced)<o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Abstract<o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Short Description (450 characters max for YouTube and mobile app)<o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Select track from dropdown<o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Tags<o:p></o:p></span>
</li></ul>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">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:<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">Who is the intended audience for your session? Please be specific.<o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">What is the problem or use case you’re addressing in this session?<o:p></o:p></span>
</li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.5pt;font-family:
"Calibri","sans-serif"">What should attendees expect to learn?<o:p></o:p></span>
</li></ul>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black">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>
<br>
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
<a href="mailto:summit@openstack.org">summit@openstack.org</a>) and hope to have track chairs decided by mid-January. Any thoughts on the process? <br>
<br>
Thanks,<br>
Lauren <o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>