►
From YouTube: Kubernetes SIG ContribEx 20181219 Weekly Update Meeting
Description
Wednesdays @ 930am PT; 4th Weds at 8p PT
A
All
right
welcome
to
our
last
update
meeting
for
2018
before
kubernetes
contributor
experience.
My
name
is
Paris
Pittman
I
am
a
co-chair
here
and
will
lead
up
this
fine
ship
for
today's
call,
I
can't
believe
it's
the
last
meeting.
Okay
I
feel
a
time
has
flown
this
year,
but
this
is
gonna
be
a
mostly
condensed
usual
episode
of
our
program.
I
did
for
those
that
are
just
joining.
A
I
did
put
our
meeting
notes
in
the
chat,
please
feel
free
to
add
your
name
under
the
attendee
for
December
19th
and
we'll
pop
the
reporting
link
in
this
meeting
note
when
we
are
done
so
first
things.
First,
we
do
have
a
code
of
conduct.
Please
be
excellent
to
each
other
I'm
going
to
try
to
monitor
the
chat.
A
So
if
you
have
something
just
raise
your
hand
if
someone
else
is
talking
and
then
that
will
be
awesome
also
if
we
have
any
new
contributors
on
the
line
right
now,
I'm
looking
at
your
faces,
I
think
Matt
is
at
war.
I
think
you've
introduced
yourself
before
how
great
but
Matt
do
you
want
to
introduce
yourself
to
folks
thank.
A
A
Let's
see
now
next,
we
usually
go
into
some
regular
program
updates
those
regular
programs
for
those
that
don't
know
our
first,
a
community
update
meet
our
contributors
and
office
hours.
Those
are
just
really
programs
that
this
part
that
this
project
owns,
and
we
really
don't
have
many
updates
because
of
the
holiday
season,
we're
not
doing
the
Thursday
community
meeting
until
January
and
I
I
believe
the
hosts
are
actually
already
on
board
and
everything's
good.
There
I
do
need
more
more
volunteers
for
January
2nd
meet
our
contributors.
A
A
Yes,
that
would
be
the
7:30
a.m.
session
and
for
those
who
don't
know
that
is
like
our
upstream
mentoring
initiative,
it's
very
similar
to
office
hours,
except
for
its
upstream
questions
that
you
would
ask
the
mentor
like
how
to
be
an
approver
and
George
is
always
looking
for
help
for
office
hours,
and
that
is
exactly
what
you
think
it
is
it's
under
user
persona
questions
and
feel
free
to
reach
out
to
George.
If
you
would
like
to
help
out
there
all
right.
So,
let's
look
at
our
project
board.
A
Everybody
see
it
all
right,
so
I
know
probably
have
a
lot
of
things
that
are
either
in
a
blocked
column
just
based
off
of
people's
time,
especially
now
the
G
phone
has
winded
down
and
also
we've
got
a
lot
of
stuff
in
progress.
So
I
wanted
to
start
with
the
lock.
Does
anybody
have
anything,
that's
blocked
that
they
wanted
to
that?
They
want
to
discuss
with
us
right
now
or
need
any
help
with.
A
Excuse
me
getting
clarified
from
the
steering
committee
as
it
relates
to
working
group
clarifications
and
things
like
that,
and
once
we
do,
then
we're
gonna
update
these
files
with
some
more
information
that
the
community
can
benefit
from,
like
what
SIG's
are
helping
out,
what
working
groups
and
what
working
groups
are
tied
to
what
SIG's
and
things
like
that.
So
all
right
as
anybody
else
blocked
on
anything
that
is
not
an
issue,
meaning
not
an
issue
and
github
all
right.
That's
awesome!
A
C
A
C
C
The
because
she's
not
gonna,
want
to
hear
that
we
need
to
revise
that.
We
want
to
revise
the
content,
so
a
couple
of
things
have
already
come
out
of
the
responses
that
I've
gotten.
So
three
things
I
mean
one
is
you
know
we
need
to
take
a
close
look
at
the
individual
content,
because
people
did
not
find
all
parts
of
the
workshop
equally
valuable
when
I
get
also
the
responses
from
Shanghai,
etc.
I'll
have
better
overall
idea
that
a
second
thing
is
one
of
the
suggestions
and
I.
C
Think
it's
excellent
I
from
Seattle
was
that
we
should
look
at
having
an
intermediate
training
like
hi
I'm,
already
a
kubernetes
contributor.
How
do
I
become
a
reviewer
yeah
now
creating
the
content,
for
that
could
be
quite
difficult,
but
it
is
something
that
at
least
a
few
people
are
asking
for,
and
it
certainly
winds
up
with
our
needs
for
the
project.
Overall,
the
that's.
A
Exactly
why
we
did
the
code
review
session
with
daniel
smith
this
year.
That's
like
starting
to
get
in
that,
like
learning
of
what
it's
like
to
be
in
a
different
role
like
Tim,
did
it
to
what,
when
we
had
it
on
the
zoom
reporting,
and
we
did
the
doc
on
like
kind
of
how
to
do
a
code,
review
I
think
that's
super
super
important
and
awesome.
Yeah.
C
I
mean
there's
a
lot
of
different
ways.
We
could
do
this,
we
could
have
a
workshop.
I
would
actually
prefer
having
sort
of
a
track
in
the
contributor
summit,
where
we
just
have
three
or
four
sessions
that
are
aimed
at
that
in
general,
because,
among
other
things,
you
know
that
point,
it
kind
of
depends
on
what
direction
somebody's
going
in
somebody
who's
doing
who's.
You
know,
working
in
a
feature.
A
D
A
Bob
and
I
actually
discovered
this
too
and
presented
the
data
to
win,
because
we
saw
that,
like
people
were
coming
from
copper
and
like
industry
related,
so
Bob
and
I
were
actually
talking
about,
like.
Let's
do
maybe
like
an
intermediate
new
contributor
track
where,
instead
of
it
being
five
hours,
it's
two
and
a
half
we
actually
someone
from
Google
actually
did
that
on
Tuesday.
A
He
did
a
tutorial
for
was
like
a
two
hour
tutorial
from
from
it
was
kind
of
like
building
from
source
and
doing
your
first
PR,
and
it
attracted
like
a
lot
of
industry
professionals
and
things
like
that.
But
I
think
there
is
a
lot
of
value
to
the
five
hour
format
for
a
lot
of
people.
I
have,
let
me
even
have
the
data
too,
so
I
think
that
it
just
means
we
need
a
cater
to
yet
another
persona.
A
A
So
that's
going
to
be
a
huge
huge
help
for
us
and
that
will
be
to
personas,
but
the
one
that
Edward
is
mainly
focusing
on
and
he
can
talk
about
this.
A
little
later
is
the
upstream
developer
and
then,
of
course,
persona
number,
two
being
the
developer
that
builds
on
top
of
kubernetes,
so
awesome
feedback,
because
this
sounds
like
all
the
directions
that
we
want
to
go
in
to
so
this
is
awesome.
A
D
Yeah
I
mean
I'm
just
getting
started,
I've
known
or
maybe
contribution
yeah,
but
reading
the
codebase
is
a
pretty
big
task
in
itself.
Yeah,
one
of
the
things
I
would
love
and
one
of
the
things
that
I
would
have
loved
and
I
would
love
to
contribute
back
when
I
get
comfortable
with
it
is,
is,
maybe
you
know
video
sessions
or
maybe
document
sessions
like
tour
of
the
code.
Bases
like
this
is
the
API
server
here
are
the
rough
packages
here
are
where
things
live.
D
E
D
A
News,
that's
also
being
worked
on.
Well,
that's
why
we
did
the
one
session
at
the
contributor
summit.
We
also
did
a
session
I'll
meet
our
contributors,
which
is
a
monthly
program
that
we
do
where
if
people
want
Co
based
tours,
they
can
ask
for
them,
and
we
did
one
on
the
kubernetes
kubernetes,
the
kubernetes
kubernetes
like
a
really
quick,
15
minute
or
so
tour
that
stips
did
the
same
one.
That
actually
did
the
API
server
walk
through.
A
A
Let's
see
here,
we
go
yep
code
based
tours
videos,
so
if
you're
as
you're,
going
through
your
journey
right
now
and
like
looking
at
all
looking
through
all
the
code
bases
and
things
like
that
and
if
you're
like
hey
I,
really
want
someone
to
explain
this
to
me
and
do
me
a
favor
and
and
come
in
here
and
write
what
you
would
like
on
the
in
a
comment.
And
then
that's
awesome
for
us,
because
on
what
I
can
do
is
recruit
those
folks
to
do
the
thing.
A
And
then
we
can
do
it
on
like
meet
our
contributors,
where
we
have
like
hundreds
of
folks
watch
that
and
it's
super
helpful,
like
birds.
So
in
agreement
with
you
that
this
is
this
is
definitely
something
that
we
think
we
need
at
this
point,
especially
with
190
180
repositories
and
so
many
of
them,
relying
on
KK
and
other
major
and
other
major
utilities,
and
things
like
that
that
we
have
in
those
repos.
So
yes,
all
awesome
suggestions
for
sure
cool.
D
E
A
Alright,
so
yeah,
that's
awesome
and
I
am
gonna,
go
ahead
and
move
this
over
to
in
progress
as
well,
because
we
have
made
some
progress
there
and
I'll
update
the
card
when
we
get
off
the
line
so
yeah
we
have
a
lot
of
stuff
going
on
and
as
Josh
alluded
to
in
progress,
I'll
do
a
quick
stand
up.
We
are
officially
wrapping
up
the
contributor
summit.
A
It
is
definitely
feels
like
the
song
that
doesn't
end
at
this
point.
We've
been
working
on
it
since
July,
but
we
are
so
at
the
homestretch
everyone.
We
are
doing
blog
posts
and
emails
and
picture
albums
and
YouTube
recordings
and
all
types
of
stocking
stuffers
for
everyone
that
relates
to
the
contributor
summit,
and
all
of
that
will
be
out
by
no
later
than
beginning
of
January
blog
post
season
and
sort
of
come
and
gone
at
this
point.
A
So
we're
gonna
wait
until
January
7th
to
get
something
out
to
folks
for
like
a
wrap-up
standpoint,
but
just
a
really
verbal
summary
of
the
contributor
summit.
It
was
awesome.
We
had
300
and
I
think
was
like
early
300
attendees.
That
was
a
roughly
I.
Think
89%
of
the
folks
that
said
they
were
gonna
come
so
they
were
going
to
come.
Bob
back
me
up
on
that.
Is
that
accurate?
A
F
A
We
go
knew
there
was
an
83
number
in
there
and
then
we
had
what
35
total
sessions
all
recordings
are
in
YouTube
verbals
that
we've
received
was
that
the
content
was
great
because
we
did
cater
to
multiple
personas,
but
we
are
sending
out
a
survey.
So
we
will
have
hard
data
on
things
like
that
here
within
I'd,
say
by
mid-january,
and
then
we
can
start.
We
can
start
chiseling
out
what
the
next
year's
contributor
summit
stuff
looks
like
and
strategies.
A
So
we'll
probably
settin
issue
shortly
here
to
get
things
kicked
off
for
strategy
plantings
and
things
like
that.
We
are
gonna,
have
a
conversation
with
sand,
CF
and
mid-january,
as
well
as
it
relates
to
budget
and
who
does
what
and
responsibilities
and
what
exactly
contributor
experience
does
in
this
process
like
what
do
we
own
etc.
So
that'll
also
help
us
with
planning
activities
in
the
future
as
well.
So
that's
my
stand
up.
That's
most
of
the
stuff
that
I've
been
working
on
Bob.
F
F
These
are
essentially
augmented
style
suggestions
from
the
main
chorus
Docs
and
taking
other
suggestions
from
like
how
gitlab,
google
and
a
bunch
of
other
groups
handle
their
documentation
and
should
help
sort
of
you
know
firm
up
how
we
handle
technical
documentation
within
the
community
repo.
So
this
is
more
so
for,
like
the
developer
guide,
contributor
guide
and
some
of
that
content
and
we'll
also
sort
of
give
all
our
pages
that
are
going
to
wind
up
eventually
on
the
contributor
site,
a
nice
like
sort
of
a
uniform,
feel.
A
A
So
this
style
guide
is
just
going
to
help
us
do
do
better,
as
it
relates
to
what
our
Doc's
should
look
like
inside
of
this
community
repos.
So
when
we
surface
them
on
contributor
sites
and
things
like
that,
we
don't
have
to
do.
Do
a
ton
of
work
to
make
them
web
friendly,
well
kind
of
already
be
like
that,
just
like
our
Doc's,
that
is,
on
the
technical
side.
A
C
A
E
F
F
G
A
And
I
know:
Bob
has
been
working
hard
on
this
as
well.
So
this
is
awesome
and
then,
on
that
same
breath,
if
you
will,
there
is
a
card
in
here
for
content
strategy
in
that
same
breath
when
we
realized
wow,
our
dogs
aren't
that
great,
when
we
were
surfacing
them
in
net
Laboy,
we
also
realized,
like
wow.
A
So
why
don't
we
just
give
them
the
resources,
and
things
like
that,
so
this
content
strategy
we're
getting
sort
of
a
little
I'm
saying
working
group
in
quotes,
meaning
this
isn't
like
we're
not
PRN
in
this
example
that
we're
having
a
working
for
if
this
is
just
within
our
little
crew,
a
little
birds
of
a
feather
crew
on
contributor
strategy
for
this
and
content
strategy.
This
would
just
be
as
doing
focus
groups
looking
at
data
that
we
already
have
maybe
collecting
data
from
other
sources,
whatever
it
is
on.
A
A
So
we
have
definitely
have
a
lot
of
work
to
do
here,
but
at
the
same
time,
I
think
we
have
enough
people
to
where
we're
going
to
be
able
to
chunk
this
work
out
and,
like
you
know,
one
person
does
a
few
focus
groups
with
the
same
questions
and
then
we've
really
suss
out
what's
needed
here
so
super
pumped
about
that
I've
done
some
content
strategies
in
the
past.
So
this
is
going
to
be
dusting
off
my
cobwebs
for
content
and
we'll
kick
that
up
next
year.
A
George
is
going
to
be
making
some
changes
to
the
cap
when
he
comes
back
to
so
we
can
rework
that
and
then
Matt.
That,
actually
is
a
really
good
segue
into
you,
because,
as
were
we
working
the
cat,
one
of
the
things
that
we
want
to
make
sure
of
is
like
what
done
means,
because
this
is
where
I
think
we
as
contributor
experience,
need
the
most
help
with
like
in
project
management
terms,
because
you
can
see.
We
have
this
a
big
humongous
board
and
we
do
obviously
have
a
complete
section
completed.
B
B
Overarching
things
which
are
actually
broken
down
into
here
are.
The
here
are
the
kind
of
tasks
that
this
breaks
down
into
and
I
guess
you
know
I
mean
again.
This
is
only
based
on
a
very
brief
look
at
this
board,
but
yeah
that,
like
we
talked
about
in
Seattle,
there's
a
there's,
there's
kind
of
a
difference
between
these
aspirational
kind
of
here's
is
what
the
end
goal
of
something
is
to
here
are
the
steps
by
which
we
get
there
and
and
I
guess.
The
minute
kind
of
feels
like
there's.
A
I'd
say:
100%,
fair
assessment
yeah,
so
I
did
put
a
call
out
on
the
contributor
role
board
for
a
project
manager
for
those
that
are
like.
What's
going
on
right
now
and
quite
a
few
people
responded,
so
many
actually
I
think
over
10
people
had
deemed
me
and
I
just
got
to
a
point
where
I
was
like.
Everybody
comes
to
cube
con
and,
let's
just
meet
there
kind
of
thing.
B
A
Now
we
have
Matt,
I
mean
you're
still,
you're,
still
very
interested.
He
actually
paying
me
and
said
that
he
was
gonna,
follow
up
with
this
video
and
then
also
probably
follow
up
with
you
to
personally
Matt.
So
I
actually
asked
quite
a
few
people
to
see
like
if
we
could
just
do
this
project
management
thing
together
and
start
to
release
us
out
like
what
our
milestones
are.
A
I
think
our
milestones
should
be
coupons,
not
necessarily
releases,
because
we
can
bribe
the
press
on
coupons
for
the
stuff
that
we
do
in
contributor
experience
and
all
awesome
stuff
that
that
should
come
out,
maybe
like
a
contributor
summits
and
things
like
that,
instead
of
releases,
because
we
don't
go
in
the
changelog
so
like
who
actually
is
seeing
our
communications
and
like
what
we
do
in
that
kind
of
summarized
format.
So
we
can
probably
like
publish
blog
posts
and
stuff
about
it
around
coupon
time.
A
B
You
know
in
some
ways
you
could
you
know
having
having
it's
quite
easy,
I
thinking
in
this
kind
of
stuff
to
end
up
with
20
or
30
and
a
growing
list
of
stuff
that
you
never
quite
get
to
the
end
of,
and
you
know
it's
probably
more
effective,
to
have
some
idea
of
what
velocity
you're
capable
of
achieving
and
actually
say
you
know.
Within
these
bounds
we
would
actually
like
to
achieve
x
y&z
rather
than
having
a
bed
and
going
partway
up
on
all
of
them.
You
know
I
think
it
makes
people
feel
better.
B
You
know
I
think
psychologically
it
can
be
quite
wearing
once
you
have
lots
and
lots
and
lots
of
projects
that
make
some
progress,
but
never
actually
reach
the
end,
and
you
know
being.
This
is
obviously
all
all
just
my
personal
opinion,
but
you
know
I
mean
so
and
and
if
you
want
to
to
have
things
that
complete,
you
know,
then
then
having
bounds
and
having
an
idea
of
what
resource
you've
got
within
those
bounds
is
always
going
to
be
a
give
we'll
approach.
A
A
A
I
know
it's
scary
word,
but
I
used
to
think
to
myself
like
when
I.
You
know
it
were
kid
like
in
big
PMO
is
and
stuff
like
that
like,
but
now
that
it's
just
like
we
do
whatever
we
like,
we
do
whatever
it's
kind
of
thrown
at
us
now,
I'm
like.
A
G
A
And
another
thing
to
Matt
that
I
don't
know
if
we
talked
about
it
or
not,
or
if
we
covered
it
when
we
talked
in
Seattle,
but
we
do
have
so
much
data
I
think
that's
one
thing
that
I
feel
this
year.
We
did
accomplish
that
we
did
not
have
what
that
we
haven't
really
talked
about
is
that
we
had
so
much
of
it
like
we
have
see.
We
have
feedback
data
for
so
many
contributor
summits.
A
A
How
can
we
actually
logically
put
that
in
place
and
and
then
also
include
that
with
include
that
in
our
project
management,
so
that
we
can
wait
it
and
I
don't
want
I,
don't
I,
don't
mean
the
word
wait
by
like
making
up
numbers
either.
It's
like
waited
as
far
as
like,
oh
that,
like,
for
instance,
the
highest
priority.
Of
course,
like
everybody
thinks
is
meant
as
mentoring,
so
it's
like
how
do
we
make
all
of
our
mentoring
stuff
like
the
highest
priority,
which,
as
you
can
see,
it's
blocked
for
the
most
part?
B
Yeah
and
I
guess
you
have
to
also
make
some
hard
choices
person.
You
know
you
have
to
say
no
to
things
and
say:
that's
not.
You
know,
because
that's
the
the
essence
of
making
priorities
is
that
you
have
to
drop
things
off
the
lot.
Yes
me
really
clearly
here,
looking
at
everything,
that's
in
this
board
right
now,
I
mean
I.
Don't
know
how
big
the
regular
contributor
pool
is,
but
I
mean
you
know
this
could
be.
There
could
be
three
person
years
of
work
in
this
place.
B
A
B
A
A
Then
not
to
sound
meta
but
file
an
issue.
Yes,
let
other
folks
know,
let's
start
to
let
other
folks
know
in
the
community
that
this
is
officially
being
worked
on.
Like
I
said,
I
already
did
file
the
like:
they
contributor
roll
board
thing
and
so
like.
Let's
just
get
this
kind
of
officially
kicked
off
at
that
school
and
I
guess,
you
know,
feel
free
to
put
like
your
first
steps
in
there.
We
can
all
communicate
via
that.
You
can
come
back
to
these
meetings
at
any
time.
You
can
slack
with
us
questions.
A
B
B
B
B
A
E
A
B
And
that's
my
absolute
approach
as
well
is
that
you
know
there's
no
point.
You
know
dragging
and
pulling
with
these
things.
You
know
I
think
even
even
to
have
you
know
a
voice
saying.
How
long
do
you
think
this
might
take
and
one
of
the
steps
by
which
you
get
there
is,
hopefully
you
know,
maybe
a
step
further
than
what
we've
got
at
the
minute
right.
So
you
know
if
I
can
be
that
voice
and
you
know
Pia
be
the
hard
one
who
everybody
wants
to
be
the
stick
and
DIF
helpful.
B
So
what
would
be
helpful
to
me
is
you
know
to
have
everybody's
thoughts
on
you
know?
What
are
the
pain
points?
You
know,
what
are
we
trying
to
solve
for
here,
because
you
know
visit
there's
a
lot
of
things
that
you
could
there's
a
lot
of
ways
you
can
you
can
go
about
this,
so
you
know
the
more
the
more
thoughts
on
from
from
this
group
on
what
are
the
pain
points
from
that
perspective
would
also
be
very
to
me.
It's
done
think
about
it.
I.
A
Can
definitely
give
you
those
for
sure,
even
today
so
yeah
yeah,
maybe
we
can
start
like
a
little
mailing
list
thread
to
and
that
would
kick
off
a
that
would
kick
off
an
issue
when
you
get
back
I'll.
Think
about
that
all
right.
Does
anybody
have
any
other
questions
for
in
relation
to
project
management,
stuff
going
on
and
or
mat.
A
B
A
That's
just
capturing
issues,
yeah
there's
a
whole
other
thing
which
is
PRS
so,
but
if
some
of
our
PRS
are
reactionary
and
don't
have
issues
or
are
touching
spelling
errors
or
what
have
you
that
aren't
related
to
an
issue?
So
but
that's
it.
That's
correct,
I'm
trying
to
like
we're
trying
to
foster
that
culture
where
everything
is
going
through
issues,
but
when
it
comes
to,
as
you
know,
community
management
topics
it's
hard
to
like
set
issues
for
slack
channels
and
stuff,
like
that.
A
B
A
H
H
H
H
A
Anyone
have
any
comments,
I
think
it's
a
good
I
think
it's
an
awesome
start
I
know
Nikita,
it's
already
commented
I
had
for
it.
It's
a
fill
with
rock,
because
he's
been
super
interested
in
getting
a
deaf
guy
kicked
off
same
with
Tim
on
the
line
Josh.
What
do
you
think
I
think
I
feel
like
you
have
some
opinions
here,
I.
C
A
Think
that's
the
largest
chunk
of
work
and
Juarez.
Once
we
have
that
once
you
have,
this
kind
of
skeleton
outline
set
is
filling
and
filling
it
in
and
then
she
I
think
you
don't
you
have
the
inventory
list.
Do
you
want
it
scroll
all
the
way
down
to
the
bottom
yeah,
so
the
other
thing
that
Anwar
is
working
on
is
just
doing
an
inventory
of
the
of
the
actual
develop
older.
A
What's
in
there
like,
if
it
should
be
in
there
if
it
should
be
linked
somewhere
else,
because
there
is
some
like
general
contributor
stuff
in
there
as
well.
That
maybe
should
be
surfaced
on
the
contributor
guide
and
really
thinking
about
that.
So
that's
a
part
of
the
next
step
that
he's
gonna
undertake
is
that
I.
H
A
Have
a
couple
different
ways:
I
think
one
way
is
looking
at
the
age
of
the
dock.
A
Maybe,
like
the
author
of
it
and
say
what
do
you
think
is
as
dark
stale,
if
you
don't
know
the
material
yourself,
for
instance,
and
then,
if
it
is,
if
you
do
have
any
other
doubts,
you
can
always
go
to
the
author
of
the
document
or
whoever
did
it
last
or
if
it's
an
API
related
dock.
You
know
that
you
can
go
to
eat
the
API
machinery.
A
Folks,
like
the
slack
channel,
is
probably
awesome
for
that
kind
of
discussion,
and
then
you
can
always
also
ask
us
in
our
contributor
experience,
lock
chat
as
well
and
we'll
read
it
and
someone
will
bound
to
have
an
opinion.
That's
the
good
thing
with
the
Dead
Bell
guide.
Is
that
a
lot
of
folks
have
a
lot
of
opinions,
so
you're
bound
to
get
something
with
an
answer?
G
Agree
with
what
Paris
has
said
and
I
also
I,
wouldn't
worry
so
much
about
that
at
first
as
you're
working
through
the
organization
and
trying
to
just
kind
of
work
out
from
your
skeleton
as
you're,
exploring
I.
Think
you're
gonna
be
asking
people
questions
like
each
of
these
docs
on
the
current
inventory.
They
have
a
get
history,
for
example,
there's
people
that
you
can
reach
out
to
through
that
to
say
like
hey.
Is
this
up-to-date
but
then
also
your
initial
reviewers
as
you're?
A
A
That
might
be
a
good
way
to
do
that
as
well.
If
you
feel
like
the
the
other
way,
is
going
too
slow
because
that's
my
fan,
there's
just
so
many
Doc's
in
this
folder
that
I
worry
if
we're
gonna
go
one
by
one,
just
like
what
kind
of
tim's
alluding
to
to
is
like,
we
might
not
necessarily
have
to
go
that
granular,
but
that
could
be
a
good
idea.
That
could
be
a
good
approach.
A
G
Option,
they're
kind
of
going
top-down
is
to
just
assume
they're
all
bad,
not
to
like
put
like
a
negative
spin
on
it,
but
if,
if
you
just
start
out
assuming
that
they
are
all
stale,
sometimes
it's
better
to
to
throw
things
away
in
bulk,
we
still
have
them
in
the
get
history,
but
starting
from
a
clean
slate,
might
give
a
more
coherent
guide.
Yeah.
A
Exactly
and
if
like,
if
you
are
both
like
bulking
them
up
like,
for
instance,
all
API
stuff,
all
architecture
stuff,
what
kind
of
mindset
you
might
be
able
to
get
a
couple
of
combo
docks
out
of
it,
where
it
might
make
better
sense
to
have
a
combo
dock
than
like
one
dock?
Or
maybe
you
see
like
a
dock
that
should
be
split,
so
that
could
be
a
good
way
in
like
your
head
to
do
the
architecture
of
the
docks
as
well.
I
hope
that
made
sense.
Thank.
E
Just
want
to
add
that
like,
if
you
just
want
to
start
off
with
something
there
are
a
few
issues
and
the
cake,
the
kubernetes
community,
we
both
which
say
hey
this
dock
is
tailored
this
dock
me.
This
dock
needs
improvement.
So
maybe
you
could
just
start
there
like,
for
instance,
I
know
the
testing
related
docks
are
steel,
so
you
could
probably
work
with
testing
folks
who
are
super
friendly
by
the
way,
and
you
could
probably
just
start
there.
Yup.
A
And
that's
another
yep,
that's
another
grouping
of
stocks
testing
so
like
testing
architecture,
API,
I'm,
so
happy
about
this
y'all
I
just
wanted
to
say
that
publicly.
This
is
so
great
and
needed
a
tour.
Thank
you!
So
much
do
you
have
any
other
questions
that
we
can
help
you
with
right
now.
Are
you
just
ready
to
dig
in.
H
G
You
click
on
raw
there,
since
your
screen
sharing.
Can
you
the
raw
button
kind
of
middle
right
yeah?
It
doesn't
often
inside
the
markdown
as
a
hidden
comment
that
doesn't
render
will
be
a
note
saying,
remove
this
file
by
such-and-such
time
in
the
future.
This
one
may
be
old
enough.
It
hasn't
been
modified
in
a
year.
G
It
may
be
old
enough
to
kind
of
predate
us
realizing
we
needed
to
to
make
those
little
reminders
and
it's
probably
a
sign
that
it's
ready
to
get
removed,
but
we
can
also
do
things
where
we
we
scour
the
repo
at
least
a
little
bit,
and
make
sure
that
anything
that
was
referring
to
this
page
gets
pointed
to
the
newer
one.
Okay,.
A
Also
like
that
approach,
so
if
yeah,
if
you
want
to
just
keep
that
as
a
note
to
yourself
and
keep
moving
that,
maybe
we
can
look
at
that
and
maybe
remove
other
instances
where
that
would
be
that
doc
would
be
called
and
then
just
delete
it.
Oh
where's,
our
style
guide,
Bob
style
guide
would
be
a
good
style
guide.
Suggestion
would
be
to
what
Tim
just
mentioned.
The.
A
A
F
A
G
F
F
A
E
A
I'm
we.
What
we
should
do,
though,
also
is
remove
this
file
when
we
do
the
style
guide,
all
right,
cool,
sorry,
I
was
kind
of
talking
to
myself
all
right
Edouard.
Thank
you
again.
So
much
that's
awesome.
We
are
going
to
be
seeing
you
for
the
next
two
plus
months,
so
I'm
sure
we
will
talk
again.
Anyone
have
any
last
minute
things
last
call
you
Tim,
Nikita,
Josh
I
will
see
Matt,
Bob,
I.
Think
that's
I
think
that's
a
wrap.
A
Oh
I'd
rather
grab
a
link
before
we
end
with
a
chat,
though
Edouard
there's
a
link
in
there
that
Tim
just
gave
you
all
right,
but
for
everybody
else
that
is
it.
Thank
you
so
much
for
everything
that
you've
done
this
year.
We
have
an
awesome
community
because
of
you
and
let's
go
on
to
2019
with
full
steam
and
a
plate
full
of
work
thanks.
Everyone.