<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<blockquote style="border: 0px none;"
cite="mid:CA+z5Dszy9ML15M4+HnOE_7bvd0zbOEMjcV9Kc=+fJMjyivC=kw@mail.gmail.com"
type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:blair.bethwaite@monash.edu"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Blair Bethwaite</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
2, 2017 at 3:56 PM</span></font></div> </div></div>
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div
dir="ltr">Jimmy,<div><br></div><div>Sorry, perhaps that came off as
overly negative?</div></div></div>
</blockquote>
Not at all :) <br>
<blockquote style="border: 0px none;"
cite="mid:CA+z5Dszy9ML15M4+HnOE_7bvd0zbOEMjcV9Kc=+fJMjyivC=kw@mail.gmail.com"
type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<div dir="ltr">
<div> I really did just mean we could do better for track changes,
I'm not saying it is horribly broken or anything, and I'm pretty sure
Rochelle and I are voicing the same concern - that any track-changed
talks after phase1 are disadvantaged (we're not bothered about
improvements creating extra work for us).</div>
</div>
</div>
</blockquote>
I agree with this. In the past we prevented talks from being changed
after Phase I, but left it open this Summit. We should consider for
next, even if it was only a handful of talks that moved.<br>
<blockquote style="border: 0px none;"
cite="mid:CA+z5Dszy9ML15M4+HnOE_7bvd0zbOEMjcV9Kc=+fJMjyivC=kw@mail.gmail.com"
type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<div dir="ltr"><div><br></div><div>It'd make it easier for me if the
track changes were highlighted in the tool (a flag, like the lightening
symbol, rather than a filter view so that as much info as possible is
up-front) and a notification was sent to the relevant track-chairs when a
change is accepted. </div></div>
</div>
</blockquote>
Notifications are a great idea! Flags are tough :\ We have so many
different flags, icons, states, etc... that it's tough from a UX POV to
make it work without overwhelming. That's why we added teh "Just Moved
Here" filter, but maybe we should make that a default filter or
something in the event a new thing has been added since the user last
logged in. I'll try to come up with some options :)<br>
<blockquote style="border: 0px none;"
cite="mid:CA+z5Dszy9ML15M4+HnOE_7bvd0zbOEMjcV9Kc=+fJMjyivC=kw@mail.gmail.com"
type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<div dir="ltr">
<div>I think in some cases it's easy to not notice track changes
until actually doing selections and giving the submissions more
attention.</div>
</div>
</div>
</blockquote>
Agreed. Will continue to work to find the right balance and appreciate
all the feedback!!<br>
<blockquote style="border: 0px none;"
cite="mid:CA+z5Dszy9ML15M4+HnOE_7bvd0zbOEMjcV9Kc=+fJMjyivC=kw@mail.gmail.com"
type="cite">
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<div dir="ltr"><div><br></div><div>Cheers,</div></div>
<div class="gmail_extra"><br><br><br clear="all"><div><br></div>-- <br><div
data-smartmail="gmail_signature" class="gmail_signature">Blair
Bethwaite<br>Senior HPC Consultant<br><br>Monash eResearch Centre <br>Monash
University<br>Room G26, 15 Innovation Walk, Clayton Campus<br>Clayton
VIC 3800<br>Australia<br>Mobile: 0439-545-002<br>Office: +61 3-9903-2800</div>
</div>
</div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:jimmy@tipit.net"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy Mcarthur</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
2, 2017 at 8:42 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
With the exception of 11
changes (out of 235 total), all Category Change requests were
taken and fulfilled before February 15. The change requests are
available for all Track Chairs to review and we also have a filter for
"Just Moved Here" so you can track presentations that are new to your
talk. In the case of the Products, Tools & Services track, only one
talk was moved after February 15. <br>
<br>
The reason that we do this in 2 phases is so everyone has a chance to
review not only their own track, but those presentations that were moved
from another track to their own. In this case, 95% of track changes
were completed before the track chairs would have started the second
phase.<br>
<br>
The impetus for the Foundation approving the changes is primarily to
take one
more thing off the plate of our Track Chair volunteers. That said, if it
presents an undue burden, let's figure out how we can make it better.
It involves a lot of discussion and support, so it would increase the
amount of time needed for volunteers.<br>
<br>
We always take feedback at the end of the process to see what did and
didn't work, so keep all of the above in mind and let's discuss how to
make your jobs easier :)<br>
<br>
Cheers,<br>
Jimmy<br>
<span>
</span><br>
<br>
<div>_______________________________________________<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><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:blair.bethwaite@monash.edu"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Blair Bethwaite</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
2, 2017 at 1:34 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div dir="auto">Rochelle, for
what it's worth at this late stage, I second your concern.<div
dir="auto"><br></div><div dir="auto">The track change process definitely
needs some refinement. This was a problem for Barcelona too. I think
the core issue is that track change requests should be reviewed and
accepted or rejected by the track chairs. There may also be some scoping
issues with generic tracks like Case Studies.</div><div dir="auto"><br></div><div
dir="auto">Cheers,</div></div><div class="gmail_extra"><br><br></div>
<div>_______________________________________________<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><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:rochelle.grober@huawei.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Rochelle Grober</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
1, 2017 at 8:30 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<meta content="Microsoft Word 15 (filtered medium)" name="Generator">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
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">Hey guys, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve just started today on my track selections and I
noticed that the number of presentations went from about12 or 18 to 37
between when I first reviewed and now.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And, a number of the presentations really belong in
other tracks. Mostly Case Studies and an NFV or two, but ….<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve requested a move, but it’s awful late and some
of these might have had a chance if they were in the right track even
just last week.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just wondering about this and if there is a short
term fix, or this is something that needs to be discussed for next
summit.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--Rocky<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>_______________________________________________<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><br></div></div>
</blockquote>
<br>
</body></html>