►
From YouTube: K8s SIG Docs Localization Subproject Meeting: 2023-02-06
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
and
welcome
to
the
February
6th
version
of
the
localization
subproject
meeting,
welcome
I,
put
an
agenda
Link
in
the
chat
and
I
just
want
to
remind
everybody
that
we
are.
This
meeting
is
being
recorded
and
remind
everyone
that
we
are
part
of
the
cncf
code
of
conduct.
So
please
be
mindful
of
that
and
be
be.
Basically,
it
boils
down
to
being
excellent,
excellent
to
each
other
as
we
go
through
our
agenda
and
being
respectful
of
everyone.
A
So
with
that
being
said,
I
can
kick
off
our
agenda,
so
if
anyone
is
new
or
we
like
I'd
like
to
welcome
any
new
contributors,
if
anyone
is
new
would
want
to
introduce
yourself
either
unmuting
yourself
or
in
chat,
please
feel
welcome
to
do
that
now.
B
Hey
there
so
I
guess
it's
my
turn
to
say:
hi
I
am
Noah
and
I
work
with
syoko
on
the
glossary
project
and
also
the
German
localization.
B
A
Awesome
welcome
this.
It's
great
to
hear.
A
I,
don't
think
we
have
anyone
else
who's
new,
so
we
can
get
started
on
our
excellent
agenda.
Let
me
share
my
screen.
I
always
end
up
sharing
having
difficulty
finding
the
right
window.
A
Okay,
sorry
about
that
I
can
never
find
the
correct
Zoom
window
so
anyway
here's
our
meeting
agenda.
A
So
the
first
thing
on
our
agenda
is
an
issue
which
was
actually
brought
up
by
Dimitri
in
the
Russian
localization
project
and
he
was
talking
about
creating
umbrella
PR's
for
all
the
localizations
to
fix
minor,
very
small,
bugs
like
a
link
fix
or
something
our
current
processes
are
set
up
to
not
allow
this.
A
So
we
we
only
want
one
language
per
PR,
so
this
helps
with
reviewing
each
language
has
their
own
review
processes
and
then
the
system
is
currently
set
up
to
assign
reviewers
based
on
the
localization
language.
That's
there.
So
this
would
mean
if
we
wanted.
A
You
know
so
so
his
idea
is
to
make
it
so
that
we
can
have
small
changes
in
a
single
PR,
so
that,
if
you
fix,
for
example,
just
a
link,
you
can
do
it
in
all
of
the
languages
without
having
to
create
tiny,
smaller,
tiny
language,
BRS
language,
specific
PRS.
A
So
this
is
something
we
definitely
would
want
feedback
from
each
localization
team
we
don't
we'd
have
to
want.
You
know
we'd
have
to
make
sure
that
it's
something
that
each
team
is
on
board
with
and
we
we
set
it
up
in
the
right
way,
so
I
wanted
to
bring
it
to
this
meeting,
I'm,
not
sure
if
he
was
able
to.
He
was
not
able
to
join
to
see
what
other
people
had
thought
about.
This
idea
add
so
just
really
just
looking
for
feedback
here
either
right
now
in
the
meeting.
A
If
we
want
to
talk
about
it
more
or
in
the
issue
later,
if
you
have
thoughts,
you
wanted
to
add
so,
does
anyone
have
any
ideas
or
thoughts
here.
C
C
So
since
we
have
our
own
procedure
and
we
related
Korean,
localization
contributorial.
C
In
case
of
Korea
localization
thing,
we
don't
need
additional
contribution
for
changing
the
current
localization
document.
Localize
the
Korean
document,
but
yes,
letting
us
know
which
she
which
document
should
be
updated,
is
very
beneficial
for
us,
so
maybe
issue
or
PR
is
okay
to
being
umbrella,
so
that
Korean
localization
team
members
contributors
know
about
which
should
be
changed.
C
D
Oh
yeah,
so
for
Portuguese
we
have
gotten
some
PRS
in
the
past
where
people
just
change
links-
and
we
usually
accept
him
so
I,
don't
think
like
having
an
umbrella,
would
be
an
issue
for
us
as
long
as
it
doesn't
include
textual
changes,
because
sometimes
we
we
notice
that
some
PRS
come
with
a
machine,
I
think
generated
translations
and
those
tend
to
be
sub-optimal.
A
Yeah,
those
are
both
excellent
points
and
I
think
it
would
have
to
be
something
very
limited.
If
we
were
to
do
this,
it
would
have
to
be
something
very
limited
to
just
things
about
the
site
or
link
updates,
because
as
soon
as
you
start
getting
into
the
languages,
then
you
need
to
make
sure
that
the
review
the
reviews
gets
too
complicated,
because
you
need
to
make
sure
that
each
review
from
each
language
is
able
to
review
that
whatever.
So
you
might
as
well.
A
Have
it
as
a
separate,
PR
and
I,
and
to
your
Point,
Circle
I
think
it
is
very
similar.
Achieving
talked
about
the
processes
for
Chinese
localization
and
he
said
very
similar
things
that
your
process
is
already
cover,
having
making
those
catching
those
changes
and
making
those
changes.
A
But
I
I
do
think,
like
you
also
pointed
out
that
we
could
be
better
about
making
sure
that
issues
are
created
to.
Let
folks
know
about
these
changes,
because
I
think
I
think
for
a
lot
of
the
localization
teams
that
have
a
lot
of
contributors.
A
It's
it's
probably
easier
to
handle
these
smaller
types
of
changes,
but
people
who
maybe
don't
have
as
many
contributors
I
think
that's
maybe
the
case
where
this
could
be
really
beneficial
because
that
we
could
get
those
smaller
changes
done
quicker,
but
I
I
do
think
in
this
case.
This
might
be
something.
This
is
something
that
we'd
have
to
do:
kind
of
All
or
Nothing.
A
We
can't
kind
of
have
a
process
that
only
includes
some
some
localizations
or
not,
but
I
I'm
really
glad
that
people
had
their
thoughts
and
were
able
to
chat
about
this
and
probably
more
discussion
but
I'm,
not
sure
I'm,
not
sure
how
effective
it
will
be
to
do
in
practice.
But
it
was
great
to
hear
everyone's
feedback
and
if
you
do
want
to
add
your
comments,
please
make
sure
that
they're
also
added
into
the
issue
too.
So
we
can.
We
can
keep
track
of
that
discussion.
A
The
next.
The
next
thing
on
the
list
is
from
me
and
it
is
about
the
catacota
shutdown.
So
catacota
is
what
we
use
for
the
interactive
tutorials
on
the
kubernetes
website.
It's
the
underlying
platform
that's
being
used
and
the
service
itself
was
being
shut
down
by
O'reilly
back
in
June.
They
made
an
exception
for
us
to
keep
it
live
and
they
are
there
they've
come.
You
know
we're
gonna
they're,
going
to
shut
down
that
service,
so
we're
working
with
them
on
a
date.
A
Probably
the
end
of
March
is
what
it
will
be
and
we're
working
on
rolling
out
Communications
the
Sig
chairs,
siddox
chairs
are
working
on
that.
So
there's
a
lot
of
work
to
do
around
Communications
and
and
making
sure
everything
on
the
website
is
removed.
But
this
will
be
a
change
this.
This
impacts
about
25
tutorials
in
the
English
language,
and
then
it
would
also
impact
all
the
the
localizations
that
have
been
made
for
those
pages.
A
So
this
is
going
to
be
a
big
change
coming
up
for
folks,
probably
by
the
end
of
March.
This
will
happen
so
I
wanted
to
make
you
all
aware
of
this
issue
specifically
and
if
you
wanted
to
help,
contribute
or
just
keep
track
of
this
issue
for
for
your
teams.
A
A
It's
very
similar
to
the
dockersham
removal
that
happened
last
year,
where
there'd
just
be
a
lot
of
small
changes
places
there
isn't
currently
an
a
replacement
for
this
tool,
although
they
would
like
to
find
one
we'd
like
to
find
one.
So
if
you
have
any
ideas
about
replacement
platforms
that
we
could
use,
that
would
also
be
really
helpful,
and
this
is
the
central
place
to
collect
information
on
this
issue.
There.
A
A
A
A
Okay
and
Soco
I
see
you
have
the
next
item
on
the
list.
If
you
wanna
I
can
stop
sharing
my
screen.
If
you
wanted
to
share.
C
Okay,
maybe
I
don't
have
to
share
my
screen.
I
just
hope
to
share
content
status
of
some
reading
peer
related
with
your
script
called
translation,
which
is
suggested
by
one
of
Korean
localization
member
for.
C
Generating
Auto
translation
trip
document
for
localized
Manner
and
it
is
waiting
for
approval
since
covers
for
reviews.
So
please
take
press
takeover
for
this
PR.
C
A
Yeah,
have
you
posted
this
in
the
main
docs
channel
to
get
some
eyes
on
it
from
the
pr
Wrangler.
C
A
I
know
I
I
saw
that
you
had
just
put
tried
to
get
one
of
the
pr
Wranglers
attention
earlier,
because
I
I
know
that
there's
been
a
lot
of
review
and
it'd
be
great
to
get
this
merged
in
and
there
is.
A
We
did
do
a
demo
of
this
during
one
of
our
localization
meetings,
I'm,
not
sure
if
we've
caught
up
on
our
slack,
not
slack
on
our
YouTube
recordings
on
the
playlist,
but
that
is
something
that
these
big
chairs
are
working
on.
So
hopefully
we
can
share
also
share
out
that
link
directly
as
well.
A
So
if
you
haven't
heard
about
this
script,
it
would
be
awesome
if
you
tried
it
within
your
localization
and
gave
feedback
and
we'll
hopefully
get
the
pr
merged.
Sorry,
that's
a
little
bit
slower.
A
Okay,
cool
well,
that
is
the
end
of
the
agenda
that
we
have
right
now.
The
only
no
I
wanted
to
add
is
that
I
will
be
going
on
leave
starting
around
mid-march
and
I
will
be
out
for
a
couple
of
months,
so
I
reached
out
about
this
in
spark,
but
we're
also
looking
for
some
folks
who
might
be
interested
in
helping
out
as
one
of
the
leaders
for
the
sub
project.
A
So
if
you
are
interested,
hopefully
we
can
maybe
chat
a
little
bit
after
this
meeting
or
it
just
reach
out,
and
we
can
chat
another
time
about
it.
If
you
want
to
get
more
information
about
what
that
means,
I
will
be
returning
to
the
role
I,
just
gonna
be
out
for
a
few
months
yeah,
but
it's
only
been
me
so
for
a
while,
so
we
we
definitely
would
like
more
folks
to
get
more
perspectives
and
more
more
help
in
the
leadership
team
within
the
community.
A
B
A
Yeah,
so
there
is,
they
have
their
own
slack
Channel.
Let
me
get
you
the
link
that
you
should
be
able
to
reach
out
to
them.
A
There
I'm
not
sure,
if
you're
already
in
the
link
in
the
channel,
so
each
team
should
have
the
reach
localization
slack
Channel,
which
they
hopefully
will
hang
out
in.
You
can
get
more
people
who
are
involved
by
reaching
out
there.
You
can
also
see
some
of
the
owners.
A
People
who
are
listed
as
reviewers,
if
you
wanted
to
get
more
information
about
people
who,
maybe
if
you
wanted
to
reach
out
to
them
directly,
I'd,
probably
direct
you
to
the
slack
Channel
first
I'm,
not
as
familiar
with
the
folks
in
that
localization
team.
B
Okay,
how
do
I
find
who?
How
do
I
find
the
reviewers.
A
Yes,
so
in
the
owner's
aliases
file
within
the
kubernetes
website,
the
each
team
has
a
list
of
reviewers
and
they
are
people
who
are
able
to
you
know
they're
the
people
who
get
assigned
to
review
PR's.
A
So
each
each
localization
team
has
their
own
set
of
reviewers,
so
it
should
be
listed
in
that
file
just
to
get
some
more
specific
names
but
yeah.
It's
not.
All
of
the
teams
are
as
active
in
slack
for
various
reasons,
but
that's
the
main
place
to
ask.
A
Okay,
does
anyone
have
anything
else,
any
other
questions.
C
Oh
yeah,
I
I
have
an
opinion,
but,
as
we
know,
not
every
localization
teams
are
actually
King.
Some
teams
are
set
of
contributors,
including
diverse
and
approvals.
They
may
not
context
through
selectional
or
other
meetings.
C
A
Yes,
that
is
an
excellent
point.
We
don't
have
a
formal
way
to
contact
each
person
within
a
lead
or
recognize
them
in
a
leadership
position.
I've
been
working
on
a
PR
which
I
can
share
again,
which
is
maybe
an
initial
effort
to
try
to
do
this,
although
it
definitely
needs
more
work,
and
this
is
just
a
way
that
we
can
at
least
list
out
who
would
be
people
who
are
owners
or
not
owners,
but
like
leaders
within
the
project
and
within
within
a
specific
localization.
A
But
we
don't
have
anything
formalized
right
now
and
this
this
is.
This
PR
itself
is
also
missing.
Some
information,
so
I
need
to
reach
out
and
find
out
who
these
people
are
and
and
how
best
to
come,
how
best
do
they
want
to
be
communicated
with?
A
But,
yes,
that
is
a
good,
very
good
point
and
something
we
need
to
be
working
on.
Yeah.
C
A
C
A
Yeah
yeah
we've
we
just
created
a
at
the
end
of
last
year.
Divya
went
through
and
sort
of
checked,
folks's
contributions
levels
and
we
we
created
a
more
cleanup
process
to
help
just
keep
in
touch
with
folks.
It's
not
the
perfect
gauge
of
whether
or
not
someone
is
still
active
or
not
because
for
various
reasons
they
might
have
low
contributions
from
localization
teams
or
low
activity,
for
other
reasons,
personal
reasons,
but
they're
planning
to
come
back
in
the
future.
A
So
there's
still
a
lot
of
reasons
why
that
might
not
catch
everyone,
but
it's
a
good
way
to
sort
of
see
who's
been
active
the
most
and
we
can
kind
of
know
who
to
reach
out
to
and
and
and
talk
to
and
and
connect
again
so
yeah.
C
A
Did
anyone
have
any
other
questions?
I
saw?
We
just
had
a
few
folks
join
if
they
wanted
to
introduce
themselves
if
they
knew
they
had
any
other
things
to
add
we're
at
the
end
of
our
agenda,
so
we're
sort
of
a
free,
open
space.
If
people
wanted
to
talk
or
having
to
come
or
had
come
with
any
questions.
A
Okay,
so,
like
I
mentioned
we're
at
the
end
of
our
agenda,
thank
you.
All
for
joining
I
can
stay
on
for
a
few
more
minutes.
I
can
end
the
recording
and
stay
on
for
a
few
more
minutes.
If
folks
wanted
to
talk
about
the
subproject
leadership
role
and
more
about
that,
but
otherwise
thank
you
all
for
joining
and
I
hope.
You
have
a
great
rest
of
your
evening
morning,
day
time.
Whatever
time
of
day
it
is
that
you're
able
to
join.
Thank
you.