►
From YouTube: Kubernetes SIG Docs monthly APAC meeting 20200728
Description
For more info see https://git.k8s.io/community/sig-docs
A
A
B
Who
should
we
should
start?
First,
should
I
should
I
start
first?
Yes,
please,
okay,
please,
to
meet
you
guys.
My
name
is
ipe
suzuki.
I
represent
a
japanese
company
called
creation
line
and
we've
been
a
cncf
silver
member
for
quite
a
while.
Currently
the
first
japanese
companies
to
become
one
and
we've
been
very
keen
in
open
source
software
for
quite
a
while
and
kubernetes
is
definitely
the
one
that
we're
riding
on
the
wave
and
we
have
our
business
is
to
provide
solutions
to
customers
in
japan.
C
Yeah,
everyone
very
pleased
to
meet
you.
My
name
is
giri.
I'm
currently
based
in
jakarta
indonesia
for
past
two
years,
working
for
a
company
called
gojek,
a
startup
in
southeast
asia.
Basically,
you
start
as
a
retailing
company
we
expanded
to
other
countries
as
well.
Nowadays
we
we
became
a
financial
technology
companies
pretty
much.
If
you,
if
you
come
around
in
southeast
asia,
you
can
you
can
see
us.
C
C
I
used
to
live
there
for
eight
years
before
I
I
came
back
home
here
in
indonesia
and
because
of
the
recent
progression
with
the
tech
community
in
indonesia,
I
started
to
start
coop
native
and
kubernetes
communities
in
indonesia
and
started
doing
this
localization
project
as
well,
because
not
everyone
knows
english.
Obviously,
here
and
I've
been
pretty
happy
seeing
the
attraction
in
the
community
as
well
trying
to
help
out
and
getting
them
engaged
the
best.
C
D
So
that's
why
I
joined
the
what
you
see
like
the
seattle
secretary
in
the
early
of
this
year,
and
then
I
tried
to
have
some
contributions
for
the
translations
or
localization
yeah,
so
my
background.
Actually
I'm
not
what
they
say.
I'm
not
a
pure
software
engineer.
Basically
before
I
work
as
a
network
engineers,
and
currently
I
also
serve
as
a
open
networking
foundation
ambassador.
D
So
mostly
I
mean
my
my
my
field
is
about
the
network,
but
now
I
little
bit
expand
my
specialty
into
like
native
area,
so
it
has
been
very
nice
what
they
say:
engagement
with
the
all
the
communities,
including
in
indonesia
or
in
some
others
event.
I
also
met
some
another
people,
so
I
hope
that
it
can
be
a
part
of
what
they
say
collaborations
between
the
networking
part
and
also
the
part
yeah.
I
think
she's
enough
yeah.
A
A
So,
let's
move
on
to
the
updates
and
reminders
and
the
other
piece
I'll
add
too.
It
sounds
like
the
people
involved
in
this
call
might
be
relatively
new
if
there's
anything
that
I'm
explaining
that
doesn't
make
sense
or
you're
like
hey.
What
is
that
you
know
buzz
word
that
you're
saying
or
that
specific
attribute
for
docs
that
you're
talking
about
feel
free
to
interrupt
me.
That's
just
the
four
of
us
happy
to
have
this
be
a
little
bit
more
of
an
informal
meeting.
If
you
would
like.
A
So,
moving
on
to
the
updates
and
reminders,
this
week's
pr
wrangler
is
myself
and
next
week
is
karen
bradshaw,
rkb
hockey
on
github
and
if
you're
an
approver
make
sure
you
know
your
scheduled
pr
wrangler
shifts,
and
there
is
a
link
in
the
agenda
which
I
will
also
send
in
the
chat
here.
If
you
don't
have
it.
C
A
Yeah,
so
there
is
the
idea
in
the
kubernetes
community
of
aging
out
certain.
Actually,
I
don't
think
it
happens
for
pr's.
I
was
thinking,
that's
more
of
issues,
but
to
answer
your
initial
question,
we
take
week-long
shift
schedules
that
we
change
with
the
different
approvers,
where
that
entire
week
the
approver
is
responsible
for
going
in
reviewing
pull
requests
and
taking
care
of
some
of
the
some
of
its
housekeeping.
Some
of
it's
seeing
the
status
of
the
pull
request.
A
There
is
an
actual,
very
good
overview
of
what
a
pr
wrangler
does
on
the
kubernetes
website
and
I'll
send
a
link
in
the
chat
here
as
well,
but
ultimately,
at
least
I'll
speak
for
myself
here
as
a
pr
wrangler
this
week.
What
I'll
end
up
doing
is
go
through
and
see
if
there
are
pr's
that
are
open,
where
someone
has
not
signed
the
cla.
A
What
that
is
the
contributor
license
agreement,
which
is
required
by
every
pull
request
and
then
I'll
start
to
work.
My
way
up
from
there
and
some
of
these
links
and
searches
are
actually
in
the
website
that
I
sent
or
the
the
link
that
I
sent
then
I'll
kind
of
work.
My
way
through,
as
far
as
what
prs
need
a
lgtm
or
it
looks
good
to
me,
tag,
I'm
not
sure
how
familiar
you
are
with
the
overall
workflow
of
the
kubernetes
project.
But
almost
everything
is
done
by
a
robot
and
and
github
comments.
A
So,
ultimately,
we'll
work
through
various
size.
Pr,
so
another
approach
that
I'll
take
as
well
is
I'll
start
with
the
smallest
prs
that
are
very
easy
to
review,
especially
when
it
comes
to
documentation
and
slowly
work.
My
way
up
to
larger
prs,
occasionally
the
pr
wrangler
is
not
just
approving
prs
for
the
sake
of
moving
the
pull
request
number
to
be
a
lower
number,
sometimes
you're
saying
this
pr
has
been
open
for
30
days
with
no
activity.
Let's
either
move
it
forward
or
make
an
agreement
to
close
it.
C
One
of
the
interesting
cases
that
we
found
out
in
our
community
is
that
a
lot
of
people
are
new
to
contributing
to
open
source.
There
is
pull
requests,
they
have
localized
the
full
full
page.
We
gave
them
comments,
but
they
didn't
address
them
so
after
like
a
month
or
so,
it's
it's
kind
of
sad.
If
we
throw
the
pier
away
right
so
what
we
ended
up
doing,
we
we
take
those
prs
and
then
we
we
raise
the
pr
with
with
this
faults
as
a
co-author
yeah.
A
Wrangling
might
close
this
issue,
unfortunately,
but
I
definitely
agree
too,
especially
when
we're
talking
localization
there
might
be
less
pull
requests
being
opened
up.
Maybe
that's
valuable
contribution,
not
that
not
the
ones
that
get
close
are
not
valuable,
but
there's
a
lot
more
contributors
to
the
english
documentation
than
there
are
for
the
localization.
So
it
makes
sense
to
me
why
you'd
want
to
keep
that
and
potentially
have
another
contributor
provide
that
full
request.
Absolutely.
A
Yeah,
so
I
don't
know
if
there's
a
necessarily
a
rule
of
thumb,
I
end
up
when
I'm
reviewing
pull
requests.
I
would
say
a
month
is
about
a
solid
timeline
to
give
somebody
to
either
respond
to
comments
make
changes.
It
really
depends
on
the
overall
contribution
the
size
of
it.
Who's
been
engaged
on
it.
How
many
reviews,
if
a
pr
has
never
been
reviewed
and
everything
else,
is
fine?
It's
not
fair
for
saying
nobody
reviewed
this,
we're
closing
it
because
there's
no
action
in
30
days
but
yeah.
A
A
A
Cool
awesome
sounds
great,
so
moving
on
to
release
updates,
so
the
release
team
has
been
doing
a
really
great
job
for
the
kubernetes
191.19
release,
they're
responsible
for
collecting
all
the
documentation
for
the
new
features
or
enhancements
in
the
119
kubernetes
release
and
cevita
has
done
a
great
job
at
making
sure
all
the
pr's
have
been
merged,
as
well
as
the
rest
of
the
sig
docs
team
and
right
now
the
status
is
green.
There's
no
merge
conflicts.
A
A
So
I'm
going
to
skip
over
these
next
two
bullet
items.
We
don't
have
a
korean
localization
update,
which
normally
junior
would
provide.
We
also
don't
have
any
updates
from
the
blog.
As
far
as
I've
seen
from
some
of
the
poll
requests
that
I
have
performed
or
reviewed,
the
blog
looks
like
it's
healthy,
it's
active
things
are
moving
well
in
that
area.
A
A
We
like
to
stay
around
100
open,
pull
requests
with
some
of
the
different
localizations
and
onboardings.
We
started
to
grow
a
little
bit
on
the.
I
was
a
mid
to
higher
side,
so
we're
more
like
125
150
is
a
healthy
spot
to
be,
and
then
I
would
say
about
a
month
or
two
ago
we
were
getting
upwards
of
around
200
open,
pull
requests
as
far
as
being
that
kind
of
running
total,
so
we're
in
a
very
healthy
spot.
Right
now,
in
my.
A
A
There's
been
a
lot
of
work
being
done
there
to
containerize
it
to
solve
some
issues.
There's
been
problems
with
building
too
many
open
files
and
there's
kind
of
multiple
streams
of
work
going
on
here.
So
the
first
stream
is
there's
too
many
files
that
get
generated.
When
you
run
hugo,
build
on
the
current
kubernetes
documentation
or
on
the
kubernetes
website,
the
too
many
files
open
is
trying
we're
trying
to
resolve
that
by
using
a
container
that
has
hugo
in
it
to
then
not
use
your
open
files
on
your
mac
or
the
number
of
open
files.
A
So
instead
of
the
instructions
saying
go
to
the
kubernetes
website,
repository
build
a
docker
image
run
that
docker
image.
You
could
ultimately
just
do
a
docker
poll,
for
example,
so
really
just
trying
to
streamline
the
contribution
aspect
of
documentation
and
really
dealing
with
some
of
the
challenges
that
were
introduced.
When
we
added
a
new
theme
to
our
docs,
which
added
a
lot
of
more
of
additional
files.
A
C
Yeah
for
me,
especially
the
the
new
release
right
once
119
kubernetes
for
us
localization
team.
So
far
we
have
translated
around
much
largest
pages.
If
I'm
not
mistaken,
and
most
of
the
pages
we
we
localize
from
from
the
english
page,
so
completely
new
pages
for
us,
which
is
easy
right.
The
challenge
comes
when
those
pages
get
updated
like
in
this
case
in
release
119,
we
don't
really
have
a
tracker
which
pages
we
have
to
update
and
then
for
us.
C
C
A
A
The
release
119
in
the
future
release
work
is
a
little
bit
easier
of
a
problem
to
solve.
I
guess
the
first
thing
is:
is
that
all
the
enhancements
that
are
going
into
the
release?
So
all
the
enhancements
that
are
going
into
119
are
attracted
by
the
documentation
team
and
there
might
be
some
sort
of
collaboration
that
can
be
done
there
to
say
what
enhancements
and
documentation
are
coming
in.
A
But
it
is
an
interesting
challenge
if
you
have
documents
that
you've
already
localized
and
then
they've
been
updated
in
english.
How
do
you
get
those
changes
back
to
the
localized
documents
and
and
that
I
don't
have
a
great
answer
for
it?
I
would
love
to
bring
this
up
at
the
at
the
tuesday
weekly
meeting
and
maybe
get
more
additional
suggestions
on
that.
C
A
Yeah,
I
don't
want
to
misspeak
here,
but
I
do
believe
there
are
some
additional
scripting
tools
and
utilities
that
the
korean
localization
team
might
use,
and
I
want
to
say
that
they're
tracking,
I
thought
it
was
just
the
different
branches,
but
it's
possible
they're
tracking
documents
that
have
changed.
So
that's
a
great
great
point,
too,
is
potentially
talking
with
joon
yi
from
the
korean
localization
team
or
if
you
haven't
joined
there
is
all
the
different
localization
slack
channels.
A
Yeah,
I
would
be
really
interested
in
hearing
how
other
teams
are
solving
this.
It's
definitely
not
a
unique
problem.
It's
a
problem
that
I
haven't
personally
considered,
but
I
mean
every
every
localization
team
is
going
to
face
this
and
keeping
up
with
this-
and
maybe
there's
already
an
answer,
I'm
just
not
aware
of
so.
Let's
make
sure
we
get
that
figured
out.
B
A
Yeah,
absolutely
and
and
once
again-
and
I
I
hate
to
keep
deferring
everybody
to
the
different
localization
slack
channels,
but
you're
going
to
get
the
most
answers
in
the
japanese
docs
channel.
Okay,
and
do
you
have
the
url
for
the
slack
too?
I
don't
know
if
everyone's
active
on
the
slack,
if
you
can
post
it
over
to
me
I'll.
A
A
A
B
Okay,
yes,
and
just
to
update
you
well,
we've
been,
we've
been
actually
localizing,
all
the
training
material
for
kubernetes
as
of
an
atp,
and
we
just
returned
all
that
resources
back
to
the
linux
foundation
and
the
terminology
that
we
have
in
there
would
be
good
to
have
all
synchronized
with
what's
going
on
in
in
in
this
localization
team.
So
that's
a
contribution
that
I'll
be
more
than
happy
to
do.
A
A
C
Cool
hear
nothing
one
more
thing:
you
got
it
any
any
suggestion
on
when,
when
when
do
we
supposed
to
promote
contributors
as
in
when
there
are
new
contributors,
the
contributors
have
been
contributing
a
lot.
When
is
the
right
time
to
promote
them
to
become
a
kubernetes,
org
member
and
then
from
there?
When
are
we
supposed
to
promote
them
again
to
reviewers
and
then
eventually,
approvers
and
owners?
Is
there
are
recommended
practices
there
like?
Like
so
far,
we've
been
gathering
consensus
on
this
and
we
get
confused.
C
We
we
at
first
we
we
come
up
with
some
sort
of
threshold
like
when
someone
already
raised
10
pr,
for
example,
they
can
get
promoted
and
things
like
that.
But
recently,
since
the
number
of
contributors
keep
growing
the
threshold
scene,
don't
make
sense
anymore,
and
I
don't
know,
and
maybe
yeah
our
team
also
grows.
Bigger
seems
that
approach
doesn't
make
sense
anymore.
A
Yeah
absolutely-
and
this
is
a
great
problem
to
have
you
know-
we
have
too
many
people
that
want
to
help
you're
in
a
good
spot.
There
there's
a
little
bit
of
a
gray
area
or
a
blur
between
the
privileges
and
responsibilities
when
you're
talking
about
localization,
mainly
because
when
a
localization
starts
the
very
first
people
who
contribute
to
a
localization
need
to
be
org
members.
They
need
to
have
some
of
these
different
higher
level
permissions.
A
Now,
with
that,
I
did
send
a
link
in
the
chat
and
I
put
a
link
in
the
agenda.
There
are
some
general
community
guidelines
that
are
followed
for
promotion
within
you
know
when
to
join
the
org,
there's
a
certain
set
of
criteria
how
to
join
the
org,
as
well
as
becoming
a
reviewer
some
of
the
responsibilities
there,
as
well
as
an
approver.
A
So
it's
a
little
bit
of
a
judgment
call
as
well
as
some
of
the
criteria
that
previously
exists.
Ultimately,
you
want
to
make
sure
that
the
people
you're
promoting
to
a
higher
level
of
trust,
understand
the
responsibilities
of
their
new
role.
What
is
expected
of
them
and
if
they've
been
active,
reviewing
tons
of
pull
requests
and
they've
been
very
active
in
the
localization
efforts
and
they
meet
the
criteria
to
be
an
approver.
A
And,
like
I
said
it's
a
little
bit
of
a
gray
area
when
it
comes
to
localization,
mainly
due
to
the
first
few
contributors
to
a
localization,
there's
a
kind
of
an
expedited
on-ramp
to
kubernetes
or
membership
as
well.
As
you
know,
approver
status
or
a
viewer
status
once
we're
talking
about
teams
that
are
expanding.
A
A
A
However,
we
can't
have
you
be
enacted
for
approver
and
not
not
contributing
okay,
make
sense,
and
I
think
that's
the
important
thing
there
is.
It's
not
a
you
know,
shame
on
shame
on
you
for
not
contributing
it's
people,
especially
now
with
how
strange
the
world
is,
and
everything
going
on
people
have
life
situations.