►
From YouTube: CNCF Glossary Working Group Meeting - March 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
So
welcome
to
the
glossary
meeting.
I
think
it's
going
to
be
the
rather
short,
at
least
for
my
end.
Hey
Noah
I
was
on
vacation
for
two
weeks
and
the
other
week
on
a
conference.
So
basically
all
the
time
gone
since
the
last
one.
So,
but
we
do
have
some
news.
A
Okay,
so
we
do
have
some
news,
so
ihor
from
the
cncf
will
be
helping
the
glossary
a
little
bit
in
the
future,
so
we're
very
excited
to
get
his
support.
I
used
to
work
with
him
back
when
we
wrote
some
cncs,
no
new
stack
articles
and
he
was
reviewing
it
and
it's
really
great
to
work
with
him.
A
So
I'm
very
excited
we'll
be
meeting
with
him
next
week,
just
to
give
them
like
a
quick
update
for
where
we're
at
and
like
how
what
would
be
helpful
on
our
end
and
yeah
so
and
the
other
thing
that
I'm
really
excited
is
the
tags
are
finally
implemented.
A
The
tags
I
mean
this
is
going
on
forever,
and
so
now,
when
you
see
here,
you
can
either
go
to
a
specific
term
or
you
can
Browse
by
tags,
and
then
it
can
have
like
just
one
tag
or
combine
them,
and
then
you'll
see
everything
that
has
those
tags
here
and
then
go
and
see
the
actual
term.
A
And
the
idea
is
basically
that
specifically
like,
if
you're
looking
for
something
specific,
of
course,
you're
going
to
use
this,
but
especially
for
people
who
are
new
and
like
if
you
want
to
get
started.
It's
like
okay
here.
These
are
all
the
fundamentals
like
if
you're
starting,
you
should
probably
kind
of
get
a
sense
of
what
this
is,
because
if
you
don't
know
what
a
cluster
is,
a
lot
of
the
definitions
will
not
make
sense
and
so
on,
and
then
maybe
you
want
to
have
fundamentals
in
architecture
right
and
and
so
on.
A
So
I
think
it's
very
helpful.
I'm
very
excited
that
that
is
now
live.
A
We
also
added
a
who
can
contribute
section
in
our
glossary
just
to
make
expectations
a
little
clearer,
I
think,
like
a
lot
of
people,
think
they
can
contribute,
but
are
not
quite
there
yet
so,
just
to
make
clear
like
what
you
need.
What
where
you
need
to
be
at
to
actually
contribute
to
the
glossary.
A
Hopefully
that
will
help,
because
I
think
it
might
have
led
to
a
little
bit
of
frustration,
because
people
think
they
are
able
to
contribute
something,
don't
have
the
background
and
then
there's
a
lot
of
back
and
forth,
and
it's
frustration
for
everyone
right.
It's
frustration
for
the
contributor
as
well,
because
they
they
really
wanted
to
participate.
We
have
a
lot
of
people
eager
to
participate
in
the
cognitive
ecosystem
and
contribute
contributing
to
open
source,
but
like
managing
that
expectations
and
making
clear
what's
needed
is
really
important.
A
So
hopefully
that
helps
and
oh
yeah,
so
that's
actually
a
thing
that
would
be
more
in
the
maintainer
discussion.
So
my,
let's
think
about
remind
remind
me
of
that
Circle,
because
I
think
it
should
be
part
of
the
template
just
check
people
that
they
have
read
it,
but
we
can
discuss
this
further
down
again.
That's
all
I
had
three
weeks
basically
gone
from
the
last
four
weeks.
So
I
don't
know,
there's
not
much
so
back
to
over
to
you
so.
C
Yeah
before
over
to
the
localization
update
I
just
mentioned
that
filters,
I'd
like
to
say
things
to
Chris
Abram
and
James
Hunt,
who
implemented
the
take
pictures,
functionality.
B
B
C
Okay,
let's
go
to
the
localization
update,
as
you
record,
the
left
left
to
meeting
I
requested
to
all
localization
branch
maintainers
to
update
their
branches
by
revisiting
onto
the
latest
main
branch
and,
as
you
can
see,
manual
localization
team
applied
I
mean
complicated.
This
text
so
I'd
like
to
say
thanks
to
all
localization
maintainers,
we
are
still
waiting
for
KRS
from
root
and
Arabic
language,
so
in
case
of
Road
language
we
already
have
PR.
C
So
it
is
working
progress
and
in
case
of
Arabic
language,
there
is
no
response
yet.
So
please
take
a
look
the
issue,
so
those
two
branches
are
remaining
tasks
for
me.
C
Okay,
next
item
is
about
to
sharing
some
additional
script
and
things
tended
to
be
localized
in
pom
pi.
B
B
C
Yeah
by
the
take
a
territory
implementation,
we
added
more
things
to
the
request
to
be
localized.
As
you
can
see,
those
new
things
should
be
localized
by
a
localization
team,
but
people
work
on
this
localization.
You
would
better
to
replace
your
development
Branch,
okay,
to
reflect
those
new
toml,
pile,
so
I
think
that's
all
from
the
localization
update.
Is
there
any
question
regarding
those
two
items.
C
Yeah
yeah
I
think
most
of
localization
maintainers
understand
what
I
mean:
okay,
I
I
think
tester
from
my
side
for
the
update,
and
maybe
you
can
go
to
individual
language
team,
Spanish,
lady,
hello,.
D
Yes,
hi
hi,
everyone
well
I,
think
I
put
the
update
that
we
are
trying
to
think
our
branch
that
is
depth
as
the
Spanish
to
the
main.
At
the
end
of
the
month.
We
are
trying
to
to
think
I.
Think
is
the
second
time
that
we
we
did
it
so
we're
trying
to
keep
this.
This
control
about
our
things,
yeah
I
think
also
I.
C
Okay,
thank
you
Carol.
Let
me
let
me
check
your
PR
regarding
the
automation
for
the
scale
issues
same
PRS.
Actually,
we
share
the
in
the
previous
meeting,
so
most
of
them
understand
what
the
pr
implement.
D
E
Okay,
yeah.
B
E
Our
workflow
a
little
bit
we
had,
as
you
can
see,
we
had
a
lot
a
little
bit
problems
to
translate
a
lot
of
terms,
and
we
are
just
three
people.
C
E
We
had
we
made
a
meeting
where
we
talked
about
how
we
can
translate
more
terms
and
find
our
flow
a
little
bit
again
and
yeah
I.
Think
till
the
next
meeting.
We
can
have
a
little
bit
more
use
more
terms,
translated,
It's
My,
Hope
and
I'm
optimistic
to
do
in
this.
E
Since
last
time
we
have
just
one
new
term
merged
and
two
iron
review,
and
we
have
the
11
published
terms
last
month
and
we've
nearly
finished,
our
blog
post
so
I
think
all
the
sex.
All
sections
are
filled,
I
also
already
reviewed
it
I,
don't
know
if
the
other
two
is
still
in
review
to
review
everything,
but
we
are
very
close
to
say
it's
finished,
I.
F
Will
I
will
also
have
a
have
a
review
again
and
then
I
I,
guess
Catherine.
You
will
probably
go
over
it
again
to
have
some
some
wordings
improved
or
something
some
editing
and
then
then
we're
good.
We
are
good
to
go.
I
guess.
E
We
and
also
we
stay
trying
to
find
new
members
for
our
team,
so
it's
also
something
we
talked
about
in
this
meeting
and
maybe
we
we
have
some
some
meet
up
in
our
city
and
Cloud
native
Meetup,
and
we
wanted
to
promote
this
localization.
There.
A
Yeah
meetups
are
I,
think
great
place
to
do
that,
and
maybe
the
blog
post
is
like
another
resource
that
you
can
share
right
because
it's
like
you
say
it
and
then,
like
people,
can
read
it
later
on
it's
nice
to
have
several
options
to
kind
of
oh
yeah.
I
know
that's
always
the
problem
finding
contributors
but
yeah.
We
have
to
keep
on
it
right.
That's
right!
A
C
So
please
feel
free
to
add
any
ideas
if
you
have
any
life
promotional
ideas,
so
it
is
just
for
sharing
this
discussion
like
yeah,
you
can
find
one
idea
from
Victor.
B
A
Yeah
and
maybe
David
when
you
go
to
the
Meetup
you
know
and
like
if,
if
that
was
successful
or
what
was
successful,
that's
something
that
you
could
add
here
right.
Hopefully
you
find
something
that
works
and
resonates
and
then,
as
we
try
things
out,
it
would
be
a
good
place
to
gather
best
practices
right
that
we
have
learned
because
yeah
it's.
A
There
are
a
lot
of
contributors
who
are
not
the
perfect
contributors,
because
they're
not
there
yet
and
then
like,
but
having
the
people
who
are
who
have
the
knowledge
they're
really
just
like
it's,
it's
a
really
a
difficult
situation.
It's
like
I,
don't
know.
Well,
we
had
a
few
yeah.
Well,
we
had
a
few
ideas
that
I
think
that
we
can
add
here
too
I.
Think
like
we
had
some
I'm
gonna
look
into
the
agenda
and
I
think
that
there
was
like
a
folder
that
I
started.
I'm
gonna.
A
Add
those
things
in
here
too.
So
there's
that's
like
our
social
source
of
Truth
to
say
right
and
we
should
keep
building
on
that
and
maybe
make
it
like
a
like
a
not
a
regular
point,
where
we
kind
of
remind
people
that
that
is
there
and
if
they
have
any
new
ideas,
because
otherwise
it's
gonna
people
are
gonna,
forget
and
then
six
months
later,
we're
like.
Oh
we're
all
missing
contributors
right,
yeah.
C
Anything
else
I'm,
sorry
yeah,
even
though,
if
you
share
any
idea
in
select
I.
B
A
And,
oh,
she
just
wrote
can
and
by
the
way
you
can
just
unmute
yourself
and
and
just
chime
in
feel
free
to
do
that.
We're
not
much
of
a
big
group.
So
if
you
can
write
up
block
blog
about
the
pro
process,
progress
do
you
mean.
B
Those
are
like
what
what's
like
currently
happening
like
from
where
we
got
started
and
what
is
the
current
progress
right
now
in
the
glossary,
and
we
can
write
a
blog
about
it
and
publish
it
on
social
media
and
like
in
the
cubicle
newsletter.
A
Yeah
yeah,
if
there
is
a
volunteer
to
write
that
we
can
just
do
that,
yeah
well,
yeah
I
mean
like
if
we
like,
with
the
blog
post,
it
has
to
be
like
I,
don't
know
like
we,
we
could
it's
a
it's
a
it's
an
idea.
Would
you
be
willing
to
get
that
started?
We
would
have
to
see
if
we
have
enough
like
things
that
are
interesting
to
say,
but
probably
we
do.
We
just
have
to
think
about
it.
B
B
No
I
just
started
like
I
just
created.
My
first
issue
like
can
we
add
a
new
team
regarding
admission
controller,
so
I
have
to
start
with
the
localization
team.
Oh
okay,.
A
With
the
Hindi,
okay,
good,
okay,
great
so
welcome
and
yeah
feel
free
to
get
started,
and
then
we
can
like
all
like.
Once
we
have
like
a
draft.
We
can
build
on
that
and
then
I'm
sure
there
are
like
cool
things
that
we
can
say
I
just
we
just
have
to
think
about
it
right
now
from
the
get-go
I.
But
it's
it's
a
good
idea.
We
should.
We
should
try
to
get
the
word
out
yeah
anything
else
for
the
open
discussion.
A
D
I
have
one
question
one
doubt
when
you
are
talking
about
new
contributors,
because
what
is
the
relation
about
the
glossary
with
kubernetes
I?
Don't
know
if
we
have
hyperlinks
to
the
concepts
because,
for
example,
I
I
received
a
lot
of
questions,
I
think
common
questions
about
how
to
start
be
a
contributor
in
kubernetes,
and
my
answer
is
that
if
you
want
to-
and
you
are
a
beginner-
you
can
start
with
the
glossary,
because
it's
more
easy,
that's
the
going
to
the
kubernetes
and
it's
like
I.
D
It's
something,
some
connections
between
the
the
people
that
is
wanted
to
start
to
contribute
to
go
to
the
grocery
first,
because
they
they
have
the
attention
on
kubernetes
I,
don't
know
how
it's
it
will
have
some
yeah.
That's
my
question.
We
have
some
relations
like
hyperlinks.
We
can
we
use
it
inside.
So
we
are
separate
projects.
A
Well,
we
are,
we
are
kind
of
separate,
but
not
yeah.
I
mean
we're
all
part
of
the
same
ecosystem.
We're
separate
in
that
way
that
our
teams
don't
necessarily
collaborate,
but
we
have
we're
also
joined
at
the
same
time
as
a
lot
of
the
the
teams.
Localization
teams
are
also
the
localization
teams
for
the
kubernetes
one,
but
there
is
no
coordination
or
anything
I
mean
I.
Think
like
interlinking
is
good.
A
The
only
thing
the
only
issue
is
that
the
kubernetes
stocks
is
very
Advanced
right
so
and
our
goal
is
to
make
things
very
easy,
so
I
don't
know
like
whenever
it
makes
sense.
We
should
link
to
it,
but
I
think,
like
probably
a
lot
of
the
things
that
are
in
the
kubernetes
darks
and
glossary
are
too
advanced
for
what
we're
looking
for.
So
there
are
probably
not
too
many
opportunities
to
do
that,
or
maybe
it's
too
detailed
for
where
people
are
at
so
I
mean
we
should
definitely
do
it.
A
It's
just
like
I
I.
Think
that's
more
the
issue,
it's
that
the
glossary
is
more
really
like
an
not
for
contributors,
but
for
people
who
want
to
learn
it.
It's
an
entry-level
resource
right,
that
is,
for
people
who
have
no
knowledge
yet
or
are
just
new
to
kubernet,
to
kubernetes,
not
to
the
cloud
native
to
Cloud
native
in
general,
and
then
that
will
help
them
to
read
more
technical
articles
right,
so
I
feel
that's
kind
of
the.
D
So
but
I
think
yeah
yeah
in
some
level,
let
us
just
say
we
always
has
beginners
even
in
kubernetes
that
are
trying
to
read
and
they,
for
example,
they
don't
know
how
is
Data
Center
or
all
the
terms
that
it's
already
the
grocery
and
that's
we
started
on
unleash
the
basic
hyperlinks
to
the
grocery
front.
Kubernetes
I,
don't
know
if
we
have
this
initiatives
only
that.
D
Yeah
common
definitions:
that
is
there
that
it's
not
in
the
in
detail
inside
of
kubernet,
but
we
can
refer
to
our
grocery
because
we
explain
especially
for
the
new
people,
and
we
have
some
connection
and
also
more
attractions
for
us
yeah.
It's
like
win-win
for
everyone.
Yeah.
A
I,
don't
know
how
the
I
know
we
have
people
from
a
localization
teams
but
like
who,
like?
How
does
the
actual
the
English
kubernetes
class
really
work?
So
could
you
know
anything
about
that?
I
mean
well.
D
Well,
I
know
some
more
of
them
because
I
participate
in
the
kubernetes
documentations.
But
if
you
want
to
to
start
this.
A
Yeah
I
think,
if
you
know
people
it
would
be
great
to
ask
if
they
have
an
interest
in
that
like
if
they,
if
they
would
be
open
to
that
I
think
they
would
be.
But
let's
ask
them,
and
that
could
actually
be
a
issue
that
we
could
create
for
real
beginners
right,
because
it's
like
going
to
the
kubernetes
docs
finding
words
that
are
covered
there
and
then
hyperlinking.
D
A
That
would
be
like
a
real
beginner's
contributor
task
right
because
it's
like
as
a
beginner
coming
up.
Like
writing.
A
definition
is
really
difficult,
but
like
linking
to
that,
that's
like
something
that
people
could
do
so
I'm
sure
we
would
find
volunteers,
but
I
would
want
to
ask
them
first
right
if
I
mean
I'm
sure
we
could
do
it
as
loudly
as
well,
but
any
thoughts
from
anyone
else.
C
C
Pr,
the
reviewers
and
the
proverbs,
and
maybe
6.3
we'll
join
for
the
discussion.
So
maybe
we
can
start
by
opening
up
here
to
add
the
links.
D
D
G
And
yeah
yeah
this.
This
is
a
very
good
question
from
from
point
from
Cuddle
and
in
my
opinion
we
can
think
about.
We
can
extend
this
for
our
project
because,
for
example,
you
have
a
prior
to
start
the
contribution
for
a
receivability.
We
have
many
other
projects
talked
about
the
representabilitys,
etc,
etc.
So
not
only
kubernetes
is
documentation
requires
access
or
use
glossary
to
Define
key
points
to
more.
G
How
can
I
can
I
say
Global
globally
Concepts,
then
other
person
also
needs,
so
maybe
I
don't
know
if
if
there
is
some
kind
of
governance
or
talk
with
other
the
other
person,
but
maybe
the
the
CSF
team,
catering
glossary
contributors,
I,
don't
know,
can
start
a
kind
of
relationship
with
other
projects
through
TLC
I.
Don't
know
what
I'm
just
saying
that
we
need
to
avoid.
First
of
all,
we
need
to
avoid
duplicates
and
duplicate
efforts
and
more.
G
They
need
to
avoid
also
not
on
duplicate
but
have
difference
of
concepts.
For
example,
if
someone
from
a
contributor
for
Prometheus
right
something
about
observability
in
general,
they're,
not
about
parameters
per
C
but
in
general
about
receiving
many
survey
ones
from
Thanos
write.
Something
like
similar
about
oversellability,
this
kind
of
global
generals
or
general
concept
could
be,
could
be
touched
in
glossary
and
be
replicated
in
all
versions
documentations.
So
there
is
a
racial
relationship
between
the
projects,
as
I
said.
G
When
is
when
you
look
to
escarole
said
when
you
look
cabernetes,
you
have
much
more
documentation,
you
have
much
more
terms
Concepts
Etc
and
help
to
this
relationship
between
the
both
projects,
documentation
for
kubernetes
and
glossary.
But
if
you
we
are
growing
the
glossary
with
Concepts
and
terms
General
terms,
we'll
touch
Concepts,
that
other
projects
are
working
and
we
create
a
documentation
and
defined
concepts
for
them.
That
may
be
not
only
a
duplicate,
but
it's
also
has
differs
right.
G
It's
don't
converge
to
a
something,
so
I
think
that
we
can.
Maybe
the
the
group
can
start
to
talk
to
think
about
something
as
a
best
practice
for
documentation
that
always
bring
to
the
general
concepts
to
glossary
and
things
for
documentation.
Will
Consulting
open,
PRS,
create
Concepts
general
concepts
and
glossary
and
use
specific
Purgatory
specific
terms
in
the
documentation
and
make
a
reference.
G
A
Yeah
I
think
the
linking
is
definitely
something
that
we
should
be
doing.
I
don't
know
if
into
like,
but
between,
like
things
that
are
like
open
source
and
right
that,
as
we
said,
we
had
that
discussion
now
to
proprietary
pages
and
mentions
I.
Don't
know
if
I
followed
completely
with
the.
A
What
you
meant
with
not
I
mean
there's
going
to
be
duplication,
always
because
people
are
always
going
to
write
their
own
definitions
or
how
you
know,
but
what
we
want
to
do
with
the
glossary
is
that
there
is
like
one
source
of
Truth
or
one
thing
where
everyone
can
contribute.
That
is
like
easy,
and
that
is
project
and
product
agnostic
and
so
on,
and
it's
like,
and
everyone
is
welcome,
to
contribute
there
and
I
think
like
it
should.
It
should
definitely
link
to.
A
A
Okay,
if
that's
all
I
would
like
to
move
to
the
maintainer
discussion.
If
that's
okay,
unless
someone
has
something
else
and
okay
and
that
basically
is
like
if
people
want
to
drop
off,
that
is
totally
fine.
You
can
also
stick
around.
We
merged
two
of
our
meetings
and
I
also
had
the
maintainer
meeting
here.
So
there
are
some
internal
things
that
we
need
to
discuss,
so
yeah
feel
free
to
do
to
get
a
few
minutes
back
or
just
stick
around.
C
C
C
Hope
to
discuss
somehow
how
to
keep
them
in
their
position.
So
that's
the
reason
why
I
brought
extending
the
maximum
number
of
operators
for
each
localization
team.
Currently,
it
is
for
my
suggestion
is
encouraging
it
to
five
so
that
localization
team
can
have
more
appropriate,
even
though
some
of
them
are
not
very
active,
but
it
is
way
to
keep
them
in
their
position
and
make
them
come
back
again.
C
D
A
Think
it's
fine
because
it's
like
first
of
all,
I
I,
think
it
should
be
up
to
the
localization
teams
like
as
well
to
decide
right.
We
definitely
do
not
recommend
for
people
to
have
15
approvals
because
it
gets
messy
right
but
I
think
sometimes
if
they
I
think
it's
good
to
say
like
restricted
to
a
slower
number
at
first
and
then
as
they
are
under
flow
and
know
how
things
work,
because
sometimes
maybe
someone
is
gone
for
two
months
speak
or
on
a
project
and
can't
do,
but
they
know
they're
gonna
be
back.
A
You
don't
want
to
have
to
downgrade
like,
like
put
them
like,
remove
them
and
put
them
back
again.
If
they
know
they're
gonna
come
back
right,
but
I
think
so
and
if
one
person
is
gone
for-
and
you
only
have
for
a
few
months-
and
you
only
have
three
approvals-
it
gets
difficult
with
the
because
you're
really
depending
on
these
two
other
persons
and
if
they're
not
available
for
a
week,
then
you
cannot
merge
something.
So
it
becomes
a
bottleneck.
A
F
You
think
yeah
I,
agree,
I,
agree
on
that
the
localization
team
should
should
decided
on
their
own
and
if
they
think
that
that
it
will
be
beneficial
because
it
doesn't
scale
otherwise
or
they
are
blocked.
Otherwise,
then
it's
totally
fair
I
guess.
A
Maybe
what
we
can
do
is
like
when
a
team
is
new,
we
restrict
it
to
the
four
or
maybe
or
the
new
one
would
be
five
and
then
we
say
like
okay
after
six
months,
you
know
like
once
you
kind
of
because,
like
sometimes
when
they're
new,
they
want
to
make
everyone.
You
know,
because
everyone
is
excited
and
every,
but
you
don't
know
how
engaged
people
are
and
then
maybe
after
six
months
or
more,
then
you
will
figure
it
will.
A
You
will
figure
out
who
is
going
to
be
doing
more
work
and
less
work
and
then
they
can
decide
who
should
actually
if
they
should
include
more
people
or
not,
because
I
think
the
reason
we
restricted
is
because
at
the
beginning
everyone
is
excited
and
everyone
wants
to
make
everyone
right,
a
approver,
but
that
that.
C
Is
enough
and
based
on
requests
from
the
localization
ongoing
localization
team,
we
can
extend
the
numbers
yeah
right.
A
A
C
I
will
share
it
to
Spanish
team
and
that
Pierre
thanks.
C
Okay,
yeah
next
item
is
about
you
Tom
suggestion
for
public
cloud.
You
can
check
that
issue
contributor,
suggested
the
public
Cloud
term
used
as
a
new
term
and
the
original
I
contributor.
The
con
the
contributor
open.
That
issue
is
the
conservatory
is
actually
working
on
defining
virtual
private
cloud
and
the
contributors
thought
in
order
to
define
the
previously
public
Cloud
time
is
required.
That's
the
reason
why
the
contributor
opened
that
issue.
C
In
my
opinion,
current,
the
VPC
virtual
private
Cloud
term
can
be
defined
without
regardless
of
the
public,
Cloud
private
cloud
and
any
other
cloud
and
I
think.
A
Well,
I
just
saw
like
because
VPC
was
still
awaiting
triage
and
people
were
signing
up
front.
We
never
kind
of
decided
if
it
should
be
part
of
the,
and
it
was
like,
oh
because
it
was
like
didn't
we
I,
don't
remember
deciding
that
it
should
be
part.
So
it's
like
the
first
discussion,
the
first
thing
that
we
should
probably
I
think
we
discussed
it.
We
started
talking
about
it,
but
then
we
never
come
came
to
a
conclusion
and
then
so
I
think
we.
C
A
C
If
I
remember
correctly,
the
reason
why
I
added
the
agreed
to
it
VPC
is
that
bpc
itself
is
a
little
bit
hard
time
to
understand
for
beginners.
But
actually
we
are
very
often
use
that
term,
even
though
it,
if
originated
by
AWS
Maybe.
But
if
there's
many
close
service
providers
are
using
that
term
in
as
general
term.
F
Is
wrong
I,
so
my
opinion
on
it
is
while
public
cloud
is
a
very
basic
concept:
I
guess
it
would.
It
would
be
fair
to
accept
it
as
well,
not
not
necessarily
to
to
define
the
VPC
one.
But
if
we
said
yes
to
VPC,
then
I
guess
it
would
be
fair
to
also
say
yes
to
public
Cloud,
even
though
it's
super
basic
but
I
I
can
imagine
that
that
people
want
to
see
how
it
may
be.
F
What
problem
it
solves
regarding
to
a
private
Cloud,
for
example,
I
mean
so
maybe
having
this
this
thing
and
the
contrast
of
Windows
both
in
our
glossary,
would
be
nice
things.
So
I
guess
my
my
feeling
would
say
to
approve
it
rather
than
to
not
approve
it.
F
F
Still
kind
of
included
it
yeah
what
what
I
think?
What
I
think
it's
it's
a
little
bit
a
little
bit
more
advanced
in
data
center
because
I
don't
know
data
centers
is
data
center,
but
with
public
Cloud
you
have
the
public
and
the
private
part.
So
you
can
really
have
this
yeah
of
the
contrast
of
those.
But
it's
just
that's
just
what
I
think
about
it.
I
mean
I
have
no
strong
opinion,
yeah,
just
a
gut
feeling,
more
or
less
yeah.
C
F
Yeah,
that's
fair!
That's
fair,
yeah,
yeah,
I
I
didn't
have
in
mind
that
that
the
cloud
computing
one
was
yeah
more
describing
the
public
Cloud
but
yeah
with
that
information.
I
guess
we
would
rather
not
accept
it
because
you're
right.
What
what
would
we
say
about
cloud
computing
about
public
Cloud,
which
is
not
already
included
in
in
the
existing
term?
Yeah.
G
Oh
I
I'm
trying
to
access
the
issue
1727
to
look
at
the
corona
boxes.
The
suggestion
public
club-
but
there
is
a
very,
very
good
definition-
come
from
nist
North,
America,
Institute
office
officer
technology
that
could
be
reference
or
use
being
publicly
private
or
any
any
kind
of
definition
of
cloud.
G
There
is
something
that
is
disconnected
from
any
provider
because
come
from
Standard
Institute,
you
can
be
could
be
used
inside
of
a
general
concept.
C
Okay,
thank
you
Paolo
for
the
this
dedication
information
and
actually
I
also
aware
of
that
definition
from
list
in
USA
and
yeah.
If
we
Define
Club
public
Cloud
as
a
Newton
in
glossary,
then
maybe
the
way
to
define
the
term
is
a
little
bit
different.
As
you
can
see,
we
have
three
sections.
What
it
is
problem
is
addressed
and
how
it
acts.
C
A
C
It
can
be
deployed
for
public
rate
or
private
way.
If
we
in
pretty
much
the
cloud
computing
in
public
way,
then
for
for
the
public
service,
then
we
call
it
public
cloud
and
if
some
companies
are
building
their
own.
C
F
I
have
a
suggest
to
make
what
if
we
just
just
extend
the
cloud
computing,
what
it
is
section
by
just
adding
one
or
two
sentences
stating
that
you
can
realize
the
cloud
computing
concept,
either
through
using
a
public
cloud
provider
like
AWS,
blah
blah
or
like
using
something
a
private
cloud
provider
like
I,
don't
know
what
is
it
we
sphere
or
yeah.
A
F
Okay
and
and
then
we
could
we
could.
We
could,
like
reference
reference,
the
VPC
if
we
want
in
that
that
converting
article
or
the
other
way
around,
which
is
reference
from
BBC
yeah
I,
like
that.
B
C
Not
accept
public
Cloud,
new
town
and
we
improve
the
term
cloud
computing
so
that
it
can
somehow
show
a
deployment,
type
or
Cloud
country
over
the
cloud
and
private
cloud.
Okay,.
B
C
I
guess
remaintenance
agreed.
A
A
Yeah
so
I
updated
observability
as
a
reminder:
observability
the
definition
was
kind
of
a
mix
between
the
property
and
the
tools
right
and
so
observability
should
be
the
property
because,
like
observable,
systems
can
be
observed
by
a
different
tools
so
because
it
is
a
property,
it
only
has
one
section
I
used
like
most
of
it
came
from
the
definition
that
was
already
there,
provided
it's
just
like
slightly
like
formulated
that
it
is
a
property
that
allows
you
to
do
those
things
instead
of
saying
it,
because
it
was
like
a
little
bit
of
a
mix
and
I
feel
like
it
must
be
clear
that
one
is
a
property
and
the
other
ones
are
tool
that
leverage
that
property
so
yeah.
A
That
would
be
for
technical,
ready
for
technical
review
and
I
put
our
back
I
know:
Noah
you've
been
you
started
that,
but
it
kind
of
got
a
little
stale.
So
if
we
could
kind
of
get.
F
That
yeah
I,
just
I
just
dragged
the
task
on
my
to-do
list
and
increase
the
the
priority
like
I
said:
I'm
I
have
a
hard
time
to
catch
up
with
all
those
things,
but
it's
on
my
radar
now
again
so
I
will
see
that
I
finished
that
one.
C
Else
then,
about
the
observability
definition.
Is
that
I
mean?
Maybe
we
would
better
to
differentiate.
C
So
since
in
Cloud
native
domain,
people
try
to
use
the
observability
term
kind
of
advanced
monitoring
way,
so
maybe
build
better
to
say
something
about
relationship
with
monitoring.
Just
monitoring.
A
Yeah
I
think
that
that
would
be
good
to
kind
of
have
that
because
it
is
similar,
yeah,
okay,
cool
yeah,
so
yeah
just
just
add
your
comments
or
suggestion
and
I'll
weave
that
in
and
then
I
also
asked.
If
ihor
could
review
it
so
Noah's
off
the
hook,
maybe
and
then
can
look
at
our
back
instead
and
so
that
we
can
get
that
updated.
Hopefully
soon.
A
Okay,
I
think
we
can
wrap
it
up.
Thank
you
for
oh
we've
got
a
new
visitor
when
we're
just
wrapping
up
thanks
for
those
whose
stick
around
even
for
the
maintainer
section.