<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)">
<!--[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:"ＭＳ ゴシック";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"ＭＳ ゴシック";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"ＭＳ Ｐゴシック";
panose-1:2 11 6 0 7 2 5 8 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:"\@ＭＳ ゴシック";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"\@ＭＳ Ｐゴシック";
panose-1:2 11 6 0 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0mm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"ＭＳ Ｐゴシック";}
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;}
tt
{mso-style-priority:99;
font-family:"ＭＳ ゴシック";}
span.18
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1343899148;
mso-list-template-ids:502270704;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0mm;}
ul
{margin-bottom:0mm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026">
<v:textbox inset="5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></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="JA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">I agree capping the number of session proposing for person,
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">it will be good opportunity for newbies to speak in summit.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">But I feel 3 is a slightly low, so is there any data or statistics<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">that how many people had submitted over 3, 4, 5, 6,.. in last summits?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">I think that data will help to decide the cap number and will be more<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">understandable from community.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black">Takashi Torii<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0mm 0mm 0mm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0mm 0mm 0mm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Lauren Sell [mailto:lauren@openstack.org]
<br>
<b>Sent:</b> Friday, December 11, 2015 3:34 AM<br>
<b>To:</b> Daniel Krook<br>
<b>Cc:</b> 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"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">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. <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><a href="https://etherpad.openstack.org/p/austin-call-for-speakers">https://etherpad.openstack.org/p/austin-call-for-speakers</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Thank you again!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">On Dec 10, 2015, at 11:30 AM, Daniel Krook <<a href="mailto:krook@us.ibm.com">krook@us.ibm.com</a>> wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">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>
<br>
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>
<br>
<br>
My own take:<br>
<br>
- 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">
https://www.youtube.com/watch?v=CxFYNZ4jqik</a><br>
<br>
- 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>
<br>
- 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>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>
<br>
- 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>
<br>
- 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>
<br>
- 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>
<br>
- 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>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Thanks,</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
</span><span lang="EN-US"><br>
</span><b><span lang="EN-US" style="font-size:13.5pt;font-family:"Arial","sans-serif";color:#888888">Daniel Krook</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Senior Software Engineer, IBM Cloud<br>
Distinguished IT Specialist (The Open Group & IBM Senior Certified)</span><span lang="EN-US"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="650" colspan="2" style="width:487.5pt;padding:0mm 0mm 0mm 0mm">
<div class="MsoNormal"><span lang="EN-US">
<hr size="2" width="100%" align="left">
</span></div>
</td>
</tr>
<tr>
<td width="396" valign="top" style="width:297.0pt;padding:0mm 0mm 0mm 0mm">
<p class="MsoNormal"><span lang="EN-US"><a href="http://www.linkedin.com/in/krook" target="_blank"><0E327443.jpg></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">
</span><span lang="EN-US"><a href="http://twitter.com/danielkrook" target="_blank"><0E696251.jpg></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">
</span><span lang="EN-US"><a href="http://github.com/krook" target="_blank"><0E483644.jpg></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">
</span><span lang="EN-US"><a href="http://www.meetup.com/members/13919430/" target="_blank"><0E434558.jpg></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">
</span><span lang="EN-US"><a href="http://www.slideshare.net/danielkrook" target="_blank"><0E317065.jpg></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">
</span><u><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue"><br>
</span></u><span lang="EN-US"><a href="http://krook.info/" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">krook.info</span></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F">
</span><span lang="EN-US"><o:p></o:p></span></p>
</td>
<td width="254" valign="top" style="width:190.5pt;padding:0mm 0mm 0mm 0mm">
<p class="MsoNormal" align="right" style="text-align:right"><span lang="EN-US"><0E100292.gif><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"><br>
<br>
<br>
<graycol.gif><span style="color:#424282">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</span><br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;color:#5F5F5F">From: </span><span lang="EN-US" style="font-size:10.0pt">Kendall Waters <<a href="mailto:kendall@openstack.org">kendall@openstack.org</a>></span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;color:#5F5F5F">To: </span><span lang="EN-US" style="font-size:10.0pt">Salvatore Orlando <<a href="mailto:salv.orlando@gmail.com">salv.orlando@gmail.com</a>></span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;color:#5F5F5F">Cc: </span><span lang="EN-US" style="font-size:10.0pt">"<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>></span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;color:#5F5F5F">Date: </span><span lang="EN-US" style="font-size:10.0pt">12/10/2015 11:46 AM</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;color:#5F5F5F">Subject: </span>
<span lang="EN-US" style="font-size:10.0pt">Re: [Openstack-track-chairs] Call for Speakers Feedback, Next Steps</span><span lang="EN-US"><o:p></o:p></span></p>
<div class="MsoNormal"><span lang="EN-US">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
<br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">Hi Salvatore,</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">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.
</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">Cheers,</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">Kendall</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">Kendall Waters<br>
OpenStack Marketing<u><span style="color:blue"><br>
</span></u></span><span lang="EN-US"><a href="mailto:kendall@openstack.org"><span style="font-size:13.5pt">kendall@openstack.org</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-size:13.5pt">On Dec 9, 2015, at 3:42 PM, Salvatore Orlando <</span><span lang="EN-US"><a href="mailto:salv.orlando@gmail.com"><span style="font-size:13.5pt">salv.orlando@gmail.com</span></a></span><span lang="EN-US" style="font-size:13.5pt">>
wrote:</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">I think the huge number of submissions that we get is kind of reasonable, considering the importance of the Openstack summit event.</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">Nevertheless, it is more than fair to add some rigour to the submission process.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">The three proposed additional questions are good in my opinion. They should actually be part of any talk abstract.</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">I think it could be worth trying to encourage submitters to add some evidence of the meat behind the abstract being reviewed.</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">Examples of such evidence could be:</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">- code repositories</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">- blog posts</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">- whitepapers, academic papers, or technical reports</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">- previous related work</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">- videos, slides, etc.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">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.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">This could be achieved with an "additional material" section.</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">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.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">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.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">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.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">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.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">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.</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">Salvatore</span><span lang="EN-US"><br>
<br>
<br>
</span><span lang="EN-US" style="font-size:13.5pt">On 9 December 2015 at 21:55, Niki Acosta (nikacost) <</span><span lang="EN-US"><a href="mailto:nikacost@cisco.com" target="_blank"><span style="font-size:13.5pt">nikacost@cisco.com</span></a></span><span lang="EN-US" style="font-size:13.5pt">>
wrote:</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US" style="font-family:"Calibri","sans-serif"">My thoughts, for what its worth:
</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Cap it at three submissions per person, including panels.
</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Strongly discourage straight up product-pitching sessions.
</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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.
</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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.
</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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.
</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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.
</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">:)</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Niki Acosta</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Cloud Evangelist</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Cisco Intercloud Services</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">(e) </span><span lang="EN-US"><a href="mailto:nikacost@cisco.com" target="_blank"><span style="font-family:"Calibri","sans-serif"">nikacost@cisco.com</span></a><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">(c) </span><span lang="EN-US"><a href="tel:%28%2B1%29%20512-912-6716" target="_blank"><span style="font-family:"Calibri","sans-serif"">(+1) 512-912-6716</span></a><br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">(t) @nikiacosta
</span><span lang="EN-US"><br>
<br>
<br>
</span><b><span lang="EN-US" style="font-family:"Calibri","sans-serif"">From: </span>
</b><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Lauren Sell <</span><span lang="EN-US"><a href="mailto:lauren@openstack.org" target="_blank"><span style="font-family:"Calibri","sans-serif"">lauren@openstack.org</span></a></span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">><b><br>
Date: </b>Wednesday, December 9, 2015 at 2:44 PM<b><br>
To: </b>"</span><span lang="EN-US"><a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank"><span style="font-family:"Calibri","sans-serif"">openstack-track-chairs@lists.openstack.org</span></a></span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">"
<</span><span lang="EN-US"><a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank"><span style="font-family:"Calibri","sans-serif"">openstack-track-chairs@lists.openstack.org</span></a></span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">><b><br>
Subject: </b>[Openstack-track-chairs] Call for Speakers Feedback, Next Steps</span><span lang="EN-US"><br>
<br>
</span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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:
</span><span lang="EN-US"><o:p></o:p></span></p>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Session Title </span>
<span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Session level (beginner, intermediate, advanced)</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Abstract</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Short Description (450 characters max for YouTube and mobile app)</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Select track from dropdown</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Tags</span><span lang="EN-US"><o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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:</span><span lang="EN-US"><o:p></o:p></span></p>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">Who is the intended audience for your session? Please be specific.</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">What is the problem or use case you’re addressing in this session?</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo1">
<span lang="EN-US" style="font-family:"Calibri","sans-serif"">What should attendees expect to learn?</span><span lang="EN-US"><o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US" style="font-family:"Calibri","sans-serif"">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
</span><span lang="EN-US"><a href="mailto:summit@openstack.org" target="_blank"><span style="font-family:"Calibri","sans-serif"">summit@openstack.org</span></a></span><span lang="EN-US" style="font-family:"Calibri","sans-serif"">) and hope to have track chairs
decided by mid-January. Any thoughts on the process? <br>
<br>
Thanks,<br>
Lauren </span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt"><br>
_______________________________________________<br>
Openstack-track-chairs mailing list<u><span style="color:blue"><br>
</span></u></span><span lang="EN-US"><a href="mailto:Openstack-track-chairs@lists.openstack.org"><span style="font-size:13.5pt">Openstack-track-chairs@lists.openstack.org</span></a></span><u><span lang="EN-US" style="font-size:13.5pt;color:blue"><br>
</span></u><span lang="EN-US"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank"><span style="font-size:13.5pt">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:13.5pt">_______________________________________________<br>
Openstack-track-chairs mailing list<u><span style="color:blue"><br>
</span></u></span><span lang="EN-US"><a href="mailto:Openstack-track-chairs@lists.openstack.org"><span style="font-size:13.5pt">Openstack-track-chairs@lists.openstack.org</span></a></span><span lang="EN-US" style="font-size:13.5pt"><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><tt><span lang="EN-US">_______________________________________________</span></tt><span lang="EN-US" style="font-family:"ＭＳ ゴシック""><br>
<tt>Openstack-track-chairs mailing list</tt><br>
<tt><a href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.openstack.org</a></tt><br>
<tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a></tt><br>
</span><span lang="EN-US"><br>
<br>
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">_______________________________________________<br>
Openstack-track-chairs mailing list<br>
<a href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
</div>
</body>
</html>