►
From YouTube: SIG Docs monthly localization meeting for 20201102
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
A
The
the
meeting
date
for
today
is
november,
2nd
2020
and
please
follow
the
the
cnc
cncf
code
of
conduct
guidelines.
So
if
we
go
look
at
the
agenda-
and
I
will
put
it
into
the
the
chat-
if
you
don't
already
have
it.
A
A
So
that
is
in
there
and
if
you
don't
have
edit
rights,
just
dm
me,
brad,
topel
and
I'll
make
sure
to
give
you
if
you're
going
to
attend
the
meeting
edit
rights
just
some
logistics,
the
that,
with
the
time
change,
we
should
have
met
an
hour
earlier.
That
was
my
mistake,
so
I
I'm
gonna
update
the
thing
to
always
just
say:
1500
utc,
because
that
was
confusing
for
people,
which
means
our
next
meeting.
A
We
will
be
meeting
an
hour
earlier
so
again
that
that
somebody
at
least
updated
it
for
the
day.
To
hide
my
shame.
So
whoever
did
that?
Thank
you
so
much,
but
but
in
general,
we're
gonna
put
this
back
at
1500.,
correct
irvy.
Does
that
make
sense.
B
A
Okay,
so
thank
you,
everyone
for
putting
up
with
with
my
inability
to
do
the
time
change
properly.
A
A
So
at
this
point
soco
I
am
going
to
hand
over
to
you.
C
Okay,
thank
you.
As
we
discussed
the
previous
in
previous
meeting,
I
prepared
the
overview
for
korean
localization
team
and
everybody's
management.
I
will
share
my
screen.
B
C
C
Comments:
okay:
first
of
all,
we
discuss
and
decide
any
issues
related
with
korean
localization
and,
like
any
other
six,
we
have
select
for
communication
flexioner
and
we
do
bi-week
limiting
and
we
open
the
meeting
notes
and
through
those
meetings
we
make
the
guideline
for
korean
localization,
and
actually
we
decide
how
to
translate
the
english
term
to
korean
tongue,
grossly.
C
C
Okay,
I'm
going
to
actually
other
localization
things.
We
hope
to
would
want
to
know
how
to
manage
the
branch
localization.
They
will
develop
french,
so
I
hope
to
discuss
it
in
in
detail.
C
There
is
master
range
and
development
branch
and
for
master
range
we
make
korean
localization
branch,
and
this
localization
branch
is
for
only
for
the
korean
translation
reason.
Why
we
make
this
kind
of
french
is
that
the
english
branch
in
the
master
range?
The
original
document,
english
documents
keep
changing
so
to
translate.
We
need
a
kind
of
checkpoint.
C
C
And
master
branch
about
the
new
wine
over
the
lily
release,
sega
dogs
release
the
previous.
We
make
the
release
branch
and
when
the
developer
has
been
converted
to
master
and
keep
going,
then
we
generate
two
table
branch.
First,
one
is
the
queen
local,
stable
balance
sheet
for
brand
localization
job
for
the
master
range,
and
we
keep
going
that
and
we
also.
C
C
C
We
make
the.
If
you
have
any
question,
tell
me:
don't
hesitate
so.
A
This
is
brad,
I
have
a
question
you're,
creating
a
branch,
but
then
most
of
the
changes
in
your
branch,
I
thought
were
going
to
be
in
the
korean
folder.
A
Yet
you
said
you
were
the
reason
you
created
the
branch
was
you
were
worried
about
changes
in
the
master,
so
so,
what's
an
example
of
a
change
in
the
master
that
that
you
needed
to
worry
about,
even
though
most
of
your
work
was
in
the
korean
folder,
I
guess
you
were
worried
about
higher
level
changes
like
changes
to
css
or
is
it?
Is
it
those
types
of
changes
that
you're
worried
about?
There
must
be
some
type
of
changes
that
you're
worried
about.
That's
why
you
created
the
branch.
C
B
C
Okay,
if
we
yeah,
if
we
use
the
initial
version
of
the
hello,
hello,
world.nbc
and
we
started
translate
and
someone
pr
opened
the
pr
with
the
translative
document.
But
during
the
review
process
we
can
notice
that
the
english
document
already
changed
or
deleted.
Then.
A
A
Right
so
it
sounds
like
what
you're
saying
is.
It
would
be
incredibly
frustrating,
as
someone
tries
to
start
translating
a
page.
Maybe
they
get
halfway
through
it
and
then
they
somehow
look
and
the
whole
page
has
changed,
and
it's
just
much
much
safer
to
just
create
the
branch
and
work
off
the
branch
and
then
after
the
translation
two-week
cycle,
then
it
sounds
like
you
merge
in
and
worry
about.
A
If
the
page,
I
guess
when
it's
time
to
merge
in,
is
that
when
you
notice,
if
the
page
might
have
changed,
that
you
translated
or
or
or
do
you
just
merge
in
because
you're
the
korean
version
and
you're
just
translating
the
older
page,
so
what
happens
when
it's
time
to
merge
in
and
the
page
that
was
translated,
the
english
version
you
realize
has
changed.
That
is
my
question.
C
Yes,
actually,
I'm
I
can
we
work
first
and
we
handle
the
outpatient
content
by
using
another
pr.
C
So
I
can
explain
from
the
another
slide:
okay,
okay,
we
can
sure
okay,
I
will
keep
going
from
this
slide
and
we
make
branch
for
the
those
regions
and,
as
you
can
see,
we're
making
some
branches
and
country
it
is
table
1,
19,
ko4
and
when
we
make
a
new
french
table
french
and
we
set
the
netelli
pie
for
libya
and
we
have
fossilization
for
the
setting
the
korean
branch
to
use
the
dateline
review,
and
then
we
make
a
milestone
to
notify
the
prp
schedule
and
branchboard
schedule.
C
And
in
this
milestone
we
include
usually
four
two
issues
and
two
peers.
It
is
used
for
the
maintenance,
maintenance
region
and
first
one
is
issued
to
invite
an
issue
to
invite
contributors
and
notify
the
schedule
for
the
table
branch,
and
next
one
is
issue
for
outdated
parts.
That's
the
product
asked
to
me
just
before,
and
we
handed
this
issue
by
opening
up
a
pair
to
reserve
that
outdated
content.
We
actually
take
the
difference
in
the
english
document
between
two
branches
and
then
there's
difference.
C
Then
the
update
korean
content
or
that
procedure,
so
we
update
korean
korean
documentation
and
then,
finally,
after
we
do
the
localization
job
and
then
we
finally
merge
that
table
branch
to
master
by
opening
up
here.
So
those
poor
issues
or
peers
are
very
important
for
korean
localization
job
yeah
and
I
am
going
to
yeah.
I.
A
C
No
problem
and
this
issues
to
invite
contributions
for
korean
local
localization
and
we
hope
to
verify
the
contributors
the.
What
is
the
current
korean
localization
level
branch.
So
we
use
we
open
this
issue
with
english
and
the
other
side
is
korean,
so
you
can
check
it
in
english,
this
issues
for
korean
localization
or
ko4
branch,
and
we
hope
to
get
any
localization
contributions
called
korean
and
also
we
in
korean
localization
team.
C
C
And
when,
after
we
open
that
headquarters
issue,
we
find
out
what
is
outdated
types
for
you
branch
and
we
use
a
tool:
python
2,
the
korean
localization
branches.
Actually,
we
already.
C
We
already
put
this
script
in
our
website.
C
Directory,
so
you
can
check
it
through
the
upstream
and
with
this
kind
of
comment,
we
can
generate
a
report
of
outdated
content
in
content,
language
directory,
for
instance,
korea,
ko
by
comparing
two
localization
team,
milestone
branches.
So,
for
instance,
we
can
use
like
this.
This
script
and
call
ko
range
will
check
different
speed
changes
in
english
documents.
C
C
C
So
it
is
also
helpful
to
issue
so
someone
tried
to
it
then
actually.
C
C
Korean
localization
guideline
document
or
special
document,
and
in
that
document
we
have
some
kind
of
information
for
team
master
management,
part
and
korean
translation
style
guide,
as
well
as
the
glossary
part
and
then
based
on
that
guide.
Contributors
provide
the
translations
in
prs
and
we
improve
the
quality
of
localization
by
evening
process.
C
C
C
C
We
start
the
another,
we
make
another
branch
and
keep
the
two
weeks
job
again
again
again:
okay,
I
introduced
the
branch,
management
and
french
switching
jobs,
and
so
it
is
a
progress
in
korean
localization
team
and,
as
you
can
see
in
the
two
sections
2018,
we
have
some
pure
localization
documents
and
now
you
can
see
there
are
lots
of
localization
document
and
localization
teams.
It's
very
good
to
see
those
and
kubernetes
websites.
C
C
And
we
checked,
we
actually
focused
on
the
the
document
part,
not
the
blog
part,
and
when
we
check
the
number
of
localized
types
longer
localized
nd
parts,
then,
as
you
can
see
in
document
part,
we
have
maybe
seven
sections
and
you
can
check
it
through
check
it
through
the
directory
and
actually
our
first
priority.
C
Translation
priority
was
tutorials
part
and
second,
priority
was
concept
part
and,
as
you
can
see,
we
for
the
concept
part
we
already
almost
covered
and
priority
tutorial
part
is
also
almost
covered,
but
we
still
have
lots
of
job
to
do
in
tasks
and
reference
part.
So
maybe
once
we
prepare
the
concept
and
tutorials
and
we
will
keep
going
to
the
the
other
parts
as
well.
A
Thank
you.
Thank
you,
soco.
That
was
outstanding.
That
was
an
outstanding
presentation
and
and
soco.
I
want
to
test
myself
and
see
if
I
really
got
the
important
points.
So
I'm
going
to
tell
you
what
I
took
away
from
your
presentation
and
let
me
know
if
I
missed
anything
so
the
key.
The
key
things
that
I
heard
were
one
you
have
two-week
development,
a
two-week
translation
cycle.
A
You
start
with
a
new
branch,
you
get
input
from
the
user
groups
and
what
was
really
really
helpful
in
the
process.
Is
you
also
have
a
python
tool,
I
believe,
to
identify
the
differences
between
your
your
two
branches.
So
as
you're
as
you're
doing
your
two-week
translation,
you
have
a
way
to
determine
the
differences
between
your
previous
branch
and
say
a
current
branch
that
the
two
branches,
the
tool,
tells
you
what's
changed
and
then
you
can
use
from
that
tool.
Those
are
the
files.
I
guess
that
you
would.
A
You
would
go
to
change
in
the
next
cycle
and
then
the
other
thing
I
took
away
is
when
it's
time
to
merge
back
into
master,
you
make
sure
to
squash
the
commits,
because
that
gives
you
a
much
cleaner
view
of
of
what
actually
occurred.
A
B
Would
you
mind
to
share
the
link
of
the
presentations
in
the
talks
that
we
have
so
maybe
the
one
that
means
these
presentations
can
read
it
later.
C
Sure
I
will
I
will
share
it
through
the
selection.
B
A
C
A
Now,
where
is
this
tool
stored?
Is
it
in
the
is
it
in
the
the
website
repository
itself?
Sure,
okay,.
A
E
A
A
C
Actually
that
script
has
been
developed
by
doctor.
He
was
the
emergence
of
korean
localized
team
team,
leader
yeah.
He
was
very
nice.
A
So
what
what
I
found
really
interesting
is
is
the
whole
process
that
you
have
seems
very
smooth
right.
It's
these
two
week,
translation
cycles
with
a
very
useful,
automated
tool
that
helps
you
define
the
differences
and
it
allows
you
to
to
to
organize
the
chaos
that
you
would
normally
hit
as
you're
trying
to
translate
the
english,
which
is
always
changing.
So
I'm
curious,
you
know:
are
there
other
processes
used
by
the
other
localization
teams?
A
Are
they
using
something
different
than
this?
Is
this
you
know,
or
is
this
the
best
practice?
It
would
be
curious
to
see
if
people
look
at
this
from
the
other
localization
teams
and
think
either?
Oh,
oh,
yes,
we
use
the
same
process.
This
is
the
best
practice
or,
if
other
teams
think
no,
we
think
we
have
a
different
process,
and
here
are
the
advantages
and
disadvantages
between
our
process
and
the
korean
process.
A
D
Actually,
I
I
talked
to
the
chinese
team
before
and
the
the
script
that
they
maintained
their
own
script
in
the
separate
repo.
If
I
remember
correctly,
okay,
what
they
do
when
they
want
to
differentiate
the
pages
they
compare,
I
think
the
commit
sha
and
the
timestamp,
so
basically
they
compare.
D
D
A
A
So
soco,
how
does
your
tool
do
it?
Just
curiously,.
D
C
Yeah
in
case
of
that
script,
we
actually
own
we
in
korean
ko
directory.
We
only
have
documents
so
that,
as
I
know,
the
script
check
the
korean
translate
price
and
we
find
the
same
pie
name
from
the
english
directory
and
then
pull
that
pipe.
There.
Here
is
the
pie
and
we
check
the
dick
whether
there's
changes
or
not.
C
Then
we
somehow
know
the
there's
korean
translated
parts
and
if
there's
aligned
the
english
document-
and
we
only
take
the
postcards
changes
and
we,
if
once
we
know
the
there,
are
some
prior
changes,
then
it
is
reported
to
us
and
we
apply
these
changes
to
korean
translated
parish.
A
Right
now,
let
me
see
if
I
understand
this,
so
you
have
a
let's
say
you
have
a
page
in
the
english
master.
Let's
just
call
it
page
foo
and
you
have
the
translated
version
of
it
in
a
certain
branch
you.
So
let's
call
that
foo
dash
ko
you've
got
the
korean
version
of
it
and
then,
when
you
go
to
your
next
branch,
when
you
run
the
tool,
you're
gonna
go
and
say:
okay,
well,
there's
there's
the
korean
version
of
the
page
of
foo.
Now
let
me
go
at
that
time.
A
Let
me
go
check
the
timestamp
or
use
git
diff
to
check
the
foo
version
of
that
from
that
branch
and
then
compare
it
to
the
one
in
the
new
branch
and
see
if
the
two,
if
the
english
version
changed
from
when
you
translated
it,
is
that
correct
or
or
am
I
messing
it
up?
Oh
that's
right:
okay
and
you're,
saying
you're
able
to
use
git
diff
to
do
that,
because
git
diff
is
able
to
to
do
that.
A
And
the
next
branch,
so
the
interesting,
the
interesting
question
is:
are
there
any
advantage?
If,
if
the
chinese
team
is
doing
it,
not
using
git
diff,
did
they
for
their
so
they're
doing
a
custom
way
of
doing
it?
We
think,
and
we
wonder
if
there's
any
advantages
for
their
custom
way
of
doing
it
compared
to
git
diff.
C
Actually,
it
is,
I
think
it
is
applicable
for
those
teams
who
use
the
branch
strategy
if
they
have.
If
chinese
team
has
a
devil
branch
similar
with
korean,
then
they
can
use
the
kind
of
tools
to
check
what
is
different
between
branches,
but
if
they
don't
use
then
maybe
they
need
to
do
it
for
each
part.
So
maybe
it's
a
little
bit
harder,
so
I'm
not
sure
it
is
applicable
for
them.
A
Okay,
so
let
me
let
me
see
if
I
understand
that
correctly,
the
way
that
your
diff
tool
works.
It
works
very
well
with
the
model
you
have
of
saying
we're
going
to
do
a
branch
for
two
weeks
and
then
do
another
branch
in
the
next
two
weeks
and
the
tool
is
really
tailored
for
that
process.
They
may
have
a
different
way
of
doing
the
tool
because
their
branching
strategy
may
be
different.
That's
what
I
interpreted
you're
saying
and-
and
you
know
the
beauty
is,
as
teams
can
decide.
However,
they
want.
A
Your
approach
is
very
well
documented,
and
then
you
know
if,
if
there's
different
ways
to
do
it,
we
make
sure
maybe
they
get
documented
as
well,
because
if
I
was
somebody
new
showing
up
for
my
new
language-
and
I
wish
I
could
think
on
the
top
of
my
head-
a
language
that
hasn't
been
translated,
I
can't
think
of
a
good
one,
but
let's
say
you
know,
let's
call
it
for
lack
of
a
let's
say
the
new.
A
Then
the
new
team
shows
up
and
we
could
say
well,
there's
different
ways.
You
could
do
this,
but
we
have
multiple
say
best
practices,
but
if
you
want
to
do
the
two-week
development
cycle
approach
that
that
the
korea
team
uses
here's
the
way,
you
do
it
and
here's
a
tool
that
makes
it
easy
and-
and
you
know
the
interesting
thing
is
you
have
this
all
in
now?
Is
this
in
all
in
the
on
the
localization
page,
or
this
is
in
your
localization
page.
C
Actually,
if
you
check
the
this
document
and
contribute
localizing
cognitive
presentation,
you
can
check
branching
strategy.
Okay,
right-
and
it
says
it
is
not
the
korean
document
in
this
english
document
and
you
can
check
similar
branching
strategies
with
korean
localization
teams.
Like
david
branch
like
this,
so
maybe
a
new
localization
team
comes
and
they
research.
C
C
Yes,
it
doesn't
don't
mention.
C
C
Because,
in
case
of
a
korean
localization
team,
we
korean
localization
team
members
are
very
similar
with
the
github
cigarettes.
Korean
owners
and
reviewers
is
very
same,
but
I'm
not
sure
for
the
other
teams
if
they
are
different.
For
instance,
if
there
is
various
liberals
in
for
one
language,
but
not
the
not
making
a
team
they
if
they
don't
discuss
or
some
issues,
then
I'm
not
sure,
and
I
think
they
are
hard
to
follow
the
those
branching
strategy.
A
But
but
your
tool
that
your
tool
will
work
will
work
correctly
if
they
follow
the
branching
strategy
described
on
the
page
already
correct
right.
I
will
improve
this
document
yeah
yeah,
so
you
might
as
well
add
the
the
the
tool
and
the
short
how
you
use
it
at
which
stage
that
would
be
fantastic,
and
you
know.
A
D
So
can
you
show
me
the
the
github
issue
you
showed
earlier?
Okay,
edition
deletion.
D
Yeah
this
one
can
you
share.
Let's
say
I
want
to
update
one
of
the
pages.
What
what
is
the
next
step
for
you.
D
Step
for
this
outdated
part
issue,
yeah,
let's
say
I
pick.
I
want
to
fix
the
content
en
slash
index
html.
What
what
should
I
do?
Should
I
and
then
run
git
div
in
that
page
to
see
that.
C
This
process
azure
and
we
report
bug
the
outdated
parts.
What
is
what
has
been
changed?
What
is
removed
and
we
provide
proposed
solution
of
the
show,
looking
large,
propose
the
solution
and
use
it
to
check
what
extensive
in
the
upstream
and
apply
the
upstream
changes
manually
to
korean
korean
korea.
Ko
directory
called
this
branch
and
we
provide
example.
C
C
What
actually
has
been
changed
and
we
opened
the
related
translated
korean
documents
and
we
applied
to
that
korean
localization
translated
korean
document,
so
change
according
to
the
english
candidates
and
make
up
here,
and
so
the
result
is
like
this.
C
For
those
korean
documents
for
those
english
document,
english
changes
and
if
you
see
the
changes-
and
we
updated
like
this
reason-
why
we
updated
this
korean
document-
is
that
english?
If
we
check
the
english
document
during
the
two
branch,
the
english
also
added
this
excitement
and
priority
1.0,
so
we
added
it
to
korean
azure.
So
actually
it
is
very
time
consuming
and
time
consuming
job.
Actually,
if
there
are
lots
of
english
changes,
then
when
we
open
this
pr,
we
need
to
do
lots
of
gel.
C
C
Then
it's
very
too
too
much
work
to
korean
localization
team.
So
it's
like,
so
you
can
you
can.
Actually
you
can
check
the
you
can
check
milestone
and
if
you
see
the
korean
milestone
milestone,
then,
as
I
mentioned,
there
are
four
main
issues
and
prs
and
you
can
check
how
how
it
works
works.
C
D
Follow-Up
question:
let's
assume,
there's
a
1000
lines
of
page
that
has
changed
right.
Let's
say,
there's
a
very
big
page
that
has
changed
roughly
20
30
lines.
C
Right
it
takes
it
actually.
So,
in
the
case,
even
though
it
is
updating
outdated
parts,
okay,
I
will
show
an
example.
C
C
C
E
C
E
In
japanese
translation,
we
only
have
like,
let's
say
like
three
to
five
active
contributors
on
each
milestone.
C
Yeah,
actually,
we
tried
to
get
more
contributors,
as
I
mentioned
before,
we
introduced
our
progress
to
coordinate
career
user
group
and
if
we
check
my
name.
C
E
A
A
The
key
thing
I
took
away
is
really
trying
in
your
country
to
engage
the
kubernetes
existing
groups
that
are
there
right,
there's
kubernetes
user
groups
and
doing
outreach
and
convincing
them.
You
could
really
use
their
help
in
translation
and
if
they
want
to
learn
how
to
contribute.
This
is
a
great
way
to
learn.
You
know,
look
for
the
people
that
I
guess
no
japanese,
know
english
and
are
just
trying
to
get
started
in
in
contributing
to
kubernetes
and
convincing
them
that
a
great
way
to
learn
more
about
how
to
contribute
to
kubernetes
would
be.
C
Actually,
I
did
a
presentation
two
days
before
and
those
are
various
efforts
to
invite
many
contributors.
But,
as
you
know,
all
contributors
cannot
keep
contribute
yeah.
Sometimes
there
are.
There
are
some
contributors
who
can
provide
lots
of
contribution
for
some
period,
but
they
cannot
keep
doing
and
we
keep
waiting
for
them
and
keep
call
them
and
try
to.
We
hope
to
promote
to
contribute
again
again
again
best
our
the
korean
localization
team,
invite
contributors.
A
Yep,
so
yes,
we
should
all
be
doing
outreach,
and
I
know
at
my
company
we
know
we
have.
We
have
ibm
and
and
japan
and-
and
I,
when
I,
when
I
encounter
those
folks
I'll
I'll
who
are
working
on
open
source
I'll
I'll,
encourage
them
that
hey
the.
If,
if
you
know
japanese
in
english,
we
we
could
use
some
help
on
the
translation.
A
A
A
I
much
personally
understand
that
the
process
much
better,
so
thank
you
so
much
soco
and
your
willingness
to
update
the
localization
document,
so
people
can
have
a
better
understanding
of
where
the
tool
the
diff
tool
is
in
the
in
the
branch
process.
I
think,
will
be
a
wonderful
addition.
So
this
was
a
fantastic
meeting.
We
were
pretty
much
out
of
time
any
any
last
closing
remarks
from
anyone.
E
A
E
A
A
So
so
everyone
we
got,
you
know,
let's
be
thinking
about,
for
our
next
monthly
meeting.
What
should
be
the
next
topic
we
cover
so
let's,
let's
all
and
I'll
I'll,
put
that
out
on
the
slack
to
think
but.
B
A
E
A
We
go,
I
did
it
real
fast.
Thank
you,
everyone
for
participating.
This
was
great
and
I'll
make
sure
to
get
the
time
slot
right
next
time.
I
promise
and
we'll
talk
in
a
month
use
the
slack
channel
if
you
need
to
talk
in
between.
Thank
you
thank.