►
From YouTube: SIG Docs Localization Subgroup Zoom Meeting for 20210405
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
monday
april
5th
2021
meeting
of
the
cube
localization
subgroup
meeting
and,
as
we
know,
we
we
run
under
the
code
of
contact
guidelines.
So
please,
let's
all
be
nice
to
each
other,
and
this
meeting's
being
recorded.
A
A
So
there's
that
and
I'll
pull
it
up.
Okay,
so
we've
got
a
short
short
agenda.
I
think
today,
but
let's
just
reel
through
go
through
real
quick
go
through
some
open
work
items.
A
One
of
the
things
that
we
had
from
the
previous
meetings
was
a
need
to
update
documentation
of
the
lsync
dot,
sh
script
in
the
readme
markdown
of
the
script
folder,
and
so
thanks
tim
and
sun
tzu
and
for
and
for
coming
for
reviewing,
but
that
looked
like
it
was
done
and
it
was
done
well
tim.
I
I
read
that
that
was
that
was
perfect,
so
that
was
great
and-
and
the
next
thing
I
had
was
also
for
tim-
is
checking
on
the
status
of
the
open
issue.
A
So
you
know
chuck,
you
know
making
changes
approval
by
the
sig
localization
teams,
so
tim
I
saw
that
you
opened
the
issue
which
is
fan.
Oh
no,
it
wasn't
you
who
opened
the
issue
was,
somebody
else
opened
the
issue,
but
you've
been
commenting
on
it.
What
is
the
status
of
that.
B
B
An
english
language
tunnel
file
and
a
korean
language
tumble
file
and
an
italian
tunnel
file.
You
still
do
they're,
moved
to
a
different
location
inside
the
data
directory
for
convenience.
Okay,
each
of
those
is
in
its
own
directory.
So
there's
a
directory
for
german,
a
directory
for
korean
a
directory
for
japanese
and
that.
A
Tim,
that's
absolutely
brilliant,
absolutely
brilliant!
That's
awesome!
So
so
everybody
gets
what
they
need:
they'll
have
their
own
owner's
file
and
the
and
and
when
they're
updating,
it's
just
symbolic
links
to
the
real
ones.
Correct
and
life
is
good.
B
C
A
All
right
we'll
have
to
see,
but
I
think
it's
worth
a
try
right,
we'll
see
what
happens
I
mean
I
mean
symbolic.
Links
are
pretty
pretty
universal
right.
That's
a
pretty
common
thing
to
do
and
you.
A
What
I'm
hoping
and
and
obviously
the
repo
wow
this
is
awesome
tim,
so
so
there's
a
pr
it
hasn't
merged.
Yet.
Is
that
correct?
It's
under
review.
A
Yeah
soco
has
already
put
it
in
the
and
and
the
meeting
agenda
doc.
So
that's
great
thanks.
C
Yeah
korean
team
localization
team
have
waited
this
kind
of
improvement
in
this
month
around
one
years
one
year.
B
I'm
very
pleased
to
empower
localization
teams
to
do
their
own
thing.
A
Tim
you're
going
to
be
very
popular
you're,
going
to
be
very
popular
person.
So
thank
you
so
much!
That's
awesome!
That's
that's
a
great
solution!
So
as
soon
as
it
merged
words
we'll
get
the
word
out
and
you
know
soca
what
we
need
to
think
about
is,
after
it
merges
the
best
way
to
document
this
right,
we'll
think
about
the
best
way
and
where
to
document
this,
so
other
teams
are
aware
of
it.
A
So
we'll
worry
about
the
documentation,
but
this
is
awesome
tim.
This
is
great.
You
gotta
come
more
often
actually
team.
A
Okay,
yeah
yeah:
let's
see
what
we
can
figure
out,
so
you
know
we'll
get
some
documentation
for
when
it's
worked
merged,
but
this
is
this
is
great
progress.
All
right
tim
you
got
to
come
more
often.
This
is
great
all
right,
so
that
issue
is
on
its
way
to
to
being
happily
resolved,
that's
awesome
and
then
then
we'll
go.
I
guess
to
soco's
items
so
soco,
please.
The
floor
is
yours.
C
Thank
you
blood.
I
have
to
share
a
status
of
korean
localization
and
price
tag.
Theme
is
for
the
korean
localization
milestone
and
from
the
previous
localization
service
meeting
we
have
merged
the
three
korean
development
branches
ko567.
C
C
This
base
of
this
branch
will
be
released.
One
point:
twenty
twenty
twelve
one
frenchy
and
this
branch
is
only
for
updating
outdated
translations,
so
we
will
check
it
and
update
it
and
debut
one
point.
A
C
C
C
Yeah,
thank
you
for
correcting
the
mistake.
The
oh
sorry,
sorry
are
heroes
like.
C
B
You'll
talk
about
back
ports.
Are
you
talking
about
back
porting
localization
fixes.
C
C
C
C
We
will
release
kubernetes
version,
one
two
one
release
and
then
we
will
watch
table
table
one
point:
two:
one
to
master
right.
B
Well,
I'm
just
I'm
not
expecting
to
have
a
release
dash
1.21
branch,
a
branch
with
the
name,
one,
sorry
with
a
branch
with
the
name
release
dash
one
point:
two
one
might
not
exist
when
you
want
it
to
right.
It's
not
a
thing
that
I
think
we
guarantee
to
have
available
during
the
the
point
of
time
when
1.21
is
the
primary.
Is
the
current
release.
C
B
C
Any
people,
people
new
release
to
master
like
table
1.
2.1,
will
be
merged
to
master
soon
and,
as
I
know
just
before,
merge
we
make
a
snapshot
for
that
for
master
branch.
Just
before
the
master
devil
branch
is
merged
to
master
we
snatch
up.
A
B
B
A
B
A
A
Okay,
now
we
got
it
right
right,
so
your
dev.120
ko8
is
based
on
release.120,
because
that
had
the
new
stuff
for
release120,
because
you
wouldn't
want
to
be
putting
1.21
into
a
1.20.
Does
that
make
sense
right,
okay
and
then
for
1.21-k01,
you
can
go
after
you'll
go
after
the
mat.
It'll
come
from
the
master,
the
master
branch,
because
tim's
saying
hey
it'll,
be
after
when
we
cut
over
and
we've
moved
all
the
1.21
features
into
master
tim.
Did
I
get
that
right.
B
Of
purpose,
I
believe
that
the
purpose
of
the
branch
dev
dash
1.20
co,
dot
8.
The
purpose
of
that
branch
is
to
is
to
round
out
any
remaining
items
that
happen
between
the
current
freeze
and
the
release
date.
One
or
two
things
might
change,
and
that
is
what
the
purpose
of
that
is
to
catch.
The
last
few
things
very
thorough
right.
C
A
C
This
release
koa
in
case
of
koa.
We,
it
is
poor,
release
one
point
to
zero
and
sometimes
people
might
want
to
see
the
previous
version
in
even
in
the
previous
version
of
the
website,
we
hope
to
align
with
english
document.
C
A
I
don't
know
what
the
name
of
the
branch
was
tim
when
it's
got.
The
features
is
that
dev
branch-
I
guess.
A
The
1.20-k08
was
just
more,
I
thought
just
more
translations
and
what
they
were
worried
about
for
getting
a
little
more
of
1.20
translated
right.
They,
if
I,
if
I
understand,
soco
how
how
the
korea
team
does
it
you,
you
kind
of
have
these
little
sprints
right
where
you
say
we're
going
to
do
these
items,
then
these
items,
then
these
items
is
that
correct,
socal.
A
So
when
you
say
updating,
outdated
translations,
that's
where
you've
run
the
tools-
and
it
said:
hey.
These
pages
have
changed
right,
and
so
that
gives
you
your
list
of
things
that
need
to
be
retranslated,
because
the
pages
change
from
the
previous
release,
a
previous,
I
guess
branch-
is
that
correct.
Soco.
A
C
Okay,
that's
all
for
the
sharing
korean
localization
maxton
and
we
hope
to
share
a
new
korean
team
member
great.
C
Organization
member
has
been
added
based
on
the
localization
korean
localization
contributions.
It's
mainly
name
is
actually
he's
my
quality,
fantastic.
A
A
A
Yeah
well
well,
thanks
to
him
and
thanks
to
you
for
your
your
innovative,
symbolic
link
solution.
You
know
we've
been
dealing
with
that
for
quite
a
while
and
hopefully
we'll
see
that
merge
soon
and
we'll
get
the
word
out.
Oh,
do
you
have
another
issue?
Soco,
oh.
C
Yeah,
okay,
I
hope
to
check
if
there,
if
we
have
any
chance
to
support
it
with
some
zoom
account
for
localization
teams.
B
C
Yeah
and
in
case
of
korean
localization
team,
we
have
our
own
account.
Actually
it
is
my
account,
but
maybe
I
will
be
changed.
C
I
mean
I
will
be
released
from
korean
localization
team
leader,
one
day,
freedom
yeah,
someone
needs
to
provide
a
gym
account
and
I'm
not
sure
we
can
officially
support
it
with
some
general
account.
I
hope
to
check.
A
C
C
A
What
we
do
and
we'll
see
how
well
it
scales
is,
you
know
you
go
talk
to
to
the
chair
and
jim
angle
and
jim
angel
and
and
and
you
asked
to
have
the
user
id
and
password,
and
you
say
when
your
meeting
is
hosted
and
then
you
can
host
your
zoom
meeting
now.
That's
worked
so
far.
I
guess
because
we've
made
sure
that
two
people
haven't
needed
the
zoom
meeting
at
the
same
time,
so
I
think
it
comes
down
to
and
and
we
we
probably
need
to
to
formalize
this
tim.
A
I'm
thinking
that
to
make
this,
I
think,
we've
just
been
getting
lucky
we'll
have
to
you
know,
talk
about,
you
know
what
are
the
policies
for
when
we
can
share
the
zoom
accounts?
Maybe
it's
on
a
first
come
basis.
Eventually,
I
so
far
it's
been
okay.
Until
we
get
two
two
translation
teams
that
want
the
zoom
account
at
the
same
time
right
then
then,
then
the
wheels
fall
off.
A
Yeah,
so
what
I
can
do
is
I'll
take
the
to-do
on
this
one
soco
I'll,
open
up
the
issue
and
and
see
you
know.
You
know
you
know,
for
the
near
term.
Is
there
a
near-term
solution?
You
know,
can
we
just
share
yet
again
with
one
more
account,
but
but
I
think
we
want
a
more
longer
term
scalable
solution
and
and
potentially
maybe
there's
an
extra
zoom
account
so
I'll
I'll
open
up
the
issue
on
that
one
soco.
A
Let
me
let
me
let
me
put
the
let
me
fill
that
out
action
item,
brad
to
open
issue,
to
discuss
policies
for
sharing
existing
zoom
account
and
conflicts.
A
Teams
they
capture
that
correctly
soco
sure
definitely.
C
C
C
So
if
there
is,
this
kind
of
support
will
promote
other
new
initialized
teams,
mm-hmm.
A
And,
and
so
can
you
just
put
in
the
document
what
what,
what
day
and
time
the
korean
team
meets,
because
you
know
the
first
thing
I
would
see
is
you
know?
Is
there
any
conflict
with
existing
meetings
so
what
time
utc
on
what
day.
A
B
A
A
Also
mention
so,
do
you
have
the
meeting
on
the
official
calendar,
because
the
other
thing
is
to
get
meeting
on
the
shared
calendar.
C
A
I
think
some
of
the
other
ones
do
and
then
I
mean
do
you,
have
your
meeting
show
up
in.
A
Fast
yeah
yeah,
your
meeting
is
there
okay,
so
your
your
meeting
is
showing
up
all
right,
so
you
did
do
that.
So
you
did
do
that,
which
is
great,
which
is
your
meeting
is
showing
up
here.
This
is
the
important
place
it
needs
to
show
up.
So
it's
there,
but
it's
not
on
the
sigdoc's
calendar
which
it's
nice,
then
you
know
people
get
a
reminder
or
what
have
you
take
a
look
at
the
calendar
so
I'll
follow
up
on
that
as
well.
Soco.
C
Oh
okay,
okay.
I
I
think
we
need
to
check
our
june
calendar
and
actually
in
the
previous
localized
korean
localization
team,
leader,
jun,
jun,
juni,
okay,.
B
C
This
calendar
and
he
kept
supporting
changing
the
date
for
the
schedule,
so.
A
Well,
let
me
ask
you
this,
I
mean,
maybe
you
like
it
the
way
it
is.
Maybe
that's
not
as
an
issue
then
do
you
like
having
your
own
calendar?
Is
that
easier?
Does
the
does
the
meeting
move?
A
lot
I
mean
the
nice
thing
about
the
sig
docs
calendar
is
if
the
meeting
isn't
moving
a
lot,
you
don't
have
to
bother
the
chairs.
A
C
Let
us
think
about
it
and
sure,
maybe
it
is,
it
has
been
issued
based
on
sharing
the
tumor
count,
so
we
will
think
about
it
because.
A
C
C
A
Fantastic
those
stays
by
weekly,
okay,
so
yeah
we
can.
We
can
track
down
the
policies
for
sharing
the
zoom
account
I'll,
get
that
on
the
agenda.
Anything
else
for
today,
soco.
A
A
No
further
questions
your
honor:
what
is
the
one
british
phrase
someone
taught
me
cop
to
the
gov?
Is
that
right?
Did
I
get
that
right,
cop
to
the
government?
I
recognize.
A
But
anyway,
yeah
henry
nash
who's
over
well,
he
used
to
be
in
london,
but
now
he
lives
in
a
beach
house
somewhere
but
yeah.
He.
He
had
told
me
a
phrase
that
he
used
a
lot
about.
I
got
a
cop
to
the
gov
on
that
one,
but
I
guess
that's
not
universal.
A
Maybe
it's
a
generational
thing.
I
don't
know
a
little
bit
older,
all
right,
that's
all
we
have
for
today.
So
thanks
everyone
for
attending.
Thank
you
all.