►
Description
[SIG Docs] Localization Subgroup Zoom Meeting for 20230904
A
A
we're
back
for
another
great
meeting
looks
like
we
have
a
lot
of
stuff
on
our
agenda.
I.
Just
like
would
like
to
welcome
everyone
and
say
first
off
that
we
are
a
cncf
meeting,
so
we
abide
by
the
the
kubernetes
code
of
conducts,
which
basically
boils
down
to
to
be
excellent
to
each
other.
So
please
carry
that
spirit
with
you.
As
you
engage
in
this
meeting,
and
we
are,
we
are
so
happy
to
have
you
all
here
looks
like
we
have
a
few
things
on
our
agenda.
A
A
B
A
B
But
there
are
some
first
notifications,
since
they
are
generated
generated
into
automatically
so
RB
created
open
on
issue
to
improve
outdated
content
running
on
localized
page
and
waiting
for
some
input
from
me,
including
me.
But
sorry,
I
am
very
late
to
respond
anyway
for
this
issue,
I'm
working
on
creating
a
script
to
check
the
current
status,
I
hope
to
see
how
many
pages
shows
this
current
outdated
notification
for
all
languages,
so
that
we
we
first
see
the
current
status.
A
A
It
is
I
think
a
great
first
step
to
have
this
message
shown,
but
then
I
I
do
think
that
there
was
some
some
site-wide
update
that
was
made
that
impacted
all
the
English
language
pages.
That
then
made
all
of
our
localization
Pages
show
this
message:
when
really
you
know
it
didn't,
didn't
necessarily
make
it
true
that
the
content
had
had
been
is
now
outdated.
A
A
A
The
whole
localization
content
guide
contribution
guide
is
this:
is
the
guide
we're
talking
about
it's
pretty
long
and
it
covers
a
lot
of
different
topics
and
I
think
that
there's
maybe
like
two
audiences,
so
it's
currently
aimed
at
people
who
are
trying
to
contribute
to
a
localization
group
and
people
who
are
trying
to
start
up
an
entirely
brand
new
localization
or
manage
a
localization
project
and
I
feel
like
that's
kind
of
two
separate
groups
a
little
bit.
So
my
idea
is
maybe
breaking
it
up
into
separate
pages.
A
So
we
have
things
a
little
broken
up
a
little
bit
more
like
how
they
are
in
the
English
guys
for
contributing
to
the
to
the
content.
It's
I'm
not
sure
if
that
would
help
as
much
but
that's
I,
just
sort
of
thought
for
bringing
it
down
into
a
couple
different
pages.
You
can
see
on
the
side.
It's
got
a
very
long.
Many
topics
covered
on
this
page
and
what
else?
No.
A
A
So
once
you
launch
your
localization
once
you
get
the
initial
translation
up,
there
is
still
work
to
continue
that
for
each
release
and
for
each
all
the
changes
that
you're
able
to
keep
up
with
so
I
think
that
that's
a
really
important
piece
to
kind
of
dig
into
more
and
and
give
people
helpful
information
to
how
to
create
the
community
around
supporting
a
localization
project
long
term.
So
I
think
this
is.
This
looks
really
great
to
me.
B
A
B
A
A
That
I
think
will
be
useful
to
kind
of
share
or
or
make
generic
or
in
some
in
some
ways
so
that
people
people
can
get
that
visual,
and
then
we
did
have
a
question
about
maintaining
older
dogs.
That
was
where
that
comment
from
it's
a
little
bit
complicated.
How
to
maintain
all
the
older
docs
on
the
on
the
website.
A
B
B
B
A
B
B
And
not
a
decisions
were
not
the
guideline
for
the
localization
teams,
but
in
case
of
Korean
localization
team.
This,
our
team
updates
the
previous
release
Branch
only
once
just
to
light
after
starting
a
new
version
milestone,
you
can
see
the
in
the
picture,
the
in
the
middle
there.
There
is
another
line
and
then
once
we
kubernetes
has
been
released
it
releases,
then
we
create
release
branch
and
we
update
master
and
keep
going
sorry.
It
is
not
master,
it
is
Main
Range
and
we
just
update
the
previous
release
spreadsheet.
B
B
Or
so
maybe
it
is,
it
would
be
beneficial
that
for
each
language,
maybe
their
target
or
or
can
be
announced
to
their
own
documents
so
that
the
local
leaders
can
understand
current
status
of
the
localization
and
the
objective.
For
instance,
in
case
of
localization,
we
can
say
that
we
only
focused
on
the
latest
eventually
latest
document,
only
that
document
or
previous
database.
A
A
They
only
work
on
the
main
docs
and
the
docs
for
the
the
upcoming
release.
We
don't
do
anything,
that's
historical
on
Past
released
branches
unless
it's
something
that
we
would
consider
like,
dangerous
or
or
potentially,
very,
very
problematic
for
users.
If
we
didn't
go
back
and
update
so
normally
for
for
even
for
the
English
talks,
we
don't
have
the
resources
to
to
to
update
all
the
past
releases
branches.
A
So
we
really
just
focus
on
what's
a
main
and
and
what's
going
the
changes
going
forward
unless
it's
something
that's
like
potentially
very
problematic
in
the
past,
so
I'd
say
that
your
workflow
really
aligns
well
with
what
the
English
language
docs
do.
But
I
do
I
do
think
it's
interesting
to
see
what
other
other
teams
are
doing
and
what
we're
kind
of,
where
they're
at
in
their
their
process
and
what
their
goals
are.
That'd,
be
interesting
to
hear
from
the
other
teams.
B
Maybe
it
is
beneficial
2
at
or
section
2
guide
how
to
manage,
redirect,
URLs
or
localize.
The
page
I
think
there's
no
local
guide
regarding
the
redirects
so
far
and
actually
I
checked
the
current
status
of
redirect
redirected
just
to
read,
directs
the
URL
to
somewhere.
So
when,
usually
we
in
qantasy
website,
we
use
it.
When
we
move
the
document
from
here
to
somewhere,
then
we
usually
put
a
line.
B
I
came
for
redirection
from
the
document
from
here
to
here
to
main
name
here
to
here,
so
we
use
this
redirect
file
in
the
purpose,
but
in
case
of
English
document,
when
we
group
English
document
somewhere,
then
English
contributors,
sometimes
it
is
redirect,
but
since
localized
documents
is
not,
it
also
should
be
moved
by
English
document,
but
there's
no
redirection
or
localized
pages.
So
far,
so
sometimes
we
we
see,
we
observe
some
foreign.
B
B
Page
does
not
exist
very
important.
Then
we
check
and
try
to
weather
to
add
the
database.
I
can
go
or
not.
So
the
pr
is
to
reduce
the
kind
of
report.
Basically
so
I
created
I
built
a
script
to
verify
for
redirect
it
tense
and
if
there's
English
redirect
then
to
predicate
localized
Beauty
dialects,
core
or
localization
languages,
so
it
is
actually
indirectly
creating
those
basically
Direct
Time.
B
A
B
B
Yeah
there
are
starting,
but
I'm,
not
sure
whether
to
see
the
video
here
in
this
meeting
or
not
yeah.
Okay
anyway,
the
video
is
how
to
use
the
script
to
indirectly
manage
it
is
file
so
that
we
don't
have
to
we
mean
localization
contributors
does
not
need
to
care
about
their
redirect
for
each
localized
age.
A
Well,
thank
you
for
raising
this.
Have
you
posted
this
in
the
localization
Channel,
also
just
to
make
people
a
little
more
aware
they,
they
weren't,
able
to
attend
today,
be
interesting
to
hear
what
what
the
what
the
outcome
of
that
conversation
is.
I
haven't
looked
too
much
into
that
issue,
but
I
will
and
I'll
see
if
I
have
any
comments
to
add
there.
A
A
Basically,
there
has
been
some
people
asking
how
we
can
use
AI
within
our
community
to
help
do
dogs
things
easier,
better,
faster,
stronger,
all
the
other
things
that
AI
is
supposed
to
help
with.
So
there
is
this
open
discussion
in
the
kubernetes
discussion
repo.
If
you
have
any
questions
to
check
it
out,
we've
had
some
great
comments
before
I.
A
Think
the
thinking
right
now
is
to
not
use
it
right
now
for
localizations,
because
there's
a
lot
of
issues
with
the
translations,
there's
a
lot
of
Burden
added
onto
the
reviewers,
and
it's
not
quite
process-wise.
It
doesn't
really
fit
with
with
our
localizations
right
now.
So
I
think
we're.
If
we
will
use
it,
it
will
be
in
use
cases
outside
of
directly
in
the
localization
and
translation
sphere,
but
that
doesn't
mean
that
it's
not
going
to
be
something
we
can
use
somewhere
else.
A
So
if
you
have
thoughts
or
you're
interested
in
this
topic,
please
feel
free
to
check
out
this
discussion.
It
is
also
something
we
are
planning
we're
looking
into
for
the
doc
Sprint
at
the
upcoming
kubecon
contributor
Summit
for
coupon
North
America
happening
in
November
in
Chicago.
So
if
you
are
able
to
attend
that
event,
please
look
out
for
the
doc
Sprint
on
the
agenda.
A
It
should
be
I,
think
it's
November
6th.
Would
it
be
there,
so
the
doc
Sprint
in
general
is
an
event
that
we
hold.
That
is
a
located
in
person,
so
it's
people
who
are
interested
in
helping
the
docs
coming
in
sitting
down
together
talking
about
docs
issues
working
on
issues
throughout
the
repo.
So
it's
a
great
opportunity
for
us
to
talk
about
just
things
going
on
in
the
community
and
things
we
might
want
to
see.
A
So
that's
why
we
have
the
idea
to
talk
about
the
AI,
because
it's
complex,
it's
not
necessarily
straightforward
and
there's
lots
of
different
things.
We
can
do
so
we're
looking
into
doing
an
AI
focused
talk
Sprint
at
kubecon.
So
if
you're
able
to
attend
it's,
unfortunately
only
in
person
right
now,
we'd
love
to
do
one
virtually,
but
we
just
don't
have
the
the
know-how
to
do
that
right
now.
A
A
Okay,
I
see
here,
the
next
meeting
will
be
October
2nd,
so
we
are
looking
forward
to
chatting
more
with
you
at
the
next
meeting
and
again
we're
always
around
in
slack
or
in
GitHub.
So
if
you
do
have
something
you
want
to
chat
about,
please
feel
free
to
reach
out
in
the
Sig
docs
localization
channel.
We
are
happy
to
chat
with
you
about
anything.