►
From YouTube: K8S SIG Docs Localization Meeting for 20220912
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
Loud
hi,
everyone
welcome
everybody
to
the
9
12.,
the
group
monthly
meeting
of
the
Sig
docs
localization
work
group.
A
A
That,
okay,
can
everybody
see
my
screen
all
right?
First
of
all,
do
we
have
anybody
new
today,
anyone
new.
C
Oh
hi
hi
guys.
My
name
is
someone
Kim:
okay,
I'm,
a
student
in
Korea
I'm
participating
in
Korean
colleges,
team.
A
Nice
to
meet
you,
anyone
else
do
today:
okay!
A
Well,
let's
start
with
our
first
item
on
the
agenda,
and
the
first
big
item
is
a
huge
congratulations
to
the
Hindi
localization
team
for
releasing
an
initial
version
of
the
Kube
docs
in
Hindi,
and
that's
just
awesome,
so
I
I
see
we
have
some
folks
here
right.
A
You
know
and
absolutely
wonderful
anybody
I,
don't
see
our
normal
folks.
Anyone
else
that
worked
on
the
Hindi
localization
are
you
on
the
call.
D
A
Fantastic
well
thanks
to
thanks
to
all
of
you
for
your
dedication
and
hard
work,
I
tweeted
about
this-
and
you
know
we
got
a
lot
of
views,
a
lot
of
views,
a
lot
of
congratulations,
so
great
job,
absolutely
great
job!
Please!
Please
keep
working
on
it,
make
it
better
and
better,
just
absolutely
wonderful
Milestone!
So
congratulations
all
right!
A
D
D
E
D
Okay-
and
this
page
has
been
localization
localized
to
a
handful
of
languages
of
these
five
languages.
Four.
A
D
Okay,
yes,
so
here
we
are
on
the
releases
page
in
the
kubernetes
docs
and,
as
you
can
see,
this
page
is
available
in
five
languages.
Four
of
these
are
functional.
French
is
not
functional
and
I
filed
an
issue
for
that.
The
main
issue
is
that
when
you
look
at
it
in
these
other
languages,
there
are
still
some
English
strings.
D
So
we
we
made
a
localization
for
this.
This
has
been
handled
in.
D
D
D
Hang
on
trying
to
make
this
menu
go
away.
Okay,
I'm
gonna,
pull
this
down
yeah.
B
D
So,
in
any
case,
what
I
did
is
I
have
this
new
issue
with
a
series
of
tasks
for
the
other
localization
teams
to
adopt
a
set
of
strings?
D
For
each
of
these
languages,
I've
created
a
specific
issue
and
assigned
it
to
your
language
group.
It
needs
to
be
triaged
and
if
you
have
any
questions,
I
can
go
over
it
with
you,
either
in
person
or
asynchronously.
Through
slack.
Mostly,
it
will
involve
updating
your
Tamil
file
I've,
given
very
specific
instructions,
so.
D
Yeah
here,
I
show
you
where
the
issue
is
here:
I
recommend
the
file
that
needs
to
be
updated
and
where
those
updates
need
to
come
from
and
I
identify,
specific
well
segments
of
that
file
that
that
you'll
need
to
localize
while
you're
at
it.
You
may
also
want
to
localize
other
strings
that
have
been
added,
but
that's
completely
optional.
For
this.
It's
just
these
five
sections
so.
A
A
D
D
Yeah
actually
I
skipped
that
one
I
wanted
to
gather
some
suggestions
on
strategies
that
localization
teams
use
to
optimize
the
rate
of
mergers
and
team
decision
making
I
see
some
teams
doing
an
excellent
job
of
this
and
I
think.
Maybe
this
isn't
the
right
form
to
discuss
them,
but
if
she
wanted
to
make
some
suggestions
as
bullet
points
here
or
what
do
you
think
do
you
want
to?
Would
we
discuss
this
or
just
gather
notes
down
below
to
any
suggestions.
A
So
I
I
think
the
thing
is,
you
know
we
could
just.
We
could
take
five
minutes
to
discuss
if
anybody
has
just
some.
You
know
high
level.
Tldrs
might
be
worth
you
know
just
identifying
if
there's
anyone
who
feels
a
on
the
call
for
you
to
follow
up
with
to
see
if
they
have
thoughts-
and
you
could
do
a
separate
meeting
come
back
to
us.
If
you
need
more
time.
A
Right
and
so
that
the
thought
process
here
is,
you
know
Soco.
What
do
you
feel
your
team
has
done
to
to
reduce
the
friction
and,
and
you
know,
you've
been
able
to
speed
up
you
know
getting
things
merged
and
and
making
decisions
quickly.
You
know
any
hints
or
tips
Soco
that
that
have
worked
since
under
your
leadership.
F
F
Localization
came,
we
have
regular
meeting
so
in
10
meeting
we
discuss
and
we
decide
whatever
we
are
in
consensus,
but
maybe
we
don't
care
about
the
speed
of
the
decision.
F
We
usually
think
what
is
important
thing
and
what
is
our
nice.
F
F
So
when
we
decide
something,
we
put
it
in
some
guided
guided
documentation
so
that
other
contributors
can
follow.
That
decision
and
usually
we
open
to
change
any
decision
from
any
anybody
and
someone
who
who
has
nicer
idea
is
to
bring
that
I
think
to
Korean
localization
team
meeting
or
team
Channel
but
yeah.
It
is
very
similar
with
our
the
current
meeting
localizations
of
meeting.
We
try
to
follow
for
a
systematic
way
in
kubernetes
community.
D
F
Or
some
contributors
are
very
dedicated
to
our
team
and
our
community,
but
they
also
have
some
periods
that
they
cannot
participate
in
contribution.
F
Yeah
yeah
I
I
think
we
don't
have
to
lose
contributors
who
active
previously.
If
we
wait
10
10
and
then
they
end
they
when
they
have
some
time
they
will
be
back
to
our
community.
F
D
F
Yeah,
that's
why
I
I
said
the
important
thing
is
not
the
speed.
We
need
to
keep
localized
our
website
that
moving
fast
food.
E
A
Iman,
do
you
want
to
just
if
you
can't
do
it
verbally?
Do
you
want
to
just
add
some
thoughts.
B
A
D
Maybe
it
would
be,
maybe
we
could
continue
amen.
Please
Speak
by
all
means
share
your
notes
and.
A
Well
then,
the
next.
The
next
issue
is
amman's,
so
I'm
on.
If
you're
going
to
be
able
to
cover
it
so
to
generalize
the
type
of
keyboards
that
generates
the
type
of
keywords
that
need
to
be
translated
and
the
ones
that
are
not
supposed
to
be
translated
and.
B
A
D
Rough,
please
go
ahead.
Okay,
so
I
think
this
is
a
general
language.
This
is
a
general
issue
for
all
localization
teams
in
and
just
as
background
so
Hindi
uses
phonetic
characters
and
very
often
with
loanwords
from
from
technology.
You
either
spell
out
the
pronunciation
of
the
word
so
kubernetes
you
would
use
script
to
do
the
syllables
something
similar.
B
B
D
D
A
So,
wouldn't
that
be
language
specific
based
on
right,
so,
for
example,
you
know-
maybe
there's
you
know
the
Chinese
team,
maybe
the
the
rule
is
you
always
use
the
English
for
certain
words
and
you
just
plop
the
English
in
and
then
maybe
there's
other
languages
where
maybe
I'm
just
jumping
Hebrew,
for
example,
where
it's
very
common
to
use
phonetic.
A
Wouldn't
it
be
possible
that
the
languages
might
have
best
practices
that
are
you
know
for
how
people
write,
and
so
you
you
wouldn't
want
to
you,
wouldn't
want
to
say,
tell
the
Chinese
folks.
Listen,
you
really
shouldn't
be
using
the
English
words.
You
should
do
it
phonetically
when
maybe
the
rest
of
the
culture
of
how
they
translate
documents
is
no.
We
we
always
use
an
English
word
here
or
here.
Does
that
make
sense.
D
Yeah
granted
that
it's
going
to
be
very
different
for
one
language
context
for
another,
but
it
would
still
we
seem
in
Hindi.
We
seem
to
be
at
a
loss,
for
it
is
a
systematic
and
we're
just
looking
to
understand
how
other
teams
have
gone
about
making
these
decisions.
Of
course,
systematizing
sayoko
I
was
wondering.
If
maybe
you
could
comment
on
how
your
team
did
it
for
Korean.
F
A
F
F
And
contributors
should
know
if
they
want
to
contribute
to
Korean
localization,
so
it
is
only
for
Korean,
but
it
can
be
applied
to
other
localization
teams
who
utilize
a
similar
way.
Also,
we
have
some
style
guideline
of
the
of
that
translation
and
it
is
very
detailed.
F
And
since
we
need
to
manage
and
maintain
the
code
itself,
we
say
the
documentation
is,
of
course
we
need
to
some
guideline.
For
instance,
you
know
some
documents
have
dprs
lift
kit.
F
F
We
cannot
easily
translate
those
API
objects
into
Korean,
so
we
need
to
decide
how
to
enter
them
and
we
also
have
very
special
cases
English
to
Korean.
We
made
this
kind
of
grocery
Korean
language
exploratory,
so
that
English
tongue
needs
to
be
translated
into
Korean
in
this
way,
and
we
have
some
notes
and
those
items
have
been
decided
in
Korean
localization
team
meeting
one
by
one.
So.
A
Right,
so
this
is
what
I
really
like
about
the
approach.
It's
it.
It
answers
a
lot
of
the
questions,
but
it
also
provides
a
an
autonomy
per
language
right
so
per
language
you're,
going
to
get
the
consistency
you
need,
and
and
unless
somebody's
incredibly
brilliant
they're,
not
going
to
necessarily
realize
that
you
know
the
standards
for
Chinese
are
different
than
the
standards
from
Korean
and
if
they
are
well,
then
they're
smart
enough
to
understand
why
it
is
that
way.
Right.
A
A
Phonetically,
here's,
the
ones
that
are
done
in
English,
and
then
we
leave
it
up
to
the
languages
to
to
decide
the
best
practices
and
then
I
think
that
gets
you
what
you
want
roll,
which
is
a
which
is
an
improved
or
I'm
on
you
know
an
improved
consistency
of
of
of
of
of
the
content
per
language,
yeah.
D
D
Been
creating
a
localization
guide
for
Hindi,
and
this
is
an
issue
in
in
PRS
that
has
come
up
in
reviews.
Sometimes
you'll
see
a
term
bounce
back
and
forth
between
one
language
and
the
other
more
than
more
than
one
time,
and
there
is
no
hard
fast
rule
I
think
maybe
I'm
on
this.
D
We
would
come
up
with.
We
could
come
up
with
a
more
general
rule
and
just
apply
it
and
say
you
know,
get
some
sort
of
consensus
around
which
way
to
do
it
and
then
just
stick
to
a
guideline.
D
B
A
Okay,
so
I'm
gonna
go
back
to
my
agenda
and
that
means
we
are
up
to
Soco
Korean
localization
team
update
feel
free
to
share.
If
you
need
to.
F
I'm
sorry
I'm
here,
yeah
I,
hope
to
share
Korean
localization
team
update.
We
are
in
24K
us3.
We
are
not
in
25
yet,
but
this
development
went
to
be
about
to
be
finished
it
soon.
So
the
Milestones
regarding
this
issue
I
mean
the
first
two
issue
for
this.
My
exponent
is
all
the
localization
except
Korean
localization.
F
Initiation
of
the
development
branch
we
targeted
this
state,
but
we
couldn't
finish
it
yet,
and
the
second
important
issue
for
this
Milestone
is
to
update
Korean
localization
Korean
Korean
document
up
to
date
with
English
relatives
to
document.
So
we
could
check
the
difference
between
English
of
often
English
document
with
Korea
localized.
The
document,
and
you
see
we
need
to
update.
F
I'll
find
I
located
a
different
issue,
but
it
is
more
than
100,
so
we
need
to
finish
it,
those
updates
and
then
we
will
complete
the
24.
Can
you
see
it
soon
and
next
will
be
the
25kano
one,
which
will
be
the
first
two
localization
report
for
25
25.,
also
I
hope
to
share
again
we
are
putting
a
localization
team
are
participated
in
contribution,
Academy
program,
which
is
hosted
by
one
of
Korean
government
agency,
and
we
invited
21
mentees
from
that
program
and
actually
the
newcomer
of
this
meeting.
H
H
F
Yeah,
thank
you
for
saying
hello.
F
She's
still
actually
are
very
active
contributor
from
this
program
and,
as
you
can
see
from
to
everyone
mentis,
we
got
a
lot
of
girls.
F
F
C
Oh,
can
you
see
this
screen?
Yes,
oh
I
for
for
localizations
I
found
that
the
tree
structure
of
these
Pages
inside
bar
is
different
with
or
do
not
perfectly
match,
with
its
localizations
and
offstream
Main
English
documentations
or
since
this
order.
The
order
of
this
structure
is
based
on
with
its
weight
like,
for
example,
every
Pages
have
have
their
own
weight
like
this
value.
C
C
So
for
this,
for
example
like
like
this
structure,
the
Upstream
has
order
of
Linux
Mac
OS
windows,
but
in
Korean
localization
the
order
is
like
macwest,
Linux
window
or
or
this
makes
every
or
this
might
be,
the
First
with
each
localization
so
or
I
I
think
it.
We
should
change
the
upstreams
values
that
have
that
is
redundant
so
and
I
have
issued
it
on
here.
C
A
A
A
So
is
my
assumption
wrong
that
if
things
have
equal
weight,
that's
pretty
much
the
localization
team
saying
or
or
whoever,
whoever
built
the
original
content
saying
whatever
order
occurs
is
fine
and
then
the
only
issue
is.
Should
we
be
concerned
that
the
order
will
be
different
across
different
localizations.
C
C
A
Unless
somebody
said,
oh,
the
alphabetical
just
landed
the
way
I
wanted
it
anyway
and
then
and
and
then
just
the
one
language
got
lucky
and
then
the
next
language
would
be
not
so
lucky
so
thoughts.
You
know
this
to
me
could
be
something
that
could
be
done,
lazily
right.
So
if
it
appeared
there
should
be
an
order
where
it
would
be
kind
of
important
to
have
things
in
a
certain
order.
Folks
could
go
change
the
weight,
correct.
G
I
would
I'd
be
a
little
in
agreement
with
you
there
Brad,
if
we
have
instances
where
the
pages
are
really
misordered
because
of
the
outlooked
different
alphabetizations,
a
different
alphabet,
if
they're,
if
they
get
really
out
of
order,
and
it
really
adjusts
how
people
would
understand
the
content.
I
think
that
that
might
be
something
to
take
priority
because,
like
you
said
there
was
a
lot
of
pages,
this
could
affect
a
lot
of
pages.
So
it
might
be
a
long,
a
bigger
project.
G
If
we
wanted
to
update
everything,
but
maybe
it's
as
you
update
Pages,
you
can
adjust
the
weights
whatever
or
if
we
do
find
something
in
the
English
language
that
you
wanted
to
make
sure
appeared
in
the
same
order
across
all
the
localizations,
we
can
go
and
change
those
did
you
find
a
place
in
the
documentation
that
really
would
have
being
the
way
out
of
order.
Is
it's
a
really
a
negative
impact
for
people
reading
the
pages
like
a
tutorial
or
something
that
has
to
go
through
each
each?
Whatever.
C
No
I
I,
don't
I
think
there
is
not
a
important
chain
important
on
nothing
matters.
In
my
opinion,
it
does
not
affect
that.
Importantly.
A
You
know,
then
then
people
then
people
could
could
open
up
and
and
ask
for
the
weights
to
be
readjusted
right,
open
up
a
bug
and
say:
could
you
readjust
this
I
know
it
looks
fine
and
say
English,
but
in
Korean
this
this
looks
really
bad
I
I
think
we
want
to
be
sort
of.
You
know,
you
know
you
can
always
be
lazy
or
you
can
be
active
right
or
eager
I.
A
Think,
maybe
because
if
you
go
eager
you're
going
to
be
making
tons
and
tons
of
changes
and
lots
of
work
and
and
maybe
perhaps
there's
only
a
few
Easter
eggs
where
it
really
makes
a
difference.
So
so
my
thought
process
would
be.
You
know,
let's,
let's
make
sure
it's
it's
documented
and
just
be
on
the
lookout
for
it
and
then,
if
there
really
is
one
or
two
that
really
needs
to
change
the
weights,
then
then
you
open
up
an
issue.
Does
that
make
sense
to
everybody?
D
Would
I,
plus
one
what
you
just
said
and
I
would
communicate
this
to
the
Sig
docs
group
generally
just
saying
this
has
come
up
just
be
aware
of
this,
make
sure
that
you
are
consciously
choosing
the
way
and
and
not
just
accidentally,
setting
it.
A
A
And
then
because
people
may
not
be
aware,
oh,
it
came
fine,
but
again
you
know
I'll
use
that
term
ugly
American
right,
we
were
focused
on
the
weights,
for
you
know
how
it
looked
on
our
page
and
it
was
just
fine,
but
you
know,
there's
a
bigger
world
out
there
and
and
to
be
aware
that
you
know:
don't
don't
necessarily
rely
on
the
alphabetical
because
it
could
hurt
somebody
else
down
the
road
right.
A
A
A
F
I
I
think
it
is
very
nice
issue
and
I
agree
with
Brad
is
suggestion
and
and
yeah
I
think
in
the
localization
so
project
meeting.
Maybe
we
need
to
also
guide
other
localization
teams
to
check
their
status
in
case
of
Korean
since
hangout
text
we
aware
of
the
situation
The
Authority
design
I
mean
the
order
of
Korean
titles
in
site
battery,
but
maybe
some
localization
is
not
aware
of
it.
F
B
A
F
Yeah
I
hope
to
share
an
issue.
Actually
it
is
already
open
issue
for
secretary
but
I
hope
to
share
some
issue.
Maybe
yeah.
So
can
you
introduce
this
issue?
Yes,
yes,
oh.
F
H
H
Oh
okay,
here
here,
I'm,
not
good
sticker,
both
the
Korean
and
English,
but
Avail
represent
something
I.
I
will
suggest
something
and
I
tested
the
broker
circumstances
and
at
least
five
or
processor
too,
for
I
think
there
is
a
Hugo
issue.
E
H
H
H
Oh,
there
isn't
a
time
up
woke,
so
you
can
see
here
here
pills
this
side
just
started
here
and
if
you
go
start
to
the
here
right
and
then
do
the
exceeded,
and
this
means
while
Hugo
building
and
then
it
it
takes
35
minutes
Flex
movie.
So
so
they
timeout
is
while
Hugo
building
and
it's
it's
not
a
magnify
issue.
So
I
searched
about
with
by
Road
car
containers
circumstances-
and
here
is
it
say
he
wants
Ubuntu
Linux
image,
and
then
you
can
hear
see
here.
H
H
I,
roughly
suppose
that
that
simplify
a
container
is
thirsty
as
CPU
is
mighty
0.4
CPU,
and
there
is
a
six
course
CPUs
and
then
memory
limits
are
one
gigabyte
memory
reduced
US
size
is
one
gigabyte
and
limits
are
eight
gigabytes,
so
it's
two
enough
Hugo
can
build
so
I
think
we
need
at
debug
and
template
metrics
of
life
for
reproduce
is
timeout
issue.
Actually
these
sizes
are
what
I,
what
I
made
it
myself
and
then
I
failed
to
reproduce.
H
These
Primal
issue
so
I
think
to
be
important
to
look
at
debug
logo
reward
that
ruled
by
System
Road,
so
I
suggest
we
widely
at
here
might
be
okay
here
like
this.
H
Can
you
see
that
deploy
preview
comments?
We
can
add
like
this
one
and
then
I
I,
think
we
need
to
keep
the
comments
until
the
issue
reproduce
bit.
Thank
you.
F
E
F
Go
ahead,
oh
sorry,
I
hope
to
share
the
contest
status
a
little
bit
more
and
yes,
could
you
stop.
C
F
F
Pair
the
tis
are
not
failed
because
of
Any
code
error.
It
is.
F
A
Know,
there's
always
these
sort
of
phantom
bugs
that
typically
occur
and
and
I
think
the
question
becomes.
They
need
to
happen
often
enough
that
they're
able
to
debug
them
because
when
they
only
happen
every
so
often
it's
just
well
just
rerun
it
right,
redo
the
build
so
and
it
looked
like
kaiming
looked
like
Kai
mean,
was
willing
to
try
and
investigate
I
think
this
is
when
you
need
to
go
to
to
the
leads
on.
My
guess,
is
you
know?
Abby
and
myself,
don't
have
the
skill
set
to
help
with
this?
A
My
my
net
net
lafly
is
is
very
limited.
I
I
won't
speak
for
Abby,
but
not
my
area
of
expertise,
but
so
you
know,
I,
think
getting
to
to
array
or
or
kaiming
might
be
the
the
just
go
directly
to
them,
because
this
really
isn't
a
language
thing.
This
is
more
a
it's
happening
for
your
language,
but
but
it's
a
build
thing
right.
It's
an
infrastructure.
F
Yeah
originally,
you
can
still
share
this
issue
in
this
meeting.
Is
that
other
localization
or
purpose
we
should
or
whatever?
Why
build
sales?
So
when
they
with
this
failed
appear,
I
mean
they're
the
CI,
they
need
to
push
another
commit
or
comment
or
another
commit.
Then
the
electricity
will.
We
will
lead
test
and
leave
the
to
fix
this
situation.
So
that's
the
reason
why
you
want
to
share
with
this
issue
in
this
meeting,
so.
F
We
need
we
need
to
guide
where
we
need
to
leave
a
message
in
select
channel
so
that
other
localization
teams,
aware
of
this
situation,.
F
A
And
and
again,
I
think
just
reporting
it
to
to
to
the
the
chairs
so
they're
aware
that
hey
this
is
maybe
happening
more
frequently
than
it
used
to
occur.
We're
seeing
this,
you
know
they
should
be
aware
if
it's
happening
more
often
than
it
was
and-
and
you
know
make
sure
they
have
I
mean
because
it's
something
that
will
apply
even
to
just
the
non-locals
and
just
English
I
mean
this
could
happen.
So
something
they
might
want
to
be
aware
of
is
my
guess.
A
Okay,
we
are
remarkably
out
of
time.
Unfortunately,
I
do
want
to
give
Abby
just
a
quick
chance
to
plug
something
for
folks
to
think
about
Abby.
If
you
could.
G
Maybe
what
didn't
go
so
well
and
things
that
we
might
be
able
to
improve
upon
as
a
group
and
so
I'm
still
really
interested
in
hearing
that
topic
and
I
think
it's
a
good
problem
that
we
ran
out
of
time
because
we
had
such
a
full
agenda,
but
it
unfortunately
means
we
can't
talk
about
it
right
now.
I'm
gonna,
try
to
post
things
in
slack,
so
I
hope
folks
are
able
to
join.
G
So
we
can
sort
of
chat
about
it,
maybe
more
asynchronously
which
might
work
for
folks,
because
timing
is
always
hard
and
then
maybe
at
the
next
meeting
we
can
give
like
a
brief
summary
of
what
we
discovered
and
sort
of
chat
about
it
more
there.
We
have
more
action
items.
So
if
that
sounds
good
for
everyone,
I
hope
to
see
you
in
slack
and
I'll,
be
I'll,
be
posting
about
that
today,
as
well.
So,
thank
you.
That'll.