►
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
Every
week
we
bring
a
new
set
of
presenters
to
showcase
how
to
work
with
cloud
native
technologies,
and
you
might
notice
where
this
is.
This
seems
like
a
rerun,
but
don't
worry
about
that
jason
closed
us
off
at
the
end
of
the
year
and
we've
got
him
back
to
kick
things
off
this
year
should
be
fun.
These
people
will
build
things,
they
will
break
things
and
they
will
answer
your
questions
join
us
wednesdays
at
11
a.m.
Eastern
time
today
is
a
little
bit
later,
but
you
know
the
rules
were
meant
to
be
broken.
A
This
week
we
have
jason
morgan
and
catherine
paganini
here
to
talk
with
us
about
the
cloud
native
glossary.
This
is
an
official
live
stream
of
the
cncf
and,
as
such
it
is
subject
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
the
code
of
conduct.
Basically,
please
be
excellent
to
one
another
and
be
respectful
of
all
your
fellow
participants
and
presenters
with
that
I'd
love
to
turn
it
over
to
jason
and
catherine
to
kick
off
today's
presentation
with
that.
B
Oh
okay,
well,
hey
folks!
Thanks
thanks,
so
much
for
joining
us,
so
we're
we're
here
today
to
talk
to
you
about
actually
not
technology,
or,
I
guess
only
obliquely
about
technology
and
a
little
bit
about
words
and
what
they
mean
and
how
we
define
them
and
catherine
you
want
to
you
want
to
add
anything
sure.
C
Yeah,
maybe
so
yeah
we're
going
to
talk
about
the
cloud
native
glossary,
and
so
I
think
we
should
probably
get
started
about
telling
you
a
little
bit
about
why
what
it
is
and
why
we
created
it
right.
C
So,
basically,
it
all
started
a
little
bit
over
a
year
ago,
when
jason,
I
launched
the
cncf
business
value
subcommittee,
so
we're
both
co-chairs
there
and
the
goal
of
the
committee
is
create-
is
to
create
resources
that
explain
why
and
how
cognitive
technology
such
has
such
a
big
impact
on
the
business
right,
and
we
want
to
explain
that
not
for
people
without
a
technical
background
and
if
you're
wondering
why
you
probably
noticed
that
cloud
native
has
become
really
mainstream
or
is
becoming
more
and
more
mainstream.
C
More
and
more
people
are
getting
touched
by
it,
just
think
of
a
decision
of
a
company
whether
to
migrate
an
application
to
a
microservices
architecture.
That's
a
huge
decision.
It
can
cost
millions
of
dollars
and
it's
not
a
decision
that
is
made
in
the
c-suite,
not
not
in
the
I.t
department.
The
c-suite
is
also
involved
right,
so
you
have
business
people
now
having
to
make
those
decisions
and
they
have
to
understand
what
the
heck
all
this
cloud-native
stuff
is
right,
so
they
need
to
get
up
to
speed.
C
But
if
you
look
out
there,
most
content
is
really
kind
of
targeted
for
technologists,
and
that
makes
it
really
difficult
to
understand.
If
you
don't
have
a
tech
background,
so
that's
the
why
for
the
business
value
subcommittee,
so
when
we
started
we
were
thinking
okay
before
we
can
do
any
of
that
right.
We
have
to
agree
on
how
we're
talking
how
we
want
to
talk
about
terms
like
if
we're
talking
about
service
mesh.
C
What
does
it
mean
right
and
also
we
don't
want
to
be
explaining
all
these
things
all
over
again
right
like
if
we're
writing
an
article
about
containers,
we
don't
want
to
be
explaining
what
containers
is
and
then
in
the
next
one
exchange
all
over
again,
so
we
realized
okay,
we
need
a
glossary
we
can
refer
to,
and
so,
although
this
all
started
like
this
thing,
we
wanted
to
do
before
we
could
do
what
we
actually
wanted
to
do
right.
C
So
the
goal
is
really
to
explain
cloud
native
concepts,
technology
and
approaches
in
very
easy
and
simple
terms,
so
we're
using
no,
no,
no
tech
jargon,
no
buzzwords
trying
to
use
real
life
examples,
something
anyone
can
relate
to
like
anyone
who
uses
a
smartphone
who
uses
a
laptop
wi-fi
all
these
concepts
of
something
that
that
you
can
understand
right
and
turns
out
that
explaining
complex
concepts
in
simple
words
is
really
really
hard
right.
So
it's
really
easy
to
fall
back
to
industry
terms
right
like
it's,
because
that's
how
everyone
talks
about
it.
C
So
it
requires
a
lot
of
discipline
and
it
is
really
incredibly
rewarding
too,
at
least
for
me
like
I
had-
or
I
have
no
technical
background.
So
for
me,
when
I
started
learning
about
this,
I
really
really
struggled
understanding
it
so
and
for
me
like
knowing
that
people
now
that
are
in
that
position
have
something
they
can
kind
of
read
and
is
easily
and
access
and
accessible.
That
makes
me
really
really
proud,
so
I'm
really
glad
we
did
this
and
yeah
jason.
Do
you
want
to
add
anything
to
that.
B
No
not
not
a
time,
catherine,
like
so
katherine
nailed
it
right
like
we,
you
know.
We
started
this
business
value
meeting.
We
probably
had
like
20
folks
on
and
like
whether
you're
a
marketing
person
a
salesperson.
Like
me,
I've
been
been
doing
like
engineering
for
about
20
years.
Well,
engineering.
Maybe
it's
a
stretch,
but
I've
been
doing
computer
work
for
about
20
years,
and
you
know
we
just
didn't
we
didn't
agree.
We
were
all
using
words
in
different
ways
and
it's
like
oh
wow.
This
isn't
like
this
isn't
bible.
B
So,
let's,
let's
define
stuff
and
and
yeah.
I
hope
folks
like
check
it
out,
so
they
posted
the
links
now
in
the
chat
post.
Some
links
in
the
chat
there's
a
a
website
and
that
website's
powered
by
git
repo
and
we'll
talk
about
all
that
as
we
go,
but
please
check
it
out.
A
Professional,
you
know
an
expert,
please
don't
try
this
at
home,
george
jensen,
it's
just
just
yeah,
hopefully
not
a
big
road
button
in
most
cases,
awesome
awesome.
Thank
you.
It's
it's
really
helpful
to
be
able
to
have
a
glossary
and
to
not
gloss
over
the
the
details
and
the
finer
points
of
these
things.
I
must
say
it's.
I
think
that
it'd
be
helpful
too,
for
when
trying
to
describe
to
friends
and
family
members
kind
of
like
what
you
do.
A
You
know
now,
there's
now
there's
a
resource
for
some
of
those
terms
and
some
of
those
things.
So
thank
you.
Thank
you
both
so
much
for
really
kicking
this
off
and
for
for
making
this
happen.
With
that
I'd
love
to
ask
both
of
you.
Can
we
can
we
take
a
little
bit
of
a
tour
through
the
glossary.
A
B
All
right,
so
I've
got
my
handy
dandy.
Laser
pointer,
draw
drop
the
mel,
I'm
sorry,
I
don't
know
how
to
say
that
name,
but
for
and
not
just
for
you,
but
for
anyone
right
like
come
check
it
out.
We
desperately
want
help
right
so
there's
about
50
terms
in
here
in
in
english,
and
thank
you,
daniel
they've,
been
about
there's
about
50
terms
in
here
today.
B
In
english
and
one
you
know,
we'd
appreciate
folks
to
just
review
individual
definitions
and
if
you
like
it
or
don't
like
it,
you
know
leave
us
a
comment.
Well,
maybe
don't
leave
an
issue
if
you
like
it,
but
leave
an
issue
or
send
a
pr.
If
there's
things
that
you
need
that
you
think
need
fixed
or
if
you
want
to
define
a
new
term,
create
an
issue
come
in
and
we'll
talk
about
that
in
a
minute,
but
we
would
we
would
absolutely
love
your
help.
B
So
with
that
all
that
talking,
if
you
go
to
glossary.cncf.io
you'll,
see
this
page.
So
this
is
our
our
little
welcome.
Tells
you
what's
going
on
how
to
contribute
some
acknowledgements
about
all
the
folks
that
have
done
then
work
to
get
get
us
to
where
we
are
and
and
yeah
a
little
bit
else
you
can
see.
We've
got
a
style
guide
which
we
can
link
to
at
the
top.
Eventually
there
we
go
style
guide,
a
little,
how
to
contribute
guide
and
then
on
the
left.
There's
definitions.
B
So,
let's
take
let's
take
cloud
computing
right
like
this.
Was
I
every
time
I
look
at
a
definition.
I
get
like
a
little
bit
of
like
flashback
to
what
it
was
like
to
try
and
define
this
in
the
first
place,
so
for
every
definition
we
go
through
and
we
talk
about
what
type
of
thing
it
is
right.
So
is
it
a
concept?
Is
it
a
technology?
Is
it
I
think
we
have
a
couple
other
things?
B
I
don't
remember
what
what
all
the
terms
are,
but
essentially
a
couple
categories
which
your
definition
may
lie
in
and
then
for
each
definition
right
to
hit
that
target
of.
I
can
explain
to
someone
that
is
not
currently.
You
know
it's
not
just
for
business
folks,
it's
anyone
that
is
not
currently
indoctrinated
in
the
language
of
cloud
native,
right
sal.
B
I
will
answer
that
and
I
absolutely
can't
wait
to
have
you
help
us
with
this,
but
you
know
for
each
for
each
one.
We
basically
drop
it
into
three
categories.
What
is
the
thing
that
we're
talking
about
what?
What
is
the
intended
problem
space
or
the
intended
problem
that
we're
trying
to
deal
with
and
then
how
does
it
help
right?
Really
simple?
What's
the
thing
what's
the
problem,
what
does
it
do
about
the
problem
right
and
with
that?
B
B
So
this
is
this
is
the
essential
path
and
then
every
you
can
link
to
every
individual
definition
and
then
you
can
link
to
individual
sections
within
the
definition.
So
you
all
get
a
little
little
clicky
link
thing.
If
you
want
to
go
to
that,
that's
the
technical
term,
by
the
way,
clicky
link
thing
and
back
to
you,
taylor,.
A
Awesome,
thank
you
so
much.
I
really
like
that.
You
have
that
ability
to
kind
of
capture,
feedback
and
and
kind
of
get
a
sense
of
you
know.
Is
there
something
we
can
improve
here
or
is
there
something
that
we
can
get
added?
One
question
that
I
have
for
you
is:
why
is
it
open
source?
Can
you
talk
a
little
bit
more
about
that.
C
Sure
I
mean
like
first
of
all,
we
all
know
that
technology
is
changing,
really
really
fast
right.
So
having
like
a
few
people
in
charge
of
updating,
it
would
be
like
a
huge
burden,
first
of
all,
like
and
so
by
inviting
community
to
help
and
become
that
becomes
a
lot
easier.
So
that's
one
reason,
but
more
importantly,
we
really
believe
that
the
end
result
will
be
a
lot
better
if
people
collaborate
right
so
jason
and
I
wrote
a
lot
of
definitions
here,
but
are
these
the
best
definitions?
C
Probably
not
right?
I
mean
we
put
a
lot
of
thought
into
it
and
we're
probably
more
attached
to
some
than
to
others
right
as
always,
but
I
mean
there
are
a
lot
of
people
out
there
that
that
may
have
a
better
definition
or
help
improve
the
current
one
right.
So
we
really
want
this
to
be
a
living
thing,
something
that
grows
and
improves
over
time
and
that's
only
feasible
if
you
open
it
up
to
the
community
and
so
open
sourcing.
It
was
really
like
the
right
approach.
C
Besides,
it's
also
a
lot
of
fun
right
people.
You
work
you
get
to
work
with
people
all
around
the
world
which
is
really
exciting
and
yeah.
Our
community
is
still
small,
but
we
hope
we
can
change
that
maybe
today
and
we
hope
to
see
it
grow
and
get
lots
of
engaged
con
contributors.
So
we
really
welcome
everyone
on
the
call
today
to
join
right,
jason.
Anything
you
would
like
to
add.
B
Yeah,
so
sorry,
I
just
want
to
say
hi
hi
time.
No,
I
don't
have
it.
I
don't
have
a
ton
to
add
right,
like
the
the
goal
of
the
business,
so
we
set
up
this
business
value
committee
and
we're
like
man,
there's
a
ton
of
resources
that
you
kind
of
need,
as
you
begin
to
address
your
market,
whether
it's
for
a
project
or
for
a
company
right-
and
you
know
what
we'd
love
to
do-
is
we'd
love
to
generate
like
as
a
group
around
the
cnc,
but
look
to
generate
some
content.
B
That's
just
reusable
right
and
that
changes
based
on
what
people
want
right.
So
I've
got
we've
got
observability
in
here
right
like
I
was
nervous
to
define
observability
right,
it's
a
property
and
like,
if
you
look
at
it,
there's
like
a
ton
of
folks
have
a
bunch
of
different
definitions
for
what
this
is
right
and
some
people
are
really
passionate.
So
what
we
need
is
we
need.
We
need
to
to
be
able
to
welcome
changes
from
folks
in
the
community.
B
Right,
like
everyone's
gonna,
be
sharp
on
different
things,
and
this
can
only
really
be
authoritative.
If
the
community
agrees
on
the
definitions
and
as
you
know,
someone
that's
been
in
tech
for
a
while.
I
was
like
well,
I
think,
the
best
way
to
make
to
get
a
community.
You
know
crowdsource
set
of
definitions
is
put
in
git
and
and
go
that
way,
yeah.
A
A
I
was
at
kubecon
just
just
at
the
at
the
end
of
this
year
here
in
la,
and
I
know
that
was
something
I
went
to
one
of
the
day:
zero
events
and
talking
about
get
ops
and
just
kind
of
those
concerns
and
get
apps
con,
and
they
were
a
lot
of
people
were
thrilled
at
the
fact
that
there
was
that
formal
definition
of
what
is
get
ops,
because
I
know
that
a
lot
of
people
have
different
ideas
and
when
we're
able
to
all
kind
of
unify
and
agree
on
what
something
means
then
we're
added
we're.
A
You
know
that
gives
it
that
much
more
meaning
and
then
people
are
able
to
take
that
and
build
with
that.
So
again,
you
know
it's
the
words
the
the
pen
is
mightier
than
the
sword.
These
words
have
a
lot
of
power
and
it's
helpful
to
kind
of
align
on
those
things.
So
again.
Thank
you.
This
is
it's!
It's
really
nice
to
have
that
ability
to
connect
with
people
in
that
way.
Awesome.
A
So
with
that
speaking
about
people
and
teams
and
kind
of
aligning
on
language,
and
in
many
cases,
why
should
someone
contribute
to
the
glossary?
Would
you
say.
C
Yeah
so,
and
just
before,
I
I
see
like
people
asking
about
bengali
and
urdu
and
so
on.
So
we're
gonna
go
about
that.
So
I'm
really
excited
because
I'm
actually
more
excited
about
like
those
those
more
smaller
languages,
because
I
think
that
would
be
really
really
cool
to
see
that
all
translated.
So
we're
gonna
come
back
to
that
in
a
minute.
But
going
back
to
your
questions,
why
someone
should
contribute
so.
C
First
of
all,
I
really
think
it's
really
fun
and
rewarding
right,
you're
really
helping
to
build
something
that
is
useful
for
a
bunch
of
people
and,
as
I
mentioned
before,
you
get
to
interact
with
people
around
the
world,
and
that
is
especially
true
for
the
people
who
are
working
on
the
localization
team,
because
we
have
like
a
slack
channel
where
all
the
teams
can
interact
as
well.
C
It
is
also
a
really
good
way
to
get
started
with
open
source
without
having
to
code
right
like
you,
don't
really
need
to
code
to
do
this
and
it's
still
open
source.
Of
course
you
do
need
to
understand
the
concept
right,
but
like
look
like
I
don't
have.
I
cannot
code,
but
still
I'm
part
of
this
project
right.
So
if
you
wanted
to
do
this,
this
is
basically
your
chance.
C
You
also
really
learn
a
lot
because,
as
I
mentioned
like
explaining
these
things
and
simple
words
is
really
really
hard,
so
you're
testing
your
own
language,
your
own
knowledge
right,
like
sometimes
you
think
you
know
something
until
you
have
to
really
break
it
down.
So
it's
a
great
great
exercise
and
I
think
there's
like
a
isn't
there
like
a
saying
about
like
if
that
the
ultimate
test
of
verifying
your
knowledge
is
when
you're
able
to
explain
it
to
a
child,
or
something
like
that.
C
So
basically,
that's
very
similar,
take
a
complex
term
and
explain
it
to
to
someone
in
a
way
that
someone
with
zero
technical
knowledge
can
understand.
If
you
can
do
that,
you
really
got
it
right
like
if
you
don't
you're,
probably
still
kind
of
missing
some
little
things.
So
it's
a
really
really
good
exercise
to
test.
If
you
actually
know
what
you
think
you
know.
B
Gonna
say
to
expand
on
that
when
we
talk
about
creating
localized
content
in
in
the
particular
native
language
or
the
particular
language
that
you,
you
are
comfortable
with
right
like
so
much
technical
content
is
like
biased
towards
english
and,
like
it's
got
to
be
like
it's
hard
in
english
right
to
operate.
If
you
don't
have
a
good
understanding
of
what
these
terms
mean
and
like
if
english
isn't
your
first
language
right
like
having
terms
in
your
language
defined
by
native
speakers,
you
know
who
are
who
are
doing
in
a
way.
B
That's
like
culturally
relevant
to
you
is
super
valuable.
So
it's
a
great
way
to
help.
You
know
one
if
you're
contributing
english
great,
do
it,
we
we
would
love
it
and
if
you
can
help
localize
and
build
definitions
for
your
language
right,
like
you're
setting
up
so
many
other
people
for
success
by
doing
it.
So
it's
a
you're
doing
something
good
for
your
community
by
adding
terms
here,
at
least
I
I
believe
you
are.
A
I
think
that's
something
that
is
is
kind
of
you
know
when
it
comes
to
localization
and
adding
in
all
these
languages.
That's
a
great
point.
Jason
is
the
fact
that
it's
it's,
it
has
to
kind
of
mean
the
same
thing
too.
I
would
imagine
right
it's
not
it's
not
like
a
quick
translation
where
you
plug
it
in
and
oh
okay,
all
of
the
words
are
now
in
this
in
this
native
language.
A
It
needs
to
be
kind
of
tuned
to
capture
the
essence,
the
meaning
of
what
is
this
thing,
whether
it
be
a
concept
or
something
else.
So
I
think
that
that's
a
mad
respect
to
the
team
for
being
able
to
kind
of
think
about
that
and
work
through
that,
and
I
think
it's
something
that
not
a
lot
of
people
realize
is
that
you
know,
as
you
go
through,
that
you
know
as
you
go
through
those
language
changes,
you
need
to
keep
that
in
mind
as
well.
So
really
really
interesting.
B
Well,
one
thing
I'd
add
before
we
go
on,
we
got
really
lucky
early
on
leonardo
marillo.
Is
that
how
I
say
his
last
name,
katherine,
so
leonardo
marillo,
like
helped
us
help
us
kind
of
just
be
like
yo
folks.
You
need
to
be
sure
that
you
are
focused
on
making
it
accessible
to
other
languages
and
like
he
just
he
set
the
stage
for
our
ability
to
you
know,
have
this
site
and
have
all
of
the
glossary
terms,
be.
A
That's
fantastic:
it's
there's
there's
nothing
like
you
know,
measuring
twice
and
being
able
to
cut
once
and
that
in
that
aspect
for
sure
I
did,
I
did
see.
One
question
come
in
from
almost
so
is
this
class
related
to
general
knowledge
in
software
development
or
mostly
related
to
cloud
cloud
native
items?
And
then
I
can
read
the
part
b
of
that
question
as
well
in
a
sec.
B
Yeah
we're
we're
focus
it's
cloud
native
glossary,
so
we're
shooting
for
cloud
native
terms,
but
there's
some
stuff
in
here.
That's
not
you
know.
Cloud
native
specific
cluster
is
defined.
I
think
we
have
yeah.
We
have
bare
metal
machine
defined.
So
a
lot
of
these
things
are
are
general,
but
you
know
in
you
know
we're
starting
with
the
lexicon
of
cloud
native
terms.
A
Awesome
awesome.
The
next
question
in
in
in
part
b,
that
question
was
how
friendly
is
it
towards
people
who
are
familiar
with
software
development,
but
in
different
fields
or
stacks
example?
Being
this
person
is
a
back
back
end
developer,
trying
to
learn,
devops,
kubernetes,
etc.
A
B
C
Yeah,
the
goal
is
that
anyone
can
understand
it
right
with
no
technical
background
with
different
technical
background.
Anyone
right
because
it's
like
I
mean
it's
yeah,
it's
it's
it's
getting
more
and
more
more
and
more
people
and
companies
are
adopting
it
and
more
people
are
really
kind
of
getting
in
touch
with
it.
So
that's
the
goal
so
yeah,
as
jason
said,
if
you
stumble
about
across
something
that
is
not,
does
not
comply
with
that,
which
I'm
sure
there
are
a
few
please
please
do
raise
an
issue
or
improve
it.
A
And,
and
with
that
kind
of
talking
about
contributions,
I
did
see
a
comment
that
came
and
said
would
be
great
if
we
shot
a
contribute
to
in
in
native
language
on
the
stream.
One
other
thing
is
kind
of
looking
at
that
in
a
more
general
sense.
B
Yeah,
so
I
can,
I
can
start
so
one
go
here,
there's
like
literally
like
a
how
to
contribute
button
right
at
the
top
which
we'll
talk
through
talk
through
the
process.
The
other
second
best
place-
and
I
don't
know
if
you'd
be
happy
to
share
the
link,
but
if
you
could
re-share
the
glossary
link,
so
it's
cncf
glossary
on
github,
so
I
can't
make
that
make
that
any
bigger.
But
this
is
mention
inclusive
naming
initiatives.
B
Oh
sorry,
I'm
gonna
finish
what
I'm
saying
and
then
I'll
I'll
look
at
the
questions.
So
here
is
the
get
repo
you
can
see.
Well
one
the
readme
talks
about
how
you
get
started
right
or
how
you
get
started
with
that
the
actual
project
and
then
the
the
issues
here.
We've
got
like
an
issue
template
so
it
so
as
you
go
in
here.
You
want
to
raise
an
issue
and
this
this
works
from
here.
B
So
again,
if
I,
if
I'm
here
and
I
want
to
report
an
issue
it,
it
brings
me
to
create
a
new
issue
right
away
and
it
actually
gives
it
to
you
on
the
term.
But
if
you
go
into
an
issue
and
you
create
a
new
issue-
we've
got
a
bunch
of
issue
templates
that
specifically
talk
about
what
language
you're
doing
and
for
all
the
folks
that
started
talking
about
you
know
how
do
I
set
it
up
for
my
particular
language?
B
If
it's
not
already
in
here,
we've
got
this
one
form
to
initiate
a
new
localization
team
and
to
be
clear
audience
members.
If
you
want
a
stream
specifically
on
how
to
set
up
a
localization
team
and
how
to
get
started
with
your
language,
we
can
set
that
up.
We
don't
have,
we
don't
have
the
per
so
we
have.
B
We
had
a
new
person
come
on
as
a
maintainer
and
they're
amazing
and
they're
helping
us
do
a
great
job
with
localization,
I'm
scared
to
say
their
name,
because
I
say
it
incorrectly
too
often,
but
it's
yoko
is
that
right,
katherine.
B
So
so
he's
been
he's
been
incredible
and
we
can
do.
We
can
do
one
specifically
on
how
how
to
get
set
up,
but
essentially
what
we
need
is
three
folks
per
language,
three,
three
folks
that
that
know
and
trust
each
other
and
are
able
to
look
over
their
definitions
together
right
and
set
approval
and
then
go
through
the
process
of
initiating
a
localization
team
for
your
language.
B
If
you
have
questions
in
the
slack,
we
have
a
localization
channel
where
you
can
connect
you
with
like-minded
folks
who
speak
the
same
language
as
you
and
and
start
rolling
to
get
you
a
localization
team
in
your
language.
But
sorry
I
I
I
strayed
a
bit
just
because
I'd
seen
so
much
about
localization
in
general,
you're,
gonna,
you're,
gonna,
open
an
issue
or
you're
gonna.
Look
at
the
particular
content
here
under
the
content
tab.
B
We
have
the
various
languages
by
language
code,
so
assuming
you're
in
english,
because
that's
the
only
one
that
I
contribute
to
you
know.
So
when
I
go
in
here
I
go
into
english.
I
pick
the
I
pick
the
particular
thing
and
then,
if
I
wanted
to
make
a
change,
I
could
just
you
know,
create
my
own
branch
and
and
actually
I
could
create
my
own
branch
and
then
I
could
actually,
you
know,
make
the
changes
that
I
want
submit
a
pr.
B
You
know
for
every
pr
you'll
see
right
so
yeah,
so
for
every
pr
right,
assuming
that
this
one's
a
good
one
you'll
get
your
little
netify
netlify
link,
so
you
can
see
the
you
can
see
the
actual
version
of
it
as
you
go.
So
you
can
see
your
changes
as
you
go.
So
it's
a
fairly
like
low
stress
thing:
no
one's
going
to
yell
at
you.
If
you
do
something
wrong
right,
where
yeah
we're
excited
to
we're
excited
to
take
any
contributions,
you've
got
and
if
you
need
help
go
into
the
slack.
B
Thank
you
sal
for
posting
that
there's
a
glossary,
localizations
slack
channel
on
on
the
cncf
slack.
There's
a
glossary
channel
right.
If
you
need
help,
let
us
know
we're
eager
to
work
with
you
and
if
you've
never
done
anything
in
git,
we
even
have
some
guides
to
how
to
get
started
using
git.
So
you
can
do
a
pr.
So
you
can
raise
an
issue
all
that
stuff.
A
Taylor,
absolutely
and-
and
one
thing
I
saw
too-
I
kind
of
like
that
that
it
has
that
following
structure
where
it's
glossary
and
I
can
see,
gloss,
glossary,
localizations
and
then
glossary
localizations
and
then
the
actual
languages
that
are
being
worked
on.
So
that's
that's.
That
makes
it
easier
and
easier
to
find
as
well
cool
awesome
really
like
how
you
have
things
set
up
too,
with
all
of
the
github
issues
and
just
trying
to
it.
You
know
it
clear.
A
It's
clear
that
you're
trying
to
make
that
accessible
and
and
kind
of
straightforward
in
terms
of
figuring
out
how
to
route
different
requests
and
things
and
request
not
only
request
things
but
actually
file
tickets
and
get
some
things
added
as
well,
but
awesome
cool.
B
A
And
to
everyone
who's
watching
today,
if
you
have
any
questions,
please
feel
free
to
throw
them
in
the
chat
where
you're
viewing
this
and
we'll
be
happy
to
answer
things
on
that
front
as
well.
A
I
did
have
one
other
question
for
you:
you're
you're,
also
looking
into
translating
the
glossary.
How
does
that
work
and
how
can
people
kind
of
join
in
the
effort
there?
I
know
we
talked
a
little
bit
about
that,
but
curious
as
to
if
you
have
a
little
bit
more
information
on
that
front,.
C
Yeah
I
mean
first
of
all
like
we're
super
excited
to
have
like
people
come,
and
I'm
also
super
excited
to
see
people
now
in
the
chat
as
well,
because
it's
like
that
is
really
really
dear
to
us,
and
we
really
want
to
get
this
effort
going,
and
so,
as
jason
already
mentioned,
right
like
there
is
a
lot
of
content
on
cloud
native
out
there
in
english.
But
most
of
the
people
in
this
world
are
not
native
speakers,
english
native
speakers
right.
C
So
it's,
like
I
mean
imagine,
learning
collaborative
concept
in
a
foreign
language,
especially
if
it's
not
like
you're,
not
super
familiar
with
it.
It's
twice
or
three
times
as
hard
right,
so
really
making
making
the
glossary
accessible
to
anyone
anywhere
is
really
something
that
we
really
want
to
help
right.
So
we
do
have
the
glossary
set
up
to
have
multiple
languages
and
we
have
teams.
You
may
have
seen
already
a
little
bit
in
this
in
the
in
the
github.
C
We
have
currently
teams
working
on
translating
in
it
into
korean
hindi,
portuguese,
italian
and
spanish
and
actually
german,
just
they
just
kind
of
had
like
a
little
group
today.
So
that
is
really
excited.
We
have
two
volunteers
from
the
police
if
anyone
interested
in
the
police
here,
please
join
and
five
of
these
teams
have
committed
to
try
to
get
the
10
first
terms
translated
by
kubecon
n
a
in
october
and
have
that
would
be
like
the
first
mini
versions
of
the
glossary
so
yeah.
Hopefully
we
can.
C
We
can
get
that
going
so
yeah
if
anyone
here
is
interested-
and
we
saw
like
some
interest
here-
of
joining
a
current
glossary,
localization
team
or
creating
a
new
one,
hop
on
the
channel,
the
glossary
localization
channel,
the
channel-
that's
shared
before
and
yeah.
Just
just
let
us
know.
C
So
so
please
join
us
and
yeah
we're
gonna
share
all
the
the
channels
again,
and
I
think,
like
we
also
have
we
published
a
blog
post
yesterday,
where
you
can
find
all
the
information
as
well
with
which
channels
to
join
and
so
on
anything.
You
would
like
to
add
jason
anything.
I
forgot
about.
B
No,
I
I
think
he
hit
the
nail
on
the
head
right.
We
need,
you
know.
We
need
three
folks
per
language
right,
like
our
goal
is
not
to
have
catherine
myself
be
be
folks
that
gate
contributions
from
languages
from
other
languages
right.
We
want
everyone,
every
language
group
to
to
self-govern
self-defined
terms,
you
know
set
set
their
own
names
for
the
terms
like
we
don't
want
you
to
just.
B
I
don't
want
you
to
go,
translate
abstraction
into
italian
right
like
I
want,
whatever
the
appropriate
italian,
you
know,
view
of
abstraction
is
right,
whatever
their
whatever
their
term
is
right,
I'm
sure
they
have
a
sure
you
have
an
italian
word.
I
was
gonna,
make
a
joke
there,
but
I
decided
no,
but
you
know
whatever
it
is.
We
want
them
to
use
their
own,
their
own
wording
right,
not
just
abstraction.
B
The
italian
version
right,
but
instead
you
know
you're
set
up
for
it
and,
in
general,
just
stay
out
of
your
way
as
you
as
you
get
to
doing
it,
and
yet
slack
is
the
best
place
to
get
in
the
loop.
A
Absolutely
agree,
I
did
see.
One
thing
come
in
that
said
from
sal,
consider
coordinating
this
with
a
cncf
kubecon
hackathon
and
could
potentially
get
a
bunch
of
valuable
localization
commits
from
a
group
of
developers.
I
I
agree
and
that's
that's
that's
the
fun
thing
about
open
source
right
is
being
able
to
kind
of
say,
hey.
I
think
we
could
do.
We
could
make
this
better.
We
could
do
this
thing
and
and
to
just
kind
of
throw
that
out
there
and
and
see
it
come
together
or
work
towards
making
it
happen.
A
So
I
agree
that
I
I'd
really
enjoy.
Seeing
that
I
I
wasn't
aware
of
the
glossary
myself
until
until
you
know,
until
january
this
year,
so
really
excited
to
see
that
this
exists.
I
I
did
have
a
couple
questions
as
well
kind
of
around
the
the
project
and
just
like
the
consumption
of
some
of
these
terms.
Do
you
know
if
there's
a
way
to
like
download
this
to
pdf
or
I
could
see
it
looks
like
there's,
there's
fuzzy
search
on
the
site?
Are
there?
A
Are
there
any
thoughts
around
other
things
in
terms
of
not
just
localization
specifically
but
any
other
ways
that
might
help
with
accessibility
or
sharing
this
around
or
kind
of
any
thoughts
on
some
of
the
technical
components
or
pieces
behind
the
site
that
you
all
have
thought
of,
or
have
any
come
up
yeah?
So
our.
B
It
was,
and
our
initial
version
was
a
pdf
and
we
dropped
that
as
quickly
as
we
possibly
could,
because
it
was
it
just
it
goes
stale
fast,
it
doesn't
auto-update
and
stuff.
If
listen.
If
folks,
you
know
here,
there's
actually
a
link
to
view
and
download
the
pdf
version.
If
you
want
to
get
it,
I'm
not
sure
that
it
auto
generates.
But
if,
if
this
is
something
everything
in
this
project,
if
you
have
an
interest
in
seeing
it
be
a
certain
way,
please
please
help
us
and
get
involved,
and
we
we
want
to.
B
We
want
to
get
it
as
long
as
we
can
build
something
you
know
like
with
pdfs.
If
we
can
build
a
thing
that
auto
generates
a
pdf
so
that
it's
always
current
when
someone
clicks
a
link,
great
right,
we'd
love
to
we'd
love,
to
see
something
like
that
and
again
I
haven't
even
dug
into
the
pdf
function
enough
to
know
whether
it's
a
static
one
or
it's
a
new
one,
every
time,
but
but
anyway,
so.
B
So
that's
an
area
that
could
use
some
improvement
right.
So
if
you
have,
if
you
have
an
interest
in
it,
then
we'd
love
to
get
your
help
so
that
we
can.
We
can
make
it
look
the
way
you
want
it
to
look.
I
saw
someone
asked
about.
You
know
the
inclusive
naming
initiative
right
and
I
actually
just
googled
it
while
we
were
sitting
around
like
and
it's
another
one
so
because
the
definitions
are
open
source
right.
B
If
you
see,
if
you
see
some
language,
that
is
not
correct
or
not
appropriate
right
like
let
us
know
well,
it's
I
can.
I
can
tell
you
personally
in
english
catherine,
and
I
will
prioritize
and
it's
like
hey:
can
we
please
remove
this
term
and
replace
it
with
this
one,
because
this
one
sucks
or
is
bad
for
some
reason,
damn
right,
like
we'd
love
to
love,
to
get
those
things
fixed,
I
saw
my
tool
matule.
Essentially
you
need.
B
You
need
three
folks
who
speak
the
same
language
who
are
interested
in
developing
some
terms
and
honestly,
if
you
have
that
go
over
here,
raise
a
new
issue
and
build
a
new
new
localization
team,
and
when
you
do
it,
it
gives
you
this
handy,
dandy,
checklist
of
all
the
stuff.
You
need
to
do
right.
So
there's
there's
a
bunch
in
there.
C
C
You
don't
have
three
yet
join
the
slack
channel.
Well,
join
it
anyways
right,
but
there
may
be
someone
there
who
also
wants
to
join
a
team
and
doesn't
have
doesn't
have
their
three
volunteers
there.
Yet
so
I
think,
like
during
the
slack
channel,
if
you're
interested
for
sure
and
yeah
like
once,
you
have
the
three,
then
you
do
the
issue,
but
we'll
we'll
try.
I
don't
know
we.
C
We
cannot
promise
to
connect
you
with
all
three,
but
we're
gonna
do
whatever
we
can
like
if
we
are
in
the
next
live
stream,
like
with
the
nepalese
one.
I
know
they
have
two
so
so
we'll
try
to
let
people
know
so
so
other
people
can
just
just
join
you.
A
Excellent,
I
I
I
do
like
again
how
it's
you've
made
this
really
accessible
to
be
able
to
add
things
and
and
kind
of
ask
for
things
and
work
through
adding
to
this
glossary.
I
think
one
selfishly
I'd
love
to
see
at
some
point
in
time
and
and
love
to
pitch
that
at
some
point
is
pronunciations
for
things
and
then
in
specific
languages,
so
we
could
and
and
maybe
for
cube,
ctl
cuddle
control.
We
can
have
a
randomizer
to
just
you
know
say
one
of
those
at
some
point
in
time
too.
B
Yeah
we
avoid
we
avoid
politics,
religion
and
and
pronunciation
of
cube,
ctl.
A
It's
I
I
I
I
bought
cubecuddle.com,
so
at
some
point
in
time.
We
need
to
make
that
something
fun.
I.
A
About
that,
but
awesome,
awesome,
wonderful,
well,
we'd
love
to
open
it
up
to
anyone
that
has
any
questions.
Otherwise
are
there
any
other
things
that
are
good
to
kind
of
keep
in
consideration
with
the
glossary,
or
are
there
any
things
that
you
all
have
your
minds
on
accomplishing
within
this
first
quarter
or
kind
of
like
any
immediate
concerns
that
you
might
want
to
share
or
talk
about
before
we
start
to
close
things
out.
C
I
think
the
focus
for
us
right
now
is
we
feel
like
we
have
like
the
basis
there,
the
foundation
right
now.
We
really
want
to
find
more
contributors
right.
So
that's
that's
now
yeah.
We
want
it
to
really
kind
of
grow
and
improve.
C
So
that's
our
focus
now
and
then
like
now,
building
as
well
like
the
localization
teams,
right
like
we,
we
have
several
teams
getting
started,
but
of
course
nothing
is
there
yet
because
it's
just
started-
and
so
I
think
the
focus
of
the
next
half
year
is
really
getting
those
mini
versions
started,
and
I
can't
wait
to
see
like
a
little
drop
down
in
the
languages
and
and
seeing
all
that
that,
like
yeah,
it's
it's
really
looking
forward
to
that
for
sure.
B
Yeah,
no,
no
doubt
our
priority
from
now
until
kubecon
is
get
as
many
languages
as
possible
to
have
10
terms
so
that
up
in
here
or
somewhere,
you
can
just
change
the
language
right
and
go
go
to
what's
what's
appropriate.
You
know
that
being
said,
if
you're
out
there-
and
you
have
some
definitions,
I
would
I
would
love
to
get
some
new
definitions
or
to
get
some
of
the
existing
ones
updated
right.
But
our
katherine's
main
focus
is
helping
the
localization
teams
as
much
as
possible.
B
B
So
what
you
do
is
come
into
the
slack
and
just
talk
about
like
talk
just
make
sure
that
everyone,
everyone
joins
the
glossary
channel
and
the
glossary
localization
channel
in
slack
and
then
yeah
go
into
the
glossary
and
raise
an
issue
to
raise
a
new
issue
to
initiate
a
new
localization
team
and
get
started
like
we're
to
be
clear,
we're
early
days
and
we're
building
out
the
localization
process.
So
we'll
need
help
to
get
you
know
to
get
to
get
the
you
know.
C
Yeah,
and
actually
there
is,
if,
if
you
go
on
the
slack
channel,
there
is
like
the
meeting
notes
sayokon,
who
is
our
maintainer,
who
manages
the
whole
process
like
he
is
he's
the
person
who's
done
like
a
lot
of
the
docs
localization
for
kubernetes,
and
so
he
has
created
all
the
steps
and
the
processes
that
we
need
for
the
glossary,
and
so
you
can
read
all
in
there.
We're
also
first,
like
he's
trying
to
do
everything
for
korean
right
now,
testing
it.
So
a
lot
of
things
may
not
go
through
right
away.
C
So
we're
testing
that
and
once
we
confirm
that
it's
all
working,
it's
going
to
be
the
process,
as
jason
said
like
it's
early
on,
so
we're
still
like,
we
still
have
to
do
our
first
one.
So
korean
is
our
kind
of
guinea
pig,
guinea,
pig
right
now
and
so
yeah.
There
are
a
lot
of
things
that
can
be
done,
but
yeah
you
find
all
that
information
in
there.
So.
C
B
And
don't
let
any
of
the
process
things
stop
you
right
like
if
you
grab
a
google
doc
and
you
and
the
people
that
you're
working
with
can
begin
defining
terms
in
a
way
that
makes
sense,
ideally
have
that
format
in
general.
For
for
most
of
these,
these
these
definitions
that
includes
what
it
is
problem
and
address,
is
how
it
helps
that
would
go
a
long
way.
Make
sure
that
you
check
out
the
the
style
guide,
and
you
know
an
appropriate
style
guide
for
your
language
would
be
great.
B
C
Yeah
and
just
talking
to
the
staff,
so
we
haven't
updated
that
for
a
while,
the
how
to
contribute
and
style
guide.
So
that's
my
priority
in
the
next
two
weeks
or
so
to
update
that
so
it's
gonna
be
more
they're
gonna,
be
more
detail
so
check
that
again
and
yeah.
Just
as
a
recommendation,
I
wouldn't
start
right
away
with
github
right
because
it's
like
ideally
you're
gonna,
could
collaborate
and
like
tweak
each
other's
things.
C
So
the
way
we
started
we
worked
on
the
terms
before
we
added
that
now
github
was
a
google
doc.
It's
just
like
a
lot
easier
because
you're
going
to
be
changing
and
updating,
and
that's
like
very
cumbersome
on
on
google
and
in
github,
and
once
you
have
something
you're
happy
with,
then
you
can
put
it
on
there,
because
it's
a
very
collaborative
process
and
back
and
forth
in
general.
C
So
I
think
github
is
kind
of
good
when
you
already
have
a
really
good
sense
of
what
you
want
to
what
you
want
to
add,
and
then
you
can
tweak
it
from
there,
but
yeah.
A
Excellent
awesome,
I
did
see
jonathan
mentioned
youtube.
Video
cube
control,
the
definitive
pronunciation
guide
absolutely
agree.
I'm
sure
that
we'll
start
to
see
things
drop
on
on
that
front
and
wonderful.
A
Thank
you
both
so
much
for
for
really
just
educating
us
today
on
the
glossary,
how
to
get
involved
some
of
the
things
that
are
coming
up
with
it
and
and
really
just
exciting,
to
see
that
it's
going
to
continue
to
kind
of
change,
shapes
and
add
definitions
and
really
help
people
out
with
understanding
and
and
being
able
to
unite
and
align
on
on.
A
You
know
what
these,
what
these
things
mean
cool
with
that
I
didn't
see
too
many
more
questions
come
in
if,
if
they
do
I'll
I'll
be
sure
to
raise
them
up
here,
as
we
start
to
close
out,
but
really
would
like
to
turn
it
over
to
to
both
of
you.
Do
you
have
any
parting
words
of
wisdom
or
anything
that
you
would
like
to
say
in
terms
of
kind
of
closing
things
out
here.
C
Well,
I
mean
for
like
I'll
just
get
started,
so
for
me
it's
just
like.
We
really
really
want
people
to
get
involved.
So
join
us.
It's
it's
a
lot
of
fun
I
really
enjoy
having
you
know
like,
inter,
like
working
with
all
of
you,
like
all
the
community
like
people
from
all
around
the
world.
I
think
that's
super
exciting
right
like
like.
I
don't
know
so
again,
it's
a
lot
of
fun.
C
It's
really
rewarding
when
you
see
it
up
in
the
up
and
running
if
you're
localizing
it
you're,
really
doing
a
huge
favor
to
the
community
and
your
country
so
yeah,
I
I
hope
I
hope
you
see
that
to
see
you
all
on.
First
on
the
slack
and
then
seeing
all
these
github
prs
coming
in.
B
I'd
add
to
that
right
if
you
like
the
glossary,
if
you've
been
to
the
to
the
landscape.
Lately
the
cloud
native
landscape
and
you've
seen
this.
It's
landscape
guide
button
now
so
there's
a
little
guide
if
you
like,
if
you
like
things
like
this,
where
you
start
to
to
explain
some
of
these
terms,
you
start
to
make
an
impact
on
cloud
native
stuff,
but
with
without
an
exclusive
focus
on
the
on
the
tech
or
on
coding.
Right.
A
Awesome,
thank
you,
but
so
much
and
thank
you,
everyone
for
joining
the
latest
episode
of
cloud
native
live
today.
It
was
really
great
to
hear
from
jason
and
catherine
about
the
cloud
native
glossary
and
you
know
it's
it's.
I
started
undefined,
but
now
I
feel
a
lot
more
defined
in
my
understanding
of
what
the
glossary
is
looking
to
do
so.
Thank
you
both
very
much.
We
really
love
the
interaction
and
questions
from
everyone
in
the
audience.
So
thank
you
so
much
on
that
front.
A
Next
week
we
will
be
joined
by
diego
braga,
who
will
present
on
from
zero
to
production
in
less
than
one
hour
with
cradio
platform.
Ops,
and
with
that,
thank
you
for
joining
us
today
and
we
will
see
you
soon
thanks.
Everyone
see
you
around.