►
From YouTube: K8s SIG Docs Meeting 20190528 (APAC)
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).
A
A
B
C
A
Cool
okay.
Thank
you.
Alright,
a
couple
of
updates
and
reminders.
The
pr
angular
this
week
is
tim
zhang
and
the
PR
angler
next
week
is
going
to
be
Cody.
Clark
and
I.
Don't
have
any
updates
from
Barney
for
1:15,
but
as
of
last
week,
it
sounds
like
they
are
getting
the
draft
submissions.
The
deadline
was
coming
up
last
week,
I'm
not
sure
if
that
was
fast
or
not
so
moving
on
to
the
agenda.
This
is
a
item
that
came
up
last
week
at
the
Sigma
X
meeting
and
I
thought.
A
A
I
know
that
we
have
a
smaller
group
attending
right
now,
so
it
might
be
something
that
we
bring
back
up
next
meeting
or
we
have
a
larger
gathering.
I
think
this
is
a
valuable
topic
and
it
can
only
lead
to
you
know
better
documentation
and
better
localization
efforts
and
a
more
collaborative
effort.
You
know
I
think
we're
doing
great
I
think
extending
that
would
be
be
awesome.
A
All
right,
it's
moving
on
with
our
agenda,
so
Junyi
can't
attend
today,
but
he
did
leave.
Some
notes
sounds
like
there's
a
new
reviewer
and
a
new
contributor
to
to
the
Korean
localization
efforts.
That's
great
I'm
glad
to
see
some
new
friendly
faces
and
they're
gonna
pause.
The
Korean
localization
burgeoning
while
they're
waiting
for
the
1:15
released
tentative
for
June
17th
and
it
looks
like
they're
going
to
elect
a
new
leader
for
the
localization
is
currently
June
Lee,
and
it
looks
like
that.
A
D
Hello,
if
you
may
hear
you
okay,
so
I
have
a
suggestion
regarding
that.
Pr
Wrangler
I
noticed
that
for
some
regions
our
PR.
D
A
A
A
A
A
Okay
looks
like
I
see
here
to
make
suggestion.
So
over
the
past
couple
weeks,
we've
accumulated
around
200
pr's,
even
with
the
PR
regular
assignments
and
I
believe
from
the
agenda
item.
The
suggestion
is
to
make
sure
that
the
PR
Wrangler
is
available
to
wrangle
PRS
as
well
as
be
available
to
field
those
coming
in.
So
we
can
keep
the
PR
account
pretty
low
and
then
the
event
someone's
not
available.
We
could
schedule
somebody
to
take
their
place.
That
I
think
it's
a
fantastic
idea.
A
D
C
Yeah
go
forward
so
this
this
came
out
of
a
a
PR
that
was
merged,
that
removed
a
couple
pages
and
left
a
bunch
of
dangling
links.
If
I'm
not
mistaken,
do
we
we
don't
currently
have
anything
in
place
to
check
for
dead
links
is
am
I.
Correct,
I
was
talking
with
a
few
people
in
the
contributor
group
in
in
Barcelona
about
maybe
looking
into
doing
something
for
that
either
automated
or
something
manual
to
start.
C
So
this
doesn't
happen
because
when
that
PR
was
merged
it,
it
left
about
56
dead
links
across
like
five
different
languages,
mostly
pointing
to
older
pages
that
don't
exist
anymore.
But
still
you
know
hanging
out,
and
you
know:
I
opened
a
PR
to
fix
the
English
ones
and
seems
like
the
other
language
teams
have
stepped
up
and
fixed
them.
It's
good.
You
know
low-hanging
fruit
for
people
good
first
issues,
but
just
something
that
I
thought
I'm
looking
into
and
I
don't
know.
If
anybody
else
has
ever
thought
about
it.
A
B
Yes,
I
just
opened
up
here
a
few
days
ago
for
a
dead
link.
I
chose
this
name
to
chatbot.
Just
as
mentioned
as
said
said,
said:
I'm
just
wondering
how
to
fix
this
problem
and
I
found.
It
was.
B
A
A
Know
one
thing
that
you
might
think
about
trying
if
you
have
a
dead
link
like
the
one
in
the
PR
that
was
sent
over
in
chat,
is
it
talks
about
AWS
and
some
of
the
code
for
the
AWS
cloud
provider?
I
think
it
might
make
a
lot
of
sense
to
look
on
slack
to
see
if
you
could
message
somebody
on
either
the
AWS
provider
channel
or
on
you
know,
potentially
a
cloud
provider
just
the
the
subproduct
I
think
that
there
would
be
a
good
way
to
get
traction
and
I.
A
C
Talking
to
Kristoff
in
in
Spain
about
this,
it's
something
he
was
very
interested
in,
because
I
know
there's
an
overall
push.
You
know,
especially
for
the
documentation
and
stuff
to
do.
You
know
spell
checking
linting
stuff
like
that,
and
there
are
some
open
source
things
that
have
been
written
to
do
you
know
just
dead
link,
checking
and
I.
Don't
know
if
we,
you
know
eventually
merge
that
into
some
sort
of
automated
command
that
checks.
C
A
A
You
know
I'm,
not
sure
if
in
situations
like
this,
if
we
could
link
to
a
specific
commit
over
the
actual
code
itself,
you
know
I,
don't
know
enough
about
the
context
to
say
one
way
or
the
other,
but
I
agree,
though
specific
commits
going
to
be
a
lot
longer
lived
linked
than
a
direct
link
to
code
in
master,
so
I
think
it's
a
great
suggestion.
I
just
don't
know
enough
context
around.
You
know
the
different
bits
and
pieces
that
are
moving
around
to
say
you
know
good.
A
A
And
then
so
the
not
sure
if
you
found
it
yet
or
not,
but
there
is
a
kind
of
walking
and
talking
here,
there's
a
cig
docks
tools
channel
on
slide,
okay,
nope
now
I
know
yeah,
so
I
would
definitely
recommend
joining
the
sig
Dax
tools
channel.
There's
a
lot
of
individuals
that
are
involved
with
the
different
tooling
around
documentation.
A
I
think
this
would
fall
under
a
project.
That's
you
know
little
wider
reaching
than
just
sig
Dax
with
sig
Dux.
You
know
the
tools
area
definitely
seems
like
somewhere
that
you
lend
a
hand,
cool
cool,
I'll
start
there
cool
yeah.
If
we
end
up
figuring
out,
there's
a
lot
more.
You
know,
as
we
start
uncovering
things
we
find
out,
there's
a
lot
more
work
to
be
done.
We
can
definitely
start
putting
this
as
a
project
for
some
of
our
goals
or
maybe
find
that
we
just
need
some
minor
housekeeping
even
better
yeah.
C
C
C
A
A
Oh
yeah
did
delayed
reaction,
but
I'm
catching
up
as
well.
Yeah
I
think
that
Roger
would
definitely
be
very
helpful
in
this
yeah
in
the
chat
just
for
context,
chiming
sent
in
there
saying
that
we
had
a
lot
of
dead
links
in
there.
Roger
was
definitely
leading
an
effort
to
clean
up
some
of
those
dead
links,
so
it
sounds
like
Seth,
then,
and
rather
compared
up
to
attack
ulis
together
and
Oakland
this
stuff.
So
definitely.