►
From YouTube: K8S SIG Docs Localization Meeting for 20220801
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
So
hello,
everyone
and
welcome
to
the
next
edition
of
our
Sig
docs
localization
sub
project
meeting,
which
is
a
mouthful
I,
need
to
remember
to
shorten
the
next
time.
I
kick
off
a
meeting,
so
it
is
August
1st
and
welcome
to
everyone.
I
posted
a
link
to
the
agenda
in
the
chat
people,
wanna,
add
in
their
agenda
items
and
I
guess
we
can
kick
off
by
seeing
if
there's
any
new
folks
who
want
to
jump
in
and
introduce
themselves.
A
Okay,
anyone
if
anyone
is
new
and
they
want
to
either
just
say
hi
in
the
chat
or
just
add
in
their
names
into
the
agenda.
That's
fine
as
well
welcome
to
anyone
who
is
new
and
let
me
look
at
the
actual
agenda
and
see
what
the
first
item
is
so
so
cool
I.
Guess
if
you
want
to
kick
things
off
with
your
items,.
B
Sure
the
first
title
is
about
my
question:
I
hope
to
find
the
official
document
for
the
former
life
to
our
localization
soft
project.
I
heard
edicts
already
official
right
in
heavy.
A
You
mean
just
having
it
updated
throughout
the
documents
for
sub-project
in
general
they're,
like
a
specific
Charter
you're.
Looking
for.
B
Sure,
actually,
in
the
last
meeting
I
heard
about
chair
chairman
shadow
or
the
sub
project,
so
I
just
so
I
hope
to
see
I
hope
to
check
who
is
ahead.
Who
has
the
leadership
for
this
sub
project
and
I
introduced
the
localization
soft
project
to
Korean
localization
team
and
in
Korean
localization
team?
There
are
also
contributors
who
are
very
experienced,
so
some
of
Korean
team
member
are
interested
in
the
some
leadership,
so
I
hope
to
share
any
documents
were
linked
to
them.
That's
a.
A
Yeah,
so
for
right
now,
Brad
and
I
are
the
the
chairs
and
I
I
actually
just
created
a
PR
which
I'll
put
a
link
in
the
chat
which
is
just
to
update
our
readme's
very
bit
minimal,
just
to
elevate
ourselves
as
a
sub-project
within
the
dogs.
A
I,
don't
know
that
we
have
a
specific
place
where
we
list
out,
who
is
our
sub
project,
but
we'd
follow
the
same
processes
as
as
the
Sig
itself,
so
wherever
Sig
docs
has
documented
how
to
become
a
leader
whatever,
but
if
people
are
interested,
this
is
open
open
to
anyone
who
who
wants
to
to
contribute
and
who,
who
wants
to
become
a
chair
or
other
leadership
positions.
If
we
have
ideas
right
now,
we
just
have
chairs,
but
I
know
there
are
other.
A
There
are
other
positions
within
things
for
for
opportunities.
If
people
want
to
come
up
with
their
own.
C
Could
certainly
create
some
Ambassador
roles
right
to
give
people
a
nice
leadership
title.
What
do
you
think
about
that?
Soco
I
think
of
opportunity,
I
think
a
nice
leadership
title
if
they're
interested
would
that
work
yeah,
maybe.
B
A
Okay,
cool
I
think
so.
Could
you
also
have
the
next
item?
I've
lost
the
agenda
yeah.
If
you
want
to
jump
into
your
updates,
that
would
be
awesome.
B
B
So
you
can
check
the
Milestone
link.
We
have
two
main
issues
for
this
Milestone
and
first
one
is
the
for
the
localization
texts
and
second,
one
is
to
update
outdated
content
in
Korean
documents.
B
Yeah
I
I
disable
the
localization
Korean
localization
Milestone,
and
is
there
any
question
regarding
Korean
localization
team
or
our
Milestone
strategy
since
I
saw
some
localization
teams
follow
some
Koreans
Korean
teams
strategy,
so
we
are
open
to
help
any
initializing
localization
teams.
Thank
you.
Is
there
any
question
or
commit.
D
D
That's
a
very
kind
offer
I'm
helping
I'm
trying
to
help
the
Indie
localization
team
and
I'd
like
to
get
your
advice.
The
Korean
localization
effort
has
an
excellent
reputation
for
doing
their
process
well
and
I'd
like
to
see
how
we
might
transfer
some
of
that
expertise
to.
B
Share,
thank
you.
If
you
have
any
question,
let
us
know,
and
it's
not
the
only
one
contributor
we
have
many
in
Korean
localization
here.
Okay
also
yeah
also
I
make
sure
the
reading,
shame,
ship,
Cloud
native
glossary
project
and
one
of
maintainers
and
I.
B
Thank
you
yeah
next
item
yeah,
it's
about
our
Korean
localization
team
mentis.
We
are,
we
invited
some
dentists
from
contribution
Academy
program.
It
is
promoted
by
an
agency
in
Korean
government,
so
we
have
21.
B
E
Yes
sure
my
name
is
Nayan
Kim
from
South,
Korea
and
I'll
be
a
senior
next
term
and
I
major
Computer
Engineering.
The
kubernetes
website
really
helped
me
studying
it.
So
it's
an
honor
to
contribute
to
it
and
participate
in
this
Meetup
nice
to
meet
you
all.
A
So
awesome
I
cannot
believe
you
I'll
have
so
many
mentees
contributing
that's
really
amazing.
It's
a
really
awesome
program
and
I'm
so
glad
to
see
all
the
new
faces.
This
is
great.
B
Thanks,
maybe
next
time
we
will
invite
more
new
contributors
from
our
Memphis
theater.
Thank
you
and
I
think
that's
all
from
issues
that
I
added
in
agenda.
So
maybe
right
your
time.
A
Cool,
thank
you
for
sharing
all
those
wonderful
updates
up.
Next
on
our
agenda
is
Ralph.
You
wanna
jump
in.
D
Yeah,
thank
you
so
I'm
on
saraf
and
I
Oman
is
a
recent
volunteer.
We're
proposing
two
strategic
projects
to
support
hi
localization
Hindi
localization
efforts.
D
One
is
to
create
the
first
item
in
the
agenda.
As
you
see,
it's
35
600.
D
is
an
umbrella
issue
to
create
pull
requests
with
the
untranslated
content
and
then
to
invite
Volunteers
in
to
provide
translations
as
comments
My,
Hope
Is
that
this
will
make
it
easy
for
them
to
provide
translations
without
doing
all
of
the
setup.
D
E
D
He
did
give
it
his
thumbs
up,
and
the
second
project
is
to
create
a
language,
specific
contributor
and
style
guide
based
on
the
one
for
Korean
I
think
it
would
be
very
helpful
to
provide
native
language
guidance
on
on
style
issues
if
we're
going
to
have
editors
and
and
comments,
it's
good
to
have
some
basic
standards
before
we
get
into
a
full
full
swing
on
translation,
so
I
welcome
your
thoughts
and
suggestions
on
these
projects,
we'll
be
getting
those
into
operation
very
quickly,
I
hope
and
we're
welcoming
volunteers
and
contributors.
So
thank
you.
A
A
How
much
of
an
impact
that
has
on
the
team
and
people's
participation,
because
I'm
curious
I,
don't
think
that's
something
we
recommend
initially,
but
if
it
is
something
that
you
think
is
is
really
helpful
that
maybe
it's
something
not
not
something
that
will
be
required
for
a
localization
team
to
get
started,
but
something
we
strongly
recommend.
B
D
Yeah
I
I
think
it
would
be
so.
My
my
train
of
thought
was
I'm
going
to
invite
all
these
people
to
contribute
content
and
how
can
I
guide
them
to
do
so
using
style.
That's
considered,
good
practice
in
Hindi.
I
know
nothing
about
the
language,
unfortunately,
and
so
I've
been
requesting
input
for
that,
but
I
I
think
it's
critical
to
have
at
least
some
basic
Style
Guidelines,
so
that
if
you
have
reviewers,
the
reviewers
can
look
for
specific
issues.
D
I,
don't
know
how
well
defined
what
you
know.
Good
good
technical
writing
style
might
be
in
that
in
that
realm,
so
anyway,
I
just
thought
that
would
be
essential
for
having
reviewers
know
what
to
review
and
look
out
for.
B
Yeah
I
hope
share,
I
mean
I
have
to
introduce
how
Korean
King
Edition
it
when
we
initiate
the
Korean
localization
We
Gather
some
members
who
are
going
to
participate
this
localization
tasks
and
we
consisted
the
team,
Korean
localization
team,
and
then
we
started
the
meeting
official
regular
meeting
among
members
in
Korean
localization
team,
and
we
did
at
that
time.
We
didn't
create
this
kind
of
Korean
languages
as
the.
B
And
we
keep
discussing
how
what
is
our
guidelines,
the
ones
we
we
see
results
now
we
can
share
this
guideline
to
other
people,
other
contributors
and
we
created
the
document
for
localization
language
testing,
foreign.
B
Maybe
it
is
a
premature,
it
can
be
a
premature
guideline
for
that.
Maybe
I
actually
better
way,
is
gathering
cheaper
request
and
then
make
them
a
team
that
they
have
a
team
and
make
them
make
the
members
in
the
team
discuss
about
this
style
or
characterize
that
rear,
automate,
localization
keywords:
it's
my
just
opinion
and
actually
the
Korean
team
follows
this
way.
D
If,
if
you'd,
like,
you
can
comment
in
the
in
the
issue
with
your,
your
thoughts
or
I,
can
go
ahead
and
try
to
make
I've
taken
notes
here
and
I
can
also
try
to
communicate
those
thoughts.
B
I
also
see
contributor
from
Hindi
localization.
D
F
Oh
I'm,
great
I,
think
we'll
need
some
kind
of
a
guide,
but
how
much
like
complex,
not
like
complex,
like
what
we
need
to
put
in
the
guide
for
Hindi
localization?
That's
the
way
we
need
to
think
about
and
work
that
we
of
course
need
some
kind
of
a
guide
to
make
things
consistent,
and
so
that's
that's
great.
Thank
you
for
starting
this
initiative
and
the
other
the
other
issue
about
the
classly
that
that
is,
of
course,
a
needed
one.
So
that's
so
we
can
start
working
on
that
right
away.
A
Awesome
this
has
been
some
really
great
issues,
so
so,
thanks
for
helping
put
those
together
all
does
anyone
have
any
other
ideas
on
this
topic
or
thoughts
before
we
move
on
cutting
at
all.
A
Okay,
the
last
item
on
our
agenda
right
now
is,
from
a
slack
conversation
that
Divya
actually
just
posted
a
few
days
ago.
A
show
folks
had
a
chance
to
see
that,
but
it
was
around
some
old
or
you
know,
stale
PRS,
that
people
have
not
gotten
a
chance
to
review
and
they've
kind
of
just
been
stuck
and
helping
to
clean
those
up.
I
don't
exactly
have
a
specific
action
item,
but
it
was
something
that
was
raised
by
Divya.
Who
was
one
of
the
chairs
of
this?
A
The
the
Sig
group
so
I
know
that
we've
been
talking
on
this
team
about
reaching
out
to
some
localization
teams
and
making
sure
folks
are
so
active,
so
I
think
that
all
kind
of
ties
in
together.
A
So
if
people
have
thoughts
and
what
they'd
like
to
do
with
some
steel,
PRS
or
older
PRS,
you
know
I
thought
we
could
have
a
discussion
topic,
but
it
is
an
ongoing
issue
that
we
probably
would
like
to
address
coming
up.
So
folks
have
any
thoughts
or
comments
about
this
thread,
or
this
topic.
I
guess
like
jump
in.
C
Yeah,
so
it
was
interesting
right,
so
you
know
for
regular
PRS.
We
have
Wranglers
I
mean
I,
wonder
if
there's
something
special,
we
need
to
do
just
to
look
for
stale
ones
for
localization.
C
It
was
interesting
how
she
found
them.
It
was
you.
A
Know
I'm
I'm
wondering
if
it's
maybe
something
we
could
do
as
like
a
Wrangler
but
for
localization
PR's,
but
not
necessarily
someone
who
would
be.
Obviously
people
will
not
know
all
of
the
languages,
but
maybe
just
have
someone
who
can
help
push
things
along
or
rotation
of
folks
in
a
Wrangler
in
that
sense,
to
kind
of
ping
people
a
little
more
regularly,
I'm,
not
sure
if
that
wouldn't
fall
under
a
regular
PR
Wrangler
position
right.
A
Okay,
maybe
that's
an
option.
I
know
like
you
had
suggested
before
we
talked
about
different
Ambassador
roles.
Maybe
this
could
be
some
a
kind
of
role
we
could
create
within
this
sub-project
to
help
help
these
type
in
these
situations.
A
We
I
don't
have
a
lot
of
solves
for
this,
but
it
is
something
we
should
probably
figure
out
some
ideas
of
how
to
address
them.
B
B
So
it
is
fine
for
Korean
localization
team.
For
now,
but
I
know
you
know
there
are
lots
of
other
languages
and
some
of
them
some
of
the
contributors
are
teamed
up
for
some
of
our
languages
has
a
Team
official
team,
but
most
of
the
languages
does
not
have
official
teams,
so
maybe
they
don't
have
Bangalore.
B
B
C
G
D
G
That
does
that
so
don't
know
I,
don't
think
it
touches
pull
requests
as
a
reviewer
when
I
when
I,
when
it's
my
week,
two
review
I,
typically
I,
don't
review
any
localization
PRS,
but
when
I'm
going
to
do
in
the
future
is
to
tag
the
owners
group
for
each
localization
for
that
PR,
because
that
is
a
group
that
we
could.
We
can
tag
and
the
reviewers
for
that
localization
will
be
notified.
A
I
guess
let
us
know
how
that
works
out
and
if
it's
something
we
can
suggest
the
other
PR
Wranglers
take
on
as
well
I,
don't
know
how
much
work
it
is
to
add
that
in
to
the
pr
Wrangler
schedule
already
I,
don't
know
how
that
would
work
out,
but
maybe
it's
a
short-term
solution
that
we
could
do
until
we
figure
out
something
a
little
more
that
might
work
a
little
better.
A
A
Okay,
did
anyone
have
any
other
thoughts
on
this
topic
or
anything
else?
We
would
might
want
to
share
that
they've
come
up.
A
Okay,
hearing
hearing
a
lot
of
Silence
so
I
believe
we've
come
to
the
end
of
our
agenda.
I
think
this
is
a
really
awesome
meeting.
Thank
you
for
everyone
to
for
coming
and
participating,
and
thank
you
to
Brad
who
I
saw
was
taking
notes.
So
thank
you
very
much
for
that.
So
we
can
keep
a
record
of
what
happened
and
our
next
meeting
will
be
next
in
September.
A
So
I
will
see
you
on
slack.
If
you
have
any
questions
or
have
anything,
you
want
the
group
to
look
at.
Thank
you
all
again
for
joining
and
have
a
good
rest
of
your
day.
Bye.