►
From YouTube: SIG Docs monthly localization meeting for 20201005
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
Hi
everyone-
this
is
the
kickoff
meeting
for
the
kubernetes
sig
docs
localization
subgroup
today
is
monday
october
5th
2020.
and
please
follow
all
cncf
code
of
conduct
guidelines
and
treat
each
other
right.
B
And
at
this
point
I
am
going
to
share
my
screen
here
we
go
here,
we
go,
and
so
hopefully
everyone
can
can
see
the
the
agenda.
A
Here
and
I
thought
we
could
just
start
by
introducing
ourselves
and
what
we
do
I'll
go.
First,
I'm
brad
topple,
I'm
a
a
a
cube,
sigdocs
maintainer
and
I
also
lead
a
lot
of
the
the
kubernetes
and
cloud
native
contributions
for
ibm
and
I've
volunteered
to
to
lead
this
new
subgroup,
and
so,
let's,
let's
go
and
introduce
and
meet
everyone
else.
So
I
guess
I'll
just
go
through
the
way
the
list
is
so
is
it
sioko
want
to
go
off.
B
C
Yes,
my
name
is
sokko
soko
okay,
yeah,
I'm
from
korea,
and
actually
I'm
I'm
leader
of
korean
localization
team
in
qualities
website,
and
I
I
work
for
actually
at
least
institute
research
institute
in
south
korea
and
it
is
government
organization
organization,
but
I
contribute
kubernetes
per
pun,
fantastic
yeah.
That's
so.
B
Thank
you,
okay,
excellent
and
we'll
go
next
to
irvy.
D
D
Okay,
so
let
me
prepare
myself
so
my
name
is
erv:
I'm
a
co-chairs
in
sick
dogs.
D
I've
been
continuing
in
to
mate
for
about
one
years
or
so
and
they're
live
I'm
a
software
engineer.
Yeah
nice.
B
A
A
Yep
and
let's
thank
you,
let's
go
to
savita.
D
Hi
everyone,
my
name,
is
avita.
I
contribute
to
sick
dogs,
siege
and
sick
country
bikes.
I've
been
doing
that
for
over
an
year
and
a
half
I
should
say,
and
it's
been
a
wonderful
experience
and
I
want
to
help
work
more
wherever
I
can,
and
during
the
day
I
work
as
a
platform
engineer
at
the
math
works,
so
it's
safe
to
say
that
I'm
living
and
breathing
kubernetes
throughout
the
day.
B
A
Excellent
welcome:
let's
go
to.
E
Masahiro
hi
I'm
masahiro
from
japan
and
founder
of
talks,
japanese
working
at
lying
corporation
and
contributing
for
my
farm.
Thank
you.
F
Hello,
my
name
is
I
work
at
red
hat
as
siri,
and
I
am
working
with
the
spanish
team
for
the
localization,
so
I've
been
working
for
about
more
than
a
year
and
a
half
or
so-
and
it's
nice
to
have
other
folks
from
other,
like
communities
to
be
able
to
put
in
common
the
what
we
learned
and
why,
how
we
are
working
and
and
let's
see
how
we
can
improve
the
the
contributors
number,
because
that's
probably
the
the
main
problem
that
we
have
as
as
location
teams,
because
it's
hard
to
get
people
involved
and
it's
harder
now
with
all
these
restrictions
and
limitations.
A
Fantastic
excellent,
thank
you
and
is
it
jiri.
G
Hi
everyone
very
nice
to
meet
you.
My
name
is
giri,
I'm
currently
based
in
jakarta
indonesia.
I
work
for
a
company
called
gojek.
We
used
to
be
a
startup.
Now
I
don't
think
it's
a
startup
anymore.
I
started
contributing
to
kubernetes.
G
I
think
in
2017
iris
prs
couple
of
various
things
and
then
I
started
this
localization
for
indonesia
since
about
one
and
a
half
year
ago,
with
irvi.
Actually
she
moved
country
recently
yeah.
This
is
a
very
great
initiative.
I
can
learn
a
lot
from
other
localization
team
folks,
I'm
also
a
cnc
ambassador.
G
Actually,
bread
we've
met
in
in
shanghai
if
it's
not
last
year,
maybe
last
last
year.
A
Okay,
so
I've
gotten
all
the
names
on
the
participant
list.
Is
there
anyone
I've
missed
or
that's
all
of
us
right
and
so
as
a
top
thing
on
the
agenda?
I'd
like
to
say
welcome.
Thank
you
all
for
participating
in
this
subgroup.
A
A
And
again,
if
you
look
at
the
mission
statement,
a
mission
of
sig
docs
localization
subgroup
is
to
work
across
the
sigdoc
localization
teams
to
collaborate
on
defining
and
documenting
the
processes
for
creating
localization
contribution
guides
and
also
worry
about
looking
for
opportunities
for,
if
need
be,
the
sharing
and
creating
of
common
tools
so
that
we
can
share
from
each
other
and
also
to
serve
as
an
opportunity
to
feedback
new
requirements
to
the
signoc
leadership
team.
A
So
so
this
is
a
a
great
place
to
to
worry
about
those
types
of
topics,
and
let
me
pause:
did
we
have
someone
join?
Was
it
kohai
koha?
Did
you
get
to
introduce
yourself.
A
So
so
that's
the
way
we
think
of
it.
We've
had
so
much
growth,
so
much
growth
in
all
the
localizations,
and
so
many
teams
working
on
localizations
that
that
it
seemed
to
make
sense
that
that
we
should
get
together
and
right
now.
I
guess
we're
scheduled
to
get
together
once
a
month
and
we
have
a
slack
channel.
A
So
we
have
a
mailing
list
and
a
slack
channel,
and
I
guess,
if
there's
a
need,
we
can
meet
more
than
once
a
month,
but
the
idea
is
to
get
us
together
and
to
be
able
to
keep
track
of
the
issues
that
are
affecting
all
your
teams
and
make
sure
we're
able
to
amplify
your
voice
on
on
what
can
be
done
to
reduce
friction.
What
can
be
done
to
help
the
teams,
all
the
localization
teams?
A
If
there's
a
way
to
do
you,
know
common
docks
and
and
and
and
make
sure
that
we
all
are
doing
things
in
a
way
that
that
makes
it
easy
to
find
the
localization
docks.
We
can
work
on
that.
We
can
work
on
like
I
said:
if
there's
a
sharing
of
ideas
sharing
of
tools,
we
we
have
that
opportunity
here
and
then,
if
we
have,
you
know
really
tough.
You
know
requirements
that
we
need
to
to
bring
forward
to
the
signoc
leadership
team.
A
We
can,
you
know,
discuss
them
here
and
then
bring
them
forward
as
a
group
and
say:
hey.
We've,
we've
worked
with
across
all
the
localization
teams,
and
this
is
this
is
really
important
to
us
right.
This
is
what
we
really
need,
so
this
is
just
a
great
opportunity
for
us
to
get
together
and
do
these
types
of
things
just
real,
quick
on
logistics.
A
I
pretty
much
got
everything
set
up.
We
got
the
mailing
list,
we
got
the
the
google
group
created,
we've
got
the
slot
channel,
we
got
you
know
the
zoom
account.
I
think
all
I
I've
got
to
update.
The
last
thing
I
need
to
do
is
just
update
the
docs
to
advertise
the
meeting,
just
the
community
doc
and
the
the
the
the
actual
sig
docs
themselves.
So
I'll
do
that
soon
and
turns
out.
A
We
already
have
two
calendars,
so
one
for
the
asian
pacific
meeting,
one
for
the
regular
sig
docs
meeting-
and
I
didn't
want
to
add
a
third
calendar
for
this,
so
we're
working
on
work
with
the
sig
chairs
to
actually
get
us
on
a
calendar
that
already
exists
instead
of
creating
a
whole
new
calendar
for
one
meeting.
A
So
we
want
to
do
that
and
let
me
pause
back
so,
let's
see
who
is
on
that,
we
missed
that
can
do
a
quick
introduction
for
themselves.
Kohei.
Were
you
able
to
get
off
mute.
H
Do
you
hear
me
I
can
now
yeah?
Oh
thank
you.
Thank
you.
Sorry.
I
was
I've
been
setting
up
my
mic
because
I
just
finished
cka
the
exam
which
went
pretty
good,
oh
good,
so
I
had
I
had
to
remove
my
microphone
from.
H
So
yeah,
hello,
everyone,
I'm
kohei
and
I'm
from
japan-
and
I
I
take
a
lead
one
of
the
leads
actually
another
one.
The
other
lead
masahiro
is
here
too
yeah,
I'm
a
japanese
localization
owner
just
with
him
nice
to
meet
you
guys.
A
Fantastic
and
then
it
looks
like
felipe,
was
able
to
join
philippe
if
you'd
like
to
do
just
a
short
intro,
we're
just
kind
of
getting.
J
A
Okay,
fantastic
good
enough,
and
so
hopefully
everybody
heard
the
the
basic
mission
statement
and
the
goals
again.
This
is
a
great
opportunity
for
us
to
work
together
if
there's
places
where
we
can
collaborate
on
common
docs
great,
if
there's
places
where
we
need
to
to
make
our
voice
louder
to
say,
hey.
This
is
our
top
requirement.
We
get
to
do
that.
A
This
is
just
a
way
for
all
of
us,
across
the
different
localization
teams,
to
stay,
organized
and
and
and
and
and
and
talk
about,
the
issues
that
affect
the
localization
teams.
So
the
the
first
thing
that
was
added
to
the
actual
agenda
and
I'll
take
notes
is
kohei.
He
says
he
wanted
to
share
japanese
localization
milestones
and
guidelines.
H
H
But
beforehand
I
would
like
to
sh
prepare.
H
H
I
don't
know
like
pretty
much
like
10
languages
right
now,
and
I
I
think,
like
from
chinese
to
korean
and
japanese,
like
active
localization
teams
to
a
relatively
new
localization
team,
such
as
ukrainian
or
I
know,
for
example,
what
else
polsky,
which
should
be
polish,
I
think
so
like
there
are
many
like
different
languages
and
they
they
all
by
run
by
different
teams
right.
So
actually
one
of
the
person
who
proposed
to
create
this
localization
team.
So
thank
you
everyone
to
joining
this
so
fir.
H
First,
I
wanted
to
share
a
brief
activity
report
about
our
localization
team
for
japanese
people,
but
basically,
basically,
I
I
learned
a
lot
of
things
from
the
korean
localization
team,
so
I
would
also
like
the
korean
team
to
provide
some
information
about
localization
too,
but
I
just
wanted
to
be.
You
know
first
to
provide
some
information
because
I
I
was
basically
the
first
one
who
raised
the
up
this
this
yeah
matter.
So
yeah
anyway,
now.
H
So
I
believe
this
webpage
is
the
very
first
place.
You
would
look
when
you
start
localization.
This
is
docs,
contribute
slash,
localization
right.
So
this
is.
This
basically
describes
how
how
you
start
localization
for
your
language
as
a
new
project
right,
but
it
doesn't
describe
how
how
you
manage
it.
H
So
this
this
is
the
most
difficult
part
when
it
comes
to
you
know:
managing
localization,
just
like
kubernetes.
It's
it's
really
easy
to
build
up
kubernetes,
but
it's
really
difficult
to
manage
it
right.
So
I
actually
we
actually
changed
the
the
structure
of
this
page
completely
from
like
describing
how
to
create
a
new
locality
project
to
how
to
localize
in
in
my
language,
japanese.
H
So,
let's
see
so
this
is
japanese.
So
I
would
just
google
translate
into
english.
A
This
is
the
version
of
the
page
that
you
all
wrote
specifically
in
japanese.
I
guess
for
the
japanese
team,
correct.
H
So
this
is
already
different,
so
we
we
basically
started
how
to
describing
how
the
workflow
works
in
the
translation,
so
flow
of,
translating
documenting,
japanese,
so
yeah.
This
is
the
basic
knowledge
you
should
know.
Everything
is
tracked
in
github
issue
and
the
cla
must
be
signed
and
the
english
documentation
is
really
good,
but
we
also
have
this.
Like
japanese
summary,
we
didn't.
I
buy
a
ramp
here
yeah.
This
is
in
japanese
so
that
the
language
barrier
will
be
free.
H
For
you
know,
japanese
people
yeah,
and
also
we
have
slack
team
describing
the
cuban
docs
jj
channel,
is
for
the
japanese
localization
and
before
you
start
translating
you
should
create
an
issue
or
search
look
for
an
issue
for
a
page.
You
want
to
translate
and
yeah
again.
If
there's
any
questions,
please
raise
a
question
on
slack
this.
I
think
this.
H
This
kind
of
thing
is
really
important,
because
when
you
have
a
problem
and
where
you
don't
you
don't
know
where
to
share
it's,
it's
really
difficult
and
this
will
be
a
really
bad
contributing
experience.
So
yeah,
please
do
not
hesitate
to
ask
the
question
yep
so
yeah.
This
is
like
before
you
translate
or
contribute
make
up
a
request
and
actually
yeah.
This
is
better
so
for
the
repository
first
then
master,
which
maybe
will
be
main
at
some
point
yeah.
So
the
directory
structure
is,
you
know,
content
and
the
language
name.
H
So
we
have
different
flows
where
there's
no
translations
so
far,
oh
and
there's
actually
an
existing
translation,
but
you
want
to
update
it
so
for
a
new
page
and
an
existing
page,
we
have
different
milestones,
because
if
you
want
to
translate
a
new
page,
you
can
just
create
the
translation
from
the
the
latest
right.
H
So
that's
fine,
but
when
it
comes
to
editing
the
existing
ones,
it
is
really
difficult
to
for
the
localization
managers
to
track
on
which
version
is
like
up
on
on
which
page
is
up
to
date
right,
so
we
we
basically
create.
B
H
So
here
we
have
like
update,
update,
update
and
make
blah
blah
follow
version
1.18
right,
so
they
also
have
like
milestones.
Although
oh,
this
is
pub
requests,
but.
A
H
Yes,
so
yeah,
we
we
keep
in
truck
using
the
git
commands,
but
we
want
to
make
it
easier,
so
any
proposals
will
come
actually
yeah,
but
anyway
we
have
this
milestone.
H
1.18.J8.1
then
yeah,
based
on
the
in
in
the
issue.
We
also
have
the
diffs
between
translating
on
version
1
the
18.
It's
like.
We
have
this
kind
of
thing.
You
know
this
has
a
huge
diffs
yeah,
but
yeah.
Basically,
there
can
be
from
you
know,
just
tiny
wording,
differences
to
complete
like
different
structures
like
this
yep,
so
they
can
assign
themselves
when
they
want
to
contribute
to
the
new
issue.
Then
just
they
make
the
progress
based
on
the
difference,
then
we
review
the
difference.
H
Can
we
comment,
I
think
this
this
photo
is
the
same
for
everyone,
but
yeah,
and
also
we
have
like
frequent
useless
used
words
like
translation
tables,
so
that
they
they
won't
be
overwhelmed
for
some
like
frequently
used
translation
words.
H
A
H
H
Yeah,
we
just
don't
try
to
make
so
much
effort
on
just
this
glossary,
because
it
will
be
a
really
hard
work.
So
only
when
we
have
problems
like
I
wonder
which
to
which
then
we
discuss
then
decide
it,
then
we
apply
the
updates
here.
C
A
C
Thank
you
yeah.
In
case
of
a
korean
localization
team,
we
managed
to
look
glossary
for
localization
for
korean
in
similar
way
with
kawaii's
team
and
we
actually
having
high
weekly
meetings
for
localization
teams,
protocolization
team
and
we
decide
the
localization
way
for
the
exclusivity,
and
we
are
actually
very
actively
managing
that
grocery.
C
Previously,
we
managed
in
google
google
docs
google
excel
spreadsheet
so
that
you
can
easily
change,
but
we
determined
to
upload
it
to
kubernetes
official
website.
Since
we
can
get,
we
can
put
the
license
to
share
creative
license
pro,
so
those
groceries
actually
in
utilized
by
other
koreans
to
translate
other
qualities
related
books
as
well.
So.
C
C
C
Yeah,
as
you
know,
if
we
publish
the
glossary
part
to
public
through
competency's
website,
then
it
means
we
provide
the
creative
for
license.
Then
other
other
teams
or
other
related
engineers
can
utilize
our
groceries.
Oh
creative.
C
I
H
They
they
said
they
pretty
previously
managed
it
the
table
with
spreadsheet,
but
it
doesn't
have
any
license.
So
they
don't.
You
know,
say
what
kind
of
copyright
they
should
you
know
have,
but
in
just
writing
on
the
kubernetes
website,
you
can
just
make
use
of
the
official
license,
because.
H
A
H
Yeah-
and
we
also
have
like
japanese
language,
specific
issues
too,
like,
for
example,
a
bracket-
and
you
know
dot
period
and
also
like
kama
or
the
japanese
kama
yeah,
and
we
also
have
this
long
ball.
So
it's
like,
for
example,
a
server
server
in
japanese
is
saba,
but
it
can
be
either
the
shop
short
one
and
the
longer
one
saba
versus
saba,
and
this
alone
this
letter
specifies
you
have
to
put
the
longbow
over
here
so
because
it
can
be
written
in
either
in
the
technical
documentation.
H
Yeah
so
yeah,
we
also
don't
forget
about
the
upstream
contribution
to
english
documentation,
because
sometimes
sometimes
they
make
pull
requests
to
japanese
localization,
but
the
the
the
mistake
can
cause
can
be
caused
by
the
english
one.
They
just
we
just
translate
it,
but
the
english
one
was
wrong.
So
you
know,
in
that
case
we
have
to
contribute
both
the
japanese
one
and
the
english
one
so
yeah.
We
also
recommend
to
commit
to
the
upstream
as
well
in
english,
yep.
That's
that's
what
we
do
in
the
localization
documentation.
A
C
Okay
for
queer
location
team,
it
is
very
good
thing.
Some
team
can
repair
our
way
and
actually
we
so
we
are
doing
very
similar
way
with
japanese
localization
team
and
we
have
a
similar
page
that
coe
just
introduced
it,
but
a
little
bit.
There
are
some
different
things,
so
maybe
we
can
share
later
not
this.
G
C
Right
yeah,
so
actually
we
are
following
the
branching
strategy.
C
There
is
guideline
localization,
localizing,
kubernetes,
documentation
guideline.
There
is
part
section
for
branching
strategy.
We
make
the
web
branch
for
localization
and
we
keep
making
milestones
and
check
the
outdated
contents
from
the
english
upstream
site.
Then
we
apply
it
to
korean
dev
branch
so
that
we
can
keep
sync
with
the
english
updated
content.
C
A
Okay,
so
so
let
me
understand
you
you're
working
on
a
document
that
talks
about
how
you
do
your
branching
strategy
and
how
you
do
your
milestone
strategy,
and
so
when
the
document
is
ready,
you
you
will
you
will
for
one
of
our
upcoming
meetings.
I
guess
you'll
you'll
want
to
talk
through
it
more
is
that
the
idea.
A
Okay,
that
sounds
excellent,
so
we
look
forward
to
that
and
and
then,
when
you're
done
with
that
document,
are
you
gonna
link
it
into
your
localization
page?
I
guess
for
korean
so
similar
to
how
soque
did
his
right
is.
That
is
that,
where
it's
going
to
show
up
in
the
docks,
when
it's
done
where,
where
where,
where
you
put
it,
when
it's
done.
A
C
J
C
Yeah
sure
we
already
our
own
page-
and
it
is
very
similar
with
corey
just
mentioned
so
actually
we
can
share
the
document,
but
I
would
like
to
introduce
to
our
localization
subgroup
how
korean
team
works.
The
document
itself
is
very
detailed,
but
I
hope
to
introduce
it
somehow
simple
way
comprehensively.
H
C
No
problem:
we
are
actually
preparing
presentation,
material.
A
But
I
think
he's
just
saying
the
document
is
under
preparation
right.
D
H
So
I
have
a
question:
how
frequently
do
you
want
to
hold
this
meeting
like
if,
like
at
one
month
like
once
a
month
or
every
two
weeks
or.
A
So
it's
really
up
to
the
team
here
right:
it's
it's!
How
we
want
to
do
it.
The
initial
thing
that
I
heard
is
people
wanted
to
hold
it
once
a
month
and
try
and
do
a
little
more
on
the
slack
which
I'm
fine
with
unless
people
feel
that
we
really
need
to
meet
more
often
than
that
or
or
you
know,
or
we
can
try
and
do
things
as
demand
driven.
A
G
I
think
once
a
month
is
a
good
start,
since
we
are
starting
anyway,
we'll
we'll
see
the
feedback
and
how?
How
good,
how
useful
the
meeting
is
for
everyone.
A
Yep
yeah,
I
think
it
depends
on
how
many
topics
we
have
right.
A
A
Yep,
okay,
good
and
then
so
I
think
we
covered
kohei's
action,
our
cohase
agenda
item
and
then
we
were
able
to
sneak
in
socos
as
well,
and
then
I
think,
what's
left
is
is
irvi.
So
I
think
it's
it's.
I
think.
That's
the
the
the
next
thing
I
think
irvy.
If
you,
the
the
the
the
floor,
is
yours.
The
meeting
is
yours.
G
Okay,
before
irving,
can
I
ask
sure,
question
sure,
yeah,
and
so
basically
the
way
you
localize
that
localization,
how
to
page
is,
is
not
really
based
on
the
original
english
structure.
Right
you,
you
modified
it.
According
to
your
needs,.
H
Yeah,
I
I
completely
changed
it.
It's
not
just
from
it's
not
from
scratch.
Actually,
because,
just
like
korean
team,
we
used
to
have
their
our
own
page
somewhere
different,
so
we
basically
just
adopted
it
to
the
markdown
style
in
the
kubernetes
document.
G
Oh
yeah,
what
I'm
trying
to
say
is
that
you
don't
literally
translate
hundred
percent
from
english.
You,
you
yeah.
H
H
Prioritize
as
in
the
translation
for
each
page.
H
H
I
think
I
think
the
documentation
has
the
google
analytics,
so
you
can
check
the
like
most
view.
Viewed
contents
based
on
the
analytics,
so
using
you
make
making
use
of
it.
The
google
analytics
you
can
start
maintaining
pages
based
on
the
demands,
but
also,
I
think
it's
just
my
opinion,
but
like
confidence
for
beginners
is
also
demanding.
Apart
from
that,
too,.
H
Oh,
that's
a
good
question,
but
I
think
you
should
start
from
english
because
you
don't
have
any
pages
at
the
beginning
right
in
your
language.
Yes,
yeah
yeah,
so
maybe
you
can
check
the
analytics
for
your
language
later,
but
for
now
maybe
you
you
just
ask
for
it.
What's
the
most
viewed
translate
ana
pages,
I
think
you
need
a
special
permission
to
check
the
analytics,
so
you
can
ask
the
chairs
first.
C
Yeah
in
case
of
korean
relationship,
we
started
from
the
tutorial
part
tutorial
part
because
we
actually
surveyed
from
the
korean
user
group
korean
coordinative
user
group
we
surveyed,
which
page
which
part
should
be
translated.
First,
then
they
mentioned
tutorials
because
tutorials
are
very
easy
part,
even
the
even
more
the
concept
part.
So
we
started
from
the
tutorial
and
concept
part
and
we
are
focusing
on
task.
Part
task
part
is
a
little
bit
harder
to
beginners.
C
So
that's
the
why
we
did,
and
currently
we
keep
translating
a
whole
document
based
on
contributors
contributors
prepares.
If
we
don't
have
contributors
pre-currents,
then
they
are
very
hard
to
translate,
not
interested
document.
So
currently
we
don't
guide
which
page
should
be
translated,
but
contributors
can
choose
which
page
should
be
translated.
A
C
C
A
Okay,
so
if
I
understand
this
correctly,
you
started
with
tutorials
and
then
you
move
to
concepts,
and
then
you
said
you
moved
to
tests.
Was
that
right?
Yes,
test
tasks,
I'm
sorry
tasks,
so
you
went
from
tutorials
to
concepts
to
tasks
and
then,
after
that
it
was
whatever
the
contributor
wanted
to
go.
Do.
C
A
H
Yeah,
once
you
have
enough
pages
to
show
people
start
recognizing.
Oh
there's
translation,
then
oh,
but
this
this
page
is
missing.
This
page
is
missing.
The
issue
will
be
created
by
those
people.
H
G
C
C
C
H
In
the
case
of
japanese
team,
we
actually
accept
pull
requests
where
they
only
translate
partially.
H
So,
for
example,
there's
like
maybe
500
lines
of
trans
english
lines
and
like
only
this
part,
is
translated
and
everything
else
is
still
english.
That's
okay.
We
just
accept
it
but
like
we
also
hope
to
update
it.
So
we
just
make
it
an
issue,
then
so
that
other
people
can
update
it.
H
Yeah,
but
I
think
there
are
pros
and
cons
on
that
way
because
it's
it's
in
the
japanese
document-
and
it
still
shows
us
english,
partially
and
you're,
not
sure
if
this
english
is
up
to
date,
because
contributors
usually
take
the
part
based
on
the
english
sentences,
that
is
in
the
japanese
page
but
like
when
it's
actually
there's
a
gap
between
the
english
one,
the
original
english
one
and
the
english
sentence
sentences,
which
is
in
the
japanese
page.
H
A
Okay,
so
these
are
all
excellent
excellent
strategies.
Irby
was
there.
Was
there
any
other
topics
that
we
wanted
to
cover
as
part
of
this,
for
today,.
A
G
So
when,
when
we
started
the
localization
team
for
indonesian
language,
our
goal
was
to
translate
as
many
as
we
could.
That
was
a
simple
goal.
We
have
translated
around
200
pages
out
of
70
contributors
now,
looking
back
since
we
are
also
planning
the
new
milestone.
G
I
want
to
ask:
what's
the
end
goal
or
ultimate
goal
of
each
of
the
localization
team,
is
it
to
translate
all
100,
the
upstream
english
pages
or
together
as
many
contributors
as
you
can
or
or
what?
Because
translation
is
that
doesn't
end
there
right?
We
have
to
maintain
the
outdated
pages,
and
it's
it's
so
much
work.
G
When
I
look
back,
I
don't
think
translating
100
of
english
pages
makes
sense
any
anymore
for
us.
So
I
would
want
each
of
yours
opinion
on
this,
especially
since
we
are
in
the
middle
of
planning.
H
H
A
current
version
so
like
1.18
1.17
1.19,
there
are
several
different
versions
right
and
also
the
english
documentation
have
the
versions
as
well.
So
I
think
translating
a
new
page
doesn't
is
not
a
big
deal
anymore.
For
us,
the
bigger
part
is
updating,
so
we
we
create
this
milestone
as
a
really
big
goal.
H
H
The
one
milestone
is
really
big,
but
I'm
not
sure
about
the
korean
one,
but
it
it
looks
like
more
flexible,
because
they're
they're
way
ahead
of
at
least
our
work
in
one
milestone.
A
H
H
A
H
A
My
guess
is
gary's
at
a
different
stage:
you're,
not
quite
at
that
stage.
Gary
of
oh
won't,
it
be
wonderful
where
we
just
have
to
look
for
the
the
changes
and
the
differences
is
that.
H
Because
he
said
he
translated
a
lot
of
pages
already
and
he
wants
to
know
what's
what
he
should
make
a
goal
at
the
next
stage.
So
that's
why
I,
what
I'm?
I
I
explain
what
I'm
doing.
H
Updated
pages,
let
me
quickly
see
because
I
don't
remember
in
my
video.
C
In
case
of
korean
localization
team,
we
actually
focusing
on
helping
people
korean
user
group.
So
if
they
think,
if
koreans
think
we
need
100
translation,
then
we
hope
to
follow
it.
But,
as
you
know,
the
contributors
are
very
limited,
so
we
are
doing
the
best
part
that
maybe
we
cannot
cover
the
100
percent,
but
we
are
doing
our
best
and
sometimes,
as
you
know,
kubernetes
is
keep
growing
every
list.
The
documentation
also
changes,
so
we
don't.
Currently
we
are
hard
to
care
the
previous
versions,
but
we
keep
focusing
on
the
current
or
latest
version.
C
So,
if
possible
we
hope
to
cover
100
percent,
but
for
now
we
are
doing
best
effort
and
somehow
we
got
we
could
have
wonderful
contributors
for
localization,
so
we
have
some
contributors
who
are
willing
to
translate
very
wrong
document.
C
So
hopefully
we
hope
to
cover
the
100
and
regarding
the
courage
comment
we
are,
we
have
the
branch
strategy
and
we
are
keep
generating
the
debit
branch
for
korean
localization
and
two
weeks
later
we
merge
it
to
master,
and
then
we
create
another
branch,
and
we
keep
repeat
those
two
week
milestones
and
the
reason
why
we
do
this
in
short
term-
is
that
we
hope
to
make
our
courier
localization
document
is
keep
updated
and
keep.
C
A
Okay,
well,
we
are
out
of
time
for
our
first
meeting,
but
we
filled
the
whole
hour
with
with
great
tips.
I
don't
think
we
got
to
everybody
looks
like
rael
added
some
things
into
the
google
doc.
I
tried
to
take
notes
as
best
as
possible
to
capture
the
key
points
that
all
of
the
the
speakers
were
making,
and
I
think
irvy
was
doing
the
same
as
well
and
and
and
others
were,
were
adding
things.
So
so
please
review
them.
A
If,
if
I
did
not
capture
them
properly,
please
let
me
know
but
butzoko
and
kohei.
I
did
my
best.
While
you
were
talking,
there
is
a
lot
of
true
expertise
on
this
call.
That
is
just
really
interesting,
and
so,
as
we
get
into
more
of
the
details
of
the
topics
like
soco
and
and
how
they're
doing
things
with
their
document,
I
know
personally,
I've
learned
a
lot
just
in
this
one
hour.
So
this
is
amazing.
A
So
I
wanted
to
thank
everyone.
This
is
just
an
absolutely
very
productive
call
and-
and
we'll
do
it
once
a
month,
and
we
have
our
our
slack
as
well
any
any
closing
statements
from
anyone
that
that
that
will
make
sure
everybody
got
a
chance
to
speak
anything
important
before
we
end
the
meeting.
H
I
H
Yeah
263
is
in
the
nation
and
we
are
like
303
yeah,
so
we're
trying
to
keep
up
and
follow,
follow
the
korean,
or
you
know
the
english
one,
of
course,
yeah.
A
A
I
don't
do
it
very
well,
I'm
going
to
practice
that
everyone.
This
was
a
great
meeting
and
thank
you
very
much.