►
From YouTube: K8s SIG Docs Meeting 20200114
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
B
C
A
E
B
C
B
We
are
all
Tim
fans
all
right,
see.
Next
week's
PR
Wrangler
is
toonder,
let's
see
and
Brad
topo
put
together
our
PR
regular
schedule
for
the
first
half
of
the
year.
So
this
is
a
really
good
time
to
go
check
out
that
schedule
and
see
where
you
fall
and
if
there's
any
conflict,
it's
better
to
try
and
switch
shifts
earlier
rather
than
later
for.
B
New
folks,
the
PR
Wrangler
is,
we
all
take
turns
all
of
the
approvers
take
turns
over
the
course
of
the
year
serving
was
the
first
point
of
contact
for
merging
and
giving
feedback
on
pull
requests
and
helping
them
get
out
the
door.
So
all
right,
that's
our
agenda
Docs.
So
first
on
the
list
is
the
kept
for
third
party
concept.
I
am
still
catching
up,
but
I
don't
know
what
it
is
about
being
in
the
shower.
It
said
the
the
medium
temperature
in
the
white
noise.
B
It
was
in
the
shower
last
night
and
it
suddenly
came
to
me
like
what,
if
we,
what,
if,
instead
of
trying
to
make
all
of
the
finely
finely
detailed
classifications
we've
made
so
far,
what
if
we
just
said,
we
maintain
what's
necessary
to
run
default.
Kubernetes
entry
I
mean
it
seems
like
it
would
be
a
much
a
much
more
reasonable
way
to
to
describe
what
it
is
that
we
do
and
don't
accept
in
terms
of
third-party
content.
What.
E
B
Sum
this
up
in
the
13
seconds,
there's
too
much
vendor
content
on
in
the
kubernetes
stocks,
how
to
get
rid
of
it.
It's
a
bit
of
a
thorny
question:
how
to
give
a
clear,
thumbs-up
or
thumbs
down
to
proposed
proposed
additions
of
third-party
content.
This
is
a
long
discussion.
It's
been
going
on
since
last
fall.
B
B
So
API
Docs
I
know
we
talked
last
week
about
giving
whether
or
not
to
prioritize
attention
to
our
API
documentation.
In
that
whole
reference
generation
process
and
I
think
we
said
what
we
say
to
most
things
that
are
really
cool,
that
we
don't
have
the
resources
to
do,
which
is
exactly
that.
It
would
be
really
cool
to
prioritize
and
fix
this,
but
that's
that's
resource
dependent
and
over
the
past
week
a
couple
of
issues
came
up
that
I
think
heightened
heighten
the
priority
of
dealing
with
API
reference
generation.
B
As
she
being
pointed
out,
there's
a
bit
of
discussion
there,
so
I
think
I,
don't
know
that
there's
anything
particularly
new
there,
just
that
it's
deepens
it
heightens
the
relief
in
which
the
our
API
reference
TOC
is
brittle
is
cast.
It
is
just
increasingly
clear
that
our
API
generation
reference
generation
process
is
it's
not
going
to
remain
fine,
I,
think
for
like
another
year,
so.
B
What's
the
kubernetes
api
is
that
be
the
default
api
s--
are
expect
out
in
is
in
an
open,
API
spec.
It
wouldn't
touch
things
like
KU
cuddled,
yet
at
least
I,
don't
think,
but
I
don't
know.
Maybe
Tim
do
you
know?
Are
you
familiar
with
the
coop
cuddle
API?
Well
enough
to
speak
about
how
it's
stepped
out,
I.
B
G
B
B
B
B
But
it
looks
a
hell
of
a
lot
better
than
it
did.
Obviously,
it's
a
very
rough
cut.
There
are
some
build
issues
that
we
need
to
resolve,
but
it
might
be
if
someone
could
find
a
link
for
that
it
might
be
worth
taking
some
time
at
the
end
of
the
meeting
to
review
what
we
look
at
so
that
I
could
give
some
preliminary
feedback
to
to
the
contractors
who
are
handling
that.
B
H
Yeah,
this
is
a
real
quick
note
and
this
is
more
housekeeping
than
anything
else.
I'm,
just
letting
everyone
know
that
if
you're
looking
at
the
meeting
agenda
today,
you're
only
gonna
see
2020
meeting
minutes
and
what
I'm
doing
is
I'm
archiving
the
2019,
Docs
and
I'm
cleaning
up
some
circular
links
that
we
have
out
there
to
old
archived
documentation.
So
just
a
general
heads
up
we're
doing
clean
up
and
links,
and
things
may
move
around
a
bit.
I'ma
try
my
best
to
make
it
not
disrupted
the
folk.
H
B
Okay
is
get
an
item
for
sigdoc
security.
I,
don't
see
Seth
on
the
call.
Ok,
we'll
skip
that.
For
now
a
blog
working
group
Katelyn
is
Katelyn
works
at
Kong
and
Kong
is
having
one
of
their
All
Hands
meetings
today,
so
we'll
defer
that
until
Caitlin
shows
up
I
see
that
so
last
week
we
talked
about
on
maybe
moving
our
meeting
time
for
our
weekly
meeting.
B
I
So
I
try
to
clean
up
the
scope
of
work
as
best
I
could
and
then
I
saw
Tim
jumped
in
and
made
some
great
recommendations.
So
it's
a
solid
draft.
If
nobody
else
has
any
other
thoughts,
I
think
it's
good
to
circulate
whatever
avenues
you
have:
Zach,
okay,.
I
B
G
J
Back
from
vacation
excited
to
be
here,
I
am
a
shadow
of
the
dog
school
and
wonder.
Dayton,
release
and
I
will
be
here
providing
the
updates
every
week
and
if
you
have
anything
new
that
we
have
retained
you're
like
any
new,
what
do
I
say
the
templates
and
everything
just
feel
free
to
me.
A
message
or
I
will
also
send
the
oh,
my
god,
I'm
just
blanking
I
will
send
the
contact
list
of
all
the
dogs
team
members
here.
1.80
Mary's
dogs,
team
members-
that's
all
from
here!
Thank
you.
H
Yet
before
sorry
I
hate,
you
know,
I
had
those
technical
difficulties
I'm
on
my
cell
phone
now
so
I
hate
not
having
y'all
only
see
up
my
nose,
but
one
real,
quick
comment.
I
wanted
to
add
on
the
docs
118
release
is
I'm
working
with
the
release
engineering
team
on
Cairo,
which
is
a
tool
that
they
use
for
branch
management.
Sorry,
now
we're
evaluating
the
Cairo
tool
for
modifying
and
merging
that
master
branch
into
the
development
branch.
H
J
J
B
I
C
Excellent
job,
thanks
to
guys
from
the
French
localization
team,
the
with
their
initiative,
because
they
first
reached
me
out
I,
had
already
this
translation
for
version
116,
but
stuck
little
bit
looking
for
approvers
and
and
they
helped
me
to
find
and
to
go
through
the
process.
So
that
was
very
important
because
when
you
first
start
reading
all
the
necessary
things,
it's
like.
Oh,
it's
impossible,
I,
never
find
the
core
viewers
which
approved
me
as
a
kubernetes,
walk
member
and
so
on,
and
they
helped
me
to
understand
and
facilitated
process.
So
that
was
very
useful.
B
A
B
Just
really
quickly,
I
am
looking
and
looking
in
the
website.
Rico
and
I
am
looking
at
the
number
of
English
pull
requests
open.
It
looks
like
we've
got
a
hundred
and
thirty-six
open
PRS,
which
is
a
lot
better
than
it
was
last
week,
so
we're
getting
down
there
I
would
still
love
to
see
it
under
a
hundred,
but
many
thanks
to
to
Brad
him
for
reviewing
and
closing
so
many
PRS
Caitlin,
hello,
hello.
K
Awesome
so
we
had
a
blog
post
go
out
today
on
the
kubernetes
bug
bounty
program,
which
is
really
exciting
to
encourage
you
all
to
check
that
out.
We
are
now
in
the
process
of
cleaning
up
some
of
the
other
updates.
We
have
to
the
blog
queue
and
we
got
a
couple
closed
out
today
and
otherwise
it's
kind
of
business
as
usual.
C
C
B
F
C
B
B
B
Obviously
this
isn't
complete,
but
this
is
what
the
conversion
looks
like
so
far.
Obviously
there
are
some
things
over
here
that
needs
to
be
addressed.
This
is
like
over
here
with
these
advanced
topics.
Sorry,
is
this
advanced
topics
link?
That's
how
I
realized
that,
even
though
it's
been
orphaned
from
any
link
to
it,
the
user
journey
content
is
still
in
the
repo.
So
I
opened
an
issue
to
basically
just
delete
those
file
paths.
B
I
H
B
H
Do
you
know
for
still
at
the
very
bottom
of
the
page,
having
the
last
time
the
page
is
updated
or
committed
and
I'm
sure
it
could
be
a
minor
fix,
if
not
I,
think
it.
That
was
very
helpful
to
see
your
content
realize
the
staleness
of
the
page
by
scrolling
to
the
very
bottom,
and
it's
already
there
perfect.
B
F
C
F
E
G
E
I
F
B
That's
good
feedback
thanks
everyone
all
right
is
there
anything
else
that
folks
would
like
to
discuss.