►
From YouTube: SIG Docs Localization Subgroup Zoom Meeting for 20210802
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
welcome
to
the
august
2nd
2021
monthly
meeting
of
the
sig
docs
localization
work
group
meeting.
This
meeting
is
being
recorded
and,
as
you
should
know,
the
cncf
code
of
conduct
rules
are
are
apply.
So
so
please
everyone
be
nice
to
each
other,
and
if
you
need
to
see
the
agenda,
I
will
put
it
in
the
chat.
A
And
if
we
go
look
at
the
agenda
soco
the
floor
is
yours.
B
Thank
you,
brad.
Okay,
let
me
share
the
current
status
of
korean
localization
team.
First
of
all,
as
you
know,
korean
localization
team
has
a
milestone
strategy,
so
we
we
make.
We
create
a
development
branch
for
korean
localization
and
currently
we
are
operating
the
table,
1
2,
21
ko7
and
it
will
be
merged
soon.
B
And
I
I
expect
the
1
22
will
the
26
122
will
be
released
soon
and
then
we
will
initiate
the
ko1
for
release
122..
B
B
Yeah
very
active
contributor
for
korean
localization
team
and
as
well
as
to
the
of
english
content
software,
so
we
are
very
welcome
for
the
new
leaver
chihun
actually
is
also
my
colleague,
my
colleague,
and
next
titan
is
election
for
the
korean
localization
team
leader,
as
I
mentioned
before,
the
my
duty
as
a
as
the
team
leader
is
actually
overdue,
and
but
during
the
election
period
we
couldn't
find
any
new
clinton
dates.
Yet
so
we
agreed
to
I
circle
will
continue
the
leadership.
B
For
this
moment
I
couldn't
escape
yeah
yeah,
so
we
will
keep
looking
for
new
candidates
for
every
minor
release
of
kubernetes.
B
Yeah,
so
we
hopefully
find
a
new
candidate
so
that.
B
B
B
B
Update
to
apply
to
all
localization
document,
but
we
are
guiding
sega
dogs
are
guiding.
B
We
need
to
separate
the
pr
for
in
case
there
are
many
parts
from
localized
content
is
invoked.
We
need
to
separate
them
to
individual
pairs.
A
You
mean
in
the
issues
document
or
so
I'm
I
clicked
on
the
link.
I
I
mean
in
the
oh,
oh
on.
A
A
B
Reason
why
we
separate
those
peers
is
that
english
reviewers
and
owners
it's
hard
to
review
localized
content,
so
we
decided
to
divide
them,
but
we
are
currently
doing
it
for
very
simple
bug:
pics
or
typo
link
update.
A
B
A
B
So
consequently,
this
year
update
literally
piloting
literally
by
status,
link
to
master
tubing,
but
it
is
applied
to
english
rhythmic.
B
Surely
we
have
a
korean
rhythm,
md
hi.
B
Sure
so
I
think
english
approval,
actually
the
approval
of
upstream.
B
A
So
so
what
what
you
would
like
is
to
be
able
to
do
a
single
pr
that
actually
is
updating
the
links
in
in
the
multiple
multiple
language
code
repositories
that
that's
the
request.
Correct
you'd,
like.
B
To
be
yeah,
oh,
I
think
if
the
pr
requires
translation
or
transit
include
translated
contents
from
contributor,
then
the
reviewers
who
can
review
that
language
should
be
involved.
A
B
We
don't
need
to
separate
it
to
individual
pr,
yeah,
that's
my
opinion,
but
I'm
not
sure
for
other
languages.
Other
things.
Maybe
we
need
to
check.
It
is
if
it
is
okay
to
him.
A
Right
so
historically,
we
have
asked
that
pull
requests
not
make
updates
to
two
different
language
repositories
and
those
single
pull
requests,
because
you
know
when
it
was
time
I
think,
for
people
to
do
branches
or
whatever
there
was
some
type
of
issue,
I'm
trying
to
remember
the
specifics,
but
that
would
cause
some
some
problems
later
on
when
people
were
either
cherry
picking
or
something.
A
I
can't
remember
the
exact
detail,
and
so
the
question
is,
you
know:
can
there
be
an
optimization
that
if
all
you're
doing
is
updating
a
link
and
there's
no
translation
required,
would
it
be
possible
to
put
all
the
different
updates
in
the
single
pr?
But
I
I
think.
A
A
Right
so
you
just
mentioned
the
problem,
so
I
I
think
what
you
might
want
to
do
is
just
add
another
comment
that
say:
here's
the
solution,
I
think,
would
work
and
then
we
could
go,
bring
it
up
with
sig
docs
and
see
if,
if
there's
issues.
B
Yeah,
I
think
you
should
build
so
chilled
with
sugar
dogs
and
yeah
yeah
anyway.
English
proverbs
need
to
know
how
to
handle
the
pr
that
includes
contents
from
multiple
languages.
A
Right
and
then
we
have
to
educate
the
other,
the
other
language
teams,
translation
teams,
because
they
might
get
scared
if
somebody
is
merging
something
into
their
code
base
right.
B
A
Yes,
so
so
this
is
interesting,
so
yeah,
I
would
think
if
you
can
just
add,
maybe
a
comment
with
just
your
proposed
solution,
and
then
we
can
go,
follow
up
and
and
see
what
sig
docs
chairs
say
if,
if
they
have
other
concerns
or
or
if
this
could
be
an
optimization
for
when
you're,
not
updating
anything
that
needs
translated.
B
A
Right,
that
is
the
standard
that
is
the
standard
thing
and
so
okay,
so
we
can
check
into
this
and
see
if
there
were
some
issues.
I
can't
remember
that
that
keep
us
from
doing
this
sure.
Thank
you
yeah,
the
very
interesting
point
and,
like
I
said,
if
you
want
to
add,
if
you
want
to
add
hey
your
proposed
solution
at
the
bottom,
you
can
obviously
I
can
bring
it
up.
A
I
understand
the
proposed
solution
you'd
like
to
be
able
to
update
multiple
language
code
repositories
into
single
pr,
but
but
okay,
good,
so
we'll
we'll
follow
up
on
that
I'll
see
I'll
put
it
on
the
agenda
even
for
tomorrow,
so
I'll
put
it
for
the
tomorrow's
agenda
and
we'll
we'll
follow
up
on
that.
A
Okay,
thank
you,
fantastic
good
question,
okay!
Well,
it's
just
the
two
of
us
for
today
any
other
issues
from
my
side.
Okay,
I'm
trying
to
schedule
my
meeting
with
jim
this
week.
I
still
need
to
follow
up
on
how
I'll
handle
if
people
want
to
use
the
the
the
shared
zoom
meeting.
Fortunately,
even
though
I've
been
delayed,
nobody's
asked
to
do
that,
so
we
haven't
had
too
many
requests,
but
but
I
am
trying
to
land
a
meeting
on
jim's
calendar
this
week.
A
A
And
we're
gonna
stop
the
recording.