<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1  l think that would be a great idea to have a place in the tool where chairs could explain their choices. Perhaps, have a rating system. This would allow presenters to have some feedback on their submission.<br><br></div><div><br>On Aug 25, 2016, at 4:13 PM, Nick Chase <<a href="mailto:nchase@mirantis.com">nchase@mirantis.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  
  
    <p>Well, when we were working on our track (both this time and for
      Austin) what we did was break it down into sections (for example,
      we might have 3 talks on "DevOps") and then try to choose a talk
      from each section.  In some cases, we had to choose between
      similar talks, and discuss what our rationale was; it wouldn't be
      a bad thing to provide a place for track chairs to explain their
      choices.  It would even provide a way for submitters to improve
      their submissions for next time.</p>
    <p>----  Nick<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 8/25/2016 3:50 PM, Shilla Saebi
      wrote:<br>
    </div>
    <blockquote cite="mid:CAPrU3jHpByRiUrOKBhdwpk8o76OCUoQNA0jN+0jWTAsgDtLx2A@mail.gmail.com" type="cite">
      <div dir="ltr">I think we should come up with a way for track
        chairs who have to make selections on talks that were submitted
        by members of their own company or team to be fair. I noticed a
        few talks go through where the track chairs worked for the same
        company as the talks that were selected, and other talks with
        more complete abstracts (in my opinion) and a more diverse set
        of speakers, was not selected. </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Aug 25, 2016 at 2:18 PM, Nathan
          C Ziemann <span dir="ltr"><<a moz-do-not-send="true" href="mailto:ziemann@us.ibm.com" target="_blank">ziemann@us.ibm.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="auto">
              <div>+1 on export. </div>
              <div><br>
              </div>
              <div>We wrapped up our final selections using a
                spreadsheet which makes it easy to evaluate multiple
                criteria and chair votes/comments in one view. <br>
                <br>
                Nate Ziemann
                <div><span>Sent from my iPhone</span></div>
              </div>
              <div>
                <div class="h5">
                  <div><br>
                    On Aug 25, 2016, at 9:54 AM, Nick Chase <<a moz-do-not-send="true" href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>
                    wrote:<br>
                    <br>
                  </div>
                  <blockquote type="cite">
                    <div>Actually the last two summits tracks I've
                      worked with have finished up in spreadsheets,
                      where we've organized submissions by topic and
                      marked off who voted for each.  It really made the
                      final processing easier. 
                      <div><br>
                      </div>
                      <div>I'd love to see a simple "export" function so
                        we don't wind up doing it by hand.</div>
                      <div><br>
                      </div>
                      <div>---- Nick<br>
                        <br>
                        On Thursday, August 25, 2016, Amrith Kumar <<a moz-do-not-send="true" href="mailto:amrith@tesora.com" target="_blank">amrith@tesora.com</a>>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          <div link="blue" vlink="purple" lang="EN-US">
                            <div>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d">On
                                    the whole, I think the process and
                                    the tool were fine, there were some
                                    hiccups that you have already
                                    identified.</span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d"> </span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d">I
                                    found the user interface
                                    (specifically the two pane format
                                    and the sizing requirement) to be a
                                    little troublesome. Eventually I
                                    just grabbed the json off the
                                    interface and populated a
                                    spreadsheet and that worked out much
                                    easier.</span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d"> </span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d">Why
                                    was that?</span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d"> </span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d">I
                                    wanted to tag each of the 93 talks
                                    with a bunch of tags that I found to
                                    be useful, things like the names of
                                    the projects covered, sales-pitch,
                                    customer-story, performance, … and
                                    so on, and later filter talks based
                                    on those tags.</span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d"> </span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d">So,
                                    if the next iteration of the tool
                                    had a way in which each chair could
                                    tag talks using an arbitrary
                                    (private) set of tags, that would be
                                    nifty.</span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d"> </span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d">-amrith
                                  </span></font></p>
                              <p class="MsoNormal"><font face="Consolas" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:Consolas;color:#1f497d"> </span></font></p>
                              <div style="border:none;border-left:solid
                                blue 1.5pt;padding:0in 0in 0in 4.0pt">
                                <div>
                                  <div style="border:none;border-top:solid
                                    #e1e1e1 1.0pt;padding:3.0pt 0in 0in
                                    0in">
                                    <p class="MsoNormal"><b><font face="Calibri" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font face="Calibri" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
                                          Kunzmann, Gerald [mailto:<a moz-do-not-send="true">kunzmann@docomolab-eur<wbr>o.com</a>]
                                          <br>
                                          <b><span style="font-weight:bold">Sent:</span></b>
                                          Thursday, August 25, 2016 3:22
                                          AM<br>
                                          <b><span style="font-weight:bold">To:</span></b>
                                          <a moz-do-not-send="true">openstack-track-chairs@lists.o<wbr>penstack.org</a><br>
                                          <b><span style="font-weight:bold">Subject:</span></b>
                                          Re: [Openstack-track-chairs]
                                          Track Chair Feedback</span></font></p>
                                  </div>
                                </div>
                                <p class="MsoNormal"><font face="Times
                                    New Roman" size="3"><span style="font-size:12.0pt"> </span></font></p>
                                <p class="MsoNormal"><font face="Calibri" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">+1
                                      nice tool.</span></font></p>
                                <p class="MsoNormal"><font face="Calibri" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></font></p>
                                <p class="MsoNormal"><font face="Calibri" color="#1f497d" size="2"><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”.</span></font></p>
                                <p class="MsoNormal"><font face="Calibri" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></font></p>
                                <p class="MsoNormal"><font face="Calibri" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Gerald</span></font></p>
                                <p class="MsoNormal"><font face="Calibri" color="#1f497d" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></font></p>
                                <p class="MsoNormal"><b><font face="Calibri" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font face="Calibri" size="2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
                                      Travis McPeak [<a moz-do-not-send="true">mailto:travis.mcpeak@gmail.co<wbr>m</a>]
                                      <br>
                                      <b><span style="font-weight:bold">Sent:</span></b>
                                      Donnerstag, 25. August 2016 02:02<br>
                                      <b><span style="font-weight:bold">To:</span></b>
                                      Christopher Aedo <<a moz-do-not-send="true">doc@aedo.net</a>>;
                                      <a moz-do-not-send="true">openstack-track-chairs@lists.o<wbr>penstack.org</a><br>
                                      <b><span style="font-weight:bold">Subject:</span></b>
                                      Re: [Openstack-track-chairs] Track
                                      Chair Feedback</span></font></p>
                                <p class="MsoNormal"><font face="Times
                                    New Roman" size="3"><span style="font-size:12.0pt"> </span></font></p>
                                <p class="MsoNormal"><font face="Times
                                    New Roman" size="3"><span style="font-size:12.0pt">+1 great
                                      tool and easy process overall.</span></font></p>
                                <div>
                                  <p class="MsoNormal"><font face="Times
                                      New Roman" size="3"><span style="font-size:12.0pt"> </span></font></p>
                                </div>
                                <div>
                                  <p class="MsoNormal" style="margin-bottom:12.0pt"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">Thanks!</span></font></p>
                                  <div>
                                    <div>
                                      <p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">On
                                            Wed, Aug 24, 2016, 4:47 PM
                                            Christopher Aedo <<a moz-do-not-send="true">doc@aedo.net</a>>
                                            wrote:</span></font></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"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">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 moz-do-not-send="true">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 moz-do-not-send="true">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>
                                            >
                                            ______________________________<wbr>_________________<br>
                                            > Openstack-track-chairs
                                            mailing list<br>
                                            > <a moz-do-not-send="true">Openstack-track-chairs@lists.o<wbr>penstack.org</a><br>
                                            > <a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-track-chairs</a><br>
                                            ><br>
                                            <br>
______________________________<wbr>_________________<br>
                                            Openstack-track-chairs
                                            mailing list<br>
                                            <a moz-do-not-send="true">Openstack-track-chairs@lists.o<wbr>penstack.org</a><br>
                                            <a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-track-chairs</a></span></font></p>
                                    </blockquote>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </div>
                        </blockquote>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            Openstack-track-chairs mailing list<br>
            <a moz-do-not-send="true" href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.<wbr>openstack.org</a><br>
            <a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-track-chairs</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      Nick Chase, Head of Technical and Marketing Content, Mirantis<br>
      Editor in Chief, OpenStack:Unlocked</div>
  

</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Openstack-track-chairs mailing list</span><br><span><a href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.openstack.org</a></span><br><span><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><br></div></blockquote></body></html>