►
From YouTube: K8s SIG Docs monthly APAC Meeting for 20220322
Description
For more info see https://git.k8s.io/community/sig-docs
A
A
Shadowing
this
week,
next
week's
PR
WR
Wrangler
is
Savita
and
you
know
just
if
you
all
need
to
know
who
are
the
next
set
of
PR
Wranglers.
Who
are
you
know
going
to
be
coming
up?
You
can
visit
the
link
and
and
get
to
know
more
or
if
you
want
to
shadow
under
a
particular
PR
Wrangler,
that's
an
option,
that's
available
as
well,
so
that
I'll
get
to
know
more
about
the
reviewing
and
approving
process.
A
A
So
yeah,
that's
that's
regarding
the
updates
reminders
bit
and
the
next
one
is
our
actual
agenda.
For
today,
which
is
you
know,
pretty
crackling,
given
that
you
know
we
are
nearing
the
release,
you
know
date
not
exactly,
but
you
know
we
are
closer
so
ahead
and
you
know
give
us
the
updates
for
the
docs
team.
C
Oh,
yes,
sure
so
we
are
in
week
11
and
our
current
status
is
yellow,
because
we
know
that
we
are
almost
around
the
deadline
for
the
placeholder
PR.
We
are
one
week
left
and
yes
still,
the
we
have
received
only
half
of
them
still
half
of
them
are
remaining
and
integration
branch
have
an
easycla
error.
So,
yes,
that's
quick
update.
A
C
C
A
A
D
D
Six
scheduling
have
been
contact,
notified
for
a
tech
review
and
Zach
recommended
six
scheduling,
hasn't
reviewed
by
the
end
of
last
week
to
just
con
to
consider
merging.
So
just
I
already
put
approved
label
on
it,
so
it
just
needs
an
LG
TM
for
this
PR.
So
anyone
could
do
an
I
think
all
org
members
could
use
slash
could
add
into
lgbtm
label
with
Slash
LG
TM
anyway.
C
E
D
D
But
we
we
did
last
last
week
or
two
weeks
and
when
was
this
yeah
23
days
ago,
we
did
but
I
I
haven't
when
I
got
around
to
take
a
look
at
it.
I
didn't
see
any
mermaid
issues,
so
I
don't
know
yeah,
so
I
don't
know
if
it's
just
if
it's
the
end
user,
if
it's
the
client
side,
the
mermaid
issue,
this
one
issue,
that's
linked
here,
there's
a
link
to
the
page
that
is
supposed
to
be
broken
and
the
Ingress
page.
D
A
D
I
think
yeah
I,
think
pushing
into
slack
is
good,
because
Chris
has
written
the
documentation
on
how
to
do
mermaid
diagrams
on
the
kubernetes
website
to
see
if
he
knows
of
any
best
practice.
I
think
any
best
practice
should
be
included
with
with
the
mermaid
diagram
instructions
that
we
have
on
kubernetes.io.
E
A
A
So
I
think
the
best
way
that
we
can
move
forward.
I'll
open
up
the
slack
shred
for
the
issue,
or
maybe
one
of
us
can
it's
not
necessarily
me
I
I
need
to
take
the
lead,
but
I
any
one
of
us
can
open
a
slab
shed
and
you
know
Cece
Chris
on
it
and
let's
see
if
we
can
actually
understand
a
like
in
general
and
from
a
wider
perspective.
A
A
B
B
D
B
A
Yeah
all
right,
so
anything
else
that
requires
attention.
I
can
see.
There
are
two
other
issues.
There
are
there's
one
about
still
milestones
and
there's
also
one
about
third
party
content.
Let
me
just
you,
know,
reshare
and
see
what
those
are
about.
I
have
not
shared
my
entire
screen,
so
just
a
second.
A
I
think
it
was
just
an
FYI
if
I'm,
if
I'm,
not
mistaken
foreign
yeah.
So
this
was
an
FYI
and
Zach
has
just
put
this
here,
so
that
we'd
all
be
aware
that
you
know
this
should
not
have
like
third
party
content
and
whenever
the
requester
is,
you
know,
available
to
refactor
the
pr
to
remove
any
mention
of
azure
competitors.
They
were
welcome
to
do
so,
and
you
know
reopen
it
whenever
they
were
ready.
So
this
was
just
an
FYI
and
the
next
one
is
the.
E
A
E
E
A
B
A
D
B
A
If,
yes,
then
you
know,
we
suggest
to
suggest
them
to
open
the
pr
reopen
the
pr
and
continue
work
on
it
or
else
what
we
would.
What
we
should
do
is
have
this
explicitly
mentioned
that
I.
We
can't
explicitly
mention
it
also
because
it's
there
already,
so
we
actually
put
it
out
somewhere
that
you
know
it's
it's
not.
This
is
not
a
a
fair
deal
that
we're
offering
to
people.
When
you
know
Amazon
and
Google
already
have
their
content
out
there
that
we're
not.
A
A
Because
otherwise,
I
don't
see
any
other
options,
given
that
you
know
Zach
is
supposed
to
be.
Pr
is
one
bit,
but
the
author
hasn't
exactly
been
responsive,
so
I
I,
don't
know
if
the
author's
original
the
original
author
is
actually
interested
in
continuing
with
the
pr.
So
I
agree
that
Zach's
comment
was
probably
a
bit
misleading.
But
again,
if
the
author
is
not
interested,
there's
not
a
lot
of
stuff
that
we
can
do
right
now.
B
B
B
A
A
So
do
we
I
actually
I'm,
not
well
aware
of
this,
so
I'm,
sorry
that
you
know
I
can't
provide
more
inside
but
I'd
be
happy
to
work
alongside
someone
who's
more
aware
and
gain
more
knowledge
on
this
so
Kimmy
any
one
of
y'all
are
aware
of
how
you
know
this
needs
to
be
done,
because
I
can
see
that
the
Japanese
ones
have
been
completed.
To
be
honest,
so,
and
there
are
the
Korean
ones
as
well
so
can
are
you
all
aware
or
do
we
need
need
to
reach.
A
B
A
E
B
E
D
E
A
A
So
what
we
can
do
on,
like
maybe
a
monthly
basis
I,
would
going
forward
again.
It's
not
you
know
right
now,
but
going
forward
on
a
monthly
basis.
What
we
could
do
is
at
the
end
of
every
month,
because
we
have
this
meeting
at
the
end
of
every
month,
because
sort
of
have
you
know
a
review
of
extremely
stale,
or
you
know
very
old,
PRS
and
figure
out
what
needs
to
be
done
with
them.
A
I
know
that
you
know
we
have
a
lot
of
PRS
that
have
ongoing
work
and
some
that
have
been
open
since
forever,
but
you
know
have
no
people
responding
over
them,
but
I
feel
like
it
requires
a
more
you
know:
structured
review,
Cadence
as
opposed
to
you
know
one
or
two
people.
You
know
picking
it
up
every
time
they
are
the
pr
Wrangler,
because
what
tends
to
happen
is
one
of
us
or
maybe
you
know
one
among
the
leads,
actually
notices
that
you
know
the
pr
numbers
are.
A
You
know
spiky
and
that's
when
we
start
taking
action.
So,
instead
of
that,
if
we
can
sort
of
have
like
a
monthly,
not
necessarily
monthly
I,
just
introduced
it
off
monthly,
but
we
could
have
like
a
review
in
an
in-person
meeting
regarding
the
number
of
PRS,
and
then
you
know
for
that
particular
month.
If
we
say
that
you
know
this,
these
are
the
specific
PRS
that
we
can
sort
of
do
away
with.
A
To
put
it
in
nice
words,
that
would
be
a
great
thing
or
if
you
know
you
all,
have
better
suggestions,
I'm
open
to
it,
because
we
had
this
issue
last
year
as
well
before
kubecon
n,
a
and
I
remember,
Jim
and
myself,
you
know
wrangling
through
most
of
it.
Jim
was
the
Wrangler,
then
so,
but
if
we
had
like
a
similar
number
that
I
as
well-
and
we
were
hacking
down
the
pr
so
that
the
number
comes
down
to
below
180,
at
least
so
that's.
D
There
are
some
reviewers
who
are
not
as
active
and
and
maybe
we
should
verify
with
with
those
reviewers
if
they
want
to
be
on
the
pr
Wrangler
schedule,
because
at
times,
if,
when
when
inactive
reviewers
are
when
it's
their
week
to
Pringle,
sometimes
those
the
PRS
aren't
being
wrangled.
So
it
it
it's.
So
the
number
of
openpr
is
keeps
increasing,
increase
increasing
until
an
active
reviewer
gets
around
to
to
review
and
a
lot.
D
That's
always
a
topic
is
to
increase
the
number
of
of
not
just
contributors,
but
also
folks
who
are
who
are
active,
reviewers
as
well,
so
I
think
that's.
We
could
also
make
make
an
effort,
I,
don't
know
what
that
effort
looks
like
right
now,
but
I
think
that
that
could
be
like
a
long-term
goal
as
well
as
some
more
active
reviewers
all
right.
Those
are
just
my
some
of
my
thoughts.
E
C
E
B
A
D
Yeah
I'm
definitely
going
to
be
on
my
on
my
on
the
reviews
are
definitely
gonna
be
on
on
my
radar
with
the
since
the
docs
placeholder
PR
deadline
is
coming
up
again
in
March,
and
then
we
have
the
several
doc
doc
related
milestones
for
the
124
release.
Shortly
I
mean
it's
going
to
be
in
within
two
weeks.
We're
gonna
have
lots
of
PRS
to
review.
A
Okay,
so
kimming
Andre.
What
what
do
you
say
to
this
suggestion
of
having
you
know,
I
mean?
Obviously
you
said
it
will
be
on
your
radar,
not
saying
no,
but
do
we
want.
You
know
to
have
someone
officially
tag
along
with
Savita
for
these,
for
this
particular
for
these
coming
for
the
next
coming
week.
Rather
because
we
are
expecting
an
influx,
or
maybe
at
least
till
the
dogs,
placehold
or
deadline
gets
done.
A
Do
we
want
extra
focus
on
the
reviewing
and
approving
bits
so
that
we
have?
You
know
that
out
of
the
system
as
soon
as
possible?
Would
that
sound
like
a
a
decent
idea?
I,
don't
know
who
is
during
the
work?
It's
just
an
initial
suggestion.
Maybe
we
can
sort
of
put
it
out
on
slack
as
well,
so
that
if
people
are
ready
to
you
know
chip
in
with
helping
or
tagging
alongside
the
Wranglers
for
the
next
couple
of
weeks,
that
might
help
and
they
can
actually
step
up.
D
A
B
A
E
A
Well,
yeah
because
I
I
agree
with
you:
timing,
kimming,
that
you
know
this
is
going
to
be
a
mammoth
effort,
given
the
number
of
placeholder
Piers
that
are
that
have
not
yet
been
filed
and
that
we
are
expecting
to
you
know
see
in
the
coming
few
days.
So
I
think
that
was
a
very
good
point
that
you
brought
up
and
thank
you
for
bringing
it
up.
A
I'll
call
for
action
on
slack
I'll
I'll
put
that
out.
If
everybody
is
okay
so
that
we
have
more
hands
on
deck
and
we
don't
need
to
you
know
struggle
with,
you
know
the
reviewing
and
approving
at
least
for
this
particular
cycle,
but
for
a
longer
term.
I
guess
you
know
what
we
should
be
doing
is
to
come
up
with
a
sustainable
idea,
but
that
is
something
that
we
can.
You
know
have
discussed
over
at
length
and
then
you
know
come
up
with.
A
D
Just
just
looking
at
the
pr
Wrangler
schedule
so
on
April
3,
it's
like
a
matches,
Brad
topple
and
we
have
Tim,
then
Divya.
So
we
have
active
reviewers
for
around
when
the
Ducks
are
actually
ready
for
review
required
to
be
in
when
the
docs
are
required
to
merge
into
the
124
Branch.
So
so
we
should
be
able
to.
B
D
A
Mean
you
can
you
can't
be
too
LAX
about
it,
because
so
we
never
know
what
what
tends
to
break
at
what
point.
So
it's
better
that
we
have
a
second
person
on
deck
and
then
you
know
also
discuss
a
sustainable,
Way
Forward,
because
I'm
I'm
very
sure
that
you
know
we
don't
want
to
encounter
a
situation
like
this
again
so
yeah.
A
D
E
D
So
the
Bengali
localization
team
asked
for
a
development,
Branch
and
I'm,
creating
that
Branch
tomorrow.
I
wanted
it
to
wanted
it
to
to
also
be
able
to
to
teach
folks
on
how
to
create
the
branch
of
we
do
have
access.
Some
I
also
wanted
to
run
it
by
the
localization
leads
as
well,
so
that
is
so
scheduled
a
time
tomorrow
to
create
the
branch
and
also
to
test
my
access
as
well
just
to
make
sure
I
have
access
to
to
create
that
development
Branch.
D
D
B
A
All
right
so
yeah,
that's
great
and
I'll
look
forward
to
seeing
your
message
on
slack
tomorrow,
so
I
intend
to
join.
Hopefully,
I
don't
have
any
other
meeting
at
that
point
which
I'm
assuming
I
do
but
I'll
try
wiggling
out
of
it,
but
yeah
so
yeah
anything
else
from
anyone
else,
because
I
think
we
are
sort
of
at
the
end
of
our
agenda.
So
anything
we
did
not
discuss
and
if
anybody
wants
to
bring
it
up
right
now
would
be
a
good
time
to
do
so.