<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class="">
<br class=""><div><blockquote type="cite" class=""><div class="">On Dec 10, 2015, at 10:45 AM, Kendall Waters <<a href="mailto:kendall@openstack.org" class="">kendall@openstack.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Salvatore,<div class=""><br class=""></div><div 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. </div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Kendall</div><div class=""><br class=""></div><div class=""><div apple-content-edited="true" class="">
Kendall Waters<br class="">OpenStack Marketing<br class=""><a href="mailto:kendall@openstack.org" class="">kendall@openstack.org</a><br class=""><br class="">
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 9, 2015, at 3:42 PM, Salvatore Orlando <<a href="mailto:salv.orlando@gmail.com" class="">salv.orlando@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I think the huge number of submissions that we get is kind of reasonable, considering the importance of the Openstack summit event.<div class="">Nevertheless, it is more than fair to add some rigour to the submission process.</div><div class=""><br class=""></div><div class="">The three proposed additional questions are good in my opinion. They should actually be part of any talk abstract.</div><div class="">I think it could be worth trying to encourage submitters to add some evidence of the meat behind the abstract being reviewed.</div><div class="">Examples of such evidence could be:</div><div class="">- code repositories</div><div class="">- blog posts</div><div class="">- whitepapers, academic papers, or technical reports</div><div class="">- previous related work</div><div class="">- videos, slides, etc.</div><div class=""><br class=""></div><div 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.</div><div class=""><br class=""></div><div class="">This could be achieved with an "additional material" section.</div><div 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.</div><div class=""><br class=""></div><div 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.</div><div class=""><br class=""></div><div 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.</div><div class=""><br class=""></div><div 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.</div><div class=""><br class=""></div><div 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.</div><div class=""><br class=""></div><div class="">Salvatore</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 9 December 2015 at 21:55, Niki Acosta (nikacost) <span dir="ltr" class=""><<a href="mailto:nikacost@cisco.com" target="_blank" class="">nikacost@cisco.com</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; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">
<div class="">My thoughts, for what its worth: </div>
<div class=""><br class="">
</div>
<div class="">Cap it at three submissions per person, including panels. </div>
<div class="">Strongly discourage straight up product-pitching sessions. </div>
<div 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. </div>
<div 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. </div>
<div 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. </div>
<div class=""><br class="">
</div>
<div 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. </div>
<div class=""><br class="">
</div>
<div class="">:)</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div class="">Niki Acosta</div>
<div class="">Cloud Evangelist</div>
<div class="">Cisco Intercloud Services</div>
<div class="">(e) <a href="mailto:nikacost@cisco.com" target="_blank" class="">nikacost@cisco.com</a></div>
<div class="">(c) <a href="tel:%28%2B1%29%20512-912-6716" value="+15129126716" target="_blank" class="">(+1) 512-912-6716</a></div>
<div class="">(t) @nikiacosta </div>
</div>
<br class="">
</div>
</div>
<div class=""><br class="">
</div>
<span class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>Lauren Sell <<a href="mailto:lauren@openstack.org" target="_blank" class="">lauren@openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Wednesday, December 9, 2015 at 2:44 PM<br class="">
<span style="font-weight:bold" class="">To: </span>"<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>><br class="">
<span style="font-weight:bold" class="">Subject: </span>[Openstack-track-chairs] Call for Speakers Feedback, Next Steps<br class="">
</div><div class=""><div class="h5">
<div class=""><br class="">
</div>
<div class="">
<div style="word-wrap:break-word" 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:
<div class="">
<ul class="">
<li class="">Session Title </li><li class="">Session level (beginner, intermediate, advanced)</li><li class="">Abstract</li><li class="">Short Description (450 characters max for YouTube and mobile app)</li><li class="">Select track from dropdown</li><li class="">Tags</li></ul>
</div>
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:<br class="">
<ul class="">
<li class="">Who is the intended audience for your session? Please be specific.</li><li class="">What is the problem or use case you’re addressing in this session?</li><li class="">What should attendees expect to learn?</li></ul>
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
<a href="mailto:summit@openstack.org" target="_blank" class="">summit@openstack.org</a>) and hope to have track chairs decided by mid-January. Any thoughts on the process? <br class="">
<br class="">
Thanks,<br class="">
Lauren </div>
</div>
</div></div></span>
</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>
_______________________________________________<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" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<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="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs<br class=""></div></blockquote></div><br class=""></div></body></html>