<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>Limiting submissions by company would be next to impossible to enforce. I say that as someone who has been responsible for collecting submissions from companies ranging in size from 40 people to over 70,000 so that we could post them to a blog. And job
transitions would create a mess for the foundation to deal with. </div>
<div><br>
</div>
<div>As in all things, we’re never going to make everyone happy. I think the spaghetti-against-the-wall thing happens for a good reason: people want to attend the summits, and it’s far easier to have travel and expenses approved when you’re on the schedule
as a speaker. So while limiting speaking submissions seems to be an agreeable alternative, we’re treating a symptom, not the cause. </div>
<div><br>
</div>
<div>Not sure we’ve done this in the past, but I’ve seen conferences that provide Business/Attendance Justification Toolkits. </div>
<div><br>
</div>
<div>Another thought might be to allow for optional “Donate to the Travel Scholarship Fund!” checkboxes to allow ticket purchasers to add an extra amount (say $25, $50, or $100) to their purchase…. Similar to what your neighborhood drugstore does to raise money
for health charities. By making it optional, I don’t find it to be obtrusive in any way. At the very least, it could be a cool experiment and if it funds one person, it’s worth it to me!</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>Rossella Sblendido <<a href="mailto:rossble@gmail.com">rossble@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, December 10, 2015 at 6:33 AM<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>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi all,<br>
<br>
</div>
+1 to limiting the number of submissions per person<br>
</div>
+1 to Stefano's proposal to have a feature in the track chair tool to get all the submission by the same speaker<br>
</div>
<div>+1 to have a random subset of presentations to vote on in the public voting <br>
</div>
<div><br>
</div>
I like the idea of adding a field where the submitter can explain why his/her talk should be selected. I'd like to see facts listed in this field. This should be the place where the submitter can add info to prove that she/he has first hand knowledge regarding
the topic. As Salvatore was already suggesting, I'd encourage people to share code repositories, papers and anything that can be useful to show their contribution.<br>
<br>
</div>
I am OK with asking if the submitter has already presented somewhere else before. It can be anywhere else, university, local meetups... this shouldn't discourage new voices.<br>
</div>
For frequent speakers we can use the data collected in Tokyo. Are they online somewhere?<br>
<br>
</div>
cheers,<br>
<br>
</div>
Rossella<br>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
<div>
<div>
<div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Dec 10, 2015 at 10:08 AM, Henry Nash <span dir="ltr">
<<a href="mailto:henry.nash@uk.ibm.com" target="_blank">henry.nash@uk.ibm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font face="sans-serif" size="2">So a couple 0.01 old English pennies:</font><br>
<br>
<font face="sans-serif" size="2">+1 for limiting submissions to 3</font><br>
<font face="sans-serif" size="2">+1 for limiting number of speakers to 3, except for panels (which I agree are good...although I'd love to encourage more question from the audience...rather than just moderator questions passed around)</font><br>
<font face="sans-serif" size="2">-1 for limiting submissions by company (let's judge submissions on merit, not on source)</font><br>
<font face="sans-serif" size="2">-1 for asking for video of previous talks (I absolutely get the goal of trying to get good speakers....I'm just concerned we raise the barrier too high for submission)</font><br>
<font face="sans-serif" size="2">+1 for trying to get a better idea of the content from the submission (Maybe don't ask for a longer abstract, but have a section that asks for a simple bullet point list of the key topics covered?)</font><br>
<br>
<font face="sans-serif" size="2">Henry</font><br>
<br>
<br>
<br>
<font face="sans-serif" size="1" color="#5f5f5f">From: </font><font face="sans-serif" size="1">"Clark, Robert Graham" <<a href="mailto:robert.clark@hpe.com" target="_blank">robert.clark@hpe.com</a>></font><br>
<font face="sans-serif" size="1" color="#5f5f5f">To: </font><font face="sans-serif" size="1">John Dickinson <<a href="mailto:me@not.mn" target="_blank">me@not.mn</a>>, "<a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank">openstack-track-chairs@lists.openstack.org</a>"
<<a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank">openstack-track-chairs@lists.openstack.org</a>></font><br>
<font face="sans-serif" size="1" color="#5f5f5f">Date: </font><font face="sans-serif" size="1">10/12/2015 01:08</font><span class=""><br>
<font face="sans-serif" size="1" color="#5f5f5f">Subject: </font><font face="sans-serif" size="1">Re: [Openstack-track-chairs] Call for Speakers Feedback, Next Steps</font><br>
</span>
<hr noshade="">
<div>
<div class="h5"><br>
<br>
<br>
<tt><font size="2">I agree with Duncan's proposed questions and the idea of capping the number of submissions somewhere from 3-5 per person (per company doesn't work imho).<br>
<br>
The biggest problem I've found as a track chair is not really knowing what a talk will focus on (or even what the content will be) from the abstract that's presented to me - this problem is significantly compounded when the talk gets many votes.<br>
<br>
We certainly have to improve the quality of abstracts and we need a way to reduce the noise level that the voters are faced with. I'm a track chair and I could barely stand leafing through the many submissions on my chosen area of specialization (security)
I can't imagine being your average attendee and really spending multiple hours voting on talks - that's just not realistic.<br>
<br>
Cheers<br>
-Rob<br>
<br>
(Also +1 to an etherpad)<br>
<br>
> -----Original Message-----<br>
> From: John Dickinson [</font></tt><a href="mailto:me@not.mn" target="_blank"><tt><font size="2">mailto:me@not.mn</font></tt></a><tt><font size="2">]<br>
> Sent: 09 December 2015 22:34<br>
> To: <a href="mailto:openstack-track-chairs@lists.openstack.org" target="_blank">
openstack-track-chairs@lists.openstack.org</a><br>
> Subject: Re: [Openstack-track-chairs] Call for Speakers Feedback, Next Steps<br>
> <br>
> Is there a difference between "submitter" and "presenter"? eg in the past one person may submit a lot of talks, all with different presenters<br>
> on them.<br>
> <br>
> I like changing the incentivization away from the spaghetti approach (throw a bunch on the wall and see what sticks). Limiting submissions<br>
> per person (and one person not being in more than a certain number of talks) is a good start.<br>
> <br>
> <br>
> Another idea (one I'm much less sure of) is having track chairs or someone giving guidance for submissions. eg "In the storage track, we'd<br>
> like to hear talks that (1) technically explain parts of the code or (2) describe a production deployment and how that contributed back<br>
> upstream". I'm not entirely sure how that would end up resulting in a different final talk selection, but I'd hope it might raise the quality of<br>
> submissions.<br>
> <br>
> --John<br>
> <br>
> <br>
> <br>
> On 9 Dec 2015, at 14:09, Kenneth Hui wrote:<br>
> <br>
> > I would second the limit on number of submissions per person.<br>
> ><br>
> > Also, we may want to consider having a submitter upload or link to a video<br>
> > of him or her presenting; this would help in assessing someone's ability to<br>
> > present to an audience.<br>
> ><br>
> > Thank you.<br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Kenneth Hui <<a href="mailto:ken@platform9.com" target="_blank">ken@platform9.com</a>> | Director of Technical Marketing and<br>
> > Partner Alliances<br>
> > Platform9 <</font></tt><a href="http://platform9.com/" target="_blank"><tt><font size="2">http://platform9.com/</font></tt></a><tt><font size="2">> - *"Private Clouds Made Easy"*<br>
> > (c) <a href="tel:347.997.0935" value="+13479970935" target="_blank">347.997.0935</a> / (t) @hui_kenneth <</font></tt><a href="https://twitter.com/hui_kenneth" target="_blank"><tt><font size="2">https://twitter.com/hui_kenneth</font></tt></a><tt><font size="2">><br>
> ><br>
> > Blogs:<br>
> ><br>
> > *<a href="http://blog.platform9.com/" target="_blank">http://blog.platform9.com/</a><br>
> > <</font></tt><a href="http://blog.platform9.com/" target="_blank"><tt><font size="2">http://blog.platform9.com/</font></tt></a><tt><font size="2">>**<a href="http://cloudarchitectmusings.com/" target="_blank">http://cloudarchitectmusings.com/</a><br>
> > <</font></tt><a href="http://cloudarchitectmusings.com/" target="_blank"><tt><font size="2">http://cloudarchitectmusings.com/</font></tt></a><tt><font size="2">>*<br>
> ><br>
> ><br>
> ><br>
> > On Wed, Dec 9, 2015 at 3:44 PM, Lauren Sell <<a href="mailto:lauren@openstack.org" target="_blank">lauren@openstack.org</a>> wrote:<br>
> ><br>
> >> Hello Tokyo Summit track chairs,<br>
> >><br>
> >> We’re moving quickly to open the call for speakers for the Austin<br>
> >> Summit next week and want to make sure we incorporate feedback from prior<br>
> >> discussions on this list. Unfortunately, we didn’t have much turnout in<br>
> >> Tokyo for the Summit tools & processes session, where we were hoping to<br>
> >> facilitate more discussion. We only had two people show up (outside of<br>
> >> Foundation staff), so we primarily discussed the mobile app and reviewed<br>
> >> the prototype.<br>
> >><br>
> >> Based on earlier feedback in this thread, there is a desire to manage the<br>
> >> growing number of submissions while increasing the quality. We have two<br>
> >> levers we could pull for the submission process, but need to make decisions<br>
> >> by the end of this week:<br>
> >> 1. Do we want to cap the number of sessions that each person can submit at<br>
> >> 5?<br>
> >> 2. Do we want to add any questions or requirements to the submission form?<br>
> >> See suggestions below.<br>
> >><br>
> >> For #2, we are already making a few minor changes this round to improve<br>
> >> session tagging and ask speakers for “links to past presentations” and<br>
> >> “areas of expertise.” For the session submission, we currently ask:<br>
> >><br>
> >> - Session Title<br>
> >> - Session level (beginner, intermediate, advanced)<br>
> >> - Abstract<br>
> >> - Short Description (450 characters max for YouTube and mobile app)<br>
> >> - Select track from dropdown<br>
> >> - Tags<br>
> >><br>
> >> I would suggest consolidating the abstract and short description to be one<br>
> >> question (because submitters often copy/paste it anyway), and then ask a<br>
> >> few additional questions:<br>
> >><br>
> >> - Who is the intended audience for your session? Please be specific.<br>
> >> - What is the problem or use case you’re addressing in this session?<br>
> >> - What should attendees expect to learn?<br>
> >><br>
> >> We are also making a few changes to the tracks, primarily grouping them<br>
> >> into content categories to better promote and layout the content across the<br>
> >> week.<br>
> >><br>
> >> Finally, we will very soon need to select the next round of track chairs.<br>
> >> The Foundation has typically accepted nominations from the community and<br>
> >> appointed track chairs based on subject matter expertise, contributions,<br>
> >> working group involvement, etc. To help bring in new perspectives, one<br>
> >> proposal was to ask track chairs to decide two people from their team who<br>
> >> would continue for the next cycle and nominate two new people from the<br>
> >> community to keep things fresh. We’ve gotten a lot of feedback that another<br>
> >> community vote for track chairs is not desirable, but we could more broadly<br>
> >> communicate the window for nominations. We’re accepting nominations now<br>
> >> (email <a href="mailto:summit@openstack.org" target="_blank">summit@openstack.org</a>) and hope to have track chairs decided by<br>
> >> mid-January. Any thoughts on the process?<br>
> >><br>
> >> Thanks,<br>
> >> Lauren<br>
> >><br>
> >> _______________________________________________<br>
> >> Openstack-track-chairs mailing list<br>
> >> <a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank">
Openstack-track-chairs@lists.openstack.org</a><br>
> >> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</font></tt></a><tt><font size="2"><br>
> >><br>
> >><br>
> > _______________________________________________<br>
> > Openstack-track-chairs mailing list<br>
> > <a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank">Openstack-track-chairs@lists.openstack.org</a><br>
> > </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</font></tt></a><tt><font size="2"><br>
_______________________________________________<br>
Openstack-track-chairs mailing list<br>
<a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank">Openstack-track-chairs@lists.openstack.org</a><br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</font></tt></a><tt><font size="2"><br>
</font></tt><br>
<br>
</div>
</div>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number 741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU<br>
<br>
<br>
_______________________________________________<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" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>