<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Hi all -<br>
<br>
Just wanted to chime in and say thank you for your hard work and
enthusiasm as Track Chairs. We are listening to your requests and have
done our best to incorporate some of them into this round. The rest of
the changes we're planning for Barcelona, so stay tuned and know that
we're working on them :)<br>
<br>
Here's what I've got so far. Please feel free to add on to them:<br>
<br>
<div class="description" style="margin: 0px; padding: 0px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; color: rgb(51,
51, 51); font-family: arial, 'lucida grandriale', 'lucida sans unicode',
tahoma, sans-serif; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: 16.5px;
orphans: auto; text-align: start; text-indent: 0px; text-transform:
none; white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background: rgb(255, 255, 255);"><div
class="wiki" style="margin: 0px; padding: 0px; border: 0px; outline:
0px; font-size: 11px; vertical-align: baseline; background:
transparent;"><p style="margin: 0px 0px 5px; padding: 0px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; background:
transparent;">This list is taken from general feedback from Track Chairs
+ requests from Foundation Staff</p><ul style="margin: 0px 0px 6px;
padding: 0px 0px 0px 40px; border: 0px; outline: 0px; font-size: 11px;
vertical-align: baseline; list-style: none; background: transparent;"><li
style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-size:
11px; vertical-align: baseline; list-style: disc outside none;
background: transparent;">Need to be able to set the # of alternates,
per track</li><li style="margin: 0px; padding: 0px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; list-style:
disc outside none; background: transparent;">For presentations that are
moved to another track, have the tool record something in the comments
showing what track it came from</li><li style="margin: 0px; padding:
0px; border: 0px; outline: 0px; font-size: 11px; vertical-align:
baseline; list-style: disc outside none; background: transparent;">Modify
submissions list by dividing it into three sections:<ul style="margin:
0px 0px 6px; padding: 0px 0px 0px 40px; border: 0px; outline: 0px;
font-size: 11px; vertical-align: baseline; list-style: none; background:
transparent;"><li style="margin: 0px; padding: 0px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; list-style:
disc outside none; background: transparent;">new (which are not reviewed
by you)</li><li style="margin: 0px; padding: 0px; border: 0px; outline:
0px; font-size: 11px; vertical-align: baseline; list-style: disc
outside none; background: transparent;">reviewed (those that were
already reviewed by you)</li><li style="margin: 0px; padding: 0px;
border: 0px; outline: 0px; font-size: 11px; vertical-align: baseline;
list-style: disc outside none; background: transparent;">moved (those
that were moved from other tracks to yours)</li></ul></li><li
style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-size:
11px; vertical-align: baseline; list-style: disc outside none;
background: transparent;">Add "Review" button to each submission in
order to make review process more consistent for Track Chairs<ul
style="margin: 0px 0px 6px; padding: 0px 0px 0px 40px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; list-style:
none; background: transparent;"><li style="margin: 0px; padding: 0px;
border: 0px; outline: 0px; font-size: 11px; vertical-align: baseline;
list-style: disc outside none; background: transparent;">"Review" button
will cover next logic just as you mentioned, but it will push reviewers
to leave a feedback for teammates. By use of such mechanism OpenStack
committee will be sure that all submissions were reviewed by not just
scrolling down a web page.</li></ul></li><li style="margin: 0px;
padding: 0px; border: 0px; outline: 0px; font-size: 11px;
vertical-align: baseline; list-style: disc outside none; background:
transparent;">Email notifications. It would be very useful to get
notification about:<ul style="margin: 0px 0px 6px; padding: 0px 0px 0px
40px; border: 0px; outline: 0px; font-size: 11px; vertical-align:
baseline; list-style: none; background: transparent;"><li style="margin:
0px; padding: 0px; border: 0px; outline: 0px; font-size: 11px;
vertical-align: baseline; list-style: disc outside none; background:
transparent;">Submission comments (it would be useful to have
notification system similar to IRC, using Track Chair names and post a
comment to whole team).</li><li style="margin: 0px; padding: 0px;
border: 0px; outline: 0px; font-size: 11px; vertical-align: baseline;
list-style: disc outside none; background: transparent;">Moved
submissions (for now, as i can see, we have to revisit portal in order
to check if any submission was moved to the track that i am responsible
for).</li></ul></li><li style="margin: 0px; padding: 0px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; list-style:
disc outside none; background: transparent;">So some way of doing a
quick pass and then iterating back over the ranks to sort them out,
would be really helpful. Some radio buttons to rank them (3 levels is
enough), and the ability to sort based on rank would be a great
addition.</li><li style="margin: 0px; padding: 0px; border: 0px;
outline: 0px; font-size: 11px; vertical-align: baseline; list-style:
disc outside none; background: transparent;">The ability to dump the
entire list of talks for a category into a CSV file (rather than the
current JSON ref’d by unique URLs) so we can import into excel etc – and
apply our own assessment columns – would be a great fallback to
building this into the tool. And save all that pointing and clicking.</li><li
style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-size:
11px; vertical-align: baseline; list-style: disc outside none;
background: transparent;">A time stamp on the comments from other tracks
chairs within my track</li><li style="margin: 0px; padding: 0px;
border: 0px; outline: 0px; font-size: 11px; vertical-align: baseline;
list-style: disc outside none; background: transparent;">A "seen by"
flag that indicates whether or not comments have been viewed</li><li
style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-size:
11px; vertical-align: baseline; list-style: disc outside none;
background: transparent;">Email notification to other track chairs when
someone on your team makes a comment (could be an option where you
opt-in)</li><li style="margin: 0px; padding: 0px; border: 0px; outline:
0px; font-size: 11px; vertical-align: baseline; list-style: disc outside
none; background: transparent;">(From Jimmy) - Speed up the entire
tool. It's super draggy.</li><li style="margin: 0px; padding: 0px;
border: 0px; outline: 0px; font-size: 11px; vertical-align: baseline;
list-style: disc outside none; background: transparent;">Add the option
to mark a presenation as "Maybe" or "Revisit". Right now it's eitehr on
the list, or off the list. Which makes it difficult to go back and
review presentations you weren't sure about since you can't find them.
So maybe something to Flag a presentation with the option to filter by
flag.</li></ul></div></div>
<br class="Apple-interchange-newline">
Thanks!<br>
Jimmy<br>
<br>
<span><a class="moz-txt-link-abbreviated" href="mailto:Sean_McGinnis@DELL.com">Sean_McGinnis@DELL.com</a> wrote:</span><br>
<blockquote
cite="mid:69112dd0cb2442c9bcccd87e00c590a0@AUSX13MPC103.AMER.DELL.COM"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal">Good enough for me. ;)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks Robert.<o:p></o:p></p>
<p>-----Original Message-----<br>
From: Clark, Robert Graham [<a class="moz-txt-link-freetext" href="mailto:robert.clark@hpe.com">mailto:robert.clark@hpe.com</a>] <br>
Sent: Tuesday, February 23, 2016 9:12 AM<br>
To: McGinnis, Sean ; <a class="moz-txt-link-abbreviated" href="mailto:yihleong@gmail.com">yihleong@gmail.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:kendall@openstack.org">kendall@openstack.org</a><br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:openstack-track-chairs@lists.openstack.org">openstack-track-chairs@lists.openstack.org</a><br>
Subject: Re: [Openstack-track-chairs] Part Two: Austin Session Selection
Process<br>
<br>
Horrible hack warning :
<a class="moz-txt-link-freetext" href="https://gist.github.com/hyakuhei/803b9a47681f569b343d">https://gist.github.com/hyakuhei/803b9a47681f569b343d</a><br>
<br>
Copy paste the tables from each page of results in the track tool into a
plain old text file<br>
Run the above script over the file and you’ll get something CSV-ish,
enough that excel/google sheets can import it happily<br>
<br>
Again, zero points for coding this up but as an ugly hack it does most
of what you want.<br>
<br>
From: <a class="moz-txt-link-rfc2396E" href="mailto:Sean_McGinnis@DELL.com">"Sean_McGinnis@DELL.com"</a><br>
Date: Tuesday, 23 February 2016 15:05<br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:yihleong@gmail.com">"yihleong@gmail.com"</a>, <a class="moz-txt-link-rfc2396E" href="mailto:kendall@openstack.org">"kendall@openstack.org"</a><br>
Cc: <a class="moz-txt-link-rfc2396E" href="mailto:openstack-track-chairs@lists.openstack.org">"openstack-track-chairs@lists.openstack.org"</a><br>
Subject: Re: [Openstack-track-chairs] Part Two: Austin Session Selection
Process<br>
<br>
I think something like this could be very useful.<br>
<br>
It would also be great if there was some kind of filter setting where I
could mark proposals that are a definite No to me so that they don’t
show up in the list anymore. That would help work through the list to
get down to a smaller subset that I think are
real candidates, rather than needing to sort through the same ones over
and over.<br>
<br>
Or an export to Excel or similar like I think was mentioned before. I
can make that list manually, but 6 pages of proposals is a lot to
transcribe.<br>
<br>
From: Yih Leong, Sun. [<a class="moz-txt-link-freetext" href="mailto:yihleong@gmail.com">mailto:yihleong@gmail.com</a>]<br>
Sent: Tuesday, February 23, 2016 12:09 AM<br>
To: Kendall Waters <a class="moz-txt-link-rfc2396E" href="mailto:kendall@openstack.org"><kendall@openstack.org></a><br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:openstack-track-chairs@lists.openstack.org">openstack-track-chairs@lists.openstack.org</a><br>
Subject: Re: [Openstack-track-chairs] Part Two: Austin Session Selection
Process<br>
<br>
Is the track-chair tool able to automatically calculate the total count
selected by track chair?<br>
For example:<br>
Proposal A is selected by 3 track chair.<br>
Proposal B is selected by 2 track chair.<br>
Proposal C is selected by 1 track chair.<br>
Proposal D is selected by 3 track chair.<br>
Proposal E is selected by 1 track chair.<br>
<br>
This can help us to easily identify the most-selected proposal (e.g..
Proposal A & D in above example) and move them into "team
selection".<br>
<br>
Thanks<br>
Leong.<br>
<br>
<br>
<br>
On Mon, Feb 22, 2016 at 12:13 PM, Kendall Waters
<a class="moz-txt-link-rfc2396E" href="mailto:kendall@openstack.org"><kendall@openstack.org></a> wrote:<br>
Hi everyone,<br>
<br>
It’s time for you to select the talks that will be included on the final
Summit schedule. You have between now and next Monday, February 29 at
11:59pm PST (March 1 at 7:59 UTC) to make your Team Selections.<br>
<br>
FIRST - WATCH TUTORIAL VIDEO<br>
Before you do anything else, watch the Part Two tutorial video HERE.<br>
<br>
The video explains how to review and add talks to your personal list and
team list. Under the Team Selections tab, you can drag and drop the
presentations into your order of preference. We'll consider the
presentations at the top of the list to be the most
important to include in the final Summit agenda.<br>
<br>
Please note that everyone on your team shares the Team Selections
column. Any changes that you make will override the selections / order
choices that your colleagues may have made in this column. Therefore,
before making your final session selections inside
the Team Selections tab - we recommend that you and your fellow track
chairs schedule time together via WebEx, Google Hangout or another
platform to discuss the final team selections. Once you have finalized
your selections as a team, add them into the Team
Selections tab. The Team Selections tab must be complete no later than
Monday, February 29 at 11:59pm PST (March 1 at 7:59 UTC).<br>
<br>
Please do NOT set expectations with any speakers ranked in your
category. The Foundation staff will send the speaker notifications the
week of March 7.<br>
<br>
COMBINING SESSIONS OR CREATING NEW PANELS<br>
Watch the tutorial video HERE. You may want to combine sessions into
panels or other formats, especially if there are multiple submissions
about the same topic. However we request that you try to limit the
number of new panels to no more than 40% of the selected
sessions in your track. If you are creating a new panel then we
strongly advise you to include at least one woman speaker on the panel.
In order to combine talks or create new panels please follow the
instructions and email the requested information to
<a class="moz-txt-link-abbreviated" href="mailto:speakersupport@openstack.org">speakersupport@openstack.org</a>.<br>
<br>
COMMUNICATING WITH YOUR FELLOW TRACK CHAIRS<br>
You have the ability to contact your fellow track chairs directly via
their contact information within the tool (by clicking on their name to
send an email), but you may also make use of this mailing list to
initiate or continue the discussion with all track
chairs.<br>
<br>
Reminder - please make all final selections in the tool no later than
February 29 at 11:59pm PST (March 1 at 7:59 UTC). If you have any
queries or issues along the way please notify us at
<a class="moz-txt-link-abbreviated" href="mailto:speakersupport@openstack.org">speakersupport@openstack.org</a><br>
<br>
Cheers,<br>
Kendall<br>
<br>
Kendall Waters<br>
OpenStack Marketing<br>
<a class="moz-txt-link-abbreviated" href="mailto:kendall@openstack.org">kendall@openstack.org</a><br>
<br>
<br>
_______________________________________________<br>
Openstack-track-chairs mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.openstack.org</a><br>
<a class="moz-txt-link-freetext" 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></p>
</div>
<pre wrap="">_______________________________________________
Openstack-track-chairs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs</a>
</pre>
</blockquote>
<br>
</body></html>