►
From YouTube: K8s SIG Docs Monthly APAC Meeting for 20220622
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
Started
so
hello,
everyone
welcome
to
the
sick
dogs,
APAC
friendly
meeting
for
the
month
of
June,
today's
the
22nd
of
June,
and,
as
is
the
case
every
month.
We
hold
this
on
the
fourth
Wednesday
of
each
month.
So
today
the
agenda
seems
to
be
pretty
light.
So
if
there
are
any
new
contributors
as
of
today
on
this
call-
and
they
want
to
go
ahead
and
introduce
themselves,
I
request
them
to
take
the
floor
and
do
so
so
yeah
I'll
just
go
on
mute
for
a
little
while.
A
Okay,
so
I'm,
assuming
that
everyone's
here,
everyone
here
is
familiar
with
the
the
meeting
proceedings
and
that
this
will
be
held.
This
will
be
held
to
the
kubernetes
code
of
conduct,
which
basically
entails
that
you'll
be
nice
to
one
another.
So
since
there
aren't
any
new
introductions,
let
us
get
to
the
agenda
for
today.
A
All
right,
so
the
updates
remind
us
for
this
week
are
basically
standard,
which
you
know
are
about
the
pr
Wrangler
shift.
So
this
week's
PR
Wrangler
is
Ray
and
he
will
be
responsible
for
you
know,
being
the
point
of
contact
for
all
PR
reviews
and
approvals.
A
So
if
there
are
any
that
require
image
and
attention
or
they
haven't
been
looked
at
in
a
while-
and
you
know
you
are
finding
a
difficult
to
find
approvals
reviewers,
whether
please
reach
out
to
him
next
week's
PR
Wrangler
is
Natalie,
and
you
know
the
pr
angler
shifts
are
on
our
GitHub
page.
So
you
can
navigate
to
this.
To
see.
A
Who
are
you
know
the
pr
regulars
for
this
and
the
next
week
or
for
any
of
the
weeks
that
you
want
to
check
out
for
also
for
those
you
know
who
are
joining
in
late
or
who
are
not
aware
of
this.
You
can
also
volunteer
to
be
a
PR
Wrangler
Shadow,
which
basically
means
that
you
can
sort
of
you
know,
be
a
PR
Wrangler
yourself
or
at
least
understand
how
how
the
pr
wrangling
process
works.
A
Well,
how
we
review
and
approve
PRS-
and
you
know,
Shadow
a
person
who's
done
it
and
gain
first-hand
experience.
So
if
this
is
something
that
you're
interested
in
doing-
and
this
would
help
all
reviewers
and
approvers-
and
you
know
lead
greatly-
please
consider
reaching
out
to
Brad
Topol
and
get
yourself
added
to
the
shadow
program.
So
what
you
essentially
need
to
do
is
just
go
to
the
pr
Wrangler
shifts
page
and
see.
A
If
you
know
there
is
a
week
or
a
specific
PR
Wrangler
that
you
want
a
shadow
against-
and
you
know
cite
your
interest
to
Brad
topple.
He
would
be
the
one
adding
you
to
the
you
know:
PR
Wrangler
shift
schedule
along
along
with
the
pr
Wrangler
as
a
shadow.
So
that
being
said,
are
there
any
questions
around
this
before
we
move
on
to
the
next
question?
You
know
section.
A
Okay,
since
it's
been
dropped,
silence
I'm
going
to
go
on
to
the
next
agenda
item,
which
is
the
release
one
or
two
five.
A
So
as
of
today,
we
don't
have
any
updates,
because
I
just
got
this
up
right
now
and
I've
actually
just
noticed
that
I
put
the
date
as
well
wrong,
I'm,
sorry
about
that,
but
we
also
have
an
ongoing
Snapchat
so
as
and
when
Christian's
able
to
sort
of
get
us
an
update,
it'll
be
there
and
it'll
reflect
here
as
well.
So
that's
that's!
That's
pretty
light
on
the
agenda.
As
far
as
the
release
items
go,
the
next
one
is
the
issues
in
PR.
A
So
are
there
any
specific
issues
or
PR's
with
respect
to
the
website,
or
you
know
localization
documentation
or
something
else
that
requires
our
attention
at
this
point
in
time.
Please
feel
free
to
you
know,
take
the
stage
and
let
us
know
about
it.
A
In
just
a
second
I'm,
not
sure
if
you're
able
to
view
this,
so
just
let
me
open
it
up
here.
A
A
B
Anyway
or
while
you
are
opening
the
the
page,
I
can
talk
about
it,
it
is
actually
about
an
improvement
to
the
reviewing
guide.
Recently.
I
have
noticed
that
some
some
reviewers
are
using
the
GitHub
requesting
changes
option
when
review
appear,
and
this
kind
of
comment
is
confusing,
but
but
other
reviewers
jumping
in
trying
to
approve
a
PR.
Also,
the
existing
request
intended
comment
cannot
be
discarded.
B
B
For
example,
if
I'm
requesting
a
change,
another
viewer
is
requesting
a
change,
they
don't
overlap
and
it
means
the
same.
Pr
has
been
held
twice.
B
I,
don't
think
that
is
necessary.
I
would
suggest
we
stick
to
what
what
was
officially
documented,
such
as
slash
rgtm.
That
is
a
approval,
and
if
you
have
the
have
been
authorized,
you
can
also
put
a
slash
approved
to
approve
a
PR.
That
is
what
we
do
as
our
daily
job,
but
putting
a
requesting
change.
That
is
confusing.
I
don't
know
if
it
is
okay
to
discard
it.
B
Sometimes
the
one
who
put
that
comment
forgot.
It.
A
B
For
four
weeks,
yep
yep
10
days
20
days,
it's
not
good
for
new
contributors.
B
In
this
community
arrogant,
they
don't
welcome
new
contributions,
yeah
people
ask
questions
and
they
walk
away.
That
is
not
good
for
the
community.
So
what
I'm
suggesting
is
in
this
in
this
VR?
We
we
can
document
this.
We
encourage
people
to
use
our
GTM
and
approve,
and
not
anything
else,
so
so
Tim
left
some
common
base
and
he
asked
for
a
meeting
discussion
for
this
change
so
that
that's
the
reason
I'm
gonna
bring
this
up
on
this
meeting.
The.
A
I
know
I
know
it's
it's
very
late
for
us
in
other,
you
know
other
APAC
countries
as
well,
so
I
don't
think
it's
a
very
feasible
time.
But
it's
it's
a
good
point
actually
and
I.
Think
Sean
had
brought
this
up
earlier,
because
I
was
using
the
approved
command
on
a
lot
of
GitHub
PRS,
as
opposed
to
the
slash
approved
thing,
and
it's
one
of
the
things
that
I
also
was
confused
about.
A
So
there's
a
very
good
discussion
to
have
brought
it
up
and
honestly
speaking,
I
do
think
having
that
sort
of
segregation.
Works
in
terms
of
you
know
just
urging
reviewers
and
approvers
to
use
the
commands
that
have
been
actually
made
for
that
specific
purpose
rather
than
using
the
GitHub
command.
B
A
Than
using
the
GitHub
options,
I
completely
agree
because
it
causes
confusion.
That's
one
thing
and
I
agree
with
the
sticky
and
unnecessary
bit
as
well,
because,
like
you
said,
okay,
it's
it's
it's
a
thing
that
I've
also
noticed
and
I'm
I've
been.
You
know
responsible
for
a
lot
of
it
as
well,
wherein
you
know
I
review
a
PRN,
unfortunately,
because
of
something
on
the
other.
It
gets
on
my
backlog
and
then
you
know
there's
somebody
else
who
has
to
take
care
of
it.
A
So
I
think
both
of
these
suggestions
are
very
valid
and
it's
obviously
not
friendly
to
the
person
who's
actually
contributing
or
reviewing
the
you
know,
PR,
like
another
person,
who's
actually
reviewing
the
pr.
It's
definitely
not
friendly
for
them.
So
I'm
I'm
in
agreement
with
the
changes
to
be
honest,
I'll,
have
a
look
at
the
pr
as
well
that
you
have
taken
in
and
I'll
see.
If
there's
any
suggestion
that
I
have,
but
thank
you
so
much
for
bringing
this
up.
A
Yep
so
I'll
just
add
this
in
the
agenda:
documentation
as
well,
so
that
you
everybody
is
able,
to
you,
know,
add
their
suggestions
or
and.
A
A
Because
I
think
it's
a
very
valuable
contribution
and,
honestly
speaking,
this
is
something
that
I
was
struggling
with
as
well.
So
thank
you
so
much
for
that.
Anybody
else
have
any
other
prisf
test.
If
this
discussion
on
this
is
done,
and
if
anybody
has
no,
nobody
has
any
further
suggestions
on
this.
Is
there
anything
else
that
you
all
want
to
discuss
with
respect
to
issues
in
PRS.
A
A
Of
issues
right,
the
not
the
PRS
are
okay,
I
guess
because
now
I
think
we're
less
than
200
if
I'm
not
mistaken.
So
the
number
of
issues
that
are
being
reported-
and
you
know
the
number
of
issues
that
are
left
for
triage
by
the
leads
and
the
chairs
are
too
high-
is
that
what
you're
trying
to
say.
A
So
I
I
don't
need
to
mandate
this
or
anything,
but
do
we
want
to
open
a
discussion
on
the
sick,
talk
slack
channel
on
how
we
could
better
improve
this?
So
one
of
the.
A
Okay,
is
that
whoever
is
the
pr
Wrangler
for
the
particular
week
right
like,
for
example,
Ray
or
Natalie,
or
myself
or
whoever
it
is
they
also
sort
of
triage
to
PRS
as
they
come
in,
so
not
not
the
pr
side,
the
issues
as
they
come
in
so
having
that
triage,
accepted
or
triage,
you
know
like
asking
for
further
information
that
could
also
be
one
of
the
responsibilities
of
the
pr
Wrangler
is
what
I
was
thinking,
but
is
that
something
that
you
know
would
be
I?
A
A
A
A
Yeah,
so
what
I
was
saying
is
that
PR
Wrangler
responsibilities
could
potentially
include
triaging
issues
as
well
for
that
particular
week,
so
that
at
least
the
incoming
issues
I
understand,
there's
a
backlog
already
and
that's
something
that
we
must
work
to
address.
A
But
I
think
the
incoming
issues
are
also
sort
of
you
know
piling
up
on
the
existing
backlog
so
would
having
you
know
the
assigned
PR
Wrangler
for
a
week
triage
the
issues
help
with
you
know
this
particular
thing:
I'm
not
saying
that
it'll
completely
eliminate
whatever
problems
we
are
having.
But
do
you
think
it
would
be
a
worthwhile
responsibility
to
assign
a
PR
angler
for
this
as
well
like
it's
an
additional
responsibility,
but
do
you
think.
B
A
fix
yes
yeah.
Yes,
we
can
remind
a
Wrangler
to
pay
attention
to
the
number
of
new
issues,
but
it
might
be
too
heavy
a
job
for
the
angular
yeah
yeah.
So
so,
on
the
other
hand,
I
would
suggest
we,
as
a
community,
take
some
some
Team
Action.
A
I
mean
what
the
other
folks
in
the
channel
have
to
say.
Since
you
know
very
few
people
are
in
attendance
right
now
and
then
we
form
a
consensus,
maybe
during
the
next
in-person
meeting.
So
just
let
me
add
this
here.
A
Okay,
so
anything
else,
foreign.
A
If
there
are
no
discussion
points
at
this
point
in
time,
you
know
we'd
be
sort
of
pointing
the
call
Hereafter
so
yeah
anything
to
be
brought
up.
A
I
think
someone
in
the
chat
had
sort
of
posted.
What
is
the
best
just
a
second,
what
is
the
preferred
way
of
communication?
I
think
that
was
anurag.
What
is
the
preferred
way
of
communication
if
I
want
myself
to
get
added
as
the
Wrangler
Shadow
so
to
address
that
the
I
think
I
specified
it
earlier
on
in
the
call
as
well
that
you
need
to
reach
out
to
Brad
Topol
he's
on
slack,
you
can
directly
reach
out
to
him
via
personal
message.
A
Tell
him
that
you
know
you
want
to
be
added
as
a
PR,
Wrangler,
Shadow
and
first
I
would
urge
you
to
actually
check
the
pr
Wrangler
shifts
and
see
which
week
you
want
to
be
volunteering
as
at,
because
the
current
week,
obviously
is
not
possible.
A
Maybe
next
week
or
the
week
after
or
if
you
have
a
specific
person,
you
want
to
be
working
with
that's
also
okay,
so
you
have
to
first
check
the
shifts,
and
then
we,
which
are
to
Brad
personally,
to
get
yourself
added
and
thank
you
kimming
for
that
message
on
the
chat
or
yeah.
A
So
any
other
questions,
folks,
anything
else
that
needs
attention
from
our
side,
because,
if
not
I
would
like
to
you
know
give
your
back
time
from
your
day.
That's
that's
the
reason
I'm
asking.
A
Okay,
so
since
that's
you
know,
nothing,
that's
come
up
yet
I
think
it's
safe
to
say
that
the
salt
that
we
had
for
today
and
if
you
have
any
questions,
concerns
or
something
you
can
post
all
the
PRS
on
the
slack
Channel
or-
and
please
please
be
mindful
that
whenever
you
are
actually
sort
of
posting
your
PRS
or
issues
for
review
on
the
slack
Channel,
you
don't
tag
specific
people,
the
reason
being
everybody
works
in
different
time
zones
and
we're
trying
to
you
know
not
have
a
lot
of
work
overload,
work
overloaded
on
specific
people,
so
that
you
know
they
are
able
to
have
a
healthy
lifestyle
with
respect
to
work
life
balance.
A
So
if
you're
posting
a
PR
for
review
the
best
person
to
reach
out
to
would
be
the
pr
Wrangler
for
that.
For
that
week
you
can
directly
tag
them
on
the
pr
not
on
the
GitHub
Channel
and
ask
them
for
review,
and
once
you
know
we
will
be
getting
to
it
chronologically.
A
Once
that's
been
done
so
and
that's
that's
one
thing,
and
the
second
thing
is
also
that
I
would
request
that
if
there
is
a
specific
PR
that
you
all
have
made
amendments
to-
and
it
has
not-
you
know
seen-
changes
like
it's
not
seen
any
comments
or
reviews
from
the
Wrangler
or
the
reviewer
in
one
or
two
days.
Please
give
us
some
time
because
we're
all
doing
this
most
of
us
are
doing
this
voluntarily
and
it
is
difficult
to
juggle
a
lot
of
things.
A
So
please
be
a
little
empathetic
and
we
will
respond
to
you
if
not
within
a
couple
of
days.
We
will
respond
to
you
in
at
least
a
week's
time,
and
if
that
doesn't
happen,
please
please
feel
free
to
Ping
us
personally.
A
It's
it's
all
a
matter
of
actually
understanding
and
collaborating
with
each
other
across
time
zones.
So
we
request
that
you
know
you
all.
Do
your
due
diligence
before
reaching
out
to
different
people
and
I
know
this
has
already
been
said
in
the
previous
meeting,
but
I
just
wanted
to
reiterate
it
in
this
one
as
well
so
yeah
that
was
just
a
long
run
from
mine,
but
if
there's
nothing
else
yeah
and
yes,
this
will
be
uploaded
on
the
sick,
dog,
slack
Channel
I'm.
A
Sorry
talks,
YouTube
channel
I'm
in
the
process
of
manually
uploading
it.
So
it
will
take
a
little
bit
of
time,
but
it
will
be
uploaded
and
for
those
and
for
the
person
who
asked
how
can
I
get
this
talk,
it's
there
on
the
meeting
invite,
but
for
your
reference,
I
have
actually
pasted
it
on
sorry.
I've
actually
pasted
it
on
the
meeting
chat
as
well.
So
hopefully
that
clarifies
your
question.
A
A
Yeah,
how
what
if
one
so
I
just
got
a
message
from
anurag
asking
me
I,
think
it
should
be
posted
in
public.
What
if
one
PR
requires
intervention
from
other
six,
how
to
reach
out
to
them
and
ask
in
a
better
way
any
suggestion
on
this.
The
best
way
to
do
this
would
be
to
tag
their
reviewer
and
approval
Team.
So
there
are
specific
teams
within
each
Sig
for
reviewing
and
approving
PRS.
Now,
that's
one
way
of
doing
it.
A
You
can
directly
tag
them
on
the
GitHub
issue
or
GitHub
PR.
Sorry,
and
if
not
the
case,
you
can,
if
they've
not
responded
for
a
really
long
time-
and
this
has
happened
with
a
couple
of
signaled
reviews
for
me
personally-
so
I
have
directly
posted
the
GitHub
PRS
on
their
slack
channel
the
list
of
GitHub
PR's
on
their
slack
Channel
and
requested
them
for
review,
because
it
I
know
that
you
know
the
other.
Six
could
possibly
miss
this
out,
given
the
number
of
PRS
that
everybody
has
to
review
and
approve.
A
So
the
first
step
would
be
to
tag
their
reviewing
and
approving
team
on
the
pr,
if
not
directly,
directly
go
and
list
the
PR,
but
also
please
be
mindful
that
when
you
do
the
when
you
do
this,
a
sufficient
amount
of
time
needs
to
have
passed.
A
It's
not
like.
If
you
don't
receive
a
response
within
two
days.
You
you
directly
start
listing
the
PRS
on
the
GitHub
channel.
It
at
least
like
I,
said
wait
for
a
week
and
if
there's
no
response,
then
try
reaching
out
did
that
answer.
Your
question.
A
A
Pr,
like
I,
also
said
we
will
be
having
PR
we'll
be
having
someone
check
this
out
and
see
what
needs
to
be
done
further
and
how
we
can
better
ensure
that
issues
are
trashed.
So
that's
one
thing
that
is
on
my
agenda,
but
I
will
check
the
issue
personally
as
well
and
see
what
can
be
done.
A
A
Okay,
so
since
there's
nothing
else,
I
think
we
can
call
it
a
day
and
see
you
on
slack
folks
stay
safe
and
thank
you
for
all
your
contributions,
as
always
bye,
foreign.