►
From YouTube: K8s SIG Docs Localization Subproject Meeting: 2023-05-08
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
a
big
cognitive
speaker,
docs
localization
soft
project
meeting
and
today
is
2023
May,
8th
yeah.
We
are.
We
are
sharing
our
meeting
notes
for
this
sub
project
localization
throughout
project,
so
you
can
check
the
checking
site.
A
A
Okay,
thank
you.
Yes,
every
on
our
writing,
your
name
in
participant
and
I.
Just
there
are
some
new
books
here,
so
maybe
we
can
have
time
to
introduce
our
staff.
A
Korean
localization
team
and
I'm
currently
helping
happy
with
a
colleague
of
this
localization
project.
A
B
Definitely
hi
everyone.
My
name
is
natalieves.
Let's
call
I
am
one
of
the
co-chairs
for
all
of
sigdocs
and
I
help
out
here
in
the
localization
sub
project
now
and
then
asoko
mentioned
Abby,
our
other
co-lead
for
the
localization
subproject
is
currently
on
leave.
So
myself
and
sioko
have
been
taking
over
some
of
the
meetings
and
doing
what
we
can
to
make
sure
the
sub-project
can
get
the
work.
B
It
needs
to
get
done
and
yeah,
and
it
was
nice
to
see
some
of
the
familiar
faces
here
from
the
sick,
docs
meetings
and
other
different
peers
and
issues
that
we're
working
on
in
docs,
so
hi.
Everyone.
C
Sure
hi
there,
everyone
I,
am
I,
currently
work
in
the
sick,
countrybooks
and
sick
talks.
Regarding
blog
writing-
and
this
is
the
very
first
meeting
of
the
sub
localization-
that
of
the
Sig
talks
that
I'm
currently
attending
and
really
looking
forward
to
it
and
learning
from
the
people
right
there.
Yeah.
Yes,.
D
E
No,
you
you
spell
you,
you
pronounced
it
right:
hi,
hi,
everybody,
I'm,
vital
I,
contribute
to
sick
dogs
and
I'm,
also
a
reviewer
for
the
Hindi
localization
of
the
documentation
nice
to
meet
all
of
you
and
look
forward
to
learning
with
learning
from
you
as
well.
Thank
you,
Thank.
F
G
Doing
some
I'm,
not
part
of
any
localization
group
but
I,
did
help
translate
a
couple
projects
already
I'm
interested
in
I'm,
not
sure
what
this
group
is
for
I'm
interested
in
starting
to
contribute
to
the
the
kubernetes
documentation
to
start
from
there
I
think
to
actually
help
translation.
Actually,
it's
probably
easier
for
me
than
I,
actually
can't
do
the
actual
English
documentation
in
the
beginning.
So
I'm
not
sure
if
this
group,
what
this
group
translate
well.
B
You're
you're
actually
in
the
right
place.
This
is
a
group
that
oversees
all
the
translations,
the
the
doxa
central
place,
where
we
can
get
together
to
basically
agree
on
processing
things
for
all
the
other
localizations
to
follow.
G
Okay,
great
yeah,
so
I
can
translate
both
the
Mandarin
Chinese
and
the
traditional
the
Chinese
so
interested
in
security
documentation.
At
this
point,
so
I
I
don't
know
how
to
start
where
to
start
foreign.
A
A
A
B
Yeah
I
think
it
was
we
had.
We
had
a
great
session.
We
had
some
really
interested
people
asking
great
questions
at
the
end
as
well,
and
some
folks
who
are
very
interested
in
helping
to
get
wanting
to
get
started
in
different
parts
of
the
localization
area,
so
yeah
it
was
a
great
time.
It
was
just
at
the
same
time
there's
a
lot
of
other
interesting
talks
in
the
Friday
afternoon.
So
so,
maybe
next
time
we
get
a
better
schedule
for
a
localization
talk.
A
Do
you
remember
any
impression,
I
mean
or
question
you
got
some
impression
in
that
talk.
B
A
B
Yeah
definitely
we
also
mentioned
that
contributing
to
localizations
that
already
exist
can
be
part
of
your
kubernetes
org
membership.
It
needed
to
make
it
very
clear
that,
if
you're
starting
a
new
localization
since
that
won't
be
live,
those
contributions
won't
count.
It
needs
to
be
things
that
are
being
deployed
to
the
main,
to
the
main
repositories
and
the
main
branches
that
we
have
for
the
different
localizations
or
for
the
kubernetes
project
as
a
whole
for
those
to
count
towards
your
membership.
A
A
As
you
know,
we
use
short
code
so
in
order
to
use
shortcut,
we
use
parameter
code
in
our
document
like
this,
but
this
pro
version
has
been
replicated
duplicated,
so
related
localized
documents
that
use
is
probably
button
short
code
should
be
updated.
According
to
this
issue,
I
created
this
issue
and
let's
check
the
ratio.
A
A
A
So
if
you
find
any
this
purpose
on
shortcut
in
your
localized
document,
you
need
to
update
and
I
created
a
umbrella
issue
to
update
all
of
localize.
The
documents
and
I
checked.
Current
status
and
I
found
the
pro
version.
A
What
in
those
localized
languages
also
Korean
includes
so
once
all
localization
have
switched
over,
then
we
can
remove
the
parameter
after
all,
So
currently
I
assigned
for
the
Korean
localization
content
and
I
actually
updated
Korean
document
that
has
the.
F
A
A
Okay,
is
there
any
question
regarding
this
parameter,
replication.
A
And
I
guess:
there's
no
question
and
focusing
this
meeting.
Please
share
this
job
to
other
contributors
so
that
they
can
help
to
handle
this
issue.
A
Okay.
Next
item
is
about
myself
and,
as
I
mentioned
before,
I
am
currently
learning
this
meeting
on
vehicle
Bobby,
who
is
called
localization
stock
project
and
I
finally
determined
to
join
the
core
leadership
of
secret
docs
sub,
protect
localization
stock
project,
yeah
I,
just
hope
to
other
folks
know
about
this
issue
and
I'm
not
sure
how
to
proceed
about.
Maybe
Natalie
will
have
me
right.
B
Yeah
I
was
about
to
say:
I
can
definitely
help
with
this,
so
firstly,
I
just
want
to
say
I'm
a
big
fan
of
you.
Stepping
up
syoko
I
think
this
is
great
for
folks
who
don't
know
in
in
the
general
governance
of
the
kubernetes
project
as
well.
B
We
always
try
and
make
sure
we
have
leads
of
the
different
areas
of
ownership,
of
either
code
or
docs
or
tests,
and
so
on,
so
that
there
can
be
easier
ways
to
do
the
work
to
make
decisions
and
so
on,
and
here
in
sigdocs
we
have
a
few
sub-projects
that
have
leads
of
those
specific
sub
projects
in
order
for
again
that
work
and
that
decision
making
to
be
easier
and
smoother.
B
We
created
the
localization
sub
project
last
year,
officially
as
a
as
a
way
to
get
all
of
the
processes
that
all
the
different
translated
docs
have
into
one
area
that
we
can
have
a
centralized
decision-making
place
and
Abby
and
previously
Brad
Topol
were
the
leads
of
this
and
Brad
recently
stepped
down
from
that
leadership
role
and
so
sierko
will
be
taking
the
other
place
of
a
co-lead
role
with
the
localization
subproject
there.
B
In
order
to,
for
example,
when
someone
goes
away
on
an
extended
leave,
like
Abby
has
done
this,
other
co-lead
can
come
in
and
still
be
able
to
continue
the
work,
that's
being
done.
So
what
would
happen
now
with
this
nomination?
Is
that
I
would,
as
the
sponsor
of
you
going
into
this
role?
Sioko
I
would
send
out
an
email
to
all
of
the
Sig
docs
mailing
list,
announcing
that
this
is
taking
place,
and
we
would
look
for
lazy
consensus,
which
generally
means
we
are
looking
to
make
make
sure.
B
If
anyone
disagrees
with
the
decision,
they
can
give
their
feedback.
But
if
no
one
disagrees
you
don't
have
to
say
anything
and
once
the
lazy
consensus
time
has
passed,
which
can
be
a
week
or
two
weeks,
whatever
information
that
we
set,
then
the
decision
is
final
and
we
update
the
readme
and
you
assume
the
role.
So
that
would
is
the
next
step
and
I
can
I'll
put
it.
I'll
put
it
in
the
notes
here,
but
I'll
have
it
to
do
to
send
out
that
email
very
soon.
A
Yeah
I
hope
not
rejected
by
others
and
yeah
I
I
would
love
to
support
other
localization
teams,
as
I'm
actually
actively
participated
in
one
of
the
localized
local
localization
team
so
and
I
have
been
contributing,
Korean,
localization,
maybe
30
or
two
years
on
our
longest
to
live
localization
team.
A
Okay,
next
testing,
I
I
just
wrote
on
question
a
question
or
in
localization
so
project
meeting
we
made
some
decisions.
I
saw
some
details,
but
we
all
have
to
find
those
separated
decisions
in
other
meetings,
several
meetings,
so
maybe
we
need
to
compile
it
somewhere,
so
I'm
not
sure,
really
is
good
place.
Maybe
we
can
use
discussion
page
in
Twitter
or
maybe
we
can
use
this.
We
think
note
in
front
of
meeting
node
for
that
productivity
decision.
B
Yeah
so
I
think
specifically
this
decision,
which
is
a
looking
at
the
idea
of
having
better
hygiene
without
PRS
that
are
open
in
the
localization
space,
specifically
for,
if
I,
just
to
give
folks
on
the
call
a
bit
of
background
of
this
information,
we
often
have
a
lot
of
newcomers
who
want
to
come
in
generally
to
docs,
but
also
to
localization
work,
who
want
to
contribute
and
help.
B
But
many
issues
or
PR's
are
often
being
worked
on
by
other
people,
and
sometimes
life
gets
in
the
way,
and
we
can't
finish
what
we've
started
or
we
need
to
maybe
step
back
from
certain
work.
B
But
it's
not
always
clear
that
that
has
to
take
place
or
people
or
don't
always
communicate
if
that's,
if
that's
needed,
and
so
what
we
wanted
to
do
as
a
way
to
free
up
certain
work
and
issues
that
are
happening,
but
also
to
keep
up
the
hygiene
of
the
amount
of
PRS
that
are
open
for
the
kubernetes
repo
the
website.
Repo.
B
Specifically,
we
wanted
to
make
sure
that
if
we
had
a
PR
that
was
open
where
the
author
of
the
pr
had
not
been
able
to
provide
feedback
or
answering
for
three
months,
then
we
can
assume
that
this
work
is
no
longer
being
done
and
we
can
close
that
PR.
B
Of
course,
information
in
the
pr
you
know,
comments
back
and
forth,
and
notices
about
this
will
be
will
be
needed
to,
but
to
be
able
to,
let's
say
document,
something
like
this
as
a
decision.
B
I
think
what
could
be
really
good
is
adding
this
information
in
the
general
localization
subproject
readme,
as
a
way
that
we
operate
also
doing
a
lot
of
message
sharing
in
slack
to
the
different
channels
of
all
the
different
localizations
is
helpful
too,
to
give
PR
reviewers
and
also
the
authors,
who
opened
them
a
bit
more
autonomy
around
things
that
are
taking
a
long
time
and
could
be
freed
up
for
other
new
contributors
to
to
take
on
as
well.
F
I
have
a
question
weaker:
do
we
currently
have
documentation
on
how
to
localize
docs
as
I'm
saying
that
I
think
I
just
realized
that
we
do
but
I'm
just
wondering
if
it
would
be
useful
for
us
to
add
this
information
in
the
contributor
documentation
on
kubernetes.dev.
B
Definitely
definitely
I
think
we
have
different
places
for
things,
the
different
policies
that
we
have
one
of
the
popular
ones,
that
we
often
mention
a
lot
with
a
lot
of
new
contributors.
Is
this
idea
of
no
cookie
licking
and
what
this
means
is?
B
If
you
claim,
let's
say
an
issue
or
something
that
you're
working
on
it
doesn't
always
mean
that
it's
only
yours,
it
really
does
mean
that
you're
saying
that
you're
going
to
work
on
something,
but
there
is
also
a
catch
there
where
it
needs
to
be
done
in
a
timely
way,
so
that
you're
not
taking
over
issues
and
and
work
that
other
people
could
also
be
working
on
just
because
you've
claimed
something
yet
have
put
no
work
towards
it
as
well.
B
But
yes,
as
you
mentioned,
Maureen
putting
it
in
the
contributor
docs,
we
also
might
be
thinking
about
putting
it
also
in
the
information
around
PR
wrangling
as
well,
because
this
is
also
something
as
a
a
cleanup
issue
as
well
for
for
Wranglers
that
happen
each
week,
but
I
think
it
could.
It
could
go
in
a
variety
of
different
places
as
a
way
to
inform
contributors,
but
also
to
help
reviewers
as
well
feel
that
they
can
have
a
bit
more
control
over
the
work
that
they're
like
giving
out
and
also
reviewing
themselves.
A
Yeah
yeah
I,
guess
that
we
can
make
up
here
when
we
have
some
product
decision
to
update
the
localization
guide
document
where
other
guided
documents-
and
maybe
I,
should
put
this
monthly
decision.
On
top
of
this
meeting,
notify
that
we
can
easily
create
a
new
pm
yeah.
B
I
think
that's
a
good
idea,
I
think
also
what
I
will
do
and
I'll
again
I.
Take
another
action.
Note
for
this.
I
can
write
it
up
in
an
email
also
to
the
stigdox
mailing
list
as
a
general
information
and
then
from
there.
We
can
use
that
same
text
in
the
different
places
that
we
need
to
update
in
our
docs
and
on
the
meeting
notes
here
so
that
it's
the
same
message
everywhere
and
it
doesn't
get
confused.
B
I
want
to
be
very
specific
about
that.
It
is
a
PR
would
be
closed
if
the
pr
author
hasn't
responded,
it's
really
on
the
person
who
is
doing
the
work,
as
opposed
to,
let's
say
a
reviewer,
because
we
know
that
reviewing
capacity
can
sometimes
be
quite
low
in
many
of
the
localizations,
and
we
don't
want
to
put
pressure
on
the
reviewers
in
the
in
that
same
way.
So
yeah
I
want
to
be
very
clear
on
the
wording.
It's
about
the
pr
author
itself.
C
Yeah
I
just
wanted
to
inform
and
confirm
one
thing
whether
we
need
to
update
this
information
on
the
spotlight
blog
for
sigdox.
B
Probably
not
on
the
on
the
blog,
given
that
this
would
be
something
that's
rather
new.
I
would
think
that
if
we
did
a
like
a
second
like
a
different
Spotlight,
specifically
on
localizations,
that
could
be
the
place
to
update
it,
but
because
this
is
a
very
specific
thing
on
this
sub
project,
rather
than
for
all
Sig
docs.
B
Actually,
our
pruning
policy
for
PR's
overall
in
docs
is
much
more
strict.
We
say
generally
for
PR
Wranglers.
If
there's
not
been
an
answer
for
up
to
two
weeks,
we
can
happily
move
on
and
and
close
or
reassign
things,
so
this
is
actually
a
policy
that's
much
longer
because
of
the
less
amount
of
contributors
and
reviewers
that
that
exist
in
the
localization
world.
A
Thank
you,
okay.
Is
there
any
idea
regarding
this
notice?
A
F
A
Guess
now
and
British:
okay,
okay,
the
last
item,
maybe
from
Netflix,
could
you
explain
British.
C
I
just
wanted
to
know
about
this
Hindi
localization
issue
that
was
being
raised
on
21st
of
August
2022
that
basically
claims
about
adding
Hindi,
localization
style,
guide,
I,
think
contributors
are
working
towards
issue
and
what
I
feel
like
I
might
be
wrong
that
this
issue
might
need
to
be
closed
because
all
the
work
that
is
happening
around
the
Hindu
localization
is
over.
That
is
what
I
think,
since
there
are
no
updates
over
the
issue.
This
issue
is
becoming
still
day
by
day.
C
Apart
from
that,
apart
from
closing
this
issue,
I
just
wanted
to
know
one
more
thing
like:
are
we
actually
making
this
certain
PR
changes
directly
to
the
main
branch
or
still
raising
PS
to
the
any
Hindi
localization
Branch?
If
it
exists
or
not.
A
A
Based
on
our
general
policy
in
baby
dogs-
and
we
have
some
original
scale
issue
and
I
forgot
the
previous
step,
but
we
have
several
lifestyle
life
cycle
or
telling
these
issues
and
PRS,
or
here
log
10
and
a
we
basically
follow
this
rule,
but
actually
the
letter
the
according
to
the
latest,
result
decision.
A
A
A
So
maybe
this
localization
style
guide
also
applies
to
same
rule,
I
guess,
but
in
case
of
this
PR
it
is
very
related.
With
kaido's
document
we
are
developed
to
construct
with
Hindi
localization
teams
and
PLO
service,
whether
we
can
close
or
we
can
make
refer
to
this
style
guide
so
that
we
can
close
our
make
a
direct
or
if
prses,.
E
Yeah
hi,
so,
regarding
this
localization
style
guide
issue,
my
personal
opinion
is
that
what
we
can
do
for
the
like,
as
the
in
the
Hindi
localization
I,
think
one
good
thing
would
be
to
ask
in
the
slack
Channel
whether
the
original
contributor
is
working
on
this
PR,
because
in
my
personal
opinion,
I
think
this
is
one
type
of
PR
that,
like
it's
important
in
the
sense
like
to
document
how
the
Hindi
localization
would
want
certain
stylings
to
their
PR
but
like
and
it's,
but
the
pi
has
not
been
worked
upon
in
a
long
in
a
very
long
time.
E
So
I
think
what
is
a
good
idea
in
this
way
is
that
we
can
ask
the
original
contributor
if
they
are
still
willing
to
work
on
it
and
if
they
are
not
working
on
this.
So
good
idea
would
be
to
close
this
issue.
Sorry,
this
PR
and
like
try
to
find
out
if
any
new
contributor
would
be
willing
to
work
on
this
issue
of
PR.
E
But
if
the
original
Earth
author
says
like
they
are
willing
to
work
on
it,
I
think
we
can
give
them
a
time
of
like
a
week
or
week
and
a
half
to
like
Elysium
working
on
this
issue.
But
is
this
still
not
able
to
do
that?
E
I
think
we
can
close
it
and
like
look
for
another
contributor
who
might
want
to
work
on
it
and
like
coming
to
a
new
thesis,
question
I
think
from
now
the
like
to
for
the
pr
for
the
Hindi
localizations,
the
all
the
peers
are
now
currently
targeting
the
main
branch.
There's
no
like
different
devs
Dev
Branch
for
Hindi,
like
the
Korean
localization,
follows
it's
directly
to
be
now
merged
in
which
which
I
remember
from
the
last
discussion
on
Snap.
G
A
I
have
a
question
in
case
of
Hindi
localization
team,
or
they
try
to
use
development
Branch
or
guiding
to
making
all
PRS
to
Main
Branch
directly.
E
I
think
I
think
yeah.
It's
directly
to
the
main
branch.
A
It
is
Titans
from
the
Hindi
localization
team
to
or
in
the
localization
contributors.
E
There
was
this
discussion
on
slack
and
after
discussing
it,
the
it
was
a
general
consensus
that
it
should
be
merged
into
like
that
PR
new
PR
should
Target
the
meme
I
think
somebody
raised
it
after
the
localization
went,
live
and
after
some
like
discussion,
General
consensus
came
that
it
should
new
PR
should
now
Target.
The
main
branch
I
can
also
like
link
to
that
discussion
in
the
meeting
notes
as
well.
A
Actually,
I
don't
mind
to
use
the
main
branch
directly
I
think
it
is
decision
from
the
localized
localization
team.
In
case
of
clear
localization
team.
We
have
some
development
branch
and
you
keep
creating
remove
the
development
bench
for
Korean
localization
in
case
of
china
simplified
to
Chinese,
they
use
main
branch
directory.
A
So
it
depends
on
the
kids
decision.
But
if
you
are,
if
Hindi
population
team
targeting
to
the
main
branch
directly,
then
this
year
referred
to
be
a
directive
right.
A
The
guy
to
the
document
should
not
be
opened
in
repetition,
so
I
guess
we
can
close
this
PR
based
on
teams
decision
or
actually
we
don't
mind
to
keep
use
this
PR
to
continue
the
Improvement.
B
I
will
say:
I
think
it's
worth
making
sure
that
Divya
and
one
of
the
and
any
other
Hindi
approver
is
involved
in
in
that
decision,
though
too,
maybe
we
just
want
to
make
sure
Vitale.
You
already
mentioned
this
jumping
into
the
Hindi
Channel,
just
to
kind
of
give
a
heads
up
of
hey.
We
should
probably
close
this
PR
and
tagging
those
approvers
just
to
make
sure
that
we're
not
doing
this
we're
not
making
a
decision
on
behalf
of
the
Hindi
approves
as
well.
B
I
think
we
should
involve
them
too.
A
Sure,
maybe
nitish
could
did
you
already
share
to
this
PR
to
the
Hindi
localization
team,
Channel.
C
B
Got
you
actually,
if
you
want
to
show
me
if
you
want
to
in
that,
where
you
brought
it
up
in
the
Hindi
slack
Channel.
If
you
want
to
tag
me,
I
can
happily
tag
in
some
of
the
other
approvers
and
just
say
following
you
know,
put
in
another
message
about
following
up
from
the
meeting
just
again,
so
that
we're
not
making
a
decision
on
behalf
of
the
Hindi
approvers.
E
Also
before
that
I
think
you
can
also
tag
the
original,
or
you
can
also
tag
Aman
in
that.
In
that
message
you
have
done
so
like
I,
don't
think
he
might
have.
He
may
or
may
not
have
seen
it.
So
can
you
just
also
tag
in
as
well
so
like
it's
also
brought
to
his
attention
as
well
like
to
his
attention
as
well
and
as
well
as
the
other
approvals
as
well.
F
A
Okay,
I
I
guess
we
can
communicate
with
the
number
of
folks
using
the
pr
and
black
Channel
and
let
me
also
participate
in
the
discussion
or
comment
in
the
pr
and
so
that
I
can
check
the
the
pr
and
PR
author
and
reviewers
are
invoked
and
actively
worked
or
not.
Maybe
if
we
can
determine
how
to
control
the
pr.
A
And
thank
you
initi
to
bring
this
issue
to
us
and
thank
you
for
watching
sharing
the
message
to
relate
to
the
perks,
Natalie,
I,
guess:
I!
Guess
we
don't
have
to
go
order
for
this
PR.
A
D
A
Okay,
I
guess
not,
and
that
was
the
last
item
of
our
meeting
agenda
and
we
have
some
time
so,
of
course,
if
you
have
any
question
you
can
say
anything
in
this
meeting.
Is
there
any
other
questions
or
other
opinions
regarding
kubernetes
website
localization.