►
Description
[SIG Docs] Localization Subgroup Zoom Meeting for 20230807
A
C
A
So
let's
go
to
our
meeting
agenda
here
today
is
August
a
and
since
this
is
meeting
so
please
try
to
be
nice
each
other
and
try
to
fulfill
the
quantities,
code
of
conduct
and
I.
Guess
you
already
can
access
this
meeting
note
and
you
can
edit
the
meeting
notes
either.
Anyone
who
cannot
access
to
this
document-
I
guess
none
and
please
have
your.
A
B
B
Looking
through
some
of
the
issues,
it's
been
a
lot,
so
I'm
very
excited
about
all
the
work
you
all
been
working
on
and
just
to
be
seeing
all
of
your
shining
faces
and
thank
you
so
much
to
Soko,
who
has
been
being
a
great
leader
of
this
group
and
also
congratulations
to
becoming
officially
officially
one
of
the
the
leads
of
the
group.
It's
really
well
deserved
and
I
am
happy
to
see
that
happen.
While
I
was
out.
A
Yeah,
thank
you
for
coming
back
and,
as
they
said,
I'm
very
newbie,
police
and
actually
now
this
very
experienced
lead
of
this
sub
project
and
Asians.
Since
I
put
several
issues
from
me,
so
let
me
introduce
my
odendas
and
the
second
one
is
about
the
some
parameter
multiplications
and
the
the
multiplication
should
be
applied
to
all
localized
contents
and
I.
We
already
shared
these
issues
and
life
and
other
nice
Works
already
contributed
nicely.
A
A
That's
the
remark,
and
the
next
item
is
about
another
umbrella
issue-
to
trace
localized
contents
related
to
calcula
removal,
and
this
one
is.
This
issue
has
been
created
by
tipish
and,
as
you
can
see,
in
order
to
apply
apply,
English
changes
regarding
katakuda
removal
to
all
localized
contents.
We
need
to
update
several
localization
localized
contents
from
each
languages,
and
actually
many
folks
are
already
on
this
issues.
A
Several
issues
have
manager,
but
some
are
not
so
literally.
The
action
I
can
in
last
three
meeting
to
me
also
about
checking
some
Heritage
status
of
all
localization
or
purpose,
since
some
of
some
localization
team
does
not
provide
any
feedback
so
far,
so
maybe
this
group
time
to
check
cases
take
us
for
each
teams
so
I
suppose
to
to
core
or
progress
localization
or
progress,
but
I
didn't
do
that
yet
so
I'm
going
to
do
it
soon.
A
A
So
if
English
document
has
been
changed
and
online
to
localization,
documents
is
not
changed,
and
this
report
is
a
lot
really
shows
automatically
in
in
Korean
localization
localization
documents,
localized
document,
this
one
is
the
column.
It
says
this
page
is
not
up
to
date
and
possibly
outdated,
but
actually
it
is
not.
A
A
To
follow
the
space
change
in
English,
but
according
to
current
automation,
if
there's
Korean
page
has
been
noted
by
the
outdated,
even
though
it
is
not
okay,
that's
the
second
case
So,
currently,
I,
think
and
also
many
Korean
contributors
think
it
does
not
work
well
yet.
So
we
need
to
find
enhancement
for
this
automation.
A
A
A
A
B
B
A
B
Yes,
I
am
not
overly
familiar
where
this
conversation
came
up
from,
but
Divya
has
been
posting
a
couple
of
messages
within
slack
and
also
this
GitHub
discussion
about
the
desire
to
update
our
contribution
docs
because
they
have
gotten
a
little
bit
out
of
date
and
maybe
don't
accurately
accurately
reflect
how
teams
are
working.
So
this
is
an
open
call
to
have
this
conversation
about
what
needs
to
be
updated.
B
What
folks
are
doing
within
their
communities
and
just
basically
an
open
call
from
what
I've
gathered
with
if
you
haven't
talked
to
her
specifically
about
this
and
she
was
not
able
to
join
the
meeting
today.
So
this
discussion,
that's
Soko,
has
opened
is
just
a
place
to
start
this
conversation,
you
can
see
here
that
it
will
be
open
for
14
days.
B
B
So
definitely,
if
you
have
comments
or
thoughts
about
what
should
be
included
in
the
localization
guide,
please
make
sure
to
add
your
comments
onto
that
discussion
or
reach
out
to
us
in
the
channel
or
or
whatever
Divya
like
I
said,
has
posted
a
lot
of
these
this
message
into
some
of
the
channels
as
well.
So
if
you
want
to
have
a
conversation
or
reach
out
to
us
that
way,
please
do
again
I'm
not
I.
This
is
my
summary
based
on
reading
her
issue.
B
A
Okay,
thank
you
and
for
for
your
information,
I
I
just
hope
to
share
that.
Maybe
the
this
question
and
give
us
this
question
is
from
the
changes
from
kubernetes
organization
membership.
Guideline
python
and
we
have
some
ins-
is
perfect
in
single
docs.
We
have
some
challenging
issues
regarding
the
initiating
a
new
localization
team.
A
So
if
you
see
the
this,
one
is
a
requirement
for
kubernetes
organization
membership.
We
recently
maybe
I,
guess
it
is
from
the
Natalie
who
is
the
second
of
the
quality
we
put.
Some
research
about.
The
this
part
demonstrate
ongoing
and
long-term
commitment
to
the
project
and
including
experience
type
of
contributions,
including
the
deputy
PR
in
kubernetes
Repository.
A
So
we
have
to
apply
I
mean
we
have.
We
need
to
update
localization
contribution
by
the
document
or
long
with
this
organization.
Members
requirements
changes
but
I
guess
DVR
said
the
update
investment
is
not
limited
for
this
updated
requirement,
but
also
other
aspects
as
well.
So
please
be
free
to
add
any
idea
or
concerning
point
in
this
discussion
so
that
we
can
actually
discuss
in
enhance
the
experience
in
localization
contribution.
B
No
question
but
I
know
this
is
a
really
great
thing
to
have
clarified,
because
it
has
been
a
stumbling
block
in
a
point
of
confusion
for
lots
of
new
folks
coming
in
and
lots
of
new
localization
teams.
So
it's
really
awesome
to
see
it's
being
clarified
and
then
The
Next
Step
of
also
updating
our
contribution
guides
to
help
help
our
help.
Our
new
teams
and
team
members
get
onboarded.
So
this
is
awesome.
Thank
you.
B
A
D
Well,
hi
again,
thanks
for
having
me
again,
I
really
appreciate
it.
So
last
time
I
chatted
with
the
localization
team.
We
discussed
lf's
willingness,
the
Linux
Foundation
cncf
to
support
documentation
with
tooling
around
generative
AI,
and
this
is
certainly
not
LF
or
cncf
telling
the
project
the
Sig
hey.
You
have,
you
know,
do
it
this
way,
it's
to
listen
and
say:
is
this
valuable?
Can
we
be
of
assistance?
Can
we
do
what
we
do
to
get
tooling
for
you
to
be
successful?
D
I
met
with
the
kind
of
Greater
Sig
docs
team
about
it,
and
they
certainly
like
the
idea,
but
then
afterwards
there
was
concerns
about
well
wait
a
minute.
Do
we
have
the
green
light
to
do
this?
There's
concerns
about
legal
opinion
and
certainly
copyright
and
and
all
that
good
stuff,
so
I
met
with
Joanna
Lee,
who
is
y'all,
know
Joanna,
so
VP,
you
know
focuses
on
legal
at
cncf
and
met
with
her
and
her.
You
know
their
opinion
is
look.
D
It's
low
risk
concerned
they're,
not
worried
about
copyright
on
documentation
as
much
as
code,
and
so
the
idea
was
all
right.
You
know:
we've
got
a
green
light
here
from
from
legal
at
cncf
to
do
something,
and
there
was
an
off-site
where
staff
came
and
and
got
in
person
discussed
hey.
How
are
things
looking
for
the
coming
year
and
I
I
chatted
with
some
of
the
team
I
was
like
well,
what
do
you
think?
D
D
Could
we
use
something
to
Auto,
generate
the
documentation,
do
a
PR
and
not
merge
until
we're
able
to
get
a
native
speaker
to
look
at
it
because
odds?
Are
it's
going
to
be
wrong
and
we
absolutely
need
a
human
there,
but
could
that
be
a
way
of
encouraging
make
that
transition
from
instead
of
well
I
I,
don't
know
whatever
language
we're
lacking
to
look
at
it
and
say
instead
of
a
native
speaker
coming
in
learning
like
like,
we
were
talking
about,
y'all
were
talking
about
onboarding
new
maintainers.
D
D
So
that's
where
we
are
I
wanted
to
check
in
with
the
team
and
and
see,
is
that
of
value
I'm
meeting
with
Jeffrey
and
Nate
next
week
due
to
vacations
and
those
sorts
of
things,
but
I
just
wanted
to
make
sure
that
at
LF
we're
being
directionally
correct
in
in
helping
you
and
supporting
you.
Do
you
see
value
in
this,
or
should
we
go
and
do
something
totally
different
to
to
support
y'all.
B
I'm,
not
sure
if
they
talked
about
this
last
time
you
hear
about,
we
have
the
minimal
viable
documentation
of
the
minimum
amount
of
content
that
needs
to
be
translated
and
before
a
localization
can
go
live
so
that
might
be
a
starting
place
of
what
would
need
to
be
translated,
although
you
could
probably
translate
all
of
it
or
what
would
need
to
be
reviewed,
I
guess
my
question
would
be
what
I
guess
what
what
languages
would
be
included?
Would
you
want
to
do
all
of
them?
B
D
This
is
just
starting
the
conversation
so
Abigail,
where
this
is
coming
from
is
okay
leadership
at
LF,
saying:
okay,
can
we
take?
Can
we
take
point
on
this?
Can
we
show
you
know?
Is
it
possible
to
use
this
tooling
to
improve
the
lives
of
our
documentation
maintainers?
Can
we
use
it
to
improve
onboarding
new
maintainers?
Is
there
an
opportunity
here?
It's
it's.
It's
really
to
say:
is
this
worthwhile
and
and
so
we're
very
early
in
it?
C
Using
platform
as
a
service,
localization
tools,
these
tools
make
contributing
and
managing
localization
vastly
vastly
easier
than
the
way
that
we
do
it
here
in
in
our
group.
They
these
tools
will
track
changes
in
the
Upstream
they
will
automatically
generate,
prompts
for
contributors
to
review,
machine
assisted
localizations.
So
something
will
change.
C
So
so
yeah
there's
tremendous
potential
here.
I
would
love
to
see
us
use
these
tools,
especially
if
we
offered
them
at
scale.
If
cncf
engaged
and
offered
these
tools
at
scale
to
its
constituent
projects,
you
would
see
you
would
see
a
huge
just,
a
transformative
effect
on
the
quantity
and
quality
and
level
of
Engagement.
So
yeah,
that's
a
big
plus
one.
D
C
D
So
if,
if
you
all
wanted
to
open
up
a
ticket
and
I
can
start
getting
engaged
in
it,
we
can
open
it
up
for
the
community,
I
I
think
there's
a
nice
dovetail.
I
I
wish
I
could
say:
I
planned
it.
The
agenda
here
with
the
previous
item
that
y'all
were
discussing
about
onboarding,
maybe
concentrating
on
that
bringing
in
new
languages
those
sorts
of
things.
But
all
of
you
have
got
vast
experience
in
this
at
your
companies.
D
But
if
you
want
to
try
something
if
there's
something
that
you've
been
wanting
to,
try,
maybe
at
your
company-
but
you
know
not
seeing
interest
or
something
like
that.
Maybe
we
can
do
it
here
and
that
helps
out
the
company
that
you
work
at
so
a
lot
of
options
here.
I
I
really
want
this
to
be
Community
Driven,
my
my
I'm
very
nervous
about
being
perceived
as
oh.
Well.
Lf
wants
to
do
this,
so
we
need
to
do
it.
It's
like
no,
no,
no!
No,
we
are
offering
assistance
and
support
vendor
connections.
D
A
C
C
C
A
Maybe
we
don't
have
to
use
GitHub
at
all,
but
maybe
if
we,
if
we
use
the
kind
of
strategy
or
tourists,
then
maybe
localization
quality
can
be
high
because
they
can
concentrate
on
their
localization
and
translation
quality,
but
as
making
a
new
member
new
contributors
to
four
kubernetes
Community,
including
the
source
code
and
other
things,
is
very
important.
The
localization
of
projects
in
six
dogs
and
using
the
kubernetes
keto
contribution
workflow.
A
C
A
The
Tyson
program,
but
inside
there
is
Google
translator
AK,
so
it
just
checks,
English
line
and
translate
English
language
to
Korean
and
generate
generation
higher
localized
height.
But
it
is
not
perfect
at
all
and
of
course,
of
course
not
yeah.
Yeah
contributors
need
to
check
the
whole
contents.
Okay
and
then
create
a
PR
and
a
vertical
Korean
reviewers
will
check
the
quality
of
this
localization.
But.
C
A
C
C
C
A
Based
workflow
fully
followed,
and
it
is
on
the
contributory
side
contribute
to.
If
we
or
contributor
use
this
kind
of
script,
then
third
result
may
be
include
machine
generated
things,
but
eventually
the
computer
should
say
it
is
my
work
and
please
review
my
words
not
automatically
generate
the
motion.
Absolutely
yeah.
D
Absolutely
we
very
much
want
a
human
to
review.
All
of
this.
This
effort
is
to
lower
the
burden
that
that's
very
much
what
this
is.
This
is
not
about
replacing
people.
This
is
having
people
do
the
kind
of
work
that
they
enjoy
doing
and
letting
the
the
computer
do
the
other
kind
of
work.
That
is
my
hope.
A
A
A
C
D
Well,
I,
that
is
all
of
these
ideas
are
wonderful
and
I
do
not
have
an
opinion
on
what
the
best
path
is
that
that's
what
this
team
decides
when
y'all
are
ready
to
make
that
decision
and
say
hey,
we
need
assistance
from
LNF
cncf,
whatever
I
want
to
try
this
vendor
I
want
to
do
this.
I
want
to
do
that.
I
need
a
project
manager
involved
here
to
help
do
some
things.
Contractors
you
know
that
kind
of
stuff,
that's
where
we
can
absolutely
come
in
and
help.
D
D
We
need
these
resources
from
Linux
foundation
and
cncf
no
problem,
and
so
when
you're
at
that
point,
that's
where
we
help
and
and
I'm
going
to
continue
to
attend
meetings,
speak
last
and
offer
my
assistance
and
so
I
I
guess
at
the
next
meeting,
we'll
you
know
maybe
we'll
be
further
along,
and
if
this
is
something
you
know
that
you
think
is
important,
but
now
it's
not
the
right
time
would
very
much
like
to
hear
that.
That
is
A-Okay
as
well.
D
A
C
C
C
B
C
B
B
B
Just
on
this
call
and
I
know,
the
Korean
localization
team
has
been
working
on
putting
together
those
tools
as
well,
so
I
think
it's
something
that
will
be
really
helpful.
We
just
have
to
figure
out
what
what
it
looks
like
in
practice
and
then
what,
like
you
said:
Robert
the
things
that
we'd
need
from
the
Linux
foundations
put
it
into
practice.
D
D
C
D
Yeah,
it's
just
I
I.
Certainly
next
somebody's
gonna
see
this
and
say
what
is
this
but
another
thing:
I
have
to
worry
about
and
and
I'm
I'm
hoping
to
do
something
very
different,
which
is
we
we
are
here
in
service
to
help
you
decide
the
direction
and
great
I
have
no
opinion
in
the
in
this.
The
only
opinion
I
have
is
that
Linux
Foundation
cncf
needs
to
support
Sig,
Docs
and
and
sigdox
localization.
C
A
Yeah,
hello,
you
and
Yoon
is
actually
a
Korean
localization
member.
Maybe
for
the
end
of
this
meeting
you
could
you
introduce
yourself
nice
to
meet
you.
I
am
I
even
live
in
Korea,
and
my
name
is
Sawyer
Yeon
I
I,
just
Curious
in
kubernetes
contributor,
contributing
activity,
also
I
I,
just
in
mind
in
secret
of
qualities
or
group
of
wrong
on
a
person.
So
I
overload
a
person
or
perform.
C
A
Say
enough
yeah,
it
is
love
and
seeing
new
folks
in
this
meeting
is
always
great
thing.
So
sorry,
the
this
request
for
your
introduction
is
introduced
and
any
Yoon
is
very
helpful
and
active
content.
Korean
localization,
contributor
and
I
just
use
the
RBM
work
for
resources,
Union
several
PRS
and
issues,
and
hopefully.