►
From YouTube: K8s SIG Docs Localization Subproject Meeting: 2022-11-07
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
Okay,
hello,
everyone
and
welcome
to
the
November
2022
big
docs
localization
meeting
yay,
so
welcome
everyone.
My
name
is
Abby.
I
am
one
of
the
well
the
at
the
moment,
project
chairs
and
we
have
an
agenda
Doc
in
our
chat.
If
you
want,
are
interested
in
joining
I
just
want
to
let
everyone
know
that
this
is
a
CNC
meeting,
so
falls
under
the
cncf
code
of
conduct,
which
essentially
boils
down
to
be
excellent
to
each
other.
So
please
follow
those
guidelines
as
we
get
started
and
go
through
our
agenda.
A
B
Hi
I'm
Dagon
I'm.
This
is
my
first
meeting
of
any
cncs
like
meetings,
so
I
just
attend
a
cubecon
this
in
this
time
in
Detroit
and
I,
was
interested
in
contributing
so
I
just
wanted
to
see
things
working.
A
C
Hi
I
am
Maureen,
I
have
been
contributing
to
localization
in
Portuguese
for
about
just
over
a
year
and
during
kubecon
I
got
the
chance
to
talk
to
other
contributors
and
I.
Had
some
ideas.
I
was
encouraged
to
bring
to
this
meeting
to
discuss
with
the
broader
audience.
A
Perfect
awesome
welcome,
please,
if
you're
able
to
add
it
into
the
agenda
and
we
will
get
to
them.
Also
I
haven't
checked
out
the
agenda.
You
probably
already
did
that
anyone
else.
D
Okay,
oh
hello,
everyone,
my
name
is
my
English
name
is
Bart
and
you
guys
can
call
me
comfortable
at
this
part,
I
mean
working
as
a
site,
reliably
engineering,
Korea
and
I'm,
using
kubernetes
in
the
in
my
job,
so
I'm
interested
in
contributing
to
the
localization
in
kubernetes,
translating
into
Korea
or
I,
just
I'm
going
to
bring
one
agenda
that
I'm
working
on
that
I
can
share
with
you
with
you
guys
can
improve
the
translation
and
performance,
so
hopefully
I
will
share
it
later
on.
Okay,
thank
you.
A
Awesome
welcome.
Do
we
have
anyone
else,
you'd
like
to
say
hello,.
E
Hi,
my
name
is
badmos
I've
been
contributing
to
open
source
for
the
past
few
years,
so
I'm
happy
to
be
part
of
this
kubernetes
or
open
source
projects.
So
I
look
forward
to
making
my
contributions.
A
Great
to
see
you
for
joining
and
like
I
said
before,
if
you
have
any
questions,
please
feel
free
to
add
them
into
the
agenda
or
put
them
in
the
chat,
and
we
can
do
our
best
to
chat
about
them
here
or
follow
up
with
you
if
we
need
to
have
a
little
more
time.
The
answer
so
up
first
on
the
agenda,
I
believe,
is
an
item
that
I
added
about.
Let
me
share
my
screen
that
might
help
if
I
can
find
the
like
button.
A
Oh
man,
okay,
well,
my
zoom
is
being
weird,
so
I'm
just
going
to
go
into
the
agenda.
Hopefully
people
can
see
it
on
their
screens.
The
first
item
I
have
is
for
page
waves
changes.
So
this
is
an
issue
filed
from
the
Korean
localization
team
about
English
language,
page
weights.
When
we
write
up
content
in
English,
we
can
define
a
page
weight
which
determines
where
a
particular
page
will
be
located
in
the
the
sidenabs.
A
If
you're,
looking
at
the
site
on
the
the
left
hand
side
of
the
screen
there
we
go
and
when
we
do
that,
if
we
either
don't
Define
a
page
weight
or
it
is
overlapping
with
with
multiple
Pages
having
the
same
weight
within
a
section,
the
site
will
default
to
using
English
alphabet
to
list
the
pages
so
that
you
know
that
comes
into
a
problem.
A
When
pages
are
then
translated,
so
that
the
alphabet
is
a
different
or
the
words
are
different
for
the
page
titles
and
it
made
makes
the
page
orders
different
between
the
English
language,
docs
and
other
docs
documentation.
So
this
issue
was
filed
and
it
was
actually
something
we
addressed
at
the
kubecon
North
America
two
weeks
ago,
and
we
had
a
really
great
participation
from
folks
in
the
community.
So
I.
Thank
you
for
everyone
there
who
helped
with
that,
but
I
just
wanted
to.
A
Let
folks
here
know
that
this
will
actually
cause
a
lot
of
changes
for
the
localization
teams,
because
the
page
weights
have
changed
in
the
English
talks
and
then,
when
you
go
to
look
different,
go
look
at
the
the
differences
between
the
English
language
docs
from
release
to
release.
A
This
will
probably
cause
a
lot
of
red
flags
and
Page
changes.
The
issue
is
not
quite
complete.
There's
still
one
section,
particularly
the
task
section
within
the
docs
that
has
not
been
addressed,
but
everything
else
and
the
auto-generated
docs
is
something
we
have
a
separate
issue
to
address.
A
But
a
lot
of
the
pages
have
changed.
This
will
be
a
change
that
localization
teams
should
be
aware
of
I
just
wanted
to
early
Advance,
communicate
that
there
are
these
changes
happening
and
if
folks
are
interested
in
new
time
contributing
that's
an
issue
to
kind
of
look
at,
because
there's
still
a
little
bit
of
work
to
do
there
and
I'm
I'm
working
on
getting
it
a
little
more
listed
out.
I
know
sioko.
You
had
some
comments
there
as
well
about
it,
so
we're
working
on
that.
A
F
I
think
who,
who
opened
this
issue
he
had
has
a
script
to
check
the
remaining
tests
for
this
issue,
or
maybe
the
specific
shape
is
not
organized
yet
so
maybe
someone
is
working
on
that.
So
maybe
we
will
see
some
remaining
issues
soon
and
someone
used
to
let
it
everybody
they
need
to
share
to
us.
A
Let
people
be
because
there
it
is
an
opportunity
for
good
first
contributions,
but
those
might
take
longer
to
close
so
I'm,
just
wondering
from
your
perspective,
if
it's
easier
for
your
your
teams,
if
it's
all
done
really
fast
or
if
it's
something
that
we
should,
we
should
give
other
folks
the
opportunity
as
a
good
first
issue
that,
but
it
just
might
take
longer
to
close.
F
Yeah
in
case
of
Korean
localization,
we
hope
to
take
this
issue
quickly
as
soon
as
possible,
because
maybe
changing
a
few
parts
as
good
first
issues
good
to
invite
new
contributors,
but
this
kind
of
method
should
be
handled
quickly
so
that
you
can
quickly
through
this
nasty
issue
so
yeah
in
case
of
Korean
localization.
As
you
know,
we
can
trace
the
difference
between
original
English
resources
between
the
Korean
localization
so
that
we
can
generate
the
issue
for
that
to
report
report
the
difference.
F
Once
we
get
the
difference,
we
will
try
to
clear
all
changes
regarding
the
this
page
rate
issue.
So
that's
our
plan
for
clear
this
issue.
A
Yeah:
okay,
great!
Thank
you
for
the
feedback.
There
did
anyone
else
have
any
comments
or
questions
on
this
issue
before
we
move
on.
A
D
Oh
yep
actually
I
share
the
I
I
made
a
with
me
for
this
demo,
so
you
guys
can
look
into
it.
This
is
just
not
the
with
me
for
the
to
be
merged.
It's
just
for
the
demo,
so
you
guys
can
check
I
I
I
put
it
in
on
the
chat
and
let
me
share
okay.
E
B
D
D
So,
to
give
a
note
that
this
is
my
repository
and
you
guys
can
look
at
this-
is
the
branch
where
the
pr
is
working,
and
this
is
actually
branch
that
I
am
presenting
you
guys.
So
you
guys
can
just
look
on
this
branch
and
this
branches
will
not
be
kept
on.
This
is
just
for
the
demo
and
I
will.
D
F
D
So
basically,
this
script
work
as
like
this
way,
and
you
give
your
target
language
here
and
you
give
your
Source
document
file
in
this
pass,
and
this
generates
the
target
translated
file
as
respect
to
the
pass
as
the
source
file
which
just
converts
this
their
language
section.
D
So
let
me
started
okay,
this
you
can
see
it's
just
generating
some
script
with
the
it's
converting
English
to
Korean.
D
B
E
D
D
I
will
just
look
quickly,
go
over
my
python
file
later
on,
so
you
can
see
that
it
just
skips
the
some
of
the
non-translated
sections,
such
as
like,
like
a
header
and
some
of
the
comments
and
which
some
of
the
yeah
there's
some
more
this
this
code
block.
This
is
not
is
skipping,
for
it
will
be
skipped
on
translation
and,
as
you
can
see
it,
it
is
line
by
line
it
it's
it
matches.
D
Then
you
can
get
the
first
draft
of
your
translation
using
this
script.
So
I
will
look
over
some
of
my
means.
Okay,
yeah.
D
Yes
yeah:
this
is
how
you
yeah
that's
the
way.
I
just
run
my
script,
and
this
is
the
description
that
is
also
on
the
readme
that
will
be
merged
in
the
main
branch,
and
there
are
some
expected
questions.
I
might
thought
that
you
guys
can
ask
for
me
and
I
will
explain
in
each
of
them
and
I.
Just
I
use
the
Google
Trends
python
package,
which
version
is
3.1.080
instead
of
stable
one.
The
reason
is
that
your
the
stable
version-
it
does
not
work
so
so
I
just
use
this.
D
The
the
pre-released
one
and
those
the
supported
language
is
which
is
actually
the
all
of
the
language
that
Google
Translation
API
supports,
and
this
script
is
just
the
line
by
line
it's
it's
not
just
it's
not
a
baroque
translation
but
work.
Translation
is
for
it,
but
it
will
be
added
in
the
future
and
there
might
be
concerns
that
the
some
it
will
be.
This
is
the
the
open
the
package
that
I'm
using
is
an
official,
so
it
might
be
blocked
by
Google.
D
So
so
I
might
consider
when
the
when
the
package
is
blocked
in
I'm
a
cons
I'm
considering
going
for
a
translation,
other
API
or
using
other
open
source,
which
is
using
a
pre-training
translation
model,
and
there
is
also
you
need
to
create
your
target
directory
before
you
print
your
target
file.
So
the
the
script
does
not
automatically
create
the
target
directory
that
the
target
file
is
created.
D
So
the
future
plan
is
to
I
might
I
am
thinking,
is
giving
a
multi-proof
files
and
source
and
give
source
as
not
a
not
just
a
file
or
as
a
directory
to
create
dreams,
draft
translation
or
a
Target
directory,
which
is
sources
directory
and
target03,
and
maybe
a
bulk
translation
for
boosting
up
the
translation,
speed
that
will
be
the
future
plan.
D
Yeah.
Those
are
the
some
of
the
concerns
that
I
was
expected.
So
I
wrote
this
here
and
yeah
the
this
is
the
python
script
that
is
making
a
translation
and
I
wrote
the
first
draft
one,
and
so
so
cool
gave
me
a
lot
of
support
for
this
one.
So
thank
thanks
to
him
and
yeah.
These
are
the
it
just
translate
line
by
line
and
it
checks
the
some
of
the
prefixes
that
might
you
might.
D
We
should
not
give
a
translation
and
just
Skip,
and
it
just
skips
the
code
block
and
yeah.
Then
you
then
then
the
translation
begin
or
if
the
translation
fails,
it
just
a
given
exception,
and
you
just
you
just
write
the
line
as
as
it
is
without
translation,
so
it
just
so
you,
as
you
can
see,
is
a
line
by
line
translation
based
on
the
official
Google
Translation
API.
Yes,.
D
Any
feedbacks
or
questions
that
you
can
anybody
can
give
me.
F
Yeah
I
think
basically
very
clean
picture
for
every
localization
things,
even
though
it
is
maybe
this
premature
to
share
to
you
or
localization
teams,
but
yeah
I
think
it
is
very
good
start
for
automating
our
localization
thanks
a
lot.
D
Thank
you,
I
wrote,
I
wrote
some
of
the
warnings
using
this
translation
script,
which
is
is
just
using
an
unofficial
translation
library
and
additional
location
is
also
required.
So
I
I
have
to
mention
that,
after
even
after
this
running
this
script,
you
need
there's
a
Still
Human
work
to
check
the
actual
localization
words.
A
Thank
you
so
much
for
putting
this
this
demo
together.
It
was
really
interesting
to
see
and
pretty
cool
if
we
can
get
something
like
this
going
and
make
it
something
useful
for
for
other
teams,
so
I'd
be
interested
to
hear
for
other
folks
on
the
call
if
they
think
this
would
be
something
helpful
for
their
localization
teams
and
I
do
want
to
just
Echo
your
point
that
there
is
additional
work
to
be
done
because
doing
things
with
the
translation.
Api
is
not
always
perfect
and
probably
very
rarely
perfect.
A
So
there
is
still
a
lot
of
work
to
be
done
to
review
the
content.
I
make
sure
it
is
accurate
and
and
makes
sense
to
folks
in
your
language.
A
So
so
there's
still
a
lot
of
caveats
for
using
this,
but
I
think
I
think
this
could
be
really
helpful
for
teams,
particularly
the
new
localization
starting
out
to
help
get
them
off
the
ground.
A
little
bit
quicker
I'd
be
interested,
like
I,
said
to
hear
from
other
localization
teams
on
the
call
up.
This
is
something
they
feel
will
be
valuable
and
then
I
also
be
interested
to
hear
how
this
would
help.
A
How
much
like
like
how
you
would
fit
this
into
your
process
for
teams
that
already
have
like,
if
you
already
had
a
file
translated
into
Korean,
would,
but
there
were
changes
in
that
file
which
you
still,
but
how
would
you
use
this
script
or
would
you
not
recommend
using
the
script
if
there
were
just
changes
within
a
file?
That's
already
been
translated,
not.
D
Yes,
oh
I
think
this
is
useful
for
the
not
translated
ones
at
first,
but
if,
if
there
is
a
already
translated
and
there
is
a
modified
version
as
the
source
which
is
English,
then
this
one
I
think
using
this
script.
It
might
not
be
a
prepaid
at
the
moment,
but
you
can,
but
if
there
it,
it
can
be
used
as
like
a
comparing
tool
comparing
to
like
they
already
done
one,
and
there
is
a
new
version
one
but
yeah
it's
just
for
the
reference.
D
But
it's
not
I
think
that
is
now.
It
will
now
be
used
for
the
additional
translation
work
just
for
the
the
not
translated
ones.
Yes,.
F
Actually,
the
the
reason:
why
part
can
we
prepared
these
Securities?
It
is
because,
in
case
of
Korean
localization,
we
try
to
make
the
translated
documents
a
constructible
or
lines.
Yes
in
translated
Korean
documents
similar
or
same
with
English,
so
that
when
we
try
to
check
out
the
Korean
Korean
part,
we
can
guess
which
line
has
been
should
be
changed
in
Korean
localization
part,
the
that's
the
reason
why
Parts
try
to
make
same
line
with
English
and
Korean
document.
So
when,
once
we
learn
this
script,
we
can
get
document.
F
So
maybe
this
will
be
beneficial
to
localization
languages,
who
use
similar
way
with
Korean
localization
team
try
to
make
same
lines
with
original
and
translated
one.
D
Yeah
I
also
agree
with
the.
If
the
source
original
language
document
which
is
English
is
restructed
or
the
the
lines
are
have
been
changed
it
can.
We
can
check
based
on
this
script,
which
is
what
line
should
we
restruct
restruct
based
on
the
The
Source
One?
Then
there
will
be
a
useful
case
that
this
tool
can
be
used.
A
Awesome,
that's
a
really
that's
a
really
good
point,
but
the
the
keeping
the
files
the
same
structure
makes
it
easier
to
help
in
doing
your
translation
work.
Awesome
did
anyone
else,
have
any
other
comments
or
thoughts
about
this
script
that
they
want
to
share.
C
Question
is
it
possible
to
skip
specific
terms
I
ask
because
in
our
Portuguese
localization
we
don't
usually
translate
terms
that
are
related
to
kubernetes
objects,
so
I
see
value
to
using
descript,
but
it
would
be
easy,
not
easier.
Let
me
take
that
back.
It
would
be
more
valuable
for
us
if
we
could
skip
terms
like
pods
or
Secrets,
or
things.
D
D
Poor
okay,
for
for
my
script,
it
just
skips
the
whole
line.
If
there
is
a
script,
some
of
the
skip
prefixes
but
I
need
to
check
the.
If
there
is
a
we
can
skip
the
by
word
word
or
by
word
word
as
a
word
unit.
D
Oh
I
need
to
check
that
one,
but
I
I
agree
with
the
your
your
comment
that
there's
some
specific
specific,
like
terms
like
that,
we
should
be
careful
with
when
translating
based
on
the
some
of
the
general
rules
that
we
use
for
the
translation
that
we
agreed.
One
like
such
as
like
pods
or
like
deployments
that
one
that
and
and
so
on.
So
maybe
some
of
the
keywords
that
should
be
not
be
translated
and
translated
in
should
be
a
I
will
check
if
the.
B
Hi
Bob,
this
was
very
nice
work.
I
can
really
see
the
value
in
it.
I
had
a
question
about.
Is
there
any
API
key
or
like
limit
on
how
many
times
you
can
call
this
API.
D
You
actually
this
is
oh
okay.
Let
me
go
to
the
the
API
page.
D
This
is
the
year
an
official
by
spy,
Google,
Trends
repo,
and
it
said
what
I
as
far
as
I
understand
that
he,
the
prettier
creator
of
this
open
source,
is
kind
of
a
use
of
a
trick
to
skip
the
API
generating
a
token
so
yeah
as
I
think
there
won't
be
a.
D
He
doesn't
mention
about
the
like
a
hard
limit,
but
if
we
use
so
many
like
API
calls
to
the
Google
Trends
and
it
could
be
blocked
at
for
a
moment.
I
think
so
so
I
didn't
test
it
but
yeah.
But
the
author
did
not
mention
about
the
unlimited
ones.
Yes,
all.
F
So
actually
that's
the
my
most
is
worrying.
Point
too.
Yes,
since
it
is
not
the
official
API
so
for
this
moment,
I
think
it
is
hard
to
make
this
script
official
sticker
docs
or
field
docs
localization
sub
project.
That's
the
reason
why
we
just
suggest.
F
To
temporarily
test
the
description
for
some
few
localization
themes,
so
that
we
can
check,
validate
and
check
efficiency
or
usability
of
this
script,
whether
we
can
choose,
we
can
go
to
next
step
to
use
official,
API
or
official.
D
A
So
so
is:
is
there
an
official
version
of
this
I'm
not
familiar
very
much
with
Google
translate,
so
is
there
an
official
version
of
that?
Is
that
something
that
we
have
to
pay
for
to
use
it's
something
paid
for
okay,.
A
Okay,
so
if
it
is
then
I,
don't
know
the
exact
processes,
but
it
might
be
something
that
we
can
get
approved
from
the
cncf
depending
on
cost
and
if
we
make,
you
know,
make
the
case
for
it.
So
this
is
really
interesting
to
see
when
there's
a
really
good
points,
and
if
it
is
something
we
want
to
adopt
more
formally,
it
might
be
something
we'd
be
able
to
get.
A
You
know:
approval
pay
payment
for
from
the
cncf,
but
I
don't
know
that
processes,
so
I
can't
guarantee
right
now,
but
it'd
be
something
we'd
be
at
least
be
able
to
propose
through
kubernetes
again
and
maybe
get
funding
for
in
some
way
just
an
option
down
the.
E
A
A
I
tried
to
take
notes
as
best
as
possible.
Hopefully
I
accurately
captured
everything,
but
if
not,
please
feel
free
to
add
in
your
comments
or
or
adjust
what
I
have
written
there.
We
can
move
on
to
the
next
item
on
here,
which
I
believe
is
from
Maureen.
So
if
you
want
to
dive
in.
C
Yes,
so
we've
been
working,
I've
been
working
with
a
team
for
the
Portuguese
localization
for
just
over
a
year,
and
they
recently
became
an
approver
in
that
localization
and
we
have
been
seeing
a
little
bit
of
friction
with
new
contributors,
because
our
team
of
reviewers
is
not
that
big
and
sometimes
it
takes
a
while
until
we
can
get
to
the
PRS
that
are
coming
in
review
them
and
get
them
merged.
C
So
we
had
this
idea
of
putting
together
kind
of
an
onboarding
documentation
that
we
could
kind
of
outline.
What
would
be
the
expectations
when
you
start
contributing?
What
is
are
the
expectations
for
the
latter?
If
you
just
started
contributing,
when
can
you
expect
to
become
a
reviewer?
When
can
you
expect
to
become
an
approver
and
just
outline
like
in
simple
terms?
What
is
the
process?
C
Because
we
also
noticed
that
some
people
start
contributing,
but
they
don't
have
experience
with
Git,
for
instance,
and
that
becomes
turns
out
to
be
a
difficulty
which
causes
some
people
to
become
frustrated
and
sometimes
just
not
continue
their
contributions.
C
So
we
had
this
idea
of
like
putting
together.
Some
kind
of
you
know
like
an
onboarding
path
and
I
kind
of
wanted
to
hear
from
other
localizations
as
well,
because
I'm
not
familiar
with
what
what
other
localizations
are
doing,
and
maybe
we
can
introduce
some
of
the
practices
that
other
localizations
are
already
using
for
Portuguese
as
well.
A
This
is
an
excellent
question
and
definitely
something
that
we
have
heard
feedback
from
from
a
lot
of
different
localizations.
So
I
am
not
aware
of
any
specific
localization
team.
That's
created
that
documents
other
than
what
is
in
the
English
language
documents,
so
it
would
be
something
kind
of
a
little
bit
Uncharted
Territory,
but
Soco
do
you
have
anything
like
this
in
the
the
Korean
localization?
Or
do
you
have
any
thoughts
on
this
as
other
sort
of
lead?
That's
here.
F
Yeah
I
think
contributing
to
localization
and
just
to
contributing
to
or
other
projects
inside
the
collectives
and
psychotics
is
very
similar.
The
workflow
or
popular
shape
is
very
similar,
so
in
case
of
Korean
localization
team,
we
just
localized
the
the
how
to
contribute
to
the
document
English
to
Korea
I,
think
that
was
a
beneficial
I
think
with
same
thing
up
and
you,
as
you
know,
we
already
have
some
documentation
regarding
the
contributor
letter,
so
we
already
have
Korean
version
of
that.
F
So
as
a
document,
those
two
documents
since
I
and
on
the
other
hand
we
try
to
with
other
possible
contributors
online
on
offline
events,
I
try
to
promote
others
and
yeah
really
essentially
at
this
stage
developmentoring
program,
so
we
meet
more
than
12.
F
C
This
is
really
helpful
yeah,
so
you
mentioned
like
mentoring:
do
you
work
in
mentoring
like
in
person,
or
is
it
like
a
more
distributed
remote
kind
of
situation.
F
F
So
maybe
in
Portuguese
import
card
there
is
the
kind
of
program
so
that
you
can
participate
and
maybe
I
think
there
are
many
open
source
contribution,
mentoring,
programs
in
Google
and
other
places,
I'm
not
sure
extensive
preceptor
has
a
kind
of
program.
Do
you
know
happy
do
you
know
we
have
the
kind
of
mentoring
program.
A
So
there
is
a
mentoring
program.
I
do
not
know
all
the
details,
I
actually
kind
of
just
heard
about
it.
Kubecon
a
couple
weeks
ago
and
I
haven't
had
an
opportunity
to
dive
into
it
by
no
Nate
Waddington
I
can
look
up
his
name.
If
you
want
to
get
get
in
touch
with
him,
he
does
the
mentorship,
so
he
might
have
some
more
resources,
so
just
review
of
what
what
the
mentorship
program
within
kubernetes
does
he's.
A
Somebody
who
works
for
the
cncf
and
he
works
on
a
mentoring,
ship
I
believe
that
that's
the
area
that
he's
been
focusing
on
so
I
can
send
you
guys
information,
so
you
can
learn
more
I
guess
something
I
just
thought
of
is
what
you're
looking
to
create.
Do
you
feel
like
it's
different
enough
specifically
look
to
your
localization
on
how
to
become
a
how
to
get
through
the
contributor
ladder
and
how
to
get
through
all
of
this?
Well,
we
what
we
have
in
English
to
become
reviewer
approver.
A
Do
you
feel
like
it's
a
different
path
enough
to
create
a
different
set
of
documentation?
I'm,
not
exactly
familiar
with
how
your
team
is
set
up.
So
I'm
just
I'm
just
wondering
what
you
think
the
differences
are
and
if
you
think
that
I
mean
we
could
also
update
the
English
documentation.
If
you
think
that
that
should
be
written
out
more
in
a
better
different
way.
That
would
help
also
help
all
the
teams
as
well.
C
It's
just
that
I
bottom
I
think
might
be
missing,
at
least
for
the
people
that
are
trying
to
contribute
to
the
Brazilian
Portuguese
localization
would
be
that
there
is
no
central
place,
that
they
can
look
for
documentation
when
they
are
onboarding,
and
that
was
kind
of
the
idea
that
we
had
is
like
just
having
like
one
Central
place.
That
could
be
consulted
for
the
old
information
that
a
new
contributor
would
like
have
foreign.
A
That
makes
that
makes
okay.
That
makes
sense.
Were
you
thinking
of
putting
that
on
the
website
like
somewhere
on,
like
your
specific
localization
or
website
or
I'm,
trying
to
find
an
issue
that
I
have
created,
so
something
that
I
would
like
to
update
eventually?
Is
our
sub
project
local
localization
guides?
A
So
this
would
be
just
more
information
about
how
localization
teams
are
structured
and
how
to
contact
them.
Let
me
share
it
in
the
chat,
so
in
general,
Sig
groups
within
kubernetes
documents
their
sort
of
process
processes
about
beam
structure
in
a
different
repo
than
the
website
repo
it's
in
in
the
community
repo.
A
Let
me
share
that
link
as
well,
so
it
might
not
be
the
place
specifically
for
the
contributor
guys
like
you're
talking
about,
but
I
do
want
to
create
a
place
that
we
can
talk
about,
how
our
sub
project
is
created
and
then
the
different,
how
kind
of
a
little
bit
more
details
about
how
specific
teams
are
created?
I
mean
who
the
leads
are
Who,
who
how
to
contact
them
where
to
find
that
information.
So
right
now,
it's
kind
of
a
little
sparse.
A
It's
because
we're
relatively
new
sub-project,
so
we
don't
really
have
that
content
documented,
but
this
might
be
another
area
that
you
can
come
we
can
create.
So
you
can
expand
this
content
in
in
that
centralized
place
if
you
didn't
feel
like
it
fit
well
with
the
website
or
anything.
So
this
is
just
another
area
of
you
know
to
be
done
documenting
in
the
same
vein
of
what
you
what
you're
saying,
but
I
did
want
to
share
that
that
issue.
A
C
Is
there
any
way
that
I
could
maybe
contribute
to
this
effort?
Because
it's.
A
Something
that
you
can
trust
me:
yeah,
I,
definitely
yeah,
so
I'm
trying
I've
been
trying
to
create
a
PR
of
what
I
have
I,
have
some
resources
that
I
have
not
made
available
for
folks,
but
I'll
try
to
create
a
PR
and
if
you
want
to
add,
add
your
thoughts,
you
know
read
through
the
issue
and
add
your
thoughts.
A
I
can
definitely
add
you
in
as
a
approval
contributor,
something
that
we
will
need
from
each
localizations
to
do
this
is
to
actually
have
them
write
in
a
little
bit
of
content
of
how
their
localization,
Works
and
and
who
you
know
like
I
mentioned,
who,
who
the
names
are
the
people
who
are
the
leads,
and
then
the
reviewers
and
approvers,
because
I
want
to
make
sure
that
one
people
are
recognized
in
the
way
in
the
community
for
the
work
that
they
are
doing
and
that
we
have
have
that
information
available
for
folks
to
contribute
so
yep
for
sure.
C
Yeah,
this
one's
good
I
think
it's
a
good,
a
first,
a
good
first
step
for
us
to
just
outline
like
some
more
information
and
like
we
can
iterate
as
we
go,
but
I
I
just
wanted
to
talk
about
the
idea
and
check
if
there
is
any
effort
going
on,
so
we
don't
duplicate
efforts
or
do
something.
That's
super
specific
for
Portuguese
but
doesn't
exist
in
other
localizations
because
they
feel
like
standardization,
is
good
nice
to
have
I.
Think
like
we
don't
want
to
drift
too
far
from
what
other
localizations
are
doing.
Foreign.
A
Yeah
for
sure,
that's
exactly
exactly
what
what
we're
looking
to
go
for.
I
think
previously,
most
of
the
teams
have
had
a
lot
of
more
latitude
to
create
the
team
and
the
structure
that
they
needed
to
to
to
to
get
the
content
moving
forward,
and
there
isn't
necessarily
any
oversight.
A
Oversight
on
how
teams
are
run
other
than
making
sure
that
they
subscribe
to
the
the
cncf's
guidelines
and
the
basic
structure
outlined
by
the
sigdocs
community
of
how
documentation
is,
is
actually
created
and
approved
and
merged
into
the
the
content.
A
But
it
I
think
it
will
be
helpful
to
to
add
in
some
recommendations
on
how
teams
have
been
structured
and
what
had
worked.
What
hasn't
worked
specifically
for
for
that
can
be
used
for
localizations
if
there's
any
differences
with
how
things
have
been
done
within
the
english
team.
A
So
that's
what
I'm
looking
to
create.
So
this
is
really
awesome
that
you're
interested
in
that
so
I'll
definitely
reach
out
for
for
ideas.
A
I
feel
like
I,
had
another
point
that
I
meant
to
bring
up,
but
I
forgot
what
it
was.
But
anyway,
that's
the
point
of
our
localization
in
general
is
to
try
to
create
a
centralized
place
to
talk
about
these
things
and
get
them
documented,
hopefully
so
that
we
can
help
all
of
the
teams
in
general.
So
awesome
I'm,
not
sure.
If
anyone
has
any
other
comments
on
this
topic,
but
I
know
you
also
had
another
topic
you
wanted
to
bring
up,
I
mean.
If
so,
if
you
wanted
to
dive
in
there.
C
C
So
I
think
when
you
enter
the
glossary,
there
is
a
blurb
explaining
what
the
glossary
is
and
then
we
have
like
this
categories
that
list
the
terms
inside
of
it
and
I
took
a
look
at
the
code
behind
that
and
it
doesn't
look
like
those
headers
are
localizable
because
they
come
from
yaml
files
and
I
at
least
by
first
looking
at
it.
It
doesn't
look
like
there
is
a
way
of
localizing.
C
Those
headers
I
also
noticed
that
it's
not
localized
in
other
localization,
so
I
guess
I
didn't
miss
anything
on
there,
but
I
was
wondering
if
there
is
an
effort
that
we
we
want
to
go
like.
We
want
to
sorry
losing
my
words
here.
I
was
wondering,
if
that's
an
effort,
we
want
to
have
at
some
point
in
time.
C
I
don't
know
if
it
would
pose
every
year
for
people
reading
documentations.
But
it
looks
a
little
strange
that
you
enter
a
localized
page.
Then
you
have
like
a
blurb
localized,
but
the
contents
like
the
the
selectors
are
not
so
I
was
just
wondering
about
that.
A
Can
you
share
where,
in
the
code
base,
this
is
because
I'm
not
familiar
with
the
glossary,
but
in
general
there
is
a
way
to
translate
to
make
these
the
phrases
translatable,
which
I
also
don't
have
handy.
Let
me
see
if
I
can
find
it
really
fast
in
the
website
foreign
which
I
should
I
think
we're
able
to
do
the
same
thing
hold
on
the
same
thing
that
we
do
in
other
places,
which
is
by
having
a
file.
C
C
So
the
the
specific
folder
we're
mentioning
is
on
the
website
the
data
slash
canonical
tags
folder.
If
I
look
at
this
correctly.
This
is
where
those
headers
are
coming
from
in
the
clustering,
I
say:
I.
Think
Soco.
Sorry,
if
I
didn't
read
your
name
right.
B
C
That
link
you
shared
is
exactly
what
I
am
alluding
to.
A
Okay,
thank
you,
and
so
here
is
the
other
part
in
the
data
file
in
the
sort
of
the
same
repo.
You
have
the
it's
internationalization,
where
we
Define
the
time
of
terms
which
are
like
the
headings
that
we'll
be
able
to
use.
So
this
is
how
we
do
it
throughout
the
site.
A
In
other
places,
we
have
the
English
file
and
then,
when
you
go
to
use
it
within
a
Content
file,
you
put
localization
a
Hugo
function
that
outputs
and
then
this-
and
it
will
read
this
file
to
Output
that
and
then
the
localization
teams
can
create
their
own
file
for
their
language
so
that
when
it
gets
outputted
on
the
site,
it'll
actually
do
the
translation.
A
In
that
way,
I
am
not
sure
how
we
can
merge
the
two,
but
that
is
how
we
do
this
similar
concept
within
other
parts
of
the
site,
so
that
might
be
something
to
look
into
the
localization
internationalization
function
within
Hugo
and
that
might
be
more
of
a
start.
I'm
not
sure
how
familiar
you
are
with
that
I'm
not
familiar
very
much
with
the
glossary,
so
cool.
If
you
okay,
meet
with
me,
calling
on
you
again
for
for
the
glossary
translation.
F
A
Yeah
I
think
that
would
be
perfect
to
talk
about.
We've
done
a
couple
of
PRS
to
clean
up
areas
where
there
are
still
like
non-translatable
strings
in
the
past
like
six
months,
but
there's
definitely
still
places
on
the
site
that
that
needs
to
be
addressed.
So
if
you
could
create
an
issue
that
would
be
really
awesome.
A
Okay,
I
believe
we
have
hit
the
end
of
our
agenda,
so
does
anyone
have
any
other
last
minute
thoughts
that
they'd
like
to
chat
about?
We
have
a
few
more
minutes.
A
Going
once
going
twice,
okay,
then
I
will
hopefully
give
you
guys
a
few
more
minutes
back.
Thank
you
for
joining
and
participating
in
the
discussion,
and
thank
you
for
for
the
demo.
It's
really
awesome
work
and
I
look
forward
to
seeing
the
future
iterations.
A
As
always,
our
next
meeting
will
be
the
next
first
Monday
of
next
month
and
in
the
meantime,
if
you
have
any
questions
or
anything,
you
want
to
chat
about.
Please
reach
out
in
the
sing
docs
localization,
Squad
Channel.
Okay,
have
a
good
rest
of
your
day
or
evening
wherever
you
are
in
the
world.
Alright,
bye.