►
From YouTube: K8s SIG Docs Localization Subproject Meeting: 2023-04-03
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
Hello,
everyone:
this
is
kubernetes
civil,
docs,
localization
soft
productivity,
so
this
meeting
is
based
on
Exchange
code
of
conduct.
So
basically,
please
try
to
respect
other
books
and
try
to
live
life.
B
A
So
let
me
start
myself
I'm,
so
cool
I'm,
currently
leading
Korean
localization
I
I
will
contributed
to
Korean
localization,
maybe
more
than
four
years
so
long
time
and
I'm
contributing
this
localization
cell
project
making
on
graph
of
RB.
Who
is
a
co-chair,
a
single
co-chair
of
desktop
project,
so
maybe
Natalie.
Can
you
introduce
yourself.
C
Sure
hi
everyone
I'm
Natalie
vladko
I,
am
one
of
the
coaches
for
sick
docs
and,
like
Circa
mentioned
with
Abby,
being
the
sole
localization
lead,
just
want
to
say
a
big
thank
you
to
Suki
sioko
for
stepping
in
to
help
out
and
hopefully
wanting
to
be.
Also
a
leader.
The
localizations
of
project,
too
yeah
I've,
been
a
stigdox
co-chair
for
a
while
now
contributor
for
a
while,
now
really
great
to
meet.
Everybody
and
I
will
pass
it
off
to
Ray.
D
Hey
folks,
my
name
is
Ray
alejano
I'm,
also
one
of
the
Sig
docs
co-chairs
as
well.
I've
been
Sig
docs
for
a
number
of
years.
I,
don't
actually
remember,
since
it's
been
about
three
years
or
four
years
or
so.
I
also
help
out
with
the
documentation
updates
for
releases
as
well.
I've
been
a
prior
release,
lead
and
I'm.
Also
one
of
the
a
previous
for
the
for
the
English
side
as
well.
All
right,
I'll
pass
it
on
to
whoever
would
like
to
go
to
Maxim,
hey.
E
Everyone
I'm
sick
dogs,
Ukrainian,
localization,
video
or
owner
I
would
call
it
in
company
I
just
and
maybe
for
three
or
more
years
right
now
we
try
to
investigate
how
it
can
be.
E
All
of
this
I
mean
translation
can
be
achieved
more
quickly
because,
as
I
remember,
where
we
just
initialized,
we
introduced
many
docs
and
right
now
we
understand
that
it's
about.
E
0.3
percent
of
author
of
documentation
that
exist
in
the
websites
website
repo
and
that's
not
cool,
just
do
it
inside
it
and
just
not
work
very
well.
A
Thank
you.
Thank
you,
Maxim
and
Welcome
to
our
community
and
welcome
to
this
meeting.
Maybe
if
they're
oriented
over
there.
F
Can
yeah
hi?
Thank
you
for
hearing
me
I'm.
My
name
is
Olin
and
I'm
I'm
contributor
and
maintainer
of
Harbor
projects
in
Valero
and
I'm
super
interested
in
translating
the
kubernetes
documentation
in
Bulgarian,
so
I'm,
one
of
the
Bulgarian
translations
leads
wannabe
and
also
by
chance
I'm
in
the
same
team
as
IB
is
so
we're
teammates
with
Abby
I,
didn't
know,
she's,
leading
that
that
effort
I
was
super
surprised,
so
yeah
I'm,
sorry
for
not
starting
my
camera,
but
I'm
at
the
hospital
right
now.
F
So
it's
not
like
the
most
appropriate
thing
to
do,
but
super
happy
to
join
you
folks,
I'm,
looking
forward
to
working
with
you
and
get
the
translation,
Bulgarian
translation
on.
Thank
you.
A
G
Yeah
I'm
actually
I'm
I'm.
Probably
this
is
the
first
time
I
joined
this
meeting,
but
I
actually
joined
some
other
related
meeting
before
I'm
yeah
I'm
I
actually
already
participated
in
several
efforts
to
translate
into
Mandarin
Chinese
yeah.
Just
I
was
not
part
of
the
original
localization
team
for
the
Mandarin
Chinese
vocabulary,
but
yeah
with
the
lab
to
contribute
wherever
there
is
a
high
priority,
translation
needed
for
anything
to
the
tremendary
Chinese.
A
That's
nice
I'm
not
sure
how
to
pronounce
it
but
yeah,
because
you're
interested
yourself.
H
C
I
Can?
Okay,
okay,
it
was
Hardware
on
you,
sorry,
guys,
hello,
I'm,
Alexa,
I'm,
another
part
of
Ukrainian
internalization
team.
Actually,
the
person
who
get
all
the
stuff
with
let's
find
the
good
of
the
platform.
So
we
could
not
just
do
translation,
but
do
it
efficient,
because
all
those
projects
are
always
short
on
people.
I
So
it's
it's
not
all
about
just
legal
theorems
or
just
sticking
with
one
tool,
but
getting
as
much
as
possible
from
one
person
free
time
as
effective
as
it
could
be.
So
I
got
to
Maxim
asked
what
was
done
for
last
two
years
and
we
started
roll
all
this
stuff
again.
Something
like
that
here,
looking
to
get
the
waste
communication
is
going
to
what
is
checking
here.
Maybe
we
will
find
some
answers
to
our
questions,
we'll
see
sometimes.
A
C
Yeah
sure
so
for
folks
who
are
new
generally
to
docs
and
especially
to
localization,
we
have
indocs
a
program
that
we
call
the
pr
Wrangler.
It
is
someone
that
has
approval
status
that
every
week
they
take
on
trying
to
make
sure
that
we
can
push
contributions
through
the
PRS
that
we
have
through
the
pipeline
efficiently,
so
that
we
don't
have
a
big
backlog
of
PRS,
especially
given
during
release
time,
where
docs
PRS
often
go
up
very
high
in
number.
C
The
pr
Wrangler
system
that
we
have
going
is
something
that
we
try
and
use
to
get
push
contributions
through
and
I
mentioned.
All
of
this,
because
part
of
that
wrangling
is
that
we
try
and
make
sure
that
we
can
get
out
PR
number
down
to
a
a
really
manageable
size
and
at
the
moment,
that's
between
around
100
to
150
open
PR's.
At
a
time,
however,
with
a
lot
more
localizations,
as
a
note,
we
had
nine
languages
live
in
2019
and
now
in
2023
we
have
15
languages
live.
C
It
does
mean
that
we
have
a
lot
more
localization
PR's
that
are
open
for
the
website
and
that
stay
open
for
a
very
long
period
of
time,
and
so
in
in
the
case
of
a
PR
Wrangler
who
is
coming
on
for
the
week
to
try
and
push
contributions
through.
We
want
to
try
and
figure
out.
C
How
can
we
also
do
so
specifically
for
the
localizations
and
do
we
want
to
perhaps
introduce
a
time
frame
a
lot
longer
than
what
we
usually
would
for
PRS
that
remain
open
on
a
localization
side,
so
that
a
a
new
contributor
to
that
localization
can
possibly
take
on
that
piece
of
work
or,
if
it's
not
being
worked
on,
it
can
be
closed
and
reopened.
C
When
it's
able
to
be
worked
on
so
I
wanted
to
bring
that
here
to
the
community
as
a
proposal
that
we
have
a
three
months
maximum
for
localization
PR's
to
be
open
and
that
localization
leads
like
sioko
Abbey
and
then
also
myself
as
one
of
the
there's,
the
stigdox
co-chair
liaison
for
localization
that
we
can
come
in
and
generally
close,
those
PRS
when
the
time
frame
has
has
been
reached
with
some
kind
of
message
around.
C
They
can
be
reopened.
When
someone
has
the
capacity
to
rework
on
them.
So
I
want
to
bring
that
here
to
the
community
as
a
possible
proposal
and
see
what
people
think.
A
Yeah
to
comment
to
Alternative
issue
regarding
the
fair
here.
If
there
are
any
question
or
comments
regarding
on
that.
D
This
is
more
of
a
comment,
just
some
other
additional
I
guess
background,
not
exactly
feedback
but
I
I.
Think
from
what
I've
seen
some
of
the
stale
PRS
is
from
a
lack
of
reviewers
and
improvers
for
the
localization.
D
So
that's
why
we
we
ask
for
to
have
at
least
minimum
two
reviewers
and
I've
I
I,
don't
know
if
if
we
should
have
a
minimum
free
reviewers
is
the
way
to
go,
because
if
you
only
have
two
reviewers,
it's
it's
and
if
one
is
out
or
or
if,
if
one
is
out,
it
makes
reviewing
more
complicated
because
we
do
like
to
have
a
two
two
of
two
reviewer
process
where
one
person
gives
the
LGT
on
one
person.
Does
the
approve
outside
of
the
pr
author?
D
So
it
might
be.
It
might
be
good
to
to
welcome
new,
a
previous
or
new
reviewers
in
a
previous
for
localizations
as
well
to
help
folks
ramp
up
in
in
the
localization.
So
that's
just
one
kind
of
just
one
comment.
C
Yeah
I
I
think
that's
actually
really
valid.
I
think
also,
you
know
everyone's
capacity.
It
changes
at
different
times,
right
and
I
think
we
should
also
be
able
to
make
room
for
that.
C
So
yeah
I
I
completely
agree
that
trying
to
get
also
more
reviewers
on
to
possibly
lower
the
amount
of,
let's
say
PR
that
would
be
closed
or
would
become
stale.
Because
of
that
is
a
problem.
I
think
that's
a
great
idea.
A
A
So
maybe
the
reason
why
some
peers
are
open
too
long
is
because
not
because
of
PR
author,
usually
because
of
review
times,
so
maybe
how.
B
About
this
I
think.
A
If
there
is
no
response
from
peer
loss
for
three
months,
then
maybe
you
can
close.
That
means
it
is
not
because
of
the
reviewer
and
review
process.
It
is
love,
there's
no
feedback
from
piano
service.
Then
maybe
you
can
close
after
three
months.
C
Yeah
I,
like
that,
a
lot
as
a
note
for
everyone
on
the
call.
We
actually
have
a
time
frame
of
two
weeks
across
the
docs,
so
I
do
want
to
make
it
a
lot
longer
in
the
localization
space
because
of
the
different
kind
of
work
it
is
and
also
the
availability
of
that
work.
We
obviously
have
a
lot
more
reviewers
and
approvers
for
English,
so
extending
that
amount
of
time
I
think
is
good.
C
But,
yes,
I
think
the
three-month
closure
is
should
be
dependent
on
no
answer
from
the
pr
author
I
really
like
that.
As
a
stipulation.
C
And
so,
if
you
want
Yoko,
you
can
put
in
a
to
do
for
me
I'm
happy
to
do
it
that
we
can
upgrade
update
our
or,
let's
say,
put
the
that
information
out
into
the
community
via
docs
and
also
maybe
the
mailing
list
and
get
some
lazy
consensus
or
just
a
general
like
feedback
around
it
as
well
outside
of
this
meeting,
just
because
it's
there's
only
a
small
amount
of
attendees
before
we
update
our
documentation
on
that.
A
Okay,
thank
you.
Let
me
finish
the
meeting
not
together.
Okay,
we
I
guess
we
already
agreed
to
with
the
clothes
in
sale,
localization
KRS.
If
the
care
author
do
not
provide
any
feedback
for
more
than
three
months.
E
Issues
exist
that
can
close
prison
issues
and
eat
able
to
send
like
hey
books.
I
will
close
this
issue
rpr
in
n
days.
If
nothing
will
happen
here,.
C
Oh
yeah
communication
would
absolutely
happen.
It
wouldn't
just
be
closed
automatically.
There'd
be
messaging
part
of
that
too,
for
sure,
part
of
the
update
for
the
other
localization
folks
would
be
to
give
this
information
to
their
channels
directly.
First,
before
we
actually
implement
the
rule
so
that
there's
a
blanket-wide
understanding
that
this
is
something
that
localization
leads
will
do.
E
C
Oh
definitely-
and
this
is
also
to
clarify-
if
you
were,
that
needs
to
reply
or
or
look
at
the
PR,
but
the
pr
also
has
done
everything
they
need.
Then
the
pr
would
stay
open
if
it's
still
just
waiting
review.
C
This
is
specifically
if
the
author
of
the
pr
hasn't
responded
to
suggested
changes
or
feedback,
or
anything
like
this.
Okay
yeah.
It's
definitely
based
on
the
pr
author.
Only.
B
A
Okay,
thank
you,
and
is
there
any
folks
who
have
any
question
regarding
this
or
comment.
A
That's
me:
I
added
several
items
in
the
agenda
and
I
just
mentioned
that
cook
continue
will
be
soon
and,
as
you
know,
many
folks
are
very
busy
in
this
period
and
until
end,
so
please
understand
that
responses
can
be
delayed
for
response
for
PR
issue
and
select.
So
please
understand
then
aware
it
is
just
to
let
post
know.
F
C
Yeah,
so
there's
not
a
specific
one
planned
for
localization,
but
we
do
have
General
a
lot
of
folks
going
to
the
contributor
Summit
for
Sig
dots,
that's
something
where
we
can
meet
there.
Otherwise,
if
you're
interested
in
putting
together
a
localization
kind
of
ad
hoc
Meetup,
we
should
definitely
try
and
figure
that
out,
maybe
in
the
stigdox
localization
channel
to
see
who's
going
to
be
there
from
kubecon.
F
Yeah
I
cannot
do
it
for
the
whole
group.
I
can
try
for
the
bigger
one.
I
have
a
lot
of
my
plate,
I
mean
for
harboring
stuff,
but
I'm
I'm,
just
curious
to
see
who
is
in
the
other
side
of
the
line,
not
just
zoom.
F
Unfortunately,
I
cannot
join
the
contributor
Summit
because
I'm
not
officially
contributor,
yet
so
I'll
try
to
figure
this
out
and
then
to
meet
you
in
person.
There.
C
Sure
yeah
I
think
there's
also,
unfortunately,
a
few
of
us
with
a
lot
on
our
plates
for
keepcon,
which
is
why
something
like
this
hasn't
been
planned,
but
yeah.
We
can
definitely
try
something
ad
hoc,
it's
also
very
hard,
given
that
it's
very
often
not
everyone
can
be
at
every
conference
too.
So
that's
we
always
try
and
make
sure
we
do
as
much
virtually
as
we
can
yeah.
F
D
There
is
also
a
talk
at
kubecon
EU
Natalie
Tim
bannister
on
above
is
how
to
localize
company's
documentation,
so
I'm
sure
a
lot
of
folks
will
will
be
there.
If
you
want
to
say
hello,
yeah.
A
A
Thank
you.
Okay.
Let's
go
to
next
item
and
I
hope
to
share
that
there
is.
There
are
new
selectioners
for
new
localization
initiation,
so
kubernetes
selection
or
Tamil,
and
there
is
a
selection
for
brigadian.
A
So
maybe
there
is
no
timer
and
guardian
contributor
in
this
meeting,
but
yeah.
Please
share
this
information
to
other
friends
if
they
are,
if
your
friends
are
interested
in
yeah.
F
Just
to
update
you
on
this
one
I
already
already
addressed
that
to
the
local
community
and
also
we're
going
to
have
a
Meetup
right
after
kubecon
I'm,
the
Bulgarian
cncf
organizer
for
meetups,
so
that
to
get
Public,
Super
quickly
and
yeah,
so
I
hope
someone
will
join
me
in
that
effort
and
also
I
spoke
with
a
few
universities,
universities
in
Bulgaria.
F
So
our
my
idea
is
to
involve
students
in
and
to
open
the
doors
for
the
open
source
for
them.
So
that's
that's
the
whole
effort
behind
the
localization.
A
Oh,
that's,
that's
the
thing
for
Korean
team
is
in
group
10,
so
maybe
we
don't
have
to
worry.
Okay,
I
just
wanted
to
share
this
information
and
I
also
got
a
DM
personally
regarding
Turkish
localization
initiation.
So
maybe
you
will
see
turkishi
selectioner
as
well
soon.
C
Yeah
I
got
DM
as
well,
and
I
think
this
might
be
something
that
I
know
it's
been
brought
on
violin
before,
but
something
that
we
may
need
to
make
sure
that
are
updated
in
our
localization
guide.
That
a
lot
of
folks
are
missing
out
that
they
need
to
be
kubernetes
organization
members
first
before
starting
a
localization.
So
that's
something
that
we've
taken
on
board
that
we
need
to
update
as
well
we're
getting
a
lot
of
interest
in
starting
localizations,
but
without
any
previous
contributions
to
kubernetes.
D
On
right,
we
are
seeing
I've
seen
in
someone's
org
membership
when
I
was
looking
at
org
memberships
I've
seen
people's
efforts
to
their
commits
to
in
a
localization,
because
it
is
a
PR
to
a
kubernetes
website
that
it's
been
used
for
org
membership,
I.
G
F
B
A
Yeah
actually
I
put
this
item
in
order
regarding
Mr
leading
sentence
in
localization
guys
it
is
about
the
membership
yeah.
If
we
check
this
localization
kite,
you
will
see
this
kind
of
sentence.
A
When
you
will
open
up
all
localization
here,
you
can
become
members
of
the
kubernetes
kit
of
organization,
so
yeah
according
to
the
actual
load
and
responsibility
becoming
a
member.
This
guide
and
regulation
request
and
list
the
five
substantial
fully
test.
So.
Currently,
our
clients
have
some
misleading
sentence,
so
maybe
not
only
is
working
on
updating
this
part.
C
Yeah
we
we
myself
and
Ray
and
Divya
Al
Avoca
who's
unable
to
be
here.
We
plan
to
update
that
soon,
given
that
it's
it's
it's
more
than
one
case
of
misleading
I,
think
so
we
need
to
make
sure
that
folks
know,
and
unfortunately
this
is
one
of
those
things
that
it
was
just
obvious
to
us,
but
completely
new
contributors
may
not
be
able
to
actually
understand
that
that's
the
case,
so
we
just
need
to
make
that
perfectly
clear.
H
H
C
So
the
the
the
short
answer
is
yes,
we
do
have
a
couple
of
steps
that
you
need
to
go
through
to
initiate
that
and
Allen
is
going
through,
actually
some
very
similar
things
at
the
moment,
like
a
gathering
community
and
making
sure
that
your
kubernetes
organization,
member,
so
that
you
can
contribute
and
become
a
leader
of
the
localization
set
of
documentation.
C
C
It's
definitely
something
that
is
a
a
community
effort,
but
just
needs
your
own
kind
of
drive
as
well.
So
have
a
look
at
the
in
the
chat
just
now
the
link
that
reposted
so
that
you
understand,
what's
required
to
start
a
localization,
but
you
don't
need
to
ask
permission
for
a
specific
language.
We
welcome
all
of
them.
Having
said
that,
there's
a
minimum
set
of
documentation
that
is
required
also,
first,
and
so
a
lot
of
that
information
is
in
the
doc.
In
the
link
that
Ray
just
sent
to
you,
there.
G
Thanks
I
understand
the
relationship
between
localization
and
helping
translation,
because
I'm
already
involved
in
helping
translation,
maybe
not
kubernetes,
is
actually
cscf
some
projects
so
but
I'm
not
I,
know
there's
already
a
localization
for
Mandarin
Chinese
I'm,
not
part
of
it.
So
it
does.
That
is
there.
Do
I
have
to
join
the
localization
group
before
helping
translation
for
even
non-kubernetes
specific
projects.
C
So
so
this
specific
localization
subproject
is
for
kubernetes
only
in
terms
of
what
we're
talking
about
for
now,
and
so,
when
you
say
join
the
group,
what
we
kind
of
mean
by
joining
is
is
really
just
engaging
with
the
community
and
that
can
be
via
the
kubernetes
slack
and
joining
the
specific
Mandarin
Chinese
channel
that
exists,
because
they'll
have
a
lot
of
information
about
maybe
what
help
they
need
or
where
they're
looking
for
support.
C
That
would
be,
if
you're
interested
in
kubernetes
specific
localization.
That
would
be
what
we
would
recommend,
but
across
other
cncf
projects
they
would
have
then
their
own
rules
or
their
own
things
and
the
processes
around
what
you'd
need
to
do
for
localization.
So
this
is
specific
for
the
kubernetes.
G
C
If
they
have
a
localization
group,
that's
that's
up
to
them,
because
you're
dealing
at
a
project
level,
you
need
to
do
what
the
project
requires,
so
the
cncf
being
the
larger
Foundation
that
has
many
projects
you
want
to
engage
specifically
with
project
maintainers
on
those
specific
rules.
For
now
for
kubernetes
we
are
the
localization
project
maintainers
and
so
for
kubernetes
joining
the
group
via
the
kubernetes
slack
and
engaging
in
the
community.
That
way
is
how
you'd
get
involved
in
localization,
okay,.
G
C
What
it's
it's
to
become
an
organization
member
you
need
to
contribute
to
kubernetes
and
organ
member
means
that
you
have
a
couple
of
extra
Privileges
and
those
privileges
are
important
specifically
for
localization
leads,
so
that
they
can
get
the
privilege
of
having
reviewer
and
approval
status
on
PRS.
C
So
it's
a
it's
a
it's
a
permissions
related
requirement,
but
not
every
project
always
has
this.
It's
you
really
do
have
to
double
check
per
project.
Whether
those
requirements
exist.
C
If
you
just
want
to
participate,
for
example,
throw
up
a
couple
of
possible
PR's
of
interest
for
the
for
the
Mandarin
Chinese
localization,
you
don't
need
to
be
a
kubernetes
member.
No
okay,.
C
A
Problem,
thank
you
Victoria
and
Natalie,
and
maybe
you
can
go
to
the
next
two
lifted.
I
came
and
if
so
by
me
and
I,
have
a
question
regarding
the
initiation
of
new
localization
I
hope
I
hope
to
check
what
is
the
minimum
number
of
local
localized
the
document
to
make
it
like?
D
D
A
So,
according
to
this
content,
you
only
just
need
a
few
few
documents
right.
A
Yeah
I
I'm,
not
sure
the
relative
to
you
localized
the
document
I
mean
I
mean
live
localization.
Let
me
let
me
check
the
this
contents
and.
A
Try
to
follow
I
mean
follow
up
the
the
latest
PR
to
make
new
localization
life
anyway.
Thank
you,
Ray
I
I
couldn't
find
this
contents.
I
Honestly,
what's
missing
on
this,
how
the
style
utilization
page
is
how
to
check?
Is
someone
already
working
on
your
language
or
not
because
you
know,
depending
on
what
stage
of
the
work
it
there
could
be
some
code
in
GitHub
there
couldn't
be.
There
could
be
group
in
the
slack
there
couldn't
be
so
honestly,
it's
not
the
clearest
way
to
check
this.
C
Yeah
I
think
that's
a
good
point
and
I
think
we
could
possibly
add
to
the
add
to
the
docs
checking
if
the,
if
a
channel
for
your
specific
language
exists,
that
means
there
has
been
or
is
some
interest
or
some
kind
of
existence
of
a
community
or
work
going
on.
C
Yeah
I
was
about
to
say
a
channel
is
a
good
indicator.
It's
not
exactly
a
yes
or
no
answer,
but
it's
a
good
indicator
of
how
you
can
go
about
searching
whether
someone's,
already
working
on
the
language
that
you're
interested
in.
C
Yeah,
that's
I,
think
that's
something
good
to
add
to
our
docs
as
well
as
there's
a
you
know.
You
should
come
into
the
kubernetes
like
and
look
for
the
channel,
and
we
mentioned
that
we
want
to
use
the
international
standard
code
so
linking
to
the
the
standard
again
and
using
the
usual
Channel
prefix,
so
that
folks
can
search.
I
C
Yeah
yeah,
maybe
pointing
them
to
the
seek
docs
localization
channel
so
that
folks,
yeah,
no
I,
think
that's
also
a
good
idea,
so
at
least
coming
into
the
select
to
ask
and
then
having
the
option
of
possibly
looking
for
the
channel
as
well.
That's
a
great
that's,
a
great
call,
it's
great
to
add
to
the
docs.
F
By
the
way,
such
thing
exists
there,
but
it's
not
exactly
that
strict
like
if
you
want
to
have
a
channel.
You
should
open
up
here
in
that
file
with
that
with
that
legalization
code
and
so
on
and
so
on.
So
if
someone
is
super
interested
in
studying
this
one,
they
will
never
literally
find
that
there
is
a
channel
requested.
F
But
it's
not
quite
super
explicit.
You
have
to
check
for
a
channel.
So
if
you
use
common
sense,
you
you
find
out
whether
it's
not
a
strict
thing.
C
Yeah
I
mean
that's,
that's
also
a
good
point,
but
I
think
an
interesting
barrier
to
entry.
Sometimes
if
people
often
won't
want
to
start
unless
there's
already
some
Community
as
well,
it
can
be
very
hard,
as
I'm
sure
you're
about
to
find
out
Holland
to
kind
of
get
started
on
your
own,
and
you
need
to
try
and
find
some
people
who
are
interested
as
you
so
sometimes
I,
think,
even
though
it
might
be
common
sense.
Spelling
it
out
a
bit
more
explicitly
like
human,
like
Alexi
mentioned,
might
be
worthwhile.
E
By
the
way,
do
you
have
some
list
of
useful
documentation,
because
we
are
right
now,
kubernetes
have
very,
very
big
docs
us
about
how
it
should
be
the
contributor
to
dogs.
Do
we
have
some
to
London
reads
list,
or
was
this
like
go
here
and
check
this
like
I,
don't
know
QRC
or
something
like
that.
I
Yeah
something
like
tldr
not
scan
through
the
Aussies,
but
you
definitely
should
know
about
this
and
this
and
these
recommendations,
something
like
this.
E
Contribution
for
localization,
because
we
are
on
secret,
docks
right
now
it
can
be
done
for
each
City
if
they
would
like
to.
But
for
my
perspective,
we
are
interested
right
now
on
localization
how
to
add
how
to
go
on
how
how
to
another
thing,
because
I
remember
when
I
have
searched
or
you're
going
to
have
a
possession
I
need
to
go,
maybe
in
three
or
four
repositories
to
just
to
understand
what
they
should
do.
C
Right
so
we
do
have
a
general
how
to
contribute
to
kubernetes
and
again
getting
started
guide
on
General
contribution,
but
only
for
localization
that
doesn't
exist
but
General
how
to
how
to
contribute.
As
a
raise
now
like
put
in
the
chat
thanks,
Ray
we've
got
localization
there
and
you
you
can
contribute
here,
but
basically
you
want
to
just
basically
also
be
going
to
General
contribution
part.
Let
me
just
put
this
here.
This
is
the
one
that
I'm
referring
to.
B
Yeah,
okay,.
E
C
Mean
so
yes,
but
I
think
what
what
I,
what
I
wonder,
is
how
what's
your
expectation
of
how
long
you
should
spend
understanding
how
to
contribute
before
you
can
contribute?
I
guess
is
my
question.
I
Perspective
some
person
wants
to
add
something
to
open
source
project.
They
ready
to
put
their
minimum
to
localization
and
they
are
not
much
Tech
persons.
They
don't
really
know
how
to
work
with
all
our
dogs,
all
our
structures,
chats,
etc,
etc,
etc.
A
quick
Link
in
the
start,
you
will
need
to
check
to
look
for
your
answers.
How
to
work
with
us
here
could
change
the
game
dramatically.
I
You
know
not
just
due
to
use
common
sense
and
look
for
all
this
stuff,
because
it's
so
the
link
in
Google
Now.
We
all
know
that
we
have
a
different
output
on
Google,
because
it's
personalized
and
the
same
is
the
background
people
with
different
backgrounds,
looking
through
this
different
way.
So
again,
a
fast
link,
just
a
few
links
for
sale
there
before
starting
to
go
to
localization.
Please
check
this.
You
need
to
know
this.
If
you
have
questions
look
here.
C
Yep,
so
on
the
link
that
I
just
sent
to
you
and
under
doc
slash
contribute
under
getting
started.
There
are
three
points
and
when
you
just
mentioned
the
let's
say
use
case
of
someone-
that's
maybe
not
so
technical
or
doesn't
know
where
to
start
under
that
specific
dock,
we've
got
getting
started
and
we
say
to
get
involved
with
documentation.
Number
one
sign.
The
CLA
number
two
familiarize
yourself
with
the
repository
and
the
static
site,
generator
and
number
three
understand
basic
process
for
opening
a
PR
and
reviewing
changes
all
with
links
attached.
I
B
E
Yeah
I
yeah,
it's
almost
exactly
what
what
we'd
like,
but
it
can
be.
Firstly,
simplify
it
because
Google
don't
need
to
contribute
to
the
documentation
at
all.
You
can
just
not
run
it
locally.
It
can
be
around
inside
VR
also
make
sure
it's
a
basically.
C
So
yes,
so
so
I
wanna,
I
wanna
stress
a
couple
of
things.
So
I
agree
with
you,
but
the
kubernetes
docs
needs
to
focus
specifically
on
kubernetes
and
we
can't
write
a
tutorial
about
how
to
open
a
PR.
Let's
say
only
like
they.
There
are
other
docs
specifically
for
GitHub
that
are
about
this
too.
So
we
do
need
to
make
sure
that
limiting
the
amount
of
content
that
we
create
or
linking
to
external
content
as
well.
If
you
know
what
I
mean.
D
You
click
on
the
link.
Steps
for
opening
up,
PR
and
using
GitHub
goes
through.
Their
workflow
goes
to
a
step-by-step
listed
directions.
It's
already
listed
there
just
on
the
link
opening
a
pull
request
using
GitHub.
A
Yeah
also,
we
have
document
guide
documents
and
also
we
have
some
Community.
We
have
a
community
for
localization
or
just
documentation.
So
maybe
there
are
very
excellent
folks
who
are
very
interested
in
mentoring,
opening
up
PR
or
other
contribution
aspect.
So
in
case
of
Korea
localization
team,
we
try
to
keep.
B
A
Or
students
who
don't
understand
the
guitar
or
yourself
we
try
to
next
study,
try
to
guide
them
so
that
they
can
a
little
bit
easily
understand
the
whole
document,
such
as
the
localization
guide
or
contribution
guide.
So
we
have
multiple
efforts
in
multiple
ways,
so
the
guide
document
is
not
just
one
way
to
make.
New
contributors
are
involved.
A
C
Your
points
about
the
simplifying
I
think
are
really
valid
and
I
think
the
best
way
is
to
look
at
that
contribute
guide
that
we've
linked
and
if
you
think
it
could
be
a
simpler
way,
submit
the
pr
to
make
it
simpler.
We
will
happily
like
review
it
I
think,
okay,
if
you
think
that
that
should
be
improved
overall
for
everyone.
A
A
Okay,
I
guess:
if
the
left
I
can
let
it
start
and
is
there
any
other
questions
or
discussion
points?
Please
prepare
to
add
any
discussion.
Point.
C
E
Anderson
from
threat
so-called
or
not
boy,
yes,
you
need
to
get
answered
from
Cynthia
Foundation
because
they
write
on
the
progress
for
this
percent.
What
does
understand
SLA
is
not
check
authors
at
all,
but
in
the
same
time
Circle
mentions
that
they
add
co-authors,
to
commits
for
some
reason,
but
if
easy
slide,
don't
check
it
for
what
purpose
they
added,
because
I'm
not
sure
how
it
matched
with
CLA
workflow
or
just
because
it's
worth
check
it.
In
previous
stage
when
PR2
feature
browse
was
measured.
C
So
I
I
want
to
go
to
back
to
the
kind
of
purpose
of
that
thread,
which
is
that
the
Ukrainian
localization
wants
to
use,
translate
a
translation
platform
to
help
make
it
more
efficient
in
terms
of
the
work
that
you're
doing
and
I
want
to
be
very
I.
Think
purposeful-
and
this
is
a
big,
not
assumption,
but
from
my
last
check.
I,
don't
believe
any
other
localization
has
any
kind
of
tool
that
they
use
in
the
way
that
you're
that
you're,
suggesting
or
proposing.
I
Yeah,
okay,
right
now,
right
and
actually
actually
from
what
I
can
see
how
I
see
the
picture
at
the
moment.
It's
all
deep
soundtrack.
It's
not
the
word
solution,
but
it's
not
effective
solution
for
translation
documents
for
managing
documents
because
of
a
lot
of
reasons,
but
it
have
its
sense
also
because
kubernetes
first
of
all
is
a
software
package
and
it
makes
sense
not
to
make
any
more
tools
and
more
and
more
and
more,
you
don't
know
when
these
two
or
that
will
die
and
everything.
I
So
we
as
a
first
looking
for
the
way
to
integrate
with
what
we
can
do
to
this
model.
So.
A
I
Is
a
second
note:
okay,
my
first
plan
was
to
create
another
repo
with
the
fork
of
kubernetes
website,
make
all
translations
there
and
work
on
the
translation
platform
there
and
from
which
make
PRS
to
the
original
Repository.
But
in
the
middle
of
the
process
we
have
faced
few
behavioral
things,
one
of
those
PRS
from
the
platform
they
all
go
in,
not
like
a
person
like
a
bot.
I
But
when
we
are
making
this
from
translation
platform
to
PRS
is
starting
to
get
messy,
because
we
need
some.
You
know
utility
proxies
some
tools
in
between.
So
what
we're
trying
to
get
Is
How
We
Do.
Could
we
do
it
better?
The
main
question
as
I'm
getting
it
from
your
side
is
how
much
machine
work
will
be
involved,
how
much
reviewers
will
be
involved,
and
what
about
CLA
Chile
is
the
simplest
one.
If
CLA
described
signed
on
the
platform
could
be
allowed
transfx
it's
a
platform
via
choose.
I
For
the
moment,
we
checked
something
like
at
least
three,
maybe
four
of
the
different
translation
platforms.
It's
most
agile
and
it's
looks
like
huge
best
for
the
need
and
it's
aloe
to
give
CLA
to
sign
to
the
any
person
who
work
on
the
project.
C
Yep
so
I
watch
I'm
in
there
Maxim
you've
already
opened
up
a
ticket
with
the
Linux
Foundation
to
check
on
a
lot
of
this.
Unfortunately,
we're
not
going
to
be
able
to
answer
legal
questions
in
this
meeting,
which
is
why
we've
just
we
discussed
about
opening
the
ticket,
because
the
CLA
problem,
the
transfx
CLA
and
the
kubernetes
CLA-
are
different.
C
They
are
different
legal
agreements
and
so
that's
going
to
be
the
bigger
issue,
and
so
that's
why
we
need
to
check
with
Linux
foundation
and
their
legal
team
as
to
how
that
could
even
work.
C
D
I
We
need
to
yeah,
yes,
that's
clear,
I'm,
just
I'm
just
clarifying
the
situation,
because
I
have
feelings
for
that
from
the
starters
the
ground
in
the
eyes
of
the
you
know,
different
people
have
changed
at
least
three
times,
maybe
five
times
so
I'm
trying
to
synchronize
everyone.
Something
like
that.
I
B
G
Personal
experience,
using
like
chat
DBT
to
fix
for
translation
for
many
Chinese,
actually
works
sort
of,
but
you,
if
you
just
put
everything
like
one
article
in
feed
into
the
chat
DBT,
it
doesn't
do
very
well
and
I
also
talked
to
the
there's,
a
German
translation
effort
on
some
of
the
Articles,
and
they
say
that
the
new
answer
doesn't
work
at
all.
So,
yes,
it
depends
I.
Think.
E
E
I
I'm
confused
that
when
we
are
mentioned
in
Translation
platform,
everyone
here
machine
translation,
that's
not
the
same
like
at
all.
We
are
not
talking
about
machine
translation.
We're
talking
about
platform
to
to
to
make
it
easier
for
translators.
Human
translators
cooperates
working
on
the
one
document
when
you
have
few
or
versions
few
options
of
the
string,
translation
on
the
same
window
when
you
or
the
whole
team
could
vote
for
the
best
translation
when
editor
could
see
those
changes.
I
When
you
see
original
Doc
and
the
translated
dog
together
and
all
the
options
and
one
of
the
benefits
which
could
use
on
the
road
is
machine
translation.
But
it's
not
the
main
goal.
It's
it's
something
like
you
know,
seven
priority,
not
the
first.
The
first
is
to
make
easier
for
translators,
reviewers,
to
check
other
text
and
to
check
the
options.
C
Okay,
so
I
think
that's
good,
because
it's
a
that
is
a
like
a
tool
that
yes,
the
Ukrainian
localization
would
want
to
use,
but
we
wouldn't
want
to.
If
that
became
a
thing
that
could
be
used,
we
would
wouldn't
want
to
only
restrict
that
to
a
single
localization
and
possibly
open
that
up
to
many
of
the
localizations
to
use
as
well.
That
would
mean
that
would
need
to
be
a
decision.
That's
just
beyond
this
meaning
and
would
have
to
actually
go
to
overall
kubernetes
membership
and
Leadership
should
I
say
to
to
approve
so
I
think.
C
C
Yeah
I
mean
that
would
be
what
I
would
recommend
if,
like,
if
we're
saying
that,
eventually,
let's
say
down
the
line,
a
tool
like
this
is
possibly
approved
to
be
used.
Why
should
only
one
localization
have
the
use
of
it
and
so
being
able
to
use
it
across
many
localizations
would
actually
require
larger
approval
than
what
we
only
in
sync
docs
can
provide.
We'd
have
to
actually
take
it
higher
up.
So
that's
something
else
that,
as
a
note
how
the
decision
process
would
be
made.
That
would
happen
need
to
happen.
C
Second,
to
make
sure
that,
like
everyone
is
aware
on
this
on
this
meeting,
and
so
that
we're
clear
we
require
in
Docs
human
review,
even
if
a
translation
machine
translation
has
be
been
used,
we're
not
against
using
a
machine
translation
at
first
to
try
and
help
with
the
process,
but
we
require
human
review
after
that
fact,
before
a
PR
is
submitted
to
make
sure
that
said,
translation
is
actually
accurate.
C
I
I
But
those
reviews
are
done
before
PR,
so
the
questions,
if
few
of
our
reviewers
already
checked
the
document
before
PR,
what
we
need
to
review
also,
what
approvals
we
need
more
or
why
we
need
two
three
four
approvals
after
the
pr
is
made
when
all
of
this
part
of
all
of
this
job
on
the
localization,
exactly
not
on
the
documents
just
localization
even
before.
C
E
Even
the
girl
from
my
site,
they
can
do
it
just
to
need
to
be
sure
that
we
can
do
localization
inside
Transit,
fast
code,
Universe,
poetry
or
other
stuff,
because
right
now
it's
a
little
bit
blocked
during
the
CLA
and
other
stuff.
Sure.
B
E
Mean
of
course,
I
I
can
grab.
For
example,
I
can
set
up
a
how
it.
E
For
one
because
it's
like
I
steal
something
work
and
commit
us
from
myself,
but
it's
it
will
work
for
a
bus
CLA.
But
it's
it's
scratch
so.
C
I
think
the
original
confusion
between
it
being
machine
or
not
Alexi,
that
you
mentioned,
is
that
none
of
us
know
any
more
about
what
this
platform
is.
So
if
you
could
provide
a
link
or
information.
C
B
C
Screen
now
yeah,
but
the
link
that
you've
just
added
in
here
that'd
be
great
I.
Think
sioko.
Could
you
please
add
that
link
to
the
these
meeting
notes
so
that
we
have
it?
We
don't
lose
it
after.
We
end
the
meeting
so
that
we
can
investigate
what
transfix
is.
I
One
of
the
options,
but
the
most
agile,
from
what
we
saw
and
once
again
we
checked
only
those
of
translation
platforms
who
suggest
free
of
free
for
open
source
or
some
other
similar
benefits.
C
Great
Ray,
that's
on
you
and
me
I
believe
to
have
a
look
at
transfx
as
well.
I
know
you
have
to
drop,
thank
you,
but
then
we
can
jump
back
in
on
the
thread
and
also
back
in
the
channels
with
yourself,
Alexa
and
Maxim.
Also,
once
we
find
out
about
the
CLA
ticket
as
well,
that.
A
Yeah,
thank
you
maximum
Lexi
and
yeah
as
a
Korean
localization
contributor
I.
Also.
We
also
have
some
difficulties
in
keep
updating
outdated,
localization
contents,
but
we
somehow
find
our
workflow
GitHub
natively
and
kubernetes
documentation
natively.
We
find
the
way
so
other
localization
teams
and
localization
languages
contributors
also
adopt
their
own
way.
So
using
a
transcript
is
also
one
way,
I
think,
but
we
need
to
see
if
beneficial
to
other
comparable
to
the
kubernetes
website,
repository
guitar
based
repositories.
A
Maybe
you
can
share
a
beneficial
point
of
strength,
transit
to
us,
maybe
kind
of
demonstration.
Okay,
yeah
I
think
it's
almost
over
our
meeting
time
and
we
discussed
over
several
items
a
lot
I
guess
we
can
close
this
meeting
now.
Is
there
any
comment
regarding
this
meeting.