►
From YouTube: SIG Docs Localization Subgroup Zoom Meeting for 20211206
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-
this
is
the
december
6
2021,
a
monthly
meeting
of
the
sig
docs,
the
localization
subgroup
meeting,
I'm
your
chair,
brad
topple
and,
as
always,
the
cncf
of
code
of
conduct
is
in
effect,
so
please,
let's
all
be
nice
to
each
other,
and
this
meeting
is
being
recorded.
A
A
Okay,
hopefully
everyone
knows
ray
natalie
you're
new
to
this
meeting
as
well,
any
anything
you'd
like
to
say
a
quick
intro
or
anything
or.
B
Yeah
sure
hi
everyone,
I'm
natalie,
I
I
do
open
source
for
wayfair
and
I
am
here
in
kind
of
like
a
sig,
docs
sort
of
capacity,
helping
out
sig
docs
with
a
few
things
and
generally
new
to
the
dock
space
for
kubernetes.
But
I
also
do
some
work
around
seaguth
and
help
them
out
a
lot
as
well,
so
just
want
to
say,
hi,
fantastic.
A
And
thanks
for
coming
and
getting
on
the
agenda
anyone
else
new,
first
time,
hey
oshie,.
C
Well,
welcome
hi
everyone.
My
name
is
sochi
and
I'm
a
computer
science
engineering
student
from
india
and
currently
working
as
an
intern
at
cloud
yoga
yeah,
that's
my
first
sick
docs
meeting.
A
A
E
E
Yeah,
so
well,
I'm
here
actually
for
the
123
release
of
the
release
lead.
I
wanted
to
give
a
quick
warning
that
k
website
will
be
frozen
later
today,
in
preparation
for
the
release
for
tomorrow,
so
be
a
thawed
once
the
dev123
branch
is
merged
to
me,
okay,
okay,
good.
A
To
know,
did
I
miss
anybody,
I'm
looking
through
my
window
here
and
I
get
to
get
everyone.
It
looks
like
I
got
everyone
I
believe.
Well,
let's
get
started
with
our
agenda.
I
am
sharing
it
and
hopefully
you're
able
to
get
to
it.
Otherwise,
but
natalie.
You
were
first
on
the
agenda,
so
please
go
ahead
and
let
me
know
if
you
need
to
share
your
screen
or
anything.
B
Sure,
thanks
so
much
I
act.
It
would
be
great
to
share
my
screen
since
I
haven't
fixed
the
permissions
of
this
one
document
that
I
would
like
to
share.
Okay,
I.
B
Hopefully
everyone
can
see
that
yeah.
I
can
see
it
yep
perfect,
so,
firstly,
yeah.
We
there's
a
small
group
of
us
that
are
doing
some
really
great
mentoring.
Work
with
jim
and
paris
pittman,
who
just
got
reelected
against
the
steering
committee
as
part
of
kubernetes
emeritus,
contribex
chair
and
where
and
myself
and
ray,
are
actually
part
of
this
little
group
that
are
trying
to
spin
up
a
localization
sub
project
for
folks
on
the
call
who
don't
know
what
a
subproject
is.
B
It's
basically
ways
that
kubernetes
likes
to
kind
of
segment
ownership
of
different
areas
of
the
project,
so
that
there
are
people
who
are
kind
of
in
charge
and
accountable
and
able
to
be
autonomous
about
different
areas
of
kubernetes
that
they
can
kind
of
affect
and
make
impact
on
in
terms
of
the
localization
project.
What
we're
looking
for
is
basically
to
put
this
together
under
a
banner
of
a
certain
group
of
leads,
and
that
would
be
kind
of
chairs
and
tech
leads
together
around
a
localization
subproject,
where
we
can
take
better.
B
I
guess
accountability
and
better
leadership
around
how
localization
works
and
how
decisions
are
made
around
localization
efforts
for
committees.
B
So
this
document,
which
I
will
fix,
sharing
permissions
and
share
with
you
all
later
on
and
we
can
add
it
into
the
agenda
scopes
out
exactly
how
sub-projects
kind
of
take
effect
and
how
they
work
and
then
also,
if
I
just
scroll
down
here,
a
little
further,
how
we
can
get
that
approval
happening
and
so
you'll
see
in
this
little
notes
that
I've
got
here
that
I'm
highlighting
that
we
recommend
in
our
little
group
that
the
approval
of
the
sub
project
go
through
the
sig
docs
tech
leads
because
they're
actually
involved
in
in
what
we're
doing
and
have
already
given
them
their
thumbs
up.
A
B
Why
I'm
here
today
chatting
about
this
is
that
what
we
do
need
in
need
around
the
localization
side.
Project
is
folks
who
want
to
take
charge
and
and
lead
the
sub
project
itself,
and
what
leading
means
is
that
we
would
love
folks
who
are
already
involved
in
the
different
localization
teams
to
come
on
board
and
help
leave
the
larger
subproject
and
what
that
would
that
would
happen
here.
What
this?
What
this
would
mean?
B
Should
I
say,
is
that
we,
the
little
subgroup
of
this
sig
docs
mentoring
group
that
is
together.
We
want
to
help
these
leads,
get
on
board
into
how
a
sub
project
is
going
to
look
like
what
that
definitely
means
in
terms
of
leadership
and
also
then
doing
the.
B
I
guess,
administrative
official
things
or
writing
the
cap
and
pushing
that
forward
to
get
the
sub
project
off
the
ground
and
in
place,
and
then
around
that
what
we've
done
a
few
of
us
have
gone
into
some
of
the
different
localization
slack
channels
to
ask
for
general
interest.
B
If
anyone
is
out
there
who
wants
to
jump
in
and
and
take
a
look
role
in
the
sub
project,
work
to
put
their
hand
up,
we've
already
gotten
some
interest
from
the
japanese
localization,
which
is
great
and
I've
shared
some
information
in
the
french
indonesian
and
polish
groups.
Today
too,
so
we'll
be
just
sharing
the
word
around
to
try
and
get
some
interest
in
generally,
making
sure
that
we
we
have
some
folks
who
have
ownership
here.
B
So
that's
my
little
pitch
for
today.
I
plan
to
sorry
brad.
A
B
D
So
I
can
get
some
a
little
bit
more
context
there
brad,
so
code
is
definitely
out
of
scope
for
right
now,
maybe
at
some
point
whoever
takes
over
the
subproject
says:
okay,
let's,
let's
bring
code
into
scope,
but
right
now
that's
totally
out
and
as
far
as
what's
the
difference
between
this
group
and
and
the
localization
sub
project,
absolutely
nothing.
D
So
if
you
were
to
rewind
back
a
couple
years,
localization
was
kind
of
this
smaller
side
project.
D
We
realized
there
was
interest
there
and
we're
trying
to
figure
out
how
to
foster
and
grow
that
community
and
then
now
we're
at
a
point
today
where
the
localization
efforts
are
so
large
that
we
had
to
create
the
separate
individual
meeting
once
a
month
to
focus
specifically
on
localization
efforts
and
all
this
is
in
the
spirit
of
putting
more
structure
around
localization
and
really
supporting
the
folks
that
are
doing
the
localization
efforts
and
traditionally
those
are
smaller
teams.
Smaller
individuals
and
building
the
community
around
them.
B
D
D
A
little
bit
more
autonomy
as
localization
has
grown.
So
it's
kind
of
a
holistic
approach
here
and
and
trying
to
bring
this
all
under
a
little
bit
more
of
an
official
structure
for
the
open
source
community.
A
Yeah,
that's
what
I
guess
I
was
trying
to
understand.
So
it
feels
like
that
would
be
more
of
giving
us
a
formal
recognition,
formal
processes,
formal.
What
have
you,
which
is
great,
because
I
guess
we've
been
kind
of
doing
it
out
of
necessity
and
being
a
a
subgroup
as
opposed
to
a
sub
project.
A
So
it's
it's
nice
to
see
that
the
work
is
seen
as
valuable.
That's
that's!
That's
really!
Wonderful!
Oh
yeah!.
F
B
And
so
I
actually,
I
definitely
want
to
mention
there
too
brad
that
that
this
is
definitely
something
that
I
would
love
if
you
put
your
hand
up
for
as
well,
given
that
you're,
if
that's
something
that
you're
down
for.
But
I
think
this
is
also
something
just
like
jim
mentioned.
This
idea
about
having
more
autonomy.
B
What's
really
interesting
is
that
you
know
localizations
can
spin
up
when
there's
community
and
interest
around
them,
but
what's
sometimes
a
bit
harder
in
open
source
is
understanding
when
maybe
localizations
don't
have
the
support
anymore,
and
so
maybe
using
this
as
an
official
way
to
be
able
to
get
more
support
and
maybe
needing
to
spin
down
localizations
if
they're
not
actually
being
supported
anymore
and
having
this
as
an
official
way
to
kind
of
keep
the
localizations
themselves
kind
of
running
and
currently.
A
Now
this
is
wonderful
natalie,
I'm
certainly
willing
to
help.
I
certainly
don't
want
to
take
on
the
whole
thing,
since
I've
been
kind
of
running
the
thing,
but
I'm
happy
to
work
with
you.
If
that's
going
to
be
the
if
you're
going
to
be
the
right
person,
I'm
happy
to
work
with
you
and
I
think
it's
wonderful
putting
in
more
structure
more
organization,
more
recognition
for
the
work
from
from
our
from
our
overlords,
above
I
think
is,
is
really
nice.
A
So
this
is
a
fantastic
idea.
I
don't
know
what
else
we
need
to
do,
except
just
figure
out
who
wants
to
help.
You
work
on
the
caps
that
we're
going
to
submit
kind
of
thing.
B
Yeah,
so
what
I
was
thinking
is
that
given
given
we've
got
only
a
we've
got
a
few
folks
on
the
call
today,
but
to
basically
widen
the
pool
of
possible
interest.
What
I
can
do
is
also
post
in
the
channel
after
the
meeting
has
taken
place,
I'll
update
the
permissions
on
this
document,
so
that
folks
can
see
it
and
then
the
idea
would
be
getting
some
interest.
B
I
can
be
the
right
point
person
for
you
and
to
communicate
between
groups,
but
basically
yeah,
putting
a
bit
more
information
out
there
by
the
channel
to
try
and
get
some
interest,
we'd
love
to
try
and
get
some
kind
of
folks,
at
least
confirmed
as
as
interested
in
leading
this
by
the
end
of
the
year.
Of
course,
we
have
to
push
to
next
year.
B
That's
okay,
but
even
if
we're
getting
some
folks
signing
up
and
then
we
can
go
to
next
steps
there
around
pushing
the
cap
and
then
getting
that
formal
recognition.
As
you
mentioned,.
A
Right,
I
think
what
would
help
you
would
be
to
frame
the
issue
with
regards
to
here
are
the
challenges
we're
facing
in
localization
and
here's
how
a
sub-project
we
feel
is
going
to
address
those
challenges,
and
then
you
know
it's
okay
to
say:
hey
we've
already,
you
know,
we've
already
had
a
you
know
traction
in
this
area
because
we've
been
doing
a
subgroup
for
you
know
the
past
year
or
what
have
you?
But
you
know,
as
you
start
thinking
about
this,
I
think
that
will
really
help
that
that
that
fit.
A
Saying
here
are
our
challenges
and
we
feel
this
sub
project
and
paris
should
be
good
at
this,
as
well
with
all
her
experience
and
expertise-
and
you
know
I've
known
her
forever,
but
but
I
think,
if
you
fill
that
in
as
sort
of
that
motivating
narrative
of
what
we're
trying
to
accomplish
and
the
challenges
we
face
and
why
they're
addressed
by
subproject,
I
think
that'll
help
people
to
understand
how
important
this
initiative
is.
B
Yeah
definitely
what
I
can
do,
then,
is
I'll.
Take
it
to
do
to
kind
of
add
that
that
that
kind
of
description,
also
in
the
notes
here,
so
that
that's
visible
for
everyone
who
gets
gets
this
shared
with
them
and
then
yeah
we'll
go
from
there.
So
give
me
just
a
let's
say
an
hour
or
so
I've
got
a
couple
meetings
and
then
I'll
be
able
to
post
that
in
the
channel.
We
can
share
that
a
little
more
widely.
A
Okay-
and
it
sounds
like
the
ask-
is
there's
an
ask
for
volunteers
for
people
who
want
to
participate
in
helping
to
get
the
sub
project
up
and
running
and
get
the
kept
going
to
just
contact
natalie,
I'm
happy
to
be
one
of
those
people
I'll
be
happy
to
help,
and
you
know
you
know:
I'm
gonna
disappear
on
december
20th
for
very
well-needed
vacation
holiday,
but
but
I'm
here
until
then.
B
Just
to
add,
I
think
the
other
ask
that
that
is
a
little
different
from
this
is
on
top
of
helping
out
with
getting
it
getting
it
up
and
running,
actually
folks
who
want
to
be
known
as
actual
owners
of
the
sub
project
and
that's
folks
who
are
going
to
be
making
decisions
around
this
as
well.
That's
something
that's
really
important.
A
B
A
A
Progress,
it's
it's
nice
to
see.
You
know.
A
lot
of
these
folks
have
been
working.
It's
nice
to
see
people
saying
hey.
This
is
really
important.
We
should
we
should
really,
you
know,
get
more
focus
on
it.
So
that's
that's!
Really
cool
yep,
wonderful,
anything
else.
On
this
topic
we
should
cover
natalie
or
or
or
does
that,
cover
it
for
now.
B
No,
that
definitely
covers
it
for
now,
thanks
for
putting
me
first
so
that
I
could
speak
in
the
first.
Yes,
yes,.
A
Yeah,
I
know
you
had
a
tight
deadline
so
happy
we
got
it
done
with
15
minutes
to
spare.
I
think
so,
fantastic
all
right.
Well,
thank
you.
Natalie!
That's
wonderful
and,
let's
see
if
we
go
to
our
next
on
the
agenda,
jim,
you
are
next
on
the
agenda.
D
Yep
yeah,
so
for
a
little
context,
it
was
brought
up
to
our
is
brought
to
our
attention
from
the
localization
groups
that
large
refactoring
changes
to
the
kubernetes
website
was
extremely
disruptive
to
the
release
process.
Understandably,
you
know
changing
actual
layout
documentation,
information
architecture,
changes
really
large
layout
changes
had
rippling
effects
across
all
localizations,
if
not
properly
notified,
and
so
this
was
brought
up
to
the
kubernetes
team
or
the
sig
docs
team,
and
we
ultimately
decided
like
there's
really
not
a
great
way
to
pragmatically
or
programmatically
figure
out.
D
What
are
those
refactoring
changes?
So
a
lot
of
credit
to
ray
for
leading
this
effort,
we
brought
in
a
label
for
the
k
website,
repository
called
refactor
and
there's
a
link
in
the
agenda,
and
I
can
send
it
as
well
in
the
chat
here
that
we're
now
using
to
apply
for
any
major
changes
and
so
what
we're
trying
to
do
here.
First
of
all,
I
think
the
the
biggest
call
to
action
is
knowing
that
this
refactor
label
exists
so
anywhere
that
you
see
any
major
changes.
The
first
call
to
action
is
slap.
D
This
label
on
there
feel
free
to
be
very
feel
free
to
be
very
empowered
to
use
this
label
wherever
you
see
fit.
We
can
always
remove
labels,
we
can't
add
them
retroactively.
So
if
you
see
something
that
looks
like
a
refactor
you're,
not
too
sure
this
goes
for
the
english
localization
as
well.
So
anybody
who
sees
a
refractor
is
empowered
to
add
that
label
to
the
actual
pull
request
itself.
A
So
make
sure
I
just
understand
that
jim.
So
if
you
see
a
pull
request
and
I'll
call
it
a
tim
like
pull
request
where
you
do
a
whole
bunch
of
layout
changes
or
something
and
you're
like
wow,
the
whole
layout
appears
to
be
changing.
That's
when
we're
so
fully.
Hopefully
somebody
adds
a
refactor
label
and
that
refactor
label
is
meant
to
inform.
I
assume
interested
parties.
That
pain
is
coming.
I
guess
in
the
localization
space
did
I
get
that
right
or
no.
D
Correct
now,
there's
one
minor
caveat:
you
can
reorganize
like
tables
of
contents
in
a
single
file,
and
so
it's
maybe
not
a
huge
refactor,
where
it's
going
to
have
that
devastating
impact
down
the
road,
and
so
it's
kind
of
that
judgment
call
there.
That's
where
I
was
saying:
if
you're
not
sure
slap
the
label
on
there,
it's
better
to
have
it
than
to
not
have
it,
but
the
the
second
piece
of
this
is
just
because
a
pr
has
a
label
on
it
doesn't
mean
it's
treated
any
differently
than
any
other
pr's.
D
D
Does
it
make
sense
to
front
load
it
so
right
before
release
right
right
after
release
comes
out
making
all
those
major
changes
and
refactoring
changes,
and
then
nothing
that
happens
after
that
first
month,
kind
of
gets
postponed
into
the
next
release
or
potentially
towards
the
tail
end
of
the
release.
It
seems
like
that
would
be
too
much
work
to
pull
in
a
refactoring
change
and
then
do
a
release
and
then
have
localizations
have
to
not
only
catch
up
on
the
release
channel
but
then
also
having
to
do
the
refactoring.
D
I
think
that
could
raise
potential
issues
so
right
now.
The
tentative
suggestion
is
that
apply
the
refactor
label.
You
know
every
time
that
you
see
it
and
then
potentially
having
a
short
window
there
after
release
where
refactors
are
permitted
and
then
potentially
blocking
them
later
and
then,
as
you
see
fit,
maybe
down
the
road
there's
some
sort
of
prowl
mechanism,
some
sort
of
blocking
function.
Maybe
we
get
a
little
bit
more
serious
about
the
enforcement
of
this
label.
As
we
see
it's
being
successful.
E
A
So
so
folks,
like
soco,
what
are
your
thoughts?
This
is
a
label
that
is
ideally
meant
to
help
teams
like
yours
and
and
and
and
and
the
other
folks
on
any
thoughts
from
anyone.
The
floor
is
open.
Does
this
help
is
it
you
know?
I
I
like
how
jim
really
described,
how
well
here's
the
label
and
then
here's
how
we
envision,
maybe
being
able
to
use
it
and
the
way
he
described
it.
It
sounded
like
he
was
like
hey.
A
G
Okay,
thank
you
in
case
of
korean
localization
team.
We
are
using
milestone
strategy,
so
we
open
our
own
development
branch
and
do
localization
job
and
close
and
open
new
branch.
And
then
we
try
to
check
the
changes
in
english
upstream
document
so
that
we
can
make
up
the
things
korean
look
like
localize.
B
G
Contents
synced
with
the
related
english
documents
and
also
we
are
making
a
issue
a
report
issue
to
check
those
out
dates
the
korean
documents,
and
then
we
can
check
which
files
are
have
large
changes
and
suddenly
try
to
check
why
the
document
has
been
changed
too
much.
G
And
the
schedule
for
the
merging
the
picture,
liability,
life
changes,
documentary.
G
G
A
A
Okay,
that's
okay!
I
just
wanted
to
make
sure
and
double
check
and
ask
so
you
know
I
think
jim
will
have
to
try
and
follow
up
with
the
china
team.
That's
the
other
major
team.
That
kind
of
does
things
differently.
A
lot
of
teams
do
what
what
soca
teams
does.
So,
I'm
going
to
assume
if
soko
says,
hey
it's
fine,
that
those
teams
will
be
okay,
we'll
have
to
track
down
that
the
china
localization
team
and-
and
you
know
I
can
take
the
to-do
there.
A
D
I
don't
believe
so,
but
that
would
be
a
great
first
poll,
a
great
first
issue.
I
think.
D
D
Awesome
and
then,
as
far
as
the
duration
goes
to
sioko,
I'm
curious.
Does
it
make
sense
for
that,
like
first
month
of
a
new
release?
Is
that
too
much
drinking
from
the
fire
hose
or
too
much
like
content
coming
all
at
once?
Should
it
be
a
little
bit
of
a
delay
so
like,
for
example,
we're
releasing
a
new
release
on
tuesday
or
tomorrow
come
wednesday
if
all
these
refactoring
changes
come
in?
What
does
the
impact
look
like
to
the
korean
localization
team?
Is
that
a
nightmare
situation.
G
In
case
of
a
clear
localization
team,
we
have
our
own
schedule,
so,
for
instance,
we
operate
one
development
branch
for
three
weeks.
So
within
three
weeks
any
changes
can
be
done
by
english.
I
mean
in
upstream
and
master
changes,
but
we
try
to
keep
up
after
three
yeah
actually.
G
Since
we
have
too
much
changes
detector
changes,
then
we
are
missing
hard
to
keep
up
so
for
us,
dylan
were
taking
care
of
her
for
as
much
as
possible.
In
short
periods.
It
is
for
it
is
good
for
us,
but,
as
you
know,
the
picturing
itself
can
be
restored
yeah.
Then
we
have
to
work
in
this
period
and
then,
if
this
in
this
period
the
picturing
has
been
reworked,
then
we
should
follow.
Okay,
it
is
very
hard
so
yeah
you.
D
So
let's
say
like
quarterly
or
you
know,
every
six
months,
all
the
major
refactoring
can
go
in
there
and
then
it
can
go
downstream
and
impact
the
other
teams,
but
it
sounds
like
the
time
could
be
structured
based
on
maybe
annually
some
sort
of
structure
there,
rather
than
pinning
it
to
a
release
or
a
structure
like
that
because
of
the
downstream
impacts
of
that
now.
Maybe
that
still
ends
up
being
tagged
to
a
release.
D
You
know,
if
you
do
it
every
quarter,
what's
the
difference
between
doing
it
after
the
release,
for
example,
but
I
agree
trying
to
limit
the
the
volume
of
changes
all
at
once.
I
think,
with
the
refactoring,
it's
going
to
be
inevitable
that
it's
going
to
be
a
very
big
change
if
we
were
to
start
to
like
consolidate
it,
but
hopefully
it's
kind
of
like
consolidating
the
pain
of
of
the
refactoring.
D
So,
instead
of
having
like
minor
major
major
issues
all
throughout
the
year,
you
have
maybe
one
time
of
the
year
where
it's
a
struggle
to
you
know,
keep
up
with
all
the
refactoring
and
then
we
postpone
for
another
year
for
additional
major
refactoring
or
something
like
that,
and
I'm
just
making
up
a
scenario
here.
I'm
not
committing
to
one
thing
or
the
other.
Just
just
talking
out
loud.
A
Yeah
I
like
the
way
you
describe
that
jim
and
you
know
making
it
this
one
thing
that
whatever
the
quite
interval
is,
if
it's
every
quarter
or
every
half
year,
that
say
well,
I'm
really
sorry,
but
here's
when
the
pain
is
going
to
come,
and
here
we
go.
That
seems
like
you
would
at
least
reduce
the
amount
of
aggravation
hopefully
for
for
the
the
localization
teams.
A
Try
and
get
that
socialized
with
the
teams
as
best
I
can
jim
any
other
thoughts
on
this
topic
or
questions.
It's
it's.
It's.
It's
good
progress
at
least
we're
getting
the
label
in
and
we're
making
preparations
whose.
E
Idea
was
it
just
curiously,
so
there's
actually
an
issue
I
put
in
the
chat,
and
I.
E
Believe
that
it
was
that
it
was
chi
ming
who,
who,
who
mentioned
oh.
A
So
I
believe,
okay
and
that's
somebody
who,
from
from
the
china
team
who
probably
did
feel
some
pain.
So
that's
a
good
sign
all
right,
good,
very
neat,
jim
any
more
on
this
topic,
or
should
we
move
on
to
the
next
one?
This
is
excellent.
Thank
you
so
much
for
coming
and
presenting
it.
D
Yeah
no
and
thanks
ray
for
for
really
taking
charge
and
getting
that
label
integrated.
The
one
thing
I
wanted
to
call
out
is:
no
action
has
been
decided
just
yet
so
we
have
the
label.
We
know
how
to
apply
it.
We
are
actively
applying
it,
but
right
now,
there's
no
level
of
enforcement.
There's
no
plan
for
the
intervals,
so
I
just
want
to
raise
awareness
that
the
label
exists.
Use
it
frequently.
B
D
It
often
as
you
see
fit,
however,
we
still
need
to
decide
how
we're
going
to
enforce
it
once
we
work
with
all
the
localization,
so
today
it
means
nothing,
but
hopefully
in
the
future,
it
is
a
more
powerful
utility.
A
Very
cool
outstanding,
okay,
all
right!
Well,
thank
you
for
that
and
if
I
look
next
on,
the
agenda
should
be
silke
right,
yes,
go.
G
Ahead
yeah
sure
I
have
to
share
korean
application
team
updates
yeah.
We
always
introduce
korean
localization
milestone
and
currently
we
just
finished
level
1
22
ko3.
It
is
the
last
localization
job
for
122..
G
G
After
then,
after
123
release,
we
will
open
table
one
two
three
ko1,
and
then
we
also
make
the
then
122
ku4
for
makeup
actually
to
update
outdates
in
the
korean
only
and
we
will
launch
it
to
release
1
22..
G
Okay,
do
you
have
any
questions
regarding
korean
localization,
my
store?
G
If
not,
let
me
introduce
next
title,
I'm
going
to
present
cognitive
signals
and
korean
localization
contribution
to
open
improv
community
days.
Korea
event
is
a
kind
of
conference
based
on
openstack
communities
I
invited
from
there,
and
also
it
is
a
local
global
event.
G
So
I'm
going
to
introduce
it.
So
it
is
sharing
some
events.
A
G
G
This
project
has
been
initiated
a
few
months
over,
I
think
so.
It
is
to
define
any
terms
related
with
cloud
native
technology
technology,
and
since
I
requested
a
contribution,
I
contributed
for
localization
with
me
for
their
repository
and
you
can
check
the
pr.
It
is
about
localization
time.
G
I
just
wanted
to
show
the
introduce
the
information
regarding
the
for
contribution
and
I
think
some
of
our
kubernetes
localization
members
expressed
their
interest
to
localize
the
cloud
native
glossary
as
well.
Thank
you.
G
A
A
Okay,
well,
thank
you.
Everyone
for
attending
this
was
a
great
end-of-year
meeting.
Jim.
Are
you
gonna
handle
scheduling
for
next
year?
I
didn't
look
so
I
didn't
know
if
you
were
gonna
put
put
us
on
our
first
of
the
month,
like
you
always
do.
I.
A
Okay,
we'll
make
sure
it
rolls
over
and
then
other
than
that
we've
had
a
really
great
year
in
the
localization
subgroup
made
a
lot
of
progress
on
a
lot
of
topics,
and
you
know
I
wish
everyone.
This
will
be
our
last
meeting
for
the
year.
So
I
hope
everyone
gets
a
holiday
break
and
get
some
time
off
and
we
look
forward
to
seeing
you
all
next
year.