<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I think a session is a great idea, but the fall summits are more
difficult for a large percentage of the target audience to get to,
especially if they DON'T have a talk, which means they're pretty
likely to want to attend this session.<br>
</p>
<p>Unless people can participate remotely...</p>
<p>---- Nick<br>
</p>
<br>
<div class="moz-cite-prefix">On 8/26/2016 9:12 AM,
<a class="moz-txt-link-abbreviated" href="mailto:Arkady_Kanevsky@DELL.com">Arkady_Kanevsky@DELL.com</a> wrote:<br>
</div>
<blockquote
cite="mid:88b88b355b684661906448b514129ccd@AUSX13MPS304.AMER.DELL.COM"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Times\000D\000A";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Times New\000D\000A";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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
{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.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Great
idea.<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"><a moz-do-not-send="true"
name="_____replyseparator"></a><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"> Yih
Leong, Sun. [<a class="moz-txt-link-freetext" href="mailto:yihleong@gmail.com">mailto:yihleong@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, August 25, 2016 5:16 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" 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>
<div>
<p class="MsoNormal">Do we need a Working Group session at
Barcelona for this "Track Chair" discussion on how to
improve the future selection process?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Aug 25, 2016 at 1:44 PM, Nick
Chase <<a moz-do-not-send="true"
href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 8/25/2016 4:28 PM, Matt
Fischer wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">I hope that the track chairs
were not only selected on the basis of technical
knowledge but on their integrity and of putting
the summit & community ahead of company goals.
I also think that the foundation has done a good
job ensuring that different communities and
companies are chosen, which hopefully avoids the
ability of one company to push their talks over
others. For me, I will never push a team talk
unless the other track chairs have it under
consideration, and if they do I'm happy to provide
honest feedback on it. I hope fellow track chairs
will concur with that.<o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal"><br>
Exactly!!<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">Opening up a requirement
that track chairs have to justify why they
chose one talk over another will only foster
further argument, it won't resolve anything.
It's also untenable when rejecting 200 talks
to justify the ranking of each one. And
regardless of what you do and whether you
justify your reasons or not, many good talks
were not picked, and some feelings were
probably hurt.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<p class="MsoNormal"><br>
I'm not suggesting that we explain why talks were
rejected, just why they were SELECTED.<br>
<br>
Feelings are always going to be hurt. I've already
gotten 3 phone calls from dejected colleagues who got
their "sorry, no thanks" letter and I've had to tell
them, "Look, you're in good company." Hell, I didn't
get in either. :)<br>
<br>
But while we've definitely been improving in the
"transparency" department, I think it wouldn't be a
bad thing to go further.<span style="color:#888888"><br>
<br>
<span class="hoenzb">---- Nick</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Aug 25,
2016 at 4:13 PM, Nick Chase <<a
moz-do-not-send="true"
href="mailto:nchase@mirantis.com"
target="_blank">nchase@mirantis.com</a>>
wrote:<o:p></o:p></p>
<blockquote
style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<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.<o:p></o:p></p>
<p>---- Nick<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On
8/25/2016 3:50 PM, Shilla
Saebi wrote:<o:p></o:p></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">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. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On
Thu, Aug 25, 2016 at
2:18 PM, Nathan C
Ziemann <<a
moz-do-not-send="true"
href="mailto:ziemann@us.ibm.com" target="_blank">ziemann@us.ibm.com</a>>
wrote:<o:p></o:p></p>
<blockquote
style="border:none;border-left:solid
#CCCCCC
1.0pt;padding:0in 0in
0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">+1
on export. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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 <o:p></o:p></p>
<div>
<p
class="MsoNormal">Sent
from my iPhone<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p
class="MsoNormal"
style="margin-bottom:12.0pt"><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:<o:p></o:p></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p
class="MsoNormal">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.
<o:p></o:p></p>
<div>
<p
class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p
class="MsoNormal">I'd
love to see a
simple
"export"
function so we
don't wind up
doing it by
hand.<o:p></o:p></p>
</div>
<div>
<p
class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p
class="MsoNormal">----
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:<o:p></o:p></p>
<blockquote
style="border:none;border-left:solid
#CCCCCC
1.0pt;padding:0in
0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D">Why
was that?</span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D">-amrith
</span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:Consolas;color:#1F497D"> </span><o:p></o:p></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"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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">
Kunzmann,
Gerald [<a
moz-do-not-send="true"
href="mailto:kunzmann@docomolab-euro.com">mailto:kunzmann@docomolab-euro.com</a>]
<br>
<b>Sent:</b>
Thursday,
August 25,
2016 3:22 AM<br>
<b>To:</b> <a
moz-do-not-send="true"
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</span><o:p></o:p></p>
</div>
</div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Times
New
",serif"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">+1
nice tool.</span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Gerald</span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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
moz-do-not-send="true"
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
moz-do-not-send="true"
href="mailto:doc@aedo.net">doc@aedo.net</a>>; <a
moz-do-not-send="true"
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</span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Times
New
",serif"> </span><o:p></o:p></p>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Times
New
",serif">+1
great tool and
easy process
overall.</span><o:p></o:p></p>
<div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Times
",serif"> </span><o:p></o:p></p>
</div>
<div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;margin-bottom:12.0pt">Thanks!<o:p></o:p></p>
<div>
<div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Times
",serif">On
Wed, Aug 24,
2016, 4:47 PM
Christopher
Aedo <<a
moz-do-not-send="true"
href="mailto:doc@aedo.net">doc@aedo.net</a>> wrote:</span><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"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Times
",serif">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" href="mailto:jimmy@openstack.org">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" href="mailto:noreply@openstack.org">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
moz-do-not-send="true"
href="mailto:Openstack-track-chairs@lists.openstack.org">Openstack-track-chairs@lists.openstack.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-bin/mailman/listinfo/openstack-track-chairs</a><br>
><br>
<br>
_______________________________________________<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.openstack.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-bin/mailman/listinfo/openstack-track-chairs</a></span><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<p
class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Openstack-track-chairs
mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank">Openstack-track-chairs@lists.openstack.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-bin/mailman/listinfo/openstack-track-chairs</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="color:#888888">-- <br>
Nick Chase, Head of Technical
and Marketing Content,
Mirantis<br>
Editor in Chief,
OpenStack:Unlocked<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Openstack-track-chairs mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openstack-track-chairs@lists.openstack.org"
target="_blank">Openstack-track-chairs@lists.openstack.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-bin/mailman/listinfo/openstack-track-chairs</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">-- <br>
Nick Chase, Head of Technical and Marketing
Content, Mirantis<br>
Editor in Chief, OpenStack:Unlocked<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<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.openstack.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-bin/mailman/listinfo/openstack-track-chairs</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
<div class="moz-signature">-- <br>
Nick Chase, Head of Technical and Marketing Content, Mirantis<br>
Editor in Chief, OpenStack:Unlocked</div>
</body>
</html>