►
From YouTube: SIG Docs monthly localization meeting for 20210301
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
and
welcome
to
the
march
1st
2021
meeting
of
the
kubernetes
sig
docs
localization
subgroup
meeting.
As
always,
the
cncf
code
of
conduct
is
in
effect,
which
means,
let's
all
be
nice
and
talk
nicely
to
each
other,
and
so
the
first
thing
we'll
start
with
is
new
attendees,
and
so
it
looks
like
we
do
have
a
new
attendee
carmenville.
Would
you
like
to
introduce
yourself
yeah.
B
Hi,
thank
you.
Thank
you,
I'm
I
don't
have
much
to
say.
Honestly,
I
don't
know
I
was
I
was
saying
before
they
started,
recording
that
I'm
gonna
be
participating
just
as
a
listener
and
just
to
be
aware
of
what
what
what
are
you
doing?
What
are
you
doing
and
what
you,
what
are
you
planning
for
the
next
month.
A
Absolutely
so
a
couple
of
resources
for
you.
I
know
you're
interested
in
and
and
the
spanish
localization
team,
hopefully
you're
aware
that
they
do
have
their
own
slack
channel.
So
have
you
been
able
to
talk
to
them
on
the
slack
channel
yeah.
B
They
they
they
programming.
Oh
please
schedule
a
a
meeting
for
tomorrow.
A
Oh
fantastic,
and
for
what
we
do
in
this
subgroup.
If
you
look
in
the
agenda,
docs
that
I've
posted
in
the
chat
you'll
see
our
full
history
from
our
initial
meeting,
which
has
our
mission
statement.
But
just
to
summarize,
we
put
this
localization
subgroup
together
because
we
had
a
large
number
of
localization
teams
and
we
were
seeing
lots
of
duplication
right,
so
everyone
say
was
building
their
own
tool
to
figure
out
what
changed
in
the
english
to
figure
out
what
they
needed
to
localize
yeah.
A
So
so
so
it
really
is
all
about
just
identifying
best
practices
and
and
common
tooling
to
to
reduce
the
workload.
A
A
So
hopefully
you
can
get
it
from
there.
Otherwise,
just
just
dm
me,
on
slack
and
and
I'll
be
happy
to
to
give
you
what
you
need.
A
All
right
fantastic!
So
if
I
look
at
the
agenda
all
right,
we
do
have
some
things
on
the
agenda
that
soco
I
just
wanted
to
check
on
any
open
work.
Me
items.
I
know
I
have
one.
I
need
to
go,
go
back
and
follow
with
the
kaiming.
A
I
need
to
double
check
and
see
we
wanted
to
to
do
to
update
this
information.
That's
on
the
script,
maybe
put
it
on
the
main
page.
I
had
a
busy
month
last
month
I
finished
my
book
and
it's
gonna
be
published
in
june,
so
I
have
been
busy.
That's
why
I've
been
delinquent,
but
it's
coming
out
in
june,
and
now
I've
got
some
free
time
to
go
back
and
do
some
work.
A
That's
my
excuse,
so
I
had
that
one
action
item
and
then
I
think
if
I
double
check
soco,
I
had
an
item.
I
believe,
to
document
that
the
localization
team
is
translating
a
previous
version
of
the
docs,
the
content
snapshot
and
that's
okay,
to
merge,
prs.
A
And
and
you
you
were
going
to
work
on
an
existing
pr,
so
soca
was
there
an
update
on
that
on
on
on
that
action
item,
or
is
it
still
in
progress?
Did
existing
pr.
D
Oh
sorry,
there
is
existing.
There
was
existing
pr,
so
I
couldn't
work
because
of
some
complete
content.
So
since
the
previous
tier
was
merged.
C
C
A
Okay,
so
this
pr
can
now
proceed
as
a
conflicting
pr
has
been
merged.
Does
that
make
sense
right?
Okay,
all
right,
cool,
okay
status,
okay,.
A
Great
all
right,
okay
and
all
right
so
soca
we're
on
to
your
topic,
so
you're
gonna
give
a
korean
localization
update
and
this
is
all
being
recorded.
So
even
if
we
don't
have
a
big
crowd,
they
can
come
watch
it
afterwards.
D
Okay,
I
just
want
to
share
korean
localization
status.
As
you
know,
we
are,
we
have
a
branch
strategy
and
we
are
currently
working
on
120
ko5.
It
is
5
3,
five
korean
localization
branch,
and
it
is
based
on
master
branch
and
we
are
still
reviewing
some
pairs
on
ko5,
but
status
screen.
So
we
are
okay
to
go
and
this
branch
will
be
merged
to
master
branch
in
this
week.
In
this
week,
oh
wow.
C
C
A
Fantastic,
that's
great,
hey,
rael,
welcome
hello!
How
are
you
good
and
hopefully,
you've
met
carmenville
he's
looking
to
to
work
on
the
spanish
translation,
so
yeah.
A
D
This
item
is
about
the
prefix
syntax
of
caretakers
for
localization.
As
we
discussed
in
localization
sub
group
previous
meeting,
we
agreed
to
to
use
prefix
for
localization
pr
title
like
eo
dash
kko,
but
we
found
that
there
are
some
actions
from
english
acrobats
that
retitling
korean
localization
title
like
like
the
second
one
or
the
style,
seems
a
little
bit
different,
but
so
I
hope
to
double
check
which
one
is
a
prepared
way
for
localization
of
globe
and
cigarette
oxide.
A
Right,
I
believe
the
preferred
is
with
the
brackets.
A
Bracket,
I
believe
so
we
can
double.
A
A
Okay,
fantastic
and
then
it
looks
like
you
have
one
more
item.
D
Okay:
this
item
is
regarding
the
actually
in
last
year,
in
localized,
localization,
suburban
meeting.
We
discussed
this
issue
localization
related
files
without
authorship
to
localization
team
such
as
ko
toml.
D
A
Yeah,
I
think
I
think
what
we
did
is.
I
made
awareness
of
this
issue
to
the
sig
docs
working
group
and
the
sigdoc
leaders,
and
you
know
they
agreed
to
to
to
be
willing
to
make
sure
that
they
any
changes
you
needed
to
that
file
were
were
given
proper
attention.
So
so
I
think
we
were
going
to
try
and
make
sure
that
they
were
there
to
make
sure
they
could
do
merge
any
updates
you
needed
to
that
file.
A
I
think
I
think
the
problem
was
how
things
were
structured.
It
wasn't
easy
to
to
to
give
out
access.
I
believe
so
I
think
they
wanted
to
try
hey.
You
know,
you
know
contact
irvy
or
jim
angle
and
say
hey.
I
need
an
you
know.
We
we
need.
A
change
to
this
file
I
think
was
was
was
the
question
just
because
I
think
it
was
hard
to
set
up
the
permissions
and
they
didn't
know
how
to
change
it.
A
D
It
is
okay
for
us,
but
maybe
some
your
localization
team
make
inquiry
regarding
this
issue,
so
maybe
you
rather
to
be
documented
somewhere,
okay,
those
files,
we
don't
provide
oscillate
authority
to
those
parts
and
then
to
change
this
style.
You
need
to
request
it
to
figure
out
leader
or
english
approval
like
that.
D
D
A
A
A
For
an
expedited
review,
slash
approval
via
slack.
Does
that
sound
about
right?
I
was
updating
it
in
real
time
in
in
the
agenda.
A
Okay,
okay,
so
I'll
work
on
that
and
I'll
bring
that
up
to
them
and
make
sure
that
that
we're
going
to
do
that.
Okay,
sure,
any
other
open
item
soco
from
you,
no
guess
so:
okay,
thanks
great
update
soccer!
Thank
you
all
right.
Next,
we
have
on
the
agenda,
is
rael
rahel?
What's
going
on
so.
D
We,
where
we
have
in
the
spanish
team,
because
after
an
event
that
was
on
on
the
end
of
january,
we
had
the
kubernetes
community
day
for
el
salvador.
That
is.
D
So
after
that
event,
I
was
giving
a
talk
and
a
lot
of
new
falls
join
it
into
the
spanish
team,
but
it's
awesome
so
we're
trying
to
get
this
kind
of
inertia
that
we
got
from
that
event
going
on.
D
So
the
first
thing
we
did
is
and
thanks
to
to
camille
that
was
on
carmarin,
sorry
that
was
what
was
the
one
proposing
that
we
had
an
event
this
week
we
were
starting
a
weekly
meeting,
so
we
are,
can
it's
a
bit
overkill,
probably
having
weekly
meetings
for
the
team,
but
it's
something
that
we
discussed
about
them,
probably
for
the
first
weeks
to
get
things
started
and
build
a
bit
of
of
the
grounds
to
get
work
done.
D
I
think
it's
totally
good
thing
having
this
weekly
meeting
and
then
probably
we'll
move
to
something
more
like
the
weekly
or
something
like
that
and
and
that's
all.
This
is
the
request.
It's
still
pending
validation.
It
has
a
look
good
to
me,
but
I
need
someone
to
approve
the
the
protoquest
and
also
I
am
talking
with
marty
jackson,
that
was
on
one
of
the
zoom
admins
to
get
the
zoom
thingy
started
and
the
configuration
how
how
to
proper
do
the
meetings
with
zoom
and
then
afterwards
publishing
them
to
youtube.
D
So
that's
thing:
I
think
it's
a
really
good
thing,
because
for
the
last
year
was
been
a
bit
rough,
a
lot
of
people
just
disappear
from
the
team
and
we
are
trying
to
get
things
starting
again
and
that
really
hits
and
also
we
are
probably
switching
one
of
the
elements
of
the
spanish,
obviously
team
because
was.
B
Yeah
yeah
yeah
no
problem,
I
I'm
not
ready
to
be
on
live
streaming,
but
who
cares
anyway?
I
would
like.
I
would
like
to
know
if
you
know
how
is
this
process,
because
I
need
to
know
who
is
in
the
group
and
able
to
do
what
we
have
to
do.
I
mean
we
can
just
organize
what
what
we
have
to
do
and
and
it's
a
lot,
but
I
would
like
to
know
the
process,
because
if
I
read
a
page
and
there
are
a
main
or
master
and
dead
which
which
branch
like
should
I
work?
B
D
Tomorrow,
I'm
going
to
be
there
and
I
have
all
the
answers
to
all
those
questions.
So
don't
worry
right
now
we
are
working
on
a
particular
branch
flow,
but,
for
example,
we
are
getting
a
lot
of
knowledge
from
the
korean
team
because
they
are
doing
a
particular
strategy
to
do
branches
and
keep
everything
on
track.
D
We
are
not
dead,
yet
we
are
working
against
always
master,
so
we
do
afford.
There
is
a
kind
of
process
described
somewhere,
but
I
think
this
is
something
that
we
want
to
to
talk
tomorrow.
So
everyone
needs
okay,
let's
go.
How
will
we
start
no,
and
we
try
to
figure
out
the
current
documentation?
If
that
is
need
for
new
documentation
on
how
to
get
things
started,
we
probably
do
a
bit
of
call
of
review
or
existing
pull
requests.
How
the
flow
is
working,
how
to
pull
the.
D
So
we
are
we're
talking
about
a
lot
of
things
tomorrow
to
get
things
started,
so
everyone
knew
from
the
community
to
the
community
can
get
things
done,
kind
of
start
working
on
the
contributing.
I
I
mean
there
is
a
lot
of
work
yeah
I
know,
but
I
always
did
a
lot.
So
the
thing
is,
we
have
already
a
list
of
the
items
that
we
think
it's
most
more
important
because
we
are
going.
We
we
have
the
analytics
from
google.
So
we
know
what
pages
are
the
most
ones.
The
more
visited.
D
B
D
Yeah,
but
that's
one
the
thing:
what
we
are
adding
these
weekly
meetings
to
be
able
to
to
split
the
world
into
smart
chunks,
so
we
can
start
working
on
the
little
things
and
then
going
over
and
over
until
it's
already
it's
a
really
long
way
from
now
to
having
the
entire
site
in
spanish,
it's
a
really
long
way,
but
we
need
to
start
some
somewhere
so,
but
this
is
something
that
we
are
going
to
discuss
tomorrow
in
the
in
the
spanish
meeting.
D
So
everyone
knows
how
to
start
why
we
choose
that
particular
set
of
pages.
Why
not?
What
is
the
current
flow?
How
we
can
improve
the
flow?
Maybe
when
grabbed
some
things
from
the
korean
team
and
try
to
to
do
some
more
branching
instead
of
going
always
around
master.
The
thing
is:
we
are
a
really
really
small
team
till
then.
Last
week
we
were
a
one
man,
only
team,
all
two
men
on
the
team,
so
we
are
trying
to
get
things
done,
but
we
need
more
people.
D
Once
we
have
new
more
people,
we
can
do
more
ambitious
branching,
for
example,
and
maybe
trying
to
keep
track
of
the
the
upstream
versions.
But
we
are
not
that
yet.
So
we
need
to
get
things
some
base
and
then
maybe,
when,
once
we
have
much
more
or
less
the
the
site
in
spanish,
we
can
start
with
going
against
branches
and
keeping
releases
and
so
on,
but
we
are
far
from
that.
We're
going
to
be
there
in
the
future
for
sure,
but
we
are
not
yet
there.
D
We
need
to
start
things
slowly
and
get
more
people
involved.
Try
to.
For
example,
there
is
a
here
in
spain.
There
is
a
summit
in
in
march,
and
I
I
published
a
proposal
for
a
talk
about
kubernetes,
contributing
and
working
on
documentation.
So
that's
another
way
to
help
to
the
dominican
team.
If
you
have
a
meet
up
for
me
at
your
your
town
or
something
like
that,
you
can
also
do
a
talk.
We
have
a
lot
of
material
on
how
to
contribute
how
to
start
working
on
documentation.
D
We
did
several
hackathons
in
the
in
the
past,
so
there
is
a
lot
of
work
to
get
new
people
involved.
So,
but
everything
is
something
that
we
are
going
to
discuss
tomorrow
with
with
the
rest
of
the
team.
So
we
have
for
we
have
the
agenda,
so
you
can
go
to
the
agenda
and
any
question
that
you
have
right
now.
You
can
just
wait
down
it
there
and
we're
going
to
talk
tomorrow
about
that.
D
Yeah,
you
have
anything
any
questions
that
you
have
put
it
there
and
we
have
a
lot
of
things
to
work
about,
because
the
same
question
that
you
have
probably
new
falls
coming
to
the
project.
We
will
have
the
same
question
so
if
we
can
write
them
down,
write
documentation,
answering
all
the
ends
on
the
questions,
probably
that
the
next
one
we
have
a
better
way
to
start
working
on
that.
So
all
right
and
the.
D
D
B
I
I
joined
it
on
february
6th,
I
mean
open
my
own
meeting
with
people
that
speak
english
and
I
I
was
thinking
where's
the
spanish
tree.
A
Very
good,
hey
rael,
so
I
looked
at
your
pr
I
put
in
the
one
that
I
did
because
I
think
there's
a
separate.
I
think,
there's
two
files.
You
need
to
update
with
your
meeting
information,
so
you
might
want
to
look
at
mine
and
then
I'm
also
just
trying
to
see
who
I
who
I
asked
to
to
merge
my
pr.
I
think
it
was
bobby
tables,
but
I'm
trying
to
look
real
fast.
A
So
I
I
put
that
both
in
the
meeting
agenda
and.
A
A
Yeah-
and
I
think
I'm
just
checking
yeah,
I
can't
remember
unfortunately,
who
merged
my
pr
so
who
you
can
ask
to
to.
I
think
it
was
mr
bobby
tables.
A
A
D
A
A
D
Probably
we'll
be
all
set,
and
tomorrow
we'll
start
like
trying
to
get
the
things
a
certain
age,
because
there
is
a
huge
project,
but
luckily,
for
us,
spanish
is
one
of
the
top
languages
in
the
world.
So
we
have
a
lot
of
people
willing,
probably
to
to
help
with
that,
and
a
lot
of
people
will
write
it.
So
that's
a
really
great
great
position.
A
Okay,
I'm
trying
to
think
of
a
of
a
proper
spanish
proverb.
I'm
going
to
have
one
that
maybe
kind
of
works.
Cuando
el
rio,
suena,
piedras,
traje.
D
D
Is
something
like
where
is
out
of
noise
regarding
something
there
is
probably
some
throughput
behind
that,
so
maybe
make
a
bit
of
sense,
yeah
yeah!
I
did.
D
A
Trying
to
be
multi-multilingual
excellent,
so
we're
making
good
progress
on
that
front
very
great.
Are
there
any
other
topics
for
today
or
we
covered
everything.
A
Yep
and
and
and
ryle's
a
great
resource,
carmenville
he's
he's
done
a
lot
of
our
our
education
in
the
past.
He's
helped
out
with
that.
So
he
can
really
give
you
a
lot
of
great
advice
on
on
how
to
get
started
on
how
to
contribute
so
he's
going
to
be
a
great
resource
for
you.
A
Well
deserved,
okay,
so
I
think
we
made
good
progress
for
today,
any
other
topics
or
we
all
get
free
time
back.
A
All
right
I'll
take
that
as
we
are
good
to
go.
Thank
you
all
for
joining
great
progress
and
we'll
keep
moving
forward.
We'll
see
you
next
month.