►
From YouTube: SIG Docs monthly localization meeting for 20210201
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
february
1st
2021
meeting
of
the
kubernetes
sig
docs
localization
subgroup.
Thank
you
all
for
joining
and,
as
you
all
know,
our
code
of
conduct,
cncf
code
of
conduct
apply.
So
everyone
treat
everyone
well
and
with
respect
and
thanks
everyone
for
joining.
A
A
And
so
all
right
people
are
adding
their
names
to
the
participant
list.
That's
great,
so
the
only
items
that
I
had
on
the
agenda
was
one
to
follow
up
on
status
from
open
work
items
from
last
year
and
then,
after
that,
an
open
discussion
to
see
if
there
are
any
items
we
wanted
to
focus
on
for
2021,
so
welcome
everyone.
A
A
B
A
Yes,
and
who
is
this,
this
is
this
your
first
time
here.
A
Fantastic
welcome
is,
is
there
a
particular
localization?
You
have
an
interest
in.
A
K
bueno,
that's
fantastic.
Well,
absolutely
welcome
what
we
do
here
in
this
meeting
and
you
can
look
in
the
google
docs
and
see
the
mission
statement.
And
what
have
you
is?
We
have
wonderful,
localization
teams,
many
come
up
with
different
innovations,
and
this
is
an
opportunity
for
us
to
share
innovations
and
collaborate,
so
each
language
isn't
building
the
same
tool
over
and
over.
I
think
that's
a
short
short
summary
okay.
So,
let's
start
looking
at
the
agenda,
so
we
had
some
status
items
for
last
year.
A
A
So
that
was
the
item
from
from
kai
ming
that
he
was
working
on
and
there
was
a
work
item
for
him
to
document
that,
and
he
says
we
have
a
script
that
does
the
that
handles
the
situation
and
the
script
has
a
long
comment
in
it
for
documentation.
A
So
one
question
might
be:
if
you
know
irvia
is,
is
that
enough
documentation
for
people,
or
does
anybody
want
to
make
that
more
explicit
and
take
the
comment
out
and
put
it
somewhere
in
our
in
our
in
our
localization
page
would
be
my
one
question,
but
but
from
coming
it
is.
It
is
at
least
documented
somewhere.
C
B
C
A
Yeah,
so
I'm
going
to
take
is
the
action
item
brad
to
see
if
kaiming
is
willing
to
do
this
or
brad
will
find
someone
maybe
himself
to
to
take
an
attempt
at
that
to
make
this
update.
A
All
right
excellent
now
the
other
items
I
think
are
soco
so
soco
I'll.
Let
you
describe
where
things
are
at
for
your
work
items
how's
that
sure
why
not.
C
Actually,
I
supposed
to
do
document
to
update
the
previous
version
of
our
document
in
case
of
typo.
Typo
is
very
simple
and
the
previous
version
of
our
document
is
just
a
snapshot,
so
it
is
okay
to
update.
I
adopt
the
changing
typo,
so
I
supposed
to
document
that,
but
I
couldn't
do
it
yet
and
I
will
there
is
open
pr
to
update,
contribute
to
localization.md.
C
You
can
see
the
link
so
currently
one
contributor
updating,
localization.md,
so
maybe
after
this
appear
completed,
I
will
work
on
to
modify
that
document
to
include
the
snapshot
versions,
type
of
pr.
A
C
B
B
A
Great
progress
and
then
there's
some
more
information
here.
So
the
note
that
the
china
team
uses
a
timestamp
based
tool.
C
D
C
We
have
discussed
several
script
localization
tools
to
keep
keep
synced
with
the
latest
english
document.
As
you
know,
the
english
documents
keep
changing
and.
C
C
So
the
basic
difference
is
that
korean
local
chinese
team
check
the
outdated
contents
for
each
pr.
C
But
korean
team
use
branch
strategy
and
we
check
it
during
between
milestones.
So
it
is
the
basic
difference
and
if
we
use
this,
this
document
so
generate
a
report
of
outdated
contents
in
contents.
Localized
contents
directory
by
comparing
two
localization
team-
milestone
branches,
for
instance
yeah.
We
use
this
this
script,
just
after
localization
branch,
switching
korean
localization
branch,
fitting,
for
instance,
level,
1
120
in
ko3.
C
B
C
So
actually
I
just
made
this
issue
and
basically
I
put
after
we
launch
run
this
execute
this
script.
We
can
get
a
report
and
it
is
just
copying
paste
of
that
report.
As
you
can
see,
there
are
20
outdated
contents
during
our
localization
branches,
so
it
is,
has
been
listed
and
you
can
check
which
one
is
very
should
be
hard
to
hard
work,
for
instance,
just
to
one
at
this
edition.
C
One
deletion
is
very
simple
and
you
can
easily
update,
but
sometimes
whole
documents
has
been.
Sometimes
all
documents
can
be
changed,
then
it
is
very
time
consuming
job.
So,
based
on
this
report,
we
share
the
jobs.
I
mean
we
assign
jobs
to
multiple
contributors,
so
you
can
check
in
the
bottom
comment.
Could
you
scroll
down
to
the
end
all.
B
A
Right
so
the
tool
generated
the
list
and
then
did
you.
You
manually,
create
this
issue
and
copy
paste
in
what
the
tool
creates.
Is
that
correct
right?
Okay?
So
so
this
is
a
great
process
right,
so
you've
got
a
tool
and
you've
got
a
process
of
of
of
taking
the
contents
of
the
tool,
creating
an
issue
and
then
giving
folks
the
opportunity
to
sign
up
for
work
right.
A
That's
fantastic
is,
is
that
does
any
of
this
need
to
be
documented,
or
this
was
just
an
education
for
the
rest
of
the
community
here
to
see
how
the
whole
end-to-end
process
is
working.
C
C
Okay,
but
I
checked
there
are
very
similar.
Similar
tools
are
included
in
the
circuit
directory,
so.
C
C
Sure,
as
I
mentioned
in
the
as
I
think,
that
sh
script.
A
Here
right,
so
so
you
put
a
description
of
how
to
use
this
already
so
so
my
guess
is,
this
work
item
is
complete,
then,
because
you
have
a
a
way
of
doing
things
and
it's
described
in
the
readme
yeah.
A
C
C
C
A
A
C
A
C
I
think
of
steam.
English
document
may
keep
changing
even
in
a
review
single
review
process,
so
I
think
it
would
be
very
hard
to
maintain-
and
it
is
just
can
be
done
by
a
team
maintainer
korean
localization
team
maintainer.
Also
we
can
get
a
showed
people.
We
can
get
contributions
for
updating,
outdated,
contentiously,
it's
not
the
duty
for
only
reviewers
and
providers,
so
it's
gross
and
also
we
have
cons
and
there
will
be
some
outdated,
localization
content
during
a
milestone
period.
C
A
A
The
only
thing
I
can
think
of
is
if
these
advantages
and
disadvantages
should
be
documented
anywhere
or
we
just
leave
them
here.
That's
the
only
thing
I
can
think
of,
but
but
it
seems
like
you
know,
you
know,
did
you
have
in
the
in
the
read
me
I
didn't
check,
but
did
you
have
hey
if
you
have
any
questions
contact
the
korean
localization
team
or
I
guess
people
would
know
to
contact
someone
if
they
have
questions
or
I
guess
they
could
come
here,
and
I
would
point
them
to
you.
C
C
And
so
forth,
go
ahead
just
post
a
question.
This
script
requires,
I
guess,
following
the
same
branching
strategy
as
the
korean
thing.
I
guess
so.
You
need
to
have
a
development
branch
that
is
upstream
with
the
english
version,
and
then
you
work
on
that
particular
branch
and
then
eventually
you
mess
these
branches
to
master.
So
you
are
checking
between
the
upstream
master
and
your
the
branch
all
the
time.
I
guess
so.
It
requires
this
kind
of
branching
strategy
for
for
the
rest
of
the
languages,
for.
C
From
the
spanish
team-
and
we
are
not
yet
following
this
strategy-
we
are
more
like
working.
We
are
a
very
small
team
and
we
are
trying
to
work
like
any
pull.
Request
goes
against
master
eventually,
so
we
are
not
doing
this
brand
require
because
we
are
yet
far
too
to
have
the
full
recommendation
in
spanish.
C
A
Yeah,
you
know,
certainly
it's
it's,
you
know
it's
it's
one
way
of
doing
things
and
if
and
if
it's
appropriate
for
your
localization
team,
we
want
to
make
sure
it's
it's
easy
to
learn
how
to
do.
I
mean,
I
think
I
think
that's
the
way
I
would
look
at
it.
I
think
that
the
china
team
will
always
probably
do
it
their
way,
but
for
new
teams
they
get
to
choose
and-
and
if
this
works
you
know,
if
yeah,
let
us
know
if
there's
any
more,
that
needs
to
be
documented.
C
Done
yet,
but
we
have
a
demonstration
actually,
in
the
first
meeting
of
this
localization
subgroup,
I
explained
how
korean
localization
teams
branches
trade
branch
strategy
works.
So
maybe
I
need
to
document
document
yeah.
C
Yeah
it
is,
it
is
actually
a
powerpoint
ppt
presentation
slide
and
it
can
be
also
shared,
and
if
you
need
more
documentation
on
that,
then
I
ca.
We
can
also
provide
it
we'll
be
very
happy
to
share
it
and
yeah.
I
will
share
the
presentation
again
in
the
subgroup
select
channel.
C
C
Maybe
that's
a
good
place
to
put
this
kind
of
how
the
the
korean
team
is
working
on
branching
on
his
approach.
Maybe
actually,
in
that
document
I
think
you
are
mentioning
the
contribute
to
localization
md
pile.
C
So
maybe
you
can
document
the
korean
localization
branch
strategy
first
and
then
maybe
you
can
check
it
with
the
contribute
to
localization.nd
in
the
website.
C
Actually,
yeah
is
very
briefly
introduce
how
korean
localization
branching
strategy
works.
Maybe
I
can
share
it.
C
C
C
C
C
So,
as
you
can
check,
there
is
section
for
branch
strategy.
That's
great.
I
didn't
see
that
yeah.
So
there
are
some
examples,
but
this
procedure
is
very
similar
with
korean
localization
team
branch
strategy.
C
A
A
Okay,
fantastic:
should
we
move
on
in
the
agenda.
A
So
we
got
that
I
think.
What's
next
was
I
think
kohei
was
going
to
investigate
if
the
korean
tool
will
meet
the
needs
of
the
japanese
localization
team.
I
don't
know
if
kohei
is
on
today.
A
Stands
for
localization
teams
look
into
adoption
of
adding
preview.
Okay,
so
I
believe
all
right.
Let
me
mark
this
one
right.
A
So,
on
the
next
one,
localization
teams
to
look
in
the
adoption
of
adding
prefix
for
the
pre-order
titles,
I
think
teams
started
to
do
that.
Correct.
A
Sure,
I'm
not
sure
yeah,
okay,
so
we'll
see
if
teams
are
starting
to
do
that,
I'll
have
to
follow
up
on
that
one.
A
So
that
would
be
interesting
and
okay
and
then
soca.
It
looks
like
you
added
some
items
here
below.
A
C
C
We
are
in
the
of
one
I
mean
localization
teams,
prefix.
C
Abroad,
what's
that
do
we?
This
are
we
discussing
about
the
localization
prefix
or
the
next
topic.
A
Well,
I
think
we'll
go
to
the
next
time.
It
looks
like
you're
willing
to
use
the
korean.
A
That's
okay,
so
it
looks
like
so
I
should
say
with
other
teams.
C
B
C
A
Okay,
so
we'll
see,
if
we'll
we'll
follow
up
there.
C
A
So
there's
two
soco:
yes,
okay,
yep,
so
we
should
just
make
this
a
recommendation
right,
something
sound
good.
Should
we
make
this
a
recommendation,
but.
C
A
C
C
C
Because
is
is
having
this
prefix
on
both
the
pull
request,
name
and
also
in
each
comic
message,
I'm
not
sure,
but
we
usually
I
mean
when
we
make
a
single
commit
with
coming
message.
Then
we
push
it
to
our
website
repo.
Then
the
automated
pr
title
is
same
with
coming
message:
okay,
yeah!
So
somehow
they
are
aligned
common
message
and
pr
title
is
aligned,
but
yeah.
C
Okay
right,
the
product
was
named.
I
think
it's
something
easy,
because
the
the
maintainers
and
the
owners
can
edit
the
pull
request
and
and
apply
the
convention,
but
commit
message.
It's
it
will
be
harder
because,
for
example,
at
least
in
the
spanish
team,
we
are
usually
new
faults
coming
all
the
time
so
having
them
to
follow.
This
policy
on
the
comments
can
be
out
of
work
because
they
usually
like
do
regular
comments,
and
then
we
try
to
help
them.
D
A
C
A
Okay,
so
do
I
need
to
document
that
somewhere
or.
A
So,
okay,
to
put
in
git
commit
message
as
well,
but
recommendation.
C
It
is
correct,
but
my
concern
is
that
it
is
hard
to
guide
to
new
contributors
yeah
actually
in
case
of
korean
localization
team.
We
don't
guide
pr
title,
but
they
usually.
C
So
since
they
follow
that
convention
it
is,
it
was
okay,
but.
C
Maybe
something
that
we
can
try
to
help
this
is
to
put
in
the
when
you
open
a
new
pull
request.
Then
pro
gets
you
a
message
like
welcome
nice
having
you
here,
and
this
is
your
purchase.
Maybe
why
not
some
information
there?
C
A
Right,
so
you
want
to
put
it
in
in
the
top
a
suggestion
message.
C
A
C
Just
for
localization
stream,
so
in
the
ci,
because
I
guess
this
is
run
by
sei.
It
does
this
message
for
the
thanks
this
the
preview
for
native
light.
There
are
a
lot
of
things
running.
Maybe
we
can
add
an
extra
step
just
for
the
website-
and
this
is
next
step-
is
information
about
how
documenting
or
how
to
work
with
the
augmentation
repo.
C
C
C
A
C
A
C
A
So
do
you
want
to
lead
that
conversation,
royale
and
and
we'll
all
chime
in
and
see
if
we
can
get
the
little
the
little
statement
that
it
should
say
we
could
do
that
on
our
slack
channel
and
then,
when
we're
happy
with
what
it
says,
then
we
can
take
it
to
sigdoc's
chair
and
see
how
we
get
it
in.
A
A
B
C
Yes,
we're
good,
we
hope
to
share
this
action,
and
korean
localization
team
started
representing
names
of
translators
for
blog
contents.
C
C
Actually,
in
korean
localization,
we
only
we
have
only
one
blog
post,
translated
blog
post
and
we
hope
to
add
more
so.
We
already
discussed
this
this
in
sega
docs
meeting
the
previous
cigarettes
meeting
and
we
have
agreement
with
the
participants,
so
we
hope
to
share.
A
C
A
Okay,
so
so
if
I
wrote
a
blog
article,
which
I
never
do
because
I'm
lazy,
but
if
I
wrote
one
and
let's
say
ryle-
decides
to
translate
it
to
spanish,
so
the
blog
article
would
be
translated
to
spanish
and
then
it
would
say
topple
translated
by
ryle
right,
fantastic
yeah.
C
C
B
C
Yeah
maintenance
from
korean
localization
team
hopes
to
be
involved
in
website
milestone,
maintainers
team
actually
milestone.
The
functional
functionality
is
useful
for
korean
localization
team
for
every
localization
korean
localization
branch.
We
make
milestone,
we
create
milestone,
and
we,
after
finish
that
branch,
then
we
close
the
milestone,
but
currently
we
are
using
github
gui
for
creating
milestone
and
assigning
milestone,
assigning
prs
to
milestone.
C
C
A
Oh
okay,
so
so
how
are
you
currently
doing
it?
If,
if
you
don't
have
the
ability
to
do
it,.
C
A
C
A
A
C
Yeah,
actually,
I'm
not
quite
sure,
but
usually
members
in
korean
korean
localization
members
who
work
on
branch
fishing
job
they
sometimes
require
to
use
milestone
functionality
and
currently
to
do
the
milestone
branching.
My
milestone,
I
mean
friendship,
switching
job
we
require
to
have
maintainer.
A
Are
enough
so
so
there
really
isn't
an
ask
from
the
korean
team.
It
sounds
like
the
korean
team
has
a
solution.
C
C
It's
not
the
question,
but
I'm
not
sure
and,
as
I
know
at
least
one
localization
team
maintainer
is
involved
in
the
milestone
maintainer
team.
I
saw
a
guideline
how
to
initiate
localization.
C
A
C
A
Okay,
so
so
the
question
is,
is
is
what
I'm
trying
to
to
see
is
is?
A
Are
you
suggesting
that
the,
if
it
be
updated,
documentation
wise
to
say,
hey,
each
each
team
make
sure
you
have
somebody
who
can
can
be
on
the
website
milestone
maintainers
team,
I'm
I'm
trying
to
to
to
capture
what
the
ask
is
here.
C
I
wanna
know
the
procedure
to
be
involved
in
that
team,
making
a
issue
in
cognitive
community.
I'm
not
sure
how
to
do
that.
C
A
C
A
C
B
C
A
Okay,
so
we
got
that
highlighted.
Okay
great
looks
like
we
are
out.
We
use
the
full
hour,
so
I'd
like
to
say,
if
there's
any
more
issues,
but
we're
kind
of
out
of
time,
but
we
can
cover
them
in
the
next
meeting
any
any
last
real,
quick
issues
that
need
to
be
discussed
before
we
close
for
the
day.
A
All
right
well
great
meeting.
We
filled
the
whole
time.
We
got
some
action
items
and
we'll
see
everybody
next
month.
I'll
do
the
quick
thing,
five
more
three,
I'm
really
terrible
at
that.
So
I'm
not
gonna.
Do
it
we'll
see
everybody
next
month
thanks
everyone
bye,
bye,.