►
From YouTube: Kubernetes Community Meeting 20160818
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Reports from SIG-UI and WG-Contribex, 1.4 Features Update, SIG-Storage offsite summary, new SIG-service-catalog announcement.
A
Alright,
so
as
I
kick
off
every
meeting
I
through
mind
you
all
that
this
is
a
public
and
recorded
meeting
of
the
Cooper
Nettie's
community
and
today
is
August
eighteenth.
We
have
an
exciting
agenda
ahead
of
us
literally
exciting
if
we,
if
we
can't
get
the
demoing
bit
working
shortly,
but
the
first
the
demo
this
morning
is
the
kubernetes
distributed,
trust
computing
and
practice
by
Matthew
Garrett
of
Korra
s.
We
also
have
queued
up
for
for
today's
meeting
special
interest
group
reports.
Mom
docks,
Phillip
and
Jared.
Are
you
guys
on
the
line.
A
A
We
have
the
working
group
contributes
where
we
have
garrett
Rodriguez
talking
about.
What's
been
going
on
in
that
space,
and
are
you
also
going
to
be
talking?
Maybe
maybe
Antoine
might
be
talking
as
well
all
right,
then.
We
also
have
an
update
on
the
1.4
features.
We
had
a
good
burn
down
meeting
yesterday.
A
Andy
horse
gonna
lead
us
through
that.
So
let's
see
what
my
chat
says,
my
chat
says
that
dan
you
are
going
to
be
up.
First,
we're
going
to
go
a
little
out
of
order,
but
before
damn
starts
one
second
I
do
actually
need
note
takers.
So
if
someone
can
jump
into
the
meeting
dock
and
take
notes,
that
would
be
super
helpful.
We'll
go
way
out
order
today
and
just
do
fun,
fun
and
entertaining
ed
hockey
genda.
C
Alright
hi
everyone,
my
name's
Dan
rom
lines,
I
mentioned
I'm
UX
designer
with
a
friend
up
and
I've,
been
working
on
the
dashboard
UX
most
recently
just
transferred
over
design
files
to
peel
is
with
the
design
lead
for
the
project
this
morning
to
start
working
on
the
navigation
for
that.
So
that's
in.
C
But
we're
going
to
consolidate
the
navigation
and
very
to
go
check
that
out
there
and
screenshots
and
envision
prototype
link
to
that
you'd
like
to
see
what
that's
when
we
ended
up
at
win
for
the
cider
other
updates.
As
far
as
a
cig,
you
I
our
next,
so
the
next
release
of
dashboards
that
we
won
for
was
syncing
up
with
the
main
communities
versioning
screen,
which
I'm
looking
forward
to
really
run
run.
Well,
we
will
be
n
run
for
45.
E
C
Number
time
frame,
then
the
three
top
priority
for
us
looking
into
that
releasing
15
are
not
much
missing
issues
here,
961,
which
is
closing
the
gap
between
CLI
and
dashboard,
and
we're
going
to
try
to
get
to
ninety
percent
parody
with
lawn
for
and
just
displaying
resources.
You
can
interact
with
human
oddities
in
the
dashboard.
C
962
monitoring
and
stubble
shooting
we
know,
that's
a
big
feature
that
people
like
to
use
dashboard
board
is
a
big
asset
using
visual
strengths
of
dashboard.
So
we
have
briefed
me
on
all
this
this
morning
and
bringing
up
to
speed.
We
have
computers
in
turn,
also
named
Theodore
recently
working
on
monitoring
graphs
for
a
CPU
and
memory,
so
anything
with
those
characteristics.
C
We
can
have
graphing
visualizations
around
I
think
in
the
two
week
time
frame
so
that
we
ready
14
as
well,
then
in
15,
we'll
look
ahead
to
being
able
to
drill
down
to
those
graphs
monitoring,
get
some
more
granular,
informative
data
from
their
focus
area,
security
off
and
login,
and
that's
been
deferred,
there's
15!
Now
we
had
two
guys
we're
working
on
this
and
they
bring
the
projects.
So
that's
still
our
third
priority.
That's
going
to
go
to
15
it's
online.
C
So
that's
enough
work
for
the
dashboard
team
for
a
couple
of
months
and
then
beyond
that
we're
looking
to
together
sprint
I
design,
a
Google
design
and
sprint
around
coupon
or
thinking
the
second
to
sixth
of
November,
so
that
we
can
look
ahead
to
the
next
scope
of
work
and
Phillip
are
huge,
pull
from
of
what
what
our
priorities
are
and
what
we
really
will
IC
incorporating
into
dashboard.
So
if
you
know
of
anyone.
A
A
Of
Eastern,
okay,
all
right,
anyone
have
questions:
okay,
Thank
You
Lachlan
for
taking
notes
and
if
you
can
go,
take
a
peek
at
the
document
and
maybe
flush
them
out
a
little
bit
for
specific
points
that
you
want
to
make.
That
would
be
super
helpful
as
well.
That
way,
we
make
sure
we
get
this
gether.
D
A
B
F
B
B
B
B
B
A
A
G
Slow
motion.
Okay,
so
if
you
go
to
the
community,
wiki
we've
had
a
issue
for
a
while
that
was
to
improve
the
pr
workflow
automation
and
actually
define
what
the
workflow
should
be.
So
if
you
click
on
the
word
cloud
definitions,
we've
got
this
document
and
a
couple
of
us
have
been
working
on
defining
what
a
good
PR
workflow
should
be,
starting
from
start
from
the
issue
level
or
the
author
submitting
it,
and
we
do
of
us
turned
it
into
like
kind
of
a
finite
state.
G
So,
at
any
point
in
the
PR
process,
you
should
be
able
to
figure
out
which
state
you're
in
have
you
signed
the
CLA
yet
have
owners
been
assigned
and
from
there
the
goal
is
that
have
it
be
abundantly
clear,
who's
like
who
scored
the
vaulted
so
that
we
can
get
PRS
emerged
as
quickly
as
possible,
we're
working
on
tracking
some
statistics
on
time
between
submitting
a
PR
and
it
actually
being
merged,
or
even
like
the
first
lgtm
and
it
being
merged.
So
we
have
some
statistics
on
how
where
the
slowdowns
are
just
pipeline.
G
G
Let's
see
as
far
as
things
that
are
complete,
I
think
we've
got
a
CLA
bot,
there's
another
one,
since
we
can't
get
to
the
CMC
f
CLA,
that's
being
changed
slightly.
We
have
something:
it's
gonna
work
for
paying
people,
so
it'll
figure
out
who
who
took
the
last
action?
The
author
change
a
file
recently.
If
so,
then
the
reviewer
needs
to
be
looking
next.
If
the
reviewer
has
lgtm
bit
and
it's
still
not
being
merged,
the
tests
are
passing,
then
it
goes
back
to
the
author.
G
E
G
All
I
wanted
to
cover.
Oh,
so
we
also
talked
about
different
strategies
or
are
different
ways
that
people
work
so
few
people,
some
people,
like
being
things,
are
getting
emails
and
have
that
like
interrupt
workflow
where
I
don't
work
out
or
dragon
must
I'm
notified,
but
the
other.
The
alternative
is
more
like
a
pulley
structure
where
you
can
actually
look
and
see
what
issues
have
been
assigned
to
you.
So
if
I
look
and.
G
D
G
A
G
A
A
A
Then
Jared's
not
able
to
join
us
this
morning,
so
I,
ok.
So
this
is
one
of
those
mornings,
apparently
because
our
because
we
also
have
challenges
with
the
demos
all
right,
so
we've
had
to
two
separate
contributors
or
not
contribute
experience.
One
contributor
experience
update
1
UI,
update
I,
guess
that
is
kind
of
an
experience
update
and
we
will
move
on
to
our
next
agenda
item.
E
E
The
Indus
coke
wanted
for
when
the
final
I
esteem
in,
like
some
states
done
from
alpha
state
but
is
going,
are
going
to
be
added
to
one
fertilized,
so
I've
bested
the
same
documented,
a
shirt
on
the
previous
making
preciate
by
we're
tracking
all
that
stuff
to
the
toes
to
the
one
makin
middle
notes.
So
everyone
may
take
a
look
at
her
and
find
some
such
news.
E
So
another
major
important
update
for
someone
who
is
interested
in
contributing
and
still
contributing
to
a
wonderfully
stick
with
us
move
the
soft
code
phrase
from
Friday
to
Monday,
so
Monday
midnight,
I,
suppose
the
Beastie
time
it
will
be
like
real
soft
got
free.
So
if
you
expecting
your
future
to
be
added
to
wanted
for
place
finalized
before
Monday
midnight
time
and
also
all
we
have
like
an
option.
Fearsome
few
exceptions,
so
we
at
TJ
government
sent
mail
ways
I'm
template.
E
A
K
Those
all
sound
like
really
like
not
released
things.
It's
I,
guess
what
I'm
trying
to
say
is
it's
unclear
to
me
looking
at
this
spreadsheet,
like
what
is
actually
functional
for
some
definition
of
functional
for
1.4,
like
I,
don't
actually
understand
what
1.4
is
going
to
look
like
entirely
based
on
this,
just
because
the
stage
column
makes
me
think
that
many
of
these
features
are
not
really
complete.
K
E
Up
and
it
prefers
the
actual
state
of
days
features,
oh
that
feature
issues
I
get,
and
then
the
these
features
are
like
in
a
before
alpha
or
like
frightened
dog.
So
something
like
that
means
like
similar
effect
and
actual
state
of
of
these
features.
So
the
most
of
features
are
going
to
be
added
only
alpha
state
because
they
have
initially
only
like
prepared
and
they
haven't
been
for
the
finalized
to
be
really
added
as
a
full
feature
to.
D
E
K
A
Aaron
I
would
I
would
subtly
shift
that,
so
the
for
Alf
in
the
feature
temple
before
alpha
is
the
list
of
all
the
things
that
are
required
to
get
to
alpha
state.
So
if
they
are
currently
in
before
alpha
and
targeted
for
this
release,
I
would
expect
them
to
be
alpha
in
this
release.
I
think,
please
tell
me
you
are
if
that's
wrong,
that
that
that's
the
way
we
should
reading
this.
K
Yes,
correct,
okay,
ready
for
alpha
or,
like
you
know,
passes
alpha
criteria
or
something
just
because
it
seems
like
that
means
it's
past
the
gate.
So
maybe
what
you're
saying
is
everything
that's
in
before
alpha
is
actually
going
to
ship
and
as
functional
is
going
to
have
release
notes
and
all
that
good
stuff
and.
K
Cool,
no
thanks
that
clears
things
up
on
and
then,
like
my
audit,
a
bunch.
My
other
concern
is
that
the
TVD
column
are
all
the
TVD
values
next
to
the
Shepherd
and
I
understand.
Maybe
this
is
just
the
learning
process
for
us
as
a
community.
We
were
trying
out
this
process
and
only
a
few
people
willing
is
China
sign
up
to
be
shepherds,
but
maybe
the
Shepherd
thing
isn't
working
out
so
well.
Maybe
we
should
give
it
another
shot.
I,
don't
know
it
seemed
interesting
yeah.
Unfortunately,.
A
A
Right
and
to
your
question,
Erin
I,
don't
think
that
was
a
silly
question
at
all.
I
think
it
was
a
very
important
question.
So
thank
you
which
meet
you
recommending
to
everyone
else
who
thinks
they
have
a
silly
question.
Please
free
ask,
because
that
really
did
clarify
something
for
me,
because
I
had
looked
at
that
feature
template
a
number
of
times
and
I
just
read
those
as
you
know.
Oh,
this
will
be
alpha
there
in
the
phase
of
getting
all
the
checkboxes
for
alpha
and
didn't
realize
it
was
not
clear
all
right
and.
A
A
Anyone
else
have
special
interest
group
updates.
I
was
trying.
Is
anyone
from
sig
storage,
someone
from
six
George's
here
wrong
boom,
so
six
storage
had
a
what
I
heard
was
a
very
good
off-site
last
week,
if
I'm,
remembering
my
weeks
correctly
and
I,
sent
out
a
note
to
the
mailing
list
here,
if
we
could
have
an
update
but
I
hadn't
seen
any
answer,
are
you
game
Michael
on
the
spot,
I'm
game?
If
there's
anyone
else
here
from
storage,
though
I
mean.
G
G
Then
all
that
into
it,
so
we
organized
a
group
to
meet
in
San
Jose
diamante
office,
thanks
big,
shout
out
to
compel
giamatti
team
for
letting
us
do
that.
We
had
a
few
goals
and
we
actually
met
most
of
those
goals.
If
not
all
one
of
those
goals
was
to
divine
design
features
that
were
quite
contentious
and
what
we
needed
to
do.
G
Because
I
think,
if
we
hadn't
done
that
face
to
face
it
wouldn't
made
in
that
release-
or
you
know
who,
yes,
that
was
productive
and
we
spent
hours
and
hours
going
over
that.
In
addition,
we
discussed
what
areas
of
investment
we
need
to
make
a
storage
area
more
make
us
more
confident.
We
make
changes
in
the
storage
area
that
those
changes
will
not
explode
or
create,
surprises
ready.
We
talked
about
testing
for
several
hours
and
then
not
only
talked
about
testy
when
came
up
with
plan,
and
we
should
be
tracking
that
plan.
G
If
anyone
wants
to
know
more
about
it,
please
come
to
the
sword,
say
we'll
find
out.
Actually
the
proof
is
in
the
pudding
we're
going
to
act
on
the
place
you
want,
but
that's
the
goal.
We
did
a
lot
of
kind
of
you
know
hugging
and
hello,
and
it's
good
certain
people
and
find
out
within
motivations
work.
We
spend
a
lot
of
time
on
the
post-mortem
for
what
was
going
on
in
13.
We
talked
about
snapshot
as
a
feature.
G
Lot
of
these
conversations
went
on
for
many
hours
and
we
kind
of
met
at
nine
in
the
morning,
and
we
left
you
know
six
or
seven
o'clock
at
night
with
more
things
to
you,
I
think
everyone.
There
agreed
that
it
was
a
good
use
of
time.
Arguably,
some
people
felt
and
I
kind
of
agree
that
we
were
debating
issues,
but
overall,
this
product
confession
and
legend
action
as
it
was
just
needing
to
hang
out
and
do
social
I
mean
there
wasn't
a
20
to
30
there.
G
You
count
everyone
GBC,
which
was
I,
heard
one
of
the
highest
attended
meetings
for
the
storage
organization
other
than
that
I.
Think
one
of
the
other
things
we
did
is
bug
scrub.
We
described
about
a
hundred
bugs
and
outlining
how
we
want
to
manage
our
bugs
in
the
storage
state
going
over
to
all
agree,
DQ
better
job,
so
we
didn't
just
focus
on
features.
We
didn't
just
focus
on
being
social.
G
We
also
try
to
focus
on
maybe
having
a
more
mature
approach
to
how
we're
going
to
debug
and
manage
our
system
going
forward
and,
like
I
said,
poop
will
be
in
the
pudding
either.
A
the
next
time
we
do
this.
He
said
one
cute
con
in
November
bill.
If
there
is
no
progress,
we're
going
to
have
to
change
and
we
approach
it,
but
I'm
already
seeing
progress
based
on
both
each
of
development
and
then
how
we
have
outlined
a
set
of
things
that
we
want
to
start
test
for
rent
it.
G
F
F
F
G
Think
what
you're,
basically
asking
your
eric
is
given
that
we
put
this
feature
into
one
dot
for
and
them
are
we
did.
We
take
enough
of
your
questions
of
upgrading
into
account,
as
we
have
now
proposal
and
I
am
sure
that
I
know
that
have
been
some
thoughts
about
upgrading
and
growing
back,
but
I
know
not
nearly
enough
to
withstand
the
Erickson's.
G
You
know
interrogation,
which
is
actually
really
cool,
and
the
fact
that
you're
interested
in
this
makes
me
happier
so
please
when
you
come
in
start
finding
out
these
questions
on
the
storage,
sig
email
list
and
let
started
responding
to
what
we
have
covered
in
what
we
think
about.
You
still
have
three
more
weeks
for
wind
up
for
so
we
have
room
to
maneuver
awesome.
A
A
T-Shirt,
yes,
alright,
any
other
special
interest
groups
that
have
met
or
have
updates
against
1.4
that
they
want
to
share
because
code
freeze
is
coming,
no
more
updates
on
that.
All
right,
then
I
am.
Unless
someone
was
unmute.
It
was
just
lock
on
doing
video
all
right.
Anyone
else
have
topics.
Questions
will
call
this
open
floor
or
want
to
make
introductions
of
themselves.
If
you
haven't
participated
in
this
meeting
this,
this
chaotic
chaotic
meeting
before
I.
I
A
I
A
K
K
A
Because
one
of
the
big
things
out
of
1.3
was
we
didn't
get
enough
people
playing
with
the
betas
and
the
alphas,
and
so
we
didn't
get
some
of
the
early
bugs
fleshed
out.
So
everyone
everyone,
everyone,
please,
as
we
release
alphas
and
betas
play
with
them,
run
them
through
whatever
weird
use
cases,
you
might
think
of
start
using
them
for
your
day
to
day
whatever
and
see
what
you
can
find
because
we've
had.
A
This,
we've
had
to
come
up
a
couple
of
times
that
we
always
make
a
point:
1
release
really
quickly
on
the
heels
of
our
point,
0
release,
and
if
we
can
get
more
testing
the
alphas
and
betas.
That
is
a
huge
step
toward
making
those
more
stable.
There
will
always
be
edge
cases.
There
will
always
be
bugs,
but
the
more
testing
we
can
do
ahead
of
time
on
those
early
releases,
the
better
we
will
all
be
set
up
for
a
stable
release
with
the
point
0
another
way.
G
G
A
Right,
so
we
want
to
light
the
cake
fire
before
the
release
all
right
before
the
party
starts
excellent,
all
right.
How
about
anyone
else
with
random
thoughts
comments
what
kind
of
cake
plates
on
fire
anyone
with
candles
in
it,
of
course,
all
right.
Anyone
else
with
questions
open
topics,
discussions
things
that
they
want
to
bring
to
the
fore.
A
A
G
Just
to
give
the
verbal
version
of
the
post
the
mailing
list,
basically
among
different
member
organizations
of
the
cloud
native
compute
foundation,
we've
been
discussing
this
notion
of
a
Service
Catalog,
which
is
about
as
a
service
operator
or
someone
that
created
a
recipe
of
some
type
and
for
running
an
instance
of
the
service
I.
You
know
I
want
to
publish
the
fact
that
my
service
exists
or
that
my
recipe
exists
and
as
a
consumer
or
potential
consumer
of
those
things,
I
want
to
be
able
to
search
for
them.
G
G
Maybe
config
mapped
with
you
know
some
other
non
secret
information
about
it,
and
the
proposal
is
to
create
a
thing
to
discuss
what
this
means
for
cuva
Nettie's
and
to
eventually
arrived
upon
a
like
very
cute
ish
way
to
leverage
these
missions
so
that
we
can
facilitate
the
development
of
like
marketplace
is
where
a
service
operator
might
want
to
establish
a
commercial
relationship
with
the
consumer
and
where
you
know
we
can
have
a
good
exchange
of
recipes
and
services.
Us.
G
So
it
differs
from
any
specific
solution
for
this,
in
that
it
is
meant
to
be
agnostic
of
whatever,
whatever
the
details
of
whatever
work
is
stricken
school
you're
using
as
a
start
and
I'm
not
fully
up
to
date
in
any
way
on
home.
But
if
perhaps
someone
can
answer
the
question
for
the
group?
There's
probably
take
that.
C
One
fall,
so
the
idea
of
a
Service
Catalog
is
allowing
someone
who
has
an
application
who
needs
to
consume
services
that
are
exposed
by
other
people
in
the
organization.
What
you
may
have
these
services
that
are
created
and
owned.
The
component
Paul
is
referring
to
that
on.
If
you
ask
for
some
services
to
be,
you
want
to
use
a
service,
some
of
those
services
might
be
dynamically
provisioned,
in
which
case
the
back
end
for
the
dynamic
provisioning
might
be
held
or
another
mechanism.
A
C
H
I
know
that
Brian
and
the
CNCs
service
management
and
specifically
Service
Catalog
I,
think
having
read
the
proposal.
I
think
this
one
is
specifically
targeted
at
a
service
broker,
API
and
and
a
service
control
or
proposal.
I.
Think
that
there's
some
discussion
around
you
know
other
companies
or
other
community
members
also
participating
in
this
and
I.
A
Think
that
it
was
okay,
fantastic,
mostly
with
these
conversations-
and
so
this
is
this-
is
now
the
second
or
maybe
possibly.
Third
time
we've
tried
to
go
through
this
new
sig
proposal
process,
which
basically
is
hey
I,
have
an
idea
for
a
cig.
We
discussed
it
on
the
mailing
list,
people
jump
in
and
say
yes,
no
and
then
we
also
mention
it
in
the
community
conversation
community
meeting
in
order
to
find
out
where
there
is
overlap
or
what
is
the
actual
scope
and
charter
of
this?
A
C
A
Yet,
but
we
will,
we
may
well
see
one
of
those
in
the
near
term
so
because
this
is
this
is
one
of
the
methods
we're
trying
to
both
be
intentional
about
what
was
starting
to
be
referred
to
as
sig
scroll,
but
also
making
sure
that
we
cover
all
the
things
that
we
need
to
talk
about
in
groups
that
make
sense
all
right.
Anyone
else
have
things
they
want
to
bring
up
in
today's
meeting
all
right.
So
then,
when
we
go
through
notice,
is
quickly
won.
A
The
code
freeze
is
coming
because,
yes,
it
is
funny
to
say
that
again,
that
is
I
believe
Monday
now
monday
Monday
midnight
now
right,
I
can't
remember
if
it
was
this
friday
or
next
friday.
I
was
hopeful
for
all
of
you,
but
no
it's
monday,
so
the
code
freeze
is
now
monday
at
midnight,
a
pacific
time.
Thank
you,
Eric
midnight
our
time,
not
yours,
midnight,
pacific
time,
then
the
other
thing
that
is,
of
course
an
awesome
notice,
is
sig.
A
Instrumentation
is
getting
itself
bootstrapped
and
it
sounds
like
we
are
about
to
kick
off
sig
service
catalog.
So
those
would
be
my
notices
for
the
day.
Does
anyone
else
have
anything
Aaron?
No,
we
are
not
going
to
rename
the
sig
leads
group
to
sig
sprawl.
Thank
you
for
your
suggestion.
It
is
duly
noted
and
yes,
you're
right.
I've
also
said
there
are
no
dumb
comments.
So
all
right,
I'm
gonna,
still
keep
that
called.
Sig
leads,
but
thank
you
all.
Does
anyone
have
any
other
notices
they
want
to
put
forward?
G
G
G
People
were
talking
to
each
other,
they
are
having
a
good
time,
one
of
those
lots
of
effort,
sort
of
events,
and
it
went
fabulously
well
with
crazy
video
games,
and
you
know
crazy
conversations
and
people
really
got
to
know
each
other
Sarah
put
a
lot
of
effort
into
it
and
I'm
not
surprised
that
she
did
not
bring
it
up
at
all
in
this
meeting
because
it
was
effortless
for
us
and
a
lot
of
enter
/.
So
I
think
we
should
say
I.
A
Need
to
call
two
more
people
out
because
they
did
even
more
than
I
did
buy
a
lot,
which
is
bob
heard
in
ski
marketing
for
Cooper,
Nettie's
and
Google
compute
engine,
and
he
sometimes
joins
this
conversation,
but
I'm,
not
sure.
If
he's
joined
us
today
and
a
new
program
manager
on
my
team
that
has
just
joined
us
and
that's
Cameron's
a
heady
and
he
did
all
hold
on
to
work
around
all
of
the
Cooper
Nettie's
birthday.
A
G
So
I
want
to
give
a
shout
out
to
all
those
people
came
and
they
were
cool
cookies
and
things
it's
a
great
time
and,
lastly,
encouraging
everybody,
no
meetups
among
ourselves,
not
just
user
groups.
It's
a
really
little
bar
sorry
sig
came
about
because
of
you
know,
one
request
and
someone
just
found
some
space
and
it
worked
out
wonderfully
to
have
people
together.
I
think
you
know
that's
basically
it.
You
should
all
know
that
you
know
breaking
our
space,
sometimes
my
routine,
to
go
meet.
Each
other
is
very
valuable.
People.
K
A
Yes
container
con,
no
there's
an
excellent
point
and
then
there's
cloud
native
day
on
next
thursday
in
toronto
as
well,
which
is
the
cloud
native
compute
foundations,
first
one-day
event,
and
that's
happening
there.
If
you
are
at
all
involved
in
the
cnc
f
or
going
to
contain
our
con.
It's
an
interesting
just
an
interesting
event
that
will
be
happening.
A
A
Alright
Joe
is
going
to
be
there
for
a
bit
Joseph's
going
to
be
there
wow.
Alright,
it
looks
to
me
as
if
Doug's
Davis
is
going
to
be
there
fantastic.
So
maybe
we
should
have
a
little
hey.
I
bet
we're
having
a
little
Cooper
nidhi's
get
together.
There.
I
will
double
check
on
specifics
and
share
that
out
as
well,
because
and
my
earlier
point
about
Bob
Ford
in
ski
doing
marketing
I
think
he
was
trying
to
hold
it
together,
an
event
there
as
well.
So
I
will
get
specifics
and
put
that
in
here.