►
From YouTube: SIG Docs Localization Subgroup Zoom Meeting for 20211101
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
Hello,
everyone
welcome
to
the
november
1st
2021
sig
docs
localization
work
group
meeting.
As
always,
the
cncf
code
of
conduct
isn't
is
in
effect,
so
please
be
nice
to
everyone
and
welcome.
Let's
see,
is
there
anyone
new
to
the
meeting
anyone
new.
B
A
A
Okay,
well
welcome
welcome
thanks
for
joining
us.
Okay-
and
I
know
anu
you've
been
here
before
so
welcome
and
soco
you've
been
here
before
she's.
Have
you
been
here
before?
I
think
so,
right.
C
A
B
A
If
does
everyone
have
access
to
the
agenda?
If
not,
I
can
get
you
access,
just
slack
me
and
I'll
get
you
access.
Just.
Let
me
know
your
dm
me,
your
email
address
and
I'll
add
it,
and
then
you
know
what
I
can
do
for
now
is
share
the
screen
here.
A
So
give
me
one
second
I'll
be
happy
to
do
that.
Let
me
just
to
be
safe
turn
this
off,
okay
and
then.
A
Okay,
hopefully
everyone
can
can
see
the
the
agenda.
So
our
first
item
was
from
our
our
sig
docs
chairs,
but
they
asked
that
we
move
it
to
the
next
month's
meeting.
They
were
one
of
them's
on
vacation
and
the
other
one
had
a
conflict.
A
So
we'll
we'll
push
the
jim
and
tim
topic
to
next
month
and
that
gets
us
to
the
next
item
on
the
agenda,
which
is
soco
so
soco.
Please
go
ahead.
D
Sure
I
hope
to
share
current
status
of
korean
localization
team,
so
I
hope
to
share
to
update
okay.
First
of
all.
First
item
for
korean
localization
team
is
about
our
korea
localization
milestone.
D
Since
in
this
building,
there
are
other
localization
contributors.
I
hope
to
share
how
korean
localization
milestone
works,
so
maybe
a
year
later,
to
share
the
screen
from
my
site.
How
about
it
right.
D
I
think
you
can
see
my
screen.
Yes,
yes,
we
are
here
and
in
case
of
korea,
localization
team.
We
operate
a
milestone
and
for
for
one
milestone,
we
spend
around
three
weeks.
D
So,
as
you
can
see,
we
create
a
development
range
during
our
milestone
and
current
development
range
with
every
one,
2
2
ko
2,
which
means
we
are
working
on
one
one,
two
two
release
and
second
microphone
of
korean
localization.
D
We
have
pr
place,
outdate
and
also
versus
target
we
after
we
finish
our
localization
work
for
around
two
two
or
three
weeks.
We
emerge
two
master
branch,
main
branch
and
you
can
check
the
our
milestone
and
see
it
is
a
milestone.
We
create
a
milestone
when
we
start
new,
my
stunt.
D
This
is
ko2
and
in
one
milestone
we
there
are
very
important
issues,
open
issues,
two
issues.
First,
one
is
announcement
of
korean
localization
work.
D
So,
as
you
can
see,
we
announced
our
localization
marks
on
new
localization
master
like
this,
this
new
issue
we
create
ourselves
and
actually
for
to
share
our
progress
to
other
localization
teams
and
signals
and
signals
localizations
of
group.
We
wrote
it
in
english
letter,
so
this
issue
is
about
korean
localization.
For
this
french.
D
D
We
try
to
guarantee
the
review
of
peers
before
pr
please
and
then
we
leave
your
same.
Opera
voice
of
korean
sometimes
work
hard
and
we
try
to
build
it
to
the
target
8.
D
If
and
we
require
any
korean
localization
contributors,
this
issue
so
that
they
know,
when
is
the
deadline
for
the
pi
submission
for
this
milestone
and
another
important
issue?
Is
this
one
outdated
korean
content
in
table
one
two,
two
ko2
branch,
so
during
our
one
milestone
on
development
branch,
since
we
spent
two
or
three
weeks
during
that
time,
english
content,
original
english
content,
obstacle
content
will
be
changed
on
some,
some
parts
will
be
changed
and
since
we
already
translated
korean
based
on
the
outdated
english
content,
so
korean
contentious
also
should
be
outdated.
D
Actually,
those
english
contents
are
translated
in
korean
already,
so
we
can
check
the
english
content,
not
translated
in
korean
beyond
put
here
only
english
content
content
already
translated
in
korean
and
changed
are
here.
So
those
are
our
test
structure.
So,
as
you
can
see,
there
are
71
changes
right.
So
we
check
one
by
one
and
update
as
you
can
see.
We
work
like
this.
We
keep
updates
based
on
this
issue.
A
D
So,
as
you
can
see,
there
are
not
prepared
or
tests
should
be
completed.
Then
we
decided
to
merge
this
branch
that
we
wanted
to
ko
branch.
D
This
one
two
master
branch,
two
main
branch,
so
we
will
make
a
new
each.
We
will
open
new
pr
to
merge
this
branch
and
then,
after
we
merge
displace
to
main
branch,
then
we
close
close
this
milestone.
D
D
Since
we
could
finish
those
two
issues,
we
could
close
this
knife,
so
we
are
actually
keep
going.
We
keep
doing
this
job,
okay,
yes,
it
is
the.
I
already
explained
this
one
is
outdated
korean
issue
that
I
mentioned
before.
So
that's
all.
I
hope
to
share
how
korean
localization
tips
keep
korean
content
updated.
D
D
D
D
Branches
by
some
actually-
and
I
am
of
korean
team
team
members,
provided
this
one
and
I
think
you
can
sign
how
to
use
it.
D
Actually
broad
suggests
to
put
how
to
use
in
this
readme-
and
here
you
can
use
like
this-
you
can
just
put
a
language
option
in
case
so
korean
you
use
ko
here.
B
D
Air
commits
are
commit,
then
it
just
show
the
same
report
issue
report
as
an
output,
so
example:
okay,
is
this
tesla
for
clear
localization
by
stone
introduction,
and
if
you
have
any
question,
then
let
me
know.
A
No,
that
that
was
fantastic
soco.
That's
that's
really
helpful.
I
I
think
it's
a
great
process,
it's
a
very
simple
process,
but
with
the
tooling,
it
allows
you
to
to
easily
focus
on
what
the
next
work
items
are
for
the
next
release.
D
These
days,
we
are
facing
hard
times,
because
the
test
to
update
outdated
korean
keep
increasing
it.
E
D
A
So
yes,
if
we
can
get
more
more
work,
you
know
maybe
at
meetups
you
can
find
more
more
folks
willing
to
contribute.
That
would
be
great
but
you're
doing
wonderfully
so
you
know
keep
doing
it.
It's
it's
going
very
well!
Thank
you!
Yeah,
okay,.
D
Yes,
this
next
item
is
about
the
new
korean
localization
team
member.
I
hope
to
introduce.
Actually
we
accept
we
actually.
D
A
Sharing
yeah
great
great
update,
soco,
we
we
appreciate
it.
So
you
know
you
know.
The
korean
team
really
has
defined
and
implemented
a
a
a
great
process
for
doing
their
translations
and
it's
you
know.
They've
they've
submitted
the
common
tooling,
so
it's
very
easy,
hopefully
for
other
teams
to
to
use
the
same
approach.
We
we
highly
recommend
it
as
a
best
practice.
A
Great
stuff.
Is
there
you
know,
that's
that's
the
formal
agenda
on
evolve.
Did
you
want
to
talk
about
how
things
are
going
and
then
anyone
else
after
that
can
tell
us
how
things
are
going,
but
on
evolve?
Would
you
like
to
let
us
know
how
things
are
going
with
the
hindi.
F
F
A
Yeah
so
on
above
that's
great
progress.
So
so
let
us
know
how
things
go
and
we'll
look
for
an
update
next
month
to
see
how
things
are
going.
A
I
I
hope
so
and
I
I'm
gonna
tweet
it
and
put
a
snapshot
of
the
hindi
page
as
soon
as
it's
ready.
So
I'm
looking
forward
to
doing
that.
A
Oh
thanks
send
it
out
on
my
social
media.
Okay,
yes,
any
other
updates
for
today
on
evolve.
A
Okay,
okay:
ashish
did
you
have
any
updates
for
today
or
or
just
listening.
A
Okay,
okay:
are
there
any
other
topics
that
we
would
like
to
discuss?
We
have
a
short
agenda
for
today,
so
one
last
chance,
any
other
topics
to
to
discuss.
A
Okay,
well
fantastic
meeting
and
thanks
again
to
soco
for
for
going
through
the
korean
process,
and
we
look
forward
to
seeing
the
progress
for
the
on
on
the
hindi
translation
and
we
will
meet
again
next
month
and
thank
you
so
much
for
attending.
We
appreciate
it.