►
From YouTube: K8s SIG Docs Localization Subproject Meeting: 2023-03-06
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
A
A
Let
me
share
the
meeting
notes
you
can
check
the
chatting
and
you
connect
with
the
meeting
notes
and
I
think
everyone
joined
at
the
team.
Note
and
yeah.
Please
add
your
name
in
participants,
yeah
I'm,
so
cool
I
am
actually
kubernetes.
Korean
localization
team
lead
and
I'm
learning.
This
meeting
on
behalf
of
Abby,
who
is
some
subject
code
share.
A
Okay,
is
there
any
new
contributor
workbooks
who
wants.
C
Thanks
for
calling
out
my
name,
hi,
everyone,
myself,
Arun
Kumar,
actually
I
was
previously
contributing
to
some
of
the
open
source
projects
like
Ubuntu
and
Destroy,
and
LibreOffice
Firefox.
C
C
So
I
would
like
to
start
my
contribution
sooner
so
yeah.
That's
a
short
introduction
about
me.
A
C
A
A
I!
Guess
everyone,
except
our
own,
are
very
expert
in
this
meeting.
So
let's
go
to
the
agenda
yeah.
Let
me
share
my
screen
so
that
you
can
check
the
meeting
document.
A
A
Thank
you.
Okay.
First
item
is
about
product
share,
Ibis
leave
coverage
actually
I'll
be
who
attended.
This
meeting
are
going
to
have
or
leave
so
we
need
to
cover
our
Leaf
around
four
months.
So
Natalie
has
volunteered
to
help
mentor
and
learn
the
localization
and
circle,
which
is
me
also
volunteer
to
help
to
run
the
localization
as
well
as
currently,
we
called
for
the
new
sub
project
call
it
so
I
plan
to
apply
the
that
responsibility
soon.
E
Nope,
just
the
general
announcer
that
I
will
be
off
pretty
much
starting.
You
know
at
the
end
of
this
week
or
kind
of
after
this
meeting
and
be
off
for
for
a
few
months,
but
I
know,
there's
been
a
lot
of
folks,
especially
people
on
this
call
who
are
available
in
the
community
to
help
and
have
a
lot
of
information
and
knowledge
about
the
localization.
So
if
you
have
questions,
definitely
reach
out
and
we're
looking
forward
to
meeting
back
again
with
you
in
the
summertime.
A
Okay,
bench:
okay:
let's
go
to
the
next
item.
It
is
about
reminder
for
the
katakoda
shutdown,
so
we
already
showed
that
this
message
in
last
weekend
and
as
I
know
Natalie
this
issue
and
for
localization
teams
and
contributors.
Once
the
replacement
were
removement,
so
katakoda
information
from
our
documented
documentation,
there
will
be
some
or
main
many
changes
in
document,
so
some
localization
language
requires
to
update
their
localized
document
so
for
that
you'd
better
to
check
issues
related
with
this
catalog
replacement
by
checking
a
detector
or
area
localization
labor.
A
I
think
people
who
participated
in
this
meeting
most
of
people
knows
about
this
reflector
and
localization
table,
but
since
some
people
will
see
the
recording
I
hope
so
what
it
is,
what
it
is
so
this
label
detector
means
English
documentary
that
issue
that
change,
PR
and
issue
that
changed
lots
of
English
content
so
requires
some
intention.
A
I
mean
some
checks
from
localization
teams,
so
you
can
check
maybe
regularly
for
this
stable
detector.
A
Also,
we
try
to
put
area
localization
labor,
which
are
very
related
with
the
localization
issues,
so
that
so
maintaining
people
folks
who
maintaining
localization
teamwork
each
linkage.
It's
better
to
check
this
area,
localization
labor
as
well.
A
D
I
did
want
to
add
that
on
the
English
side
we
will
be
putting
together
very
soon,
a
team
of
people
who
wish
to
help
taking
away
the
links
to
those
category
tutorials
once
that
shutdown
has
taken
place
again
with
the
shutdown
being
at
the
end
of
March.
At
the
end
of
this
month,
we've
got
a
bit
of
time
to
put
that
crew
together.
D
So
if
anyone
on
the
call
or
if
you
know
of
anyone
that
is
looking
for
possible,
interesting
work
to
do
and
they'd
like
to
help
volunteer
to
be
part
of
that,
there's
the
issue
linked
there
that
we've
got
some
information
on
that
they
can
put
their
name
on
to
say
that
they're
interested
in
some
of
that
work,
I
know
Nate
Waddington
who's,
one
of
the
technical
writers
for
the
cncf
has
already
put
his
hand
up
to
help
with
some
of
this
work,
and
so
this
will
also
help
to
inform
other
localized
documentation
about
the
work.
A
That's
nice
and
Natalie:
maybe
you
are
going
to
put
the
detector
and
area
localization
label
to
relate
to
the
TRX
right.
Yes,.
D
We
will
definitely
do
as
much
as
we
can
to
help
out
with
with
all
that
information,
including
adding
the
right
labels
correct.
A
Fantastic
and
I
will
I
will
check
cash
right.
Thank
you.
Okay.
Then,
let's
go
to
the
next
item
and
actually
this
item
also
a
kind
of
reminder
and
show
the
status
Finance
status,
and
there
is
an
issue
regarding
the
using
Umbrella
appears
for
small
changes
in
multiple
localization.
B
A
You
know
we
guide
a
written,
a
recite
that
chain
not
creating
a
PR
for
changing
multiple
languages
in
not
here,
but
sometimes
we
need
to
open
too
many
PRS,
even
though
the
change
are
very
small.
A
So
that's
the
reason
why
a
contributor
suggested
using
a
nuclear
issue
umbrella
peer
value
issue
for
customer
changes.
B
B
On
this,
which
is
that
we
should
really
avoid
doing
that,
because
a
contributor
is
busy
or
because
it's
annoying
to
do
small
things,
but
I
think
it's
different
if
we
wanted
to
if
we
have
to
make
an
exception,
for
example,
there's
two
big
things:
to
communicate:
there's
the
catechod
of
removals
and
there's
the
change
to
registry.cakes.io
when
things
are
high
value
for
the
project.
That's
that
tips
to
balance
I
think
so.
B
A
A
Actually,
the
current
state
status
regarding
this
issue
is
the
issue
is
closed.
It
was
closed
and,
according
to
the
last
localization
meeting,
we
kind
of
have
agreement
regarding
this
issue
not
not
apply
this
time,
but
keep
discussing
regarding
this
issue.
A
So
that's
the
reason
why
a
bigger
coordinated,
the
Dead
Issue,
so
maybe
I
like
Kim,
said.
Maybe
we
need
to
talk
about
what
is
good
for
us
and,
if
necessary,
we
need
to
find
a
common
workflow
and
maybe
for
the
umbrella
PR.
A
Okay,
is
there
any
test,
General
comments
regarding
on
this
issue,
protocol
comment.
A
Okay,
I
guess
none
and
let's
go
to
the
final
agenda
item.
I
I
put
this
item.
A
B
A
A
Period
is
from
some
short
code
short
code,
but
there
is
no
problem
in
main
branch,
but
maybe
some
localization
development
branches
have
faced
some
issues
so
I'd
like
to
share
how
Korean
team
fixed
this
issue.
As
you
know,
Korean
localization
team
has
our
own
Milestone
bench
strategy.
So
we
we
use
our
own
development
bench
based
on,
which
is
on
the
main
branch
like
this
ko1.
It
is
Korean
current
Korean,
localization
branch
and
it
is
ongoing
and
to
this
target.
There
are
many
peers,
localization
players
and
those
localization
KRS
currently
face
for
the
metullified
preview.
A
So
I
think
some
of
localization
teams
are
using
similar
way
with
career
localization
team.
Maybe
they
are
utilizing
their
development,
their
own
development
branch
and
I
hope
to
share
how
to
reserve
it.
The
localization
team,
you
that
use
their
own
development
branch
due
to
release
that
development
branch
and
we
get
contributors
to
update
their
ongoing
tier
localization
peers
with
that
branch.
Then,
then,
it
will
reserve
the
problem
and
is
it
actually,
a
team
suggested
way
right.
A
A
Person,
development
branches
that
cannot
apply
libation
rebasement,
such
as
Korean
localization
team
branch.
We
are
hard
to
apply
libase
to
that
Branch.
It
is
because
of
we
have
our
own
policy.
Regarding
that,
maintaining
that
Branch
we
we
try
to
avoid
elevation,
and
in
that
case
you
I
think
you
can
use
the
telephone
or
comment
from
domain.
You
can
check
the
link
it
is
away.
B
So
there's
rebasing
is
right
for
if,
if
one
person
is
working
on
something,
if
Natalie,
for
example,
is
working
on
a
PR
and
then
that
PR
is
not
building
because
of
the
the
rare
breaking
change
domain,
then
Natalie
you
should
be
base.
B
If
a
bunch
of
people
are
working
or
there
is
a
branch
that
has
worked
from
a
bunch
of
people,
then
the
usual
thing
to
do
is
to
merge
maina
into
that
PR.
So
you
would
see
this,
for
example,
with
the
dev
1.27
branch
we
have
the
dev
1.727
Branch.
We
won't
ask
people
to
reboost
those
changes,
that's
not
a
good
approach.
We
would
merge
Main
in
and
then
dev127
will
build
and
that's
a
good
choice
for
branches
where
there
are
multiple
pieces
of
work,
except
that
Korean
has
a
very
valid
way.
B
B
It
shouldn't
be
a
cherry
pick
where
conflict
conflict
resolutions
needed,
because
that
is
going
to
force
someone
else
to
do
another
conflict
resolution
in
the
future.
So
what
I
saw
on
Korean
looks
absolutely
fine
happy
with
it.
A
Okay,
thank
you.
Kim
for
the
declarative
in
additional
information.
Yeah
I
agree
opposed
to
Ray.
Revising
I
mean
the
varging,
their
development
Branch
to
main
first
and
think
each
other
with
a
better
way
and
both
desirable
way,
but
in
case
of
Korean
localizes
same,
we
are
utilizing
a
branch
strategy
in
our
own
way.
A
It
is
to
check,
update
the
contents
between
two
development
Korean
development
Branch,
so
that
we
can
check
what
has
been
changed
during
our
localization
chart
job
tasks
in
English
document.
Then,
by
checking
those
two
branches,
we
can
easily
gather
update
the
Korean
documents.
D
Yeah
I
think
just
what
you
mentioned.
Circle
I,
think
that's
very
useful
to
note
again,
which
is
the
Korean
way,
is
very
good
and
you're
doing
really
great
work
on
the
Korean
side,
but
for
other
localizations
who
are
listening.
That
doesn't
need
to
be
the
specific
way
for
you
to
go
about
this
as
well.
So
it
really
kind
of
depends
on
what's
going
to
work
for
the
different
teams,
so
yeah
I
think
that's
a
great
call
out.
A
If
any
teamwork
localization
team
face
any
difficulty,
then
or
technically
team
team
yeah,
then
they
will
help
you
right.
C
Since
I'm
the
very
beginner
in
this
localization,
but
I
would
like
to
understand
how
do
I
begin
so
I
use
the
main
branch
from
the
main
branch
and
then
start
working
on
the
changes
then
send
a
PR
to
the
back
to
the
team
or
shall
I
use
the
devil,
branch
and
poke
that
Branch
to
my
workspace,
then
make
changes
NPR.
So
what
is
the
best
way
for
me
to
begin
with,
in
order
to
contribute.
A
D
Help
here,
I
think
the
first
thing
Aaron
just
to
just
to
note
is
it
firstly
depends
on
the
on
the
way
that
the
localization
team
that
you'll
be
actually
contributing
to
your
work,
so
I
think
the
first
thing
that
you'll
want
to
do
is
actually
jump
into
the
slack
channel
of
the
localization
group
that
you'll
be
helping
to
contribute
to
and
engaging
with
those
folks
there
and
then
once
you've
done
so,
there
they'll
actually
have
quite
a
lot
of
likely
detailed,
planned
out
issues
and
things
that
they're
working
on
that
you'll
be
able
to
then
jump
into
and
start
working
on
as
well.
D
So
you
won't
have
to
make
any
of
those
decisions
on
your
own.
At
the
same
time,
like
you
mentioned,
Tim
Tamil
is,
is
very
early
on
and
so
I
think.
That's
part
of
the
reason
why
you
want
to
jump
into
that
community
and
actually
work
with
people
together,
rather
than
having
it
to
figure
it
out
by
yourself
to
see
what
they're,
already
preferring
in
terms
of
how
they're
tackling
some
of
that
work.
E
I
think
this
is
this
would
be
a
first
first.
We
don't
have
a
channel
for
that.
Localization
yeah.
This
was
like
very,
very
early
Beginnings
of
how
to
get
started.
So,
yes,
possibly
we
might
need
to
create
that
black
channel
to
build
start
building
that
Community
to
decide
what
the
best
path
is
or
for
folks,
which
I
am
not
sure
how
to
create
a
slack
channel
so
folks
have
any
I
can
have
some
recommendations.
There,
I.
C
I
heard
on
one
member
or
contacted
me
in
this
in
the
same
channel
earlier
and
then
I
also
had
previous
members
who
were
contributing
to
other
open
projects.
So
they
are
willing
to
contributed
in
this
project
as
well.
So
I
was
in
talk
with
them,
but
I
I
wanted
to
approach
in
the
right
way
so
that
there
is
no
struggling
in
between.
C
I
have
read
many:
the
I
mean
some
of
the
initial
documents,
which
is
very
important
for
any
beginner
to
start
contributing
to
the
localization
and
from
there.
What
I
understand
I
need
to
have
at
least
meaning
two
members
per
language
to
begin
with,
so
that
one
can
review
the
other
other
person's
contribution
in
order
to
make
sure
it
goes
well,
then,
how
to
send
the
pr.
C
A
Yeah
Arun,
thank
you
for
sharing
your
concern
and
questions,
and
can
you
I,
as
you
can
see,
the
screen
folks
participated
in
this
meeting
shared
the
variable
document
links
so
regarding
the
new
localization
could
be
testing
new
localization
group.
You
can
check
this
document
first
and
then
you
can
also
start
a
new
localization
by
changing
this
contribution.
Localization
type
and
you
can
check
the
oral
contents
regarding
localizing
the
document
and
you
can
find
start
new
localization
here.
B
A
Please
share
it
to
this
sub
project,
Channel
localization,
so
project
Channel.
Then
we
are
going
to
help
you
is
it
okay
alone.
D
You
yeah
further
in
that
documentation
Aaron,
once
some
of
the
more
administrative
tasks
have
been
looked
at,
which
is
creating
the
community
and
also
your
directory
and
so
on.
It
does
then
go
further
into
the
workflow,
but
there's
a
couple
more
steps
that
would
probably
need
to
be
completed
first,
first
of
all,
and
then
once
that's
done,
there
is
a
guide
of
the
minimum
amount
of
documentation.
You
should
start
localizing
as
well.
A
Thank
you
Natalie
for
the
additional
information.
Okay.
Is
there
any
question
or
comment
regarding
additional
discussion?
A
Further
additional
discussion,
the
attempts
in
the
agenda
is
end.
So
if
there
is
no
comment
or
question,
then
we
can
end
this
meeting
soon.
D
I
just
have
one
last
thing,
which
is
to
give
a
big
thank
you
to
Abby
for
all
of
her
great
work
so
far
with
running
the
localization
subproject
and
she's
about
to
go
on.
Some
very
well
deserved
very
well
deserved,
yet
still
very
busy
leave
just
busy
with
a
a
different
localization
project,
so
to
speak,
but
just
want
to
say,
yeah,
big
thanks
to
Abby
and
also
a
big
thank
you
for
entrusting
the
localization
group
to
Seiko
and
myself
and
and
yeah.
D
We
look
forward
to
welcoming
you
back
in
the
summer.
A
A
Thank
you
for
the
remark
of
this
meeting
and
I
guess
it
is
end
of
this
meeting
and
I'd
like
to
say
thank
you
all
and
it
especially
to
be
so
see
you
soon
yeah.
This
meeting
is
sent.
Thank
you.
Thank
you.
Bye,
bye,.