<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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* 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;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{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 WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 56.7pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sorting function is definitely needed.
<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 an anonymized description of community voters would be nice to see if any community bias exists.<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">Otherwise, great tool, easy process, great co-chairs
</span><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Ulas<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"><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""> Kunzmann, Gerald [mailto:kunzmann@docomolab-euro.com]
<br>
<b>Sent:</b> Thursday, August 25, 2016 12:22 AM<br>
<b>To:</b> openstack-track-chairs@lists.openstack.org<br>
<b>Subject:</b> Re: [Openstack-track-chairs] Track Chair Feedback<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1 nice tool.<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">Would be great to have a sort function e.g. by “community vote”.<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">Gerald<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"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Travis McPeak [<a href="mailto:travis.mcpeak@gmail.com">mailto:travis.mcpeak@gmail.com</a>]
<br>
<b>Sent:</b> Donnerstag, 25. August 2016 02:02<br>
<b>To:</b> Christopher Aedo <<a href="mailto:doc@aedo.net">doc@aedo.net</a>>; <a href="mailto:openstack-track-chairs@lists.openstack.org">
openstack-track-chairs@lists.openstack.org</a><br>
<b>Subject:</b> Re: [Openstack-track-chairs] Track Chair Feedback<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">+1 great tool and easy process overall.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks!<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Aug 24, 2016, 4:47 PM Christopher Aedo <<a href="mailto:doc@aedo.net">doc@aedo.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal">Thank you for all the hard work you've put into this tool (and all the<br>
other OpenStack bits you're always improving.) This was my second<br>
time around and I thought the tool worked great - looking forward to<br>
seeing even more improvements for Boston!<br>
<br>
Thank you Jimmy!<br>
<br>
-Christopher<br>
<br>
On Wed, Aug 24, 2016 at 3:20 PM, Jimmy McArthur <<a href="mailto:jimmy@openstack.org" target="_blank">jimmy@openstack.org</a>> wrote:<br>
> All -<br>
><br>
> Thanks again for your hard (and quick!) work on the OpenStack Barcelona<br>
> Summit Track selections. You all did an amazing job and we're really<br>
> grateful to each of you.<br>
><br>
> I took notes of feedback, but please feel free to add to the list if you<br>
> feel I've missed something:<br>
><br>
> Better ability for Track Chairs to merge<br>
><br>
> Option to email all speakers from one or more presentations<br>
> Ability for Speakers to submit/propose a new Title / Abstract as an<br>
> attachment or within the thread<br>
> Track Chairs ability to deactivate merged talks, and save one with new<br>
> abstract (or merge into a new record so we don't taint the originals)<br>
><br>
> Email issues<br>
><br>
> Track conversations with users within the Track Chair tool i/o just via<br>
> email. Could also consider using ZenDesk API for this?<br>
> There was a problem with Sendgrid API this go round, so there were just<br>
> generally problems. They were:<br>
><br>
> No CC of other track chairs<br>
> Reply address was <a href="mailto:noreply@openstack.org" target="_blank">noreply@openstack.org</a> i/o the ZenDesk ticket<br>
> Adding name of Presentation and other details automatically within the email<br>
> "Track chair XYZ has a question about your presentation: ABCD"<br>
> Email all speakers i/o just one<br>
><br>
> Need the option back of being able to compare everyone's list side by side<br>
><br>
> The new method of using the dropdown makes it difficult for the team to<br>
> compare selected talks<br>
> A way to auto-select common talks for placement in the team section would be<br>
> cool, or at least a way to quickly view that list, along with the # of team<br>
> members that selected each talk<br>
><br>
> An option for a Track to "Close" their selections<br>
><br>
> Send an email to track chairs list<br>
> Mark Track as "Closed" for non-admins<br>
><br>
> Another suggestion for the Boston CFP process might be to consider separate<br>
> user and developer sub-tracks. For example. What might be considered a How<br>
> To/Best Practice for developers might be completely irrelevant to users.<br>
> We at Dev Tools track found out that there are a lot of drafts related to<br>
> the CI/CD and Testing processes. Seems reasonable to add such a track<br>
> (Deployment and Testing) as an option for the next summit. What do you<br>
> think?<br>
><br>
><br>
> Thank you again!<br>
> Jimmy<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>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><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>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>