►
From YouTube: CNCF Glossary Working Group Monthly Meeting - June 2023
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
Recording
that
we
can
share
as
well.
So
let's
just
start
the
official
time
like
no
okay,
so
welcome
to
the
glossary
meeting.
A
few
glossary
updates,
Nate
the
cncf
deaf
Advocate
will
help
with
technical
reviews
and
we've
been
talking
or
I've
mentioned,
the
cloud
native
Learning
Journey
for
a
while,
because
we've
been
like
Gathering
ideas,
basically
like
have
all
these
different
resources
in
one
spot,
like
all
cncf
resources
right
like
starting
with
stuff
that
is
very
basic
and
then
like
going
with
more
advanced
in
advance.
A
So
we
have
a
developer
assigned,
which
is
the
same
as
for
the
Chris
Abraham,
the
same
person,
who
does
the
glossary
page
so
we'll
be
working
on
that
so
that,
like
actually
kind
of,
was
kicking
off
and
the
goal
is
to
have
that
Life
by
kubecon
and
then
have
the
cncf
push
it
out
and
yeah
just
so,
people
can
discover
different
resources,
including
the
glossary
and
seoko.
Are
you
oh?
His
audio
is
connecting.
Can
you
hear
us
now.
A
B
A
You
want
to
talk
through
your
section.
Sorry,
Al
I
can
put.
A
A
B
Actually
hope
to
share
that
some
latest
updating,
localization
related
issues,
I
hope
to
hear
share
that
there
is
new
localization
initiative
from
Japanese,
so
we
already
included
Japanese
members.
A
B
So
we
already
initiate
the
Japanese
and
we
are
we
already
created
Japanese
development
branch
and
they
already
opened
a
initial
PR
for
initiating.
They
are
supposed
to
to
compute
configurating,
their
localization
branch.
B
So
maybe
after
we
approval
up
here
that
need
to
lead
maintenance
or
forward,
then
they
can
start
their
translation
job.
So
I'm
going
to
ask
you
maintain
us
to
approve
the
Japanese
configurations
here.
B
Yeah
this
that
I
want
to
share
the
first
topic
and
second
one
is
actually
the
about
the
some
configuration
changes
regarding
the
Chinese
content.
B
Simplifies
the
Chinese
team
already
we
already
have
and
between
them
we
need
some
coordination
between
them.
Actually,
the
traditional
Chinese
majorly
used
by
Taiwan
people.
B
And
the
traditional
I
mean
simplified
the
Chinese,
youth,
divider,
Mandarin
and
Mainland
Chinese.
So
somehow
we
need
to
coordinate
them,
and
my
professor
is
that
the
we
have
to
change
the
context
to
original
context,
to
Chinese
to
into
the
simplified
Chinese
and.
B
I
try
to
suggest
to
change
current
Chinese
content
into
the
simplify
the
Chinese
content
and
we
already
added
the
traditional
Chinese.
B
A
B
C
A
Like
okay,
like
something
needs,
you
cannot
just
say,
Chinese
right
and
so
apparently
yeah
I
thought
it
was
really
interesting,
which
you
can
see
here.
This
is
much.
C
A
A
A
It's
like
okay,
what
is
the
actual
way
to
kind
of
differentiate
between
the
writing
styles,
and
so
that
was
a
interesting,
because
we
didn't
think
about
that
when
the
first
team
came
on
right
and
we
want
to
make
sure
that
we
accommodate
different
different
countries
with
different
versions
and
different
yeah,
who
use
like
yeah
different
writing
styles,
like
to
be
sure
that
we
can
accommodate
all
of
these.
If
we
want
to
have
them
eventually,
anyways
I
thought
it
was
interesting.
So
I
learned
a
lot.
B
I
I
just
want
to
say
that
it
is
the
based
on
our
discussions
between
other
localization
groups
as
well
as
closely
maintainers.
We
didn't
just
decide.
B
B
Is
there
any
opinion
or
question
regarding
on
that?
B
B
Yeah
thanks.
Actually,
we
already
decided
this
mirror
and
we
are
going
to
change
some
contents
regarding
the
the
existing
just
Chinese
content
into
the
simplify
the
Chinese,
so
that
you
can
accommodate
both
simplified
and
traditional
one
as
well.
So
we
are
going
to
do
that.
Actually
I
hope
to
see
folks
who
are
maintaining
co-maintaining
Chinese,
but
I
don't
see
in
current
meetings.
B
So
maybe
we
have
to
post
this
message
to
select
okay
anyway,
I
have
to
go
to
the
next
few
contents
and
I
like
to
share
that
we
actually
have
to
keep
localization
members
have
to
keep
updates
this
t-o-n-l
file,
which
can
convert
the
localization
content
based
on
some
body
very
uppers.
They
can
use
the
frequently.
B
So
if
we
change
English
content
in
climate
file,
it
should
be
applied
to
localization
content
surgery.
So
recently
we
added
this
some
UI
GUI
regarding
the
you
cannot
say
about
or
sensitive
related
contents
in
English,
so
localization
members
should
check
the
qml5
and
they
have
to
make
their
own
televisions.
Theory
in
my
pi.
B
The
section
should
be
localized
for
all
localization
contents,
so
I
hope
to
share
it,
but
I
guess
currently
people
who
joining
this
meeting
are
English
and
the
overall
maintainers.
So
let
me
share
this
message
to
localization
Channel.
B
A
A
B
Some
of
them
know
so,
ladies
yeah
are
we
I
will
introduce
it
later,
really
exporting
using
credit
cloud
and
public
cloud
in
just
usual,
Cloud,
mineral
or
Cloud
native
mineral
as
well?
So
maybe
I
hope
to
invite
the
Sloan
of
these
members
to
contribute
to
this
localization
effort
or
our
cluster.
That.
B
Yes,
the
I
I
covered
the
third
item
and
of
course
the
last
item
is
about
the
workflow
to
report
outdated
content
in
localization
content.
As
you
Arduino,
there
are
many
February
localization
branches
and
thanks
the
main
branch
English
contains
keep
changing.
We
need
to
keep
update
the
localization
branches
Etc,
and
it
is
not
easy
and
in
case
of
Korean
localization
team,
we
we
already
have
a
experimental
workflow.
B
Github
action
that
automates
the
difference,
taking
the
difference
between
English
content
and
localization
contents
and
making
a
report
for
using
our
own
issue.
So
you
can
check
the
the
link
I
provide.
B
Yeah
Catherine
you
can,
you
can
just
check
the
link
and.
B
You
say
it
is
issue,
and
it
is
kind
of
report
and
Korean
localization
team
try
to
check
the
changes
during
Korean
localization
job
regarding
the
English
content.
So
we
checked
the
changes
in
English
and
we
found
four
five
have
been
changed
during
our
localization
job
So.
Based
on
this
report,
we
can
check
which
content
should
be
changed
before
Korea.
A
That
this
can
be
automated.
It's
kind
of
crazy,
so
I
know
it's
great
to
capture
them
here,
but
we
were.
A
We
were
kind
of
thinking
of
creating
a
a
page
on
the
glossary
like
on
in
the
docs
or
something
where
we
can
capture
all
these
workflows.
So
there's
one
plate
because,
like
no
one
will
go
through
I
mean
if
it's
here
it's
going
to
be
lost
at
some
point
right.
We
want
to
make
sure
that
they
are.
These,
things
are
all
captured
somewhere
where
people
can
go
and
find
them
all
together
and
not
search
for
them
within
an
agenda.
A
So
we're
because
we
were
talking
about
it
right
to
create
like
a
I,
don't
know
we
have
or
it
could,
it
doesn't
have
to
be
here.
It
can
actually
be
in
the
in
the.
B
B
We
made
a
workflow
effective
to
Korean
only,
but
once
Korean
team
think
it
is
very
beneficial
for
for
all
localization
teams
globally,
then
we
will
keep
share,
how
it
works
and
how
to
apply
it.
B
Then
I
think
it
is
very
beneficial
to
other
localization
teams
who
are
struggling
struggling
in
the
keep
updating
the
English
content
to
their
local
life
contents.
A
Yeah
I
mean
it's
a
question
that
comes
over
and
over
again,
so
if
you
figured
a
good
workflow,
we
have
to
put
it
prominently
somewhere
on
the
localization
dock,
so
people
can
find
them
okay.
So
if
you
say
you
want
to
test
it
first
and
kind
of
be
sure
that
it
works,
that's
great,
but
let's
not
forget
to
because
to
add
it
right:
okay,
cool.
B
Sure,
thank
you
and
I
would
like
to
say
that
it
is
not
perfect,
it
cannot
be
perfect.
Actually,
it
is
based
on
my
experience
in
kubernetes
technical
documentation
localization
since
after
the
four
years
it
is
not
perfect,
but
you
have
to
keep
update,
really
means
the
color,
localization
team
hope
to
collaborate
and
keep
update,
and
actually
we
need
more
collaborations
from
other
localization
teams.
I
hope
to
mention
that.
A
B
A
Let's
kind
of
maybe
like
put
a
call
to
action
in
the
localizations
channel
as
well
like
for
other
teams
to
help
with
that.
B
Sure,
okay
and
okay,
that
next
time,
yeah
I,
think
we
can
go
to
the
the
next
item.
A
So
the
Italian
team
wrote
here
that
it
would
be
nice
to
have
an
automation
that
creates
a
new
issue
for
localization
teams.
Every
time
a
new
term
is
emerged
in
the
English
French.
A
B
B
B
So
maybe
we
can
perlance
well
whenever
we
have
changes
something
and
making
our
issue.
Opening
issue
is
not
good
for
maintenance,
since
we
have
to
keep
trace
the
changes.
B
So
maybe
we
have
some
consensus
on
the
a
trade
of
in
this
manner
since
we,
the
people
participating
with
this
meeting,
is
or
maintain
Earth.
B
Maybe
another
way
is
to
creating
a
new
label
for
localization,
so
that,
if
we
make
lots
of
changes
in
terms
where
we
make
a
new
term
in
English,
then
you
can
put
a
new
label
localization
so
that
other
localization
teams
keep
checking
the
new
changes
or
new
terms.
How
about
that.
A
Yeah,
so
that's
on
us
to
remember
to
do
that.
The
same
thing
would
be
with
a
new
with
a
new
term
right,
a
completely
new
term.
We
could
remember
to
post
something
in
the
channel
as
well
right
like
more
or
do
like
and
do
an
issue.
C
I
kind
of
don't
understand
is
if
the
solution
that
you
were
talking
about,
Circle
that
you
already
have-
and
you
have
to
test
it
if
it
can
detect
both
the
changes
and
the
new
stuff.
B
B
So
if
we
say
there
are
not
sure
30
English
terms
and
Korean
localization
team
translated
the
15.
C
C
It
understandable
yeah,
yeah,
I
I
got
it
so
so
so
this
this
concern
that
the
Italian
people
brought
up
would
not
be
would
not
be
catched
by
that
solution.
So
we
maybe
would
have
to
think
about
such
an
automation
right.
B
Sure
actually
I
think
in
case
of
Korean
localization
team.
We
try
to
make
our
workflow
that
automate
checking
the
outdated
contents,
but
the
other
localization
teams,
don't
so
in
case
of
Italian
localization
team.
Think
if
we
keep
changing.
If
we're
making
us
some
changes
in
English
content,
then
they
think
how
why
English
don't
keep
changing
and
how
to
play
and
how
to
sense
the
change
with
content.
B
So
the
reason
why
I
suggest
to
to
making
a
new
label
localization
is
that
I
would
like
to
announce
the
localization
who
maintainers
can
check
major
changes
in
English
terms
so
that
they
can
hinder
the
differences
yeah.
C
B
A
B
A
Then
an
issue
for
new
terms
right
and
say
like
attention:
localization,
Team,
new
term
whatever
and
then.
C
Yeah
I
mean
I
mean
it
in
the
very
end.
It
doesn't
really
matter
from
automation,
point
of
view.
If
we
create
the
label
or
or
a
new
issue,
well
I'm,
a
huge
fan
of
creating
labels
versus
then
issues
to
be
honest,
but
yeah
I,
I,
I.
Guess
we
because
this
topic
is
already
showing
up
since
a
long
time
period.
I
guess
maybe
always
in
different
kind
of
shapes
but
yeah,
I,
guess
I,
guess
we.
We
should
investigate
a
little
bit.
B
Sure
no
we
have
to
investigate
and
keep
saying
that
it
is
the
workflow
from
South
Korean.
It's
not
perfect
and
the
supportive
way
is
making
a
a
localization
labor
so
that
provide
we
can
just
put
the
localization
label
or
actually
detector
label
to
the
PRS.
B
That
changes
English
content,
a
lot
yeah
I
I
think
it
is
both
ways
so
yeah
in
case
of
Noah.
You
cares
about
the
grocery
overly,
as
well
as
the
German
localization.
So
if
you
are
the
co-maintainer
of
localization
for
Germany,
then
maybe
you
can
check
the
that
refactoring
or
localization
labor
to
keep
up
to
date.
B
Your
the
German
contents,
but
maybe
maybe
sometimes
later,
if
Korean
localization
team
will
Brazilian
team
have
make
a
new
best
practice
to
update
the
changes
in
English
content,
then
maybe
you
try
to
follow
or
emails.
C
Yeah
yeah
I
try
to
I
try
to
catch
up
if
I,
if
I
get
everything
right.
So
your
suggestion
is
to
to
introduce
the
refactoring
label,
for
example,
and
that
we
apply
it
to
to
pull
requests.
That,
then,
would
imply
changes
on
the
English
term.
No,
it's
the
other
way
around
right.
So
every
time
yeah
yeah.
B
By
majorly
by
PR,
so
if
we
change
some
Tom
in
English
yeah
then-
and
we
maintain
this-
maybe
think
it
is
too
much
changes.
Then
maintenance
or
localization
maintainers
can
put
that
kind
of
localization,
labor
or
localization
some
detector,
so
that
other
members
yeah
who
maintaining
localization
can
check
and.
C
B
B
B
C
A
C
A
A
C
B
Yeah
yeah
actually
I
need
some
feedback
from
localization,
co-maintainers
or
purpose,
but
yeah
I'm
going
to
share
this
mirror
to
selection,
a
leisure
so
that
others
can
provide
any
feedback
from
on
this
issue.
Yeah.
C
B
Are
we
putting
it
to
the
next
two
meeting
as
well?
Thank
you,
Lord.
C
I
guess
it's
it's
it's
time
to
to
give
an
update
about
the
German
localization.
So
I
guess
the
block
is
finished.
We
we
have
all
the
content
right.
B
B
C
But
I
checked
that
only
11
are
online.
We
I
I
just
need
to
to
do
a
rebase
and
to
yeah
to
to
to
to
merge
the
we
need
to
merge
the
the
branch
with
the
main
branch
to
update
everything.
C
We
have
three
terms
in
review
at
the
moment
and
we
have
one
new
active
kind
of
active
person
and
it
would
be
cool
if
we
we
can
manage
to
to
keep
that
person
in
the
team
yeah.
So
that's.
A
B
C
A
A
C
Which
is
kind
of
cool
and
yeah?
It's
pretty
similar
to
our
team.
The
team
is
starting
to
be
more
active
and
have
more
exchanges
and
the
path
to
publish
the
first
version
has
been
shared
and
the
green
between.
So
apparently
they
have
kind
of
agreed
on
a
workflow,
which
is
a
good
thing.
I
guess.
A
So
they
decided
as
well
to
kind
of
select
terms
that
make
sense
together,
so
they
kind
of
they
didn't
just
do
it
like
ad
hoc,
which
was
kind
of
interesting.
They
had
like
a
strategy.
So
I
was
like
oh
interesting,
so
once
they
go
live,
it
will
actually
be
pretty
solid,
like
there
will
be
a
lot
more
to
it,
which
is
kind
of
cool.
A
Round
robin
I
would
like
to
I
guess,
I
think
so.
Could
you
put
some
kcd
info
in
here.
B
And
I
I
suggest
to
to
a
smart
talk
to
cage
the
Taiwan
and
accept
it
so
I'm
going
to
say
about
some.
B
B
It
will
happen
in
July
and
I
already
have
a
an
appointment
on
appointment
regarding.
B
Contribution
in
Cloud
native
it,
the
content
should
be
majorly
in
kubernetes
figured
off
but
I
hope
to
introduce
regarding
the
grocery
as
well.
A
Yeah
and
just
be
sure
to
let
people
know
I
think
like
at
the
beginning
of
the
conference.
Like
you
know,
just
letting
people
know
that
there
is
a
glossary,
that
they,
because
it's
not
only
contributing,
is
like
letting
people
know
that
there
is
a
glossary
in
Korean
right,
so
I
think
it
doesn't
need
to
be
a
session
or
anything
but
like
since
you're
one
of
the
co-organizers.
A
B
B
So
may
not
have
too
much
the
introduction
Pages
it
really
just
to
majorly
focused
on
how
to
processes
how
to
contribute
to
extensive
managers.
Kubernetes.
B
This
those
presentations
and
I
just
thought
to
share
I'm
working
on
the
party
address.
B
A
B
A
B
I'm,
sorry,
if
co-worker
from
here
eyes,
luckily
I
aware
of
what
this
is
about
and
I
have
to
introduce
that
we
are
using
using
setting
workflow
in
our
GitHub
repository
setting,
so
that
workflow
applies
our
sharing
configuration
into
GitHub
repository.
B
So
if
we
need
to
update
operas
or
maintain
our
permissions
new
development
branches,
then
I'm
I'm,
very
sorry.
It's
very
hard
place
in
South,
Korea
and.
B
B
It
is
how
we
works
when
we
add
new
localization
members
or
when
you
exchange,
maintain
us
permission,
but
recently.
B
Exchange
ship
organization
added
new
workflow
kind
of
workflow
in
the
covers
for
repositories
in
shenshi
Phuket
table
organization,
that's
effective
to
change
organization,
which
is
people.
B
Checked
all
members
in
chainsafe
organization
and
actually
cares
and
Sheriff
with
our
individual
repositories
repositories
at
not
confirmed
or
embedded
members
or
permissions.
B
Is
it
understandable,
yeah.
A
B
A
B
A
Things
but
I
think
like
circle
like
the
whole
thing
like
how
to
do
like
the
whole,
the
technical
stuff
like
honestly,
it's
like
you
and
jihoon
are
kind
of
like
always
been
our
leads.
It's
like
just
do,
whatever
you
think
is
yeah.
C
I
think
that's
what
I
was
going
to
say
so
I
mean
I.
I
cannot
really
say
if
it's
like
good
or
bad.
That
way,
if
you
guys
say
that
yes,.
B
B
B
A
Sorry
yeah,
so
we
only
have
three
more
minutes.
I
just
want
to
be
sure
that
we
get
through
the
suggested
terms
as
well,
so
I
put
the
little
thumbs
ups
and
downs
and
question
marks
that
we
had
on
Slack.
A
So
I
don't
know
who
did
what
like?
Oh
to
be
honest
for
sure,
abuse
has
two
thumbs.
B
C
No
I
was
just
suggesting
that
we,
just
maybe
maybe
or
the
ones
who
are
clear,
like
Cloud
native
storage,
is
it
three
times
thumbs
up
and
the
Chrome
drops
like
three
times
thumbs
down.
We
just
we
can
just
go
on
and
label
them
accordingly.
I
could
do
it
right
now.
B
C
To
concentrate
otherwise.
B
Yes,
I
I
think
the
the
thumbs
over
early
I
think
are.
They
are
very
fundamental
Thomas
except
the
web
assembly
part.
B
So
I
mostly
put
the
thumbs
down
in
case
of
me
and
in
case
of
the
message
queue
I
put
Curious
mark
since
I
think
they
I
think
the
message
that
you
are
very
foreign.
B
So
in
the
perspective,
I
think
we
should
include
the
term
but,
as
you
know,
the
term
is
very
general
term
than
General
technology
or
general
functionality
in
not
only
the
cloud
computing
but
also
in
just
Computing
part.
A
B
So
I
think
I
I
saw
a
barely
related
to
the
term
already
to
find
the
time
in
Colorado
closely,
which
is
eventually
been
architecture
which
includes
some
kind
of
description
related
with
kapka
are
actually
Caprica
is
a
solution.
They
provide
the
kind
of
message
queue,
so
they
are
very
relative.
So
maybe
we
can
lead
the
contributor
to
update
the.
B
Event
disturbing
architecture
thumbs
about
the
message
too,
not
just
to
not
affecting
them.
B
C
I
I
said
thumbs
down
so
I
I
think
event-driven
architecture
is
valid,
but
message
cues
is
like
a
certain
technology,
so
I
don't
know
I
I,
don't
think
it's
it's
also.
It
exists
also
without
like
without
cloud
native
yeah,
so
I
would
I
would
I
would
not
accept
it.
B
B
A
A
B
You
yeah
thank
you
so
yeah
in
case
of
the
web
assembly,
part
I
think
we
got
some
agreement
from
Chris
Visual
and
I
am
I.
B
A
Was
like
that,
when
we
decided
that
we
forgot
to
okay,
so
I'll
highlighted
that.
B
Yeah
so
pretty
the
okay.