►
From YouTube: CNCF CNF WG Meeting - 2022-12-05
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from April 17-21, 2023. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
B
B
Okay,
I
will
show
the
screen
up.
Bobby,
oops,
okay,
I,
think
that
you
can
see
my
screen
right.
A
B
Okay,
well
in
terms
of
announcements,
we
have
company
for
the
next
or
something
common.
A
I
don't
know
well,
let's
see
there
is
one
this
week.
Well,
not
some
announcement,
but
this
week
is
Telecom
TV
event
on
Thursday
yeah.
The
great
talker
debate
hold
on
a
second
all
right.
A
B
So
it's
streaming
event
or
like.
B
B
B
A
A
B
But
yeah
I
found
like
this
week.
It's
the
open
source
Summit
in
Japan.
B
There
is
one
single
topic
which
are
related
with
telcos
I,
don't
know
if
it's
meant
to
be
Japanese
or
but
and
I
I
didn't
introduce
you
because
the
ticket
for
this
one
is
25
dollars
per
for
for
the
virtual
event,
so
I
didn't
consider
like
just
paying
25
or
a
single
topic
which
I
don't
know
if
this
is
going
to
be
in
in
English
or
in
Japanese
or.
A
B
Probably
later
we
can
access
to
the
recorded
inch
and
see
what
what
happened
right.
B
B
B
B
Okay,
nice
job
any
any
other
event.
I,
probably.
A
A
It
have
been
some
Watson,
especially
has
been
looking
into
it,
but.
A
A
Tools
and
existing
documentation
and
other
stuff
I
think
it
would
be
good
to
contribute
Upstream
from
Silva
and
then
for
folks
to
be
engaged
with
them
to
incorporate,
directly
and
and
think
about.
You
know
the
direction
they're
going.
B
A
Yeah
I
have
it
listed
right
there.
Look
at
that
CNF
tests
would
be
the
test.
Suite
I'm
guessing
you
know
just
kubernetes
in
general,
but
I
think
they're,
actually
gonna
at
least
have
some
part
of
the
kubernetes
ede
test
or
cube
ref
or
something
which
will
be
related
to
the
kubernetes
conformance
or
I'll
say
that
ensuring
that
it's
compatible.
B
Yeah
from
my
understanding,
it's
like,
let's
be
taking
the
I,
don't
get
air
I2
or
IRT
errors
you
just
focusing
in
these
particularly
like
I,
mean
they're
they're,
not
trying
to
cover
their
their
A1
or
so
yeah.
B
B
B
Box
not
all
right
the
recordings
of
the
one
Thomas.
B
Yeah
well,
I
was
probably
one
of
that
I
like
it
was
from
from
China.
B
She
has
that
good
presentation
talking
about
the
the
bronzo,
the
turquoise
like
at
the
direction
that
they
are
checking
the
wise
are
or
the
reasons
that
they
are
they
having
to
to
start
working
with
Matthew
and
but
Matthew's
proposing
so
I
guess
she
summarized
very
well
like
the
main
goals,
and
the
reason
behind
that
probably
for
now
is
one
of
the
great
attention
that
I
have
seen
in
the
ones-
oh
at
least
not
a
great
one,
but
just
offering
like
a
different
point
of
view
of
things.
B
Yeah,
the
rest
of
them
are
are
interesting
ones,
but
probably
not
too
much
rare,
but
we
have
been
trying
to
do
our
no
friend
different
perspectives
of
things.
B
They
provide
like
a
the
source
code
and
yeah
for
sort
of
things,
but
I
don't
know
if
you
have
a
chance
to
attend
it
or.
A
B
Well,
I
like
the
way
that
John
explain
certain
Concepts
and
things
so.
B
One
of
the
terms
which
is
so
confused
for
me
is
packaged
in
terms
like
a
nephew
I
guess
it's
more
like
like
a
kind
of
a
Helm
chart
but
more
like
open,
and
it
has
an
option
to
to
the
way
to
to
treat
things
from
Upstream
combined
with
the
the
downstream.
B
So
here
he
has
all
these
contents
defined
there
and
try
to
clarify
all
these
things
for
the
workshop
yeah.
It
has
a
lot
of
things.
I
mean
it's
not
easy
to
reproduce,
because
definitely
you
need
like
a
virtual
machine
in
gcp
and
have
a
GitHub
repo
associated
with
RPM
and
things
like
that,
and
that
relation
is
based
on
the
hostname
but
but
yeah
just
reading
the
documentation
is,
is
very
valuable
in
terms
like
these
clarify
a
few
things
and,
from
my
point
of
view,
is
stuck
with
the
starting
point
right.
A
I
definitely
would
like
to
watch
that
video
been
trying
to
get
her
engaged
some
she's
okay,
open
source
Summit
in
Vancouver
before.
A
Things
officially
really
got
started
like
some
of
the
initiative.
Some,
it
was
just
a
small
Gathering
to
communicate
what
was
where
things
were
going
and
she
had
spoken
back
then
about
like
adoption
of
stuff,
like
that
wasn't
happening
like
cicd
practices
and
things,
so
it
would
be.
B
All
right
do
we
have
to
have
like
a
PRS
open
or
things
like
that.
A
B
For
me,
I'm,
okay,
so
do
we
have
to
wait
for
come
to
keep
thumbs
up
or
no
one
else,
I
I,
guess
well
yeah.
We
can
wait
first,
but.
A
Adding
more
content
to
that
ex
best
practice
thanks
listener
or
creating
other
best
practices
like
there's
some
other
content,
yeah
I
mean
it
says,
user
stories
and
stuff,
but
I
guess
it's
valid
for
everything.
There's
maybe
enough,
and
we
just
need
to.
If
you
go
open,
the
actual
go
ahead
and
merge,
it
I
think
with
listing
on
your
nobody
objects,
it's
a
title:
it's
minimum.
B
Chrome:
okay,
it's
an
exceptions.
B
B
A
B
A
A
B
A
Well,
I'm
not
saying
about
a
feather
template,
I'm,
saying
literally
just
modify
this
one
best
practice
and
delete
the
extra
stuff-
that's
not
necessary,
but
so
it's
clean
at
the
end
and
we
can
add
them
back
if
if
it
makes
sense
but
user
stories
for
this
particular
best
practice,
don't
really
don't
seem
to
matter.
Unless
you're
going
to
write
your
own
right
here,
I
guess
we
could
write
a
user
story
that
says
here's
an
example
of
someone
having
a
best
best
practice
that
they're
going
to
ignore
they're
not
going
to
follow
a
best
practice.
A
B
A
B
Well,
we
haven't
gone
in
the
other
documents.
Well,
we
have
information
for
them
right,
like.
A
A
The
references
and
I
I
guess
we
could
open
issues
mark
them,
as
when
they're
we
had
some
input
from
there's
a
way
to
say:
hey,
we're
open
to
anyone,
collaborating
they're,
adding
two
things:
help
on
it
like
the
tax,
there's,
a
I
think
that's
like
first
contribution
or
whatever
you're
tagging
it
and
people
are
starting
to
click
through
tags
and
just
help
on
any
project.
A
So
if
there's
anybody
that's
looking
to
contribute,
you
know
we've
had
people
drop
in
on
this
call
before
so
we
could
add
a
I
guess
that
ticket
add
title
to
exceptions
that
would
have
been
straightforward
for
pretty
much
anybody
to
go
in
and
read
and
go
okay.
Here's
what
the
summary
and
motivation!
Let
me
come
up
with
the
title:
it's
document
your
exceptions.
A
We
could
create
new
tickets
like
ad
references
to
that
best
practice
and
for
that
particular
one
I
think
someone
could
go
through
and
add
a
reference.
So
here's
an
example
of
documenting
your
compliance.
There's
there's
a
lot
of
examples
out
there
for
different
any
project.
It
doesn't
really
matter
this
isn't
specific
to
Cloud
native
or
tell
comments
communicating
if
you're
following
standards.
Community
standards
best
practices,
whatever
can
you
close
ticket
227.
A
A
B
B
I,
don't
like
discussion
in
the
community
about
the
modifying
the
apis
and
what
they're
trying
to
do
in
the
kubernet
CPI
to
support
multiple
interfaces.
B
So
so
that's
why
it's
like
a
hold,
because
I
don't
know
if,
if
we
don't
have
to
say
like
a
best
practice
for
that,
mostly
we're
going
to
have
or
to
follow
what
the
current
Community
is
going
to
propose.
B
B
No
I
don't
know
no
from
my
understanding
that
they
they
want
to
modify
the
current
API
definition.
So,
actually
that's
why
I
understand
it's
like
in
your
ball
definition,
you
will
have
to
add
the
different
interfaces
and
implementation
on
Motors
is
going
to
follow
that
new
API
definition.
B
So
if
you're
I
still
don't
know
how
they
are
going
to
implement
that
probably
yeah,
probably
the
the
thing
that
I
should
refer
here,
is
like
to
all
the
discussions
that
are
hot
in
the
community.
That
way,
we
can
correlate
things
yeah
yeah,
because
they
have
a
lot
of
documents
and
precautions
in
the
community
which
are
not
affected
here.
B
But
yeah
I
guess
in
in
the
regarding
this
traffic
I
think
it's
for
now
it's
better
to
keep
it
as
it
is
like
a
draft
and
see
what
is
happening
in
the
community.
A
I
mean
if,
if
we
can
write
it
where
it's
aligned,
then
we
can
move
forward
if
it's
already
aligned,
then
I
think
we
can
move
forward.
Now,
aside
from
that,
I
think
it'd
be
good
to
get
an
update
from
I
I,
don't
know.
What's
going
on
with
the
discussions
the
current
discussions
with
Sig
Network:
do
you
have
you
been
keeping
up
with
those.
B
A
I'm
trying
to
find
the
actual
I
don't
even
can't
find
that.
B
B
Oh
yeah,
they
have
a
specific
Channel.
That's
right
communities.
A
Topic,
I
guess
this
was
foreign.
B
This
is
a
very
interesting
Doctrine.
This
talks
about
the
different
use
cases
and
they
discuss
why
why
they
are
doing
these.
B
So
so
what
I'm
going
to
do
is
add
chat.
These
two
documents
here,
right,
like
at
least
I,
mean
like
a
reference
for
the
community
Zoom
right
soon,.
A
So
The
annotation
document,
the
best
practice
to
me,
seems
still
relevant
annotating,
whether
telling
people
that
they
need
to
do
annotations
for
how
they're
setting
up
their
network
is,
is
moving
people
towards
coordinated
practices.
Even
if
the
community
hasn't
started
on
where
that
could
be,
you
can
still
implement
the
some
of
the
Core
Concepts
for
doing
doing
these
things,
the
configuration
declaring
your
declaring
your
intentions
and
what
you're
wanting,
even
if
you're
doing
it
in
vendor
specific
annotation
types,
I
mean
that
it's
still
moving
towards
that
versus
saying.
A
Oh
we're
going
to
statically
generate
what
we
need
with
a
shell
script
that
generates.
You
know
the
things
on
the
Fly
by
talking
to
some
external
database,
and
you
have
no
idea
what's
going
on,
because
it's
statically
configured
by
a
network
admin
ahead
of
time,
right
that
wouldn't
make
Cloud
native.
A
And
then,
if
we
have
a
more
generic
way
of
doing
things,
that's
directly
aligned
with
core
kubernetes,
then
that
configuration
that
someone
is
already
using
with
maltes
and
a
m
or
whatever,
like
you've
done
it
that
works
with
all
of
them
like
just
adding
all
of
the
different
ones
and
then
determining
based
on
the
cni.
That's
there
you
can
do
it
well,
if
you've
already
done
that
now,
you
can
simplify
your
code
because
you're
in
my
mind,
you
should
be
able
to
simplify
it
because
you're
moving
it
all
to
one
standard
configuration.
B
B
So
and
also
you
can
apply
the
same
same
approach
right
so
so
you
can
specify
all
all
the
the
major
ones
or
like
all
the
different
rotations
and
doesn't
matter
like
I
mean
at
the
end
of
the
day,
earpod
or
your
deployment
are
going
to
take
just
the
annotations
which
are
relevant
to
the
particular
h8
controller
right,
no
matter
if
you
have
for
once,
those
the
other
ones
are
going
to
be
ignored,
and
especially
the
main
idea
is
not
restrict
the
number
of
annotations
that
you
can
put
in
your
file.
B
A
A
A
You
know,
maybe
we
could
talk
with
hop
on
like
a
a
multis
call,
which
I
think
they
were
talking
on
the
Plumber's
working
group,
but
that
one
might
not
be
as
good
but
commune
getting
feedback
from
other
folks
would
be
good.
So
whether
it's
written
up
in
a
pull
request
happens.
That
would
be
fine
and
then
say
hey.
We
want
feedback
on
this.
A
A
Yeah
and
I
mean
it
the
way
it's
written
is
a
little
bit
more
General
to
where
it
might
be
helpful
for
the
Sig
multi-network
or
what
they're
doing
and
how
they're
wanting
to
apply.
It
probably
would
have
been
good
to
show
them
that
at
the
kubecon
meeting,
but
if
we
could
get
it
on
a
future
one
that
would
be
good.
B
Yeah
also,
if
I
did
sum
up
some
sensor
like
if
companies
missing
there
be
free
to
have
it,
like
probably
a
very
good
documentary
and
things.
A
I'm
up
for
working
with
you
to
try
to
get
something
ready
and
maybe
pull
in
some
other
info
and
Silva.
You
know
if
we
can
get
on
and
talk
with
them
and
say
Here's,
an
area
where
we're
trying
to
do
I
I
seems
like
they're
trying
to
move
forward
on
implementation,
and
it
would
relate
to
ra2
rc2
stuff
with
aniket,
so
maybe
reaching
out
to
Silva
and
I.
B
I
barely
involved
in
you
know,
I
mean
yeah
it
just
I
I
didn't
attend
all
the
meetings
just
and
see.
If
can
propose
that.
A
All
right
I'd
like
to
see
if
we
can
talk
about
the
silver
folks
and
then
the
other
part
would
be.
A
A
Like
what
what
I
think
I
mean
thinking
forward,
of
course,
if,
if
something
moves
forward
and
Sig
multi-network,
then
there's
going
to
end
up
being
e
to
e
test
around
that
eventually
that'll
go
into
kubernetes
conformance,
but
it
the
so
once
it's
in
kubernetes,
then
there's
going
to
be
different
things
that
could
be
tested
like
in
the
CNF
test
suite
and
everything.
If
you
have
a
CNF
coming
up
and
it's
using
multiple
interfaces,
is
it
using
this
new
multi-network
thing
that
whatever
comes
out
of
that,
but
thus
far
future?
A
B
Yeah
he's
he's
got
interesting
topic
right
now.
The
thing
is
like
NSM,
the
nfm.
In
the
previous
release.
They
did
a
complete
refraction
of
source
code,
so
obviously
the
the
way
to
define
things
and
to
use
all
the
apis.
They
must
complete
everything.
So
the
the
source
code
that
I
used
to
have
for
NSM
is
not
working
with
their
latest
release
that
they
have
so
I.
Don't
know
why
they
decide
to
do
that.
B
Probably
they
had
their
own
thinking
reasons
to
do
that,
but
yeah
I
need
to
check
with
I,
don't
know
if
Brad
can
help
me
to
to
fixing
those
things,
because
I
I
couldn't
make
to
work
for
for
the
current
release
that
NSM
I
try
to
to.
Basically
what
I'm,
trying
to
say,
I
tried
to
update
the
source
code
that
I
have
for
making
sure
that
a
system
valid,
but
you
have
some
issues
with
NSM
tenant,
seems
to
be
deprecated.
B
No
one
is
updating
the
source
code
anyway,
I
I,
tested
I'm
still
working
with
still
good
news.
Multus
is
still
working
as
expected,
so
so
yeah
it's.
My
only
concern
is,
with
MSN
NSM,
proposed
a
new
different
approach
compared
with
Moto
Santana.
B
You
know,
Motors,
you
have
to
predefine
the
networks
and
you
have
to
say
well,
I
have
all
these
different
networks
and
my
bots
are
going
to
attach
to
those
networks
during
the
per
request
in
NSM.
The
approach
is
different.
Like
you
don't
Define
anything.
So
the
only
thing
that
you
find
is
your
deployment.
B
Msm
is
going
to
start
connecting
or
creating
the
networks
during
the
execution
or
the
creation
time.
So
it's
more
like
an
only
man
solution.
B
So
this
this
source
code
seems
to
be
working
before
like
and
I,
have
the
end-to-end
testing
and
checking
all
these
things
and
try
to
split
in
different
pieces.
For
example,
it's
just
it's
just
focusing
the
infrastructure
design.
B
The
thing
is
necessary
for
for
the
infrastructure,
so
I
and
I
have
different
things
like,
for
example,
this
component
can
be
replaced
with
either
no
offers
a
similar
solution.
I
haven't
tested,
but
yeah.
The
the
main
concern
is
this
one,
which
was
a
huge
problem
because
they
Nana's
hand
they
decide
to
change,
and
then
they
do
have
two
documentation.
How?
How
can
you
use
your
their
their
SDK
to
consume
those
services.
B
So
this
it
used
to
be
the
initial
approach,
which
was
perfectly
fine
for
my
proposal.
Now
is
I,
don't
know.
B
A
A
We're
cutting
forward
the
idea
of
a
best
practice
before
there's
a
community
consensus
on
how
to
do
things.
A
B
A
It
would
be
okay,
it's
since
things
are
going
to
continue
changing
in
network
service,
mesh
and
other.
A
I
guess
it
can
be
a
what
we
had
referred
to
as
carrot:
I.
Guess
it's
a
carrot
test
or
it's
a
test
that
indicates
that
you
could
be
doing
something
Cloud
native,
but
we
don't
know
if
you're
not
like
you
may
be
doing
something
we're
not
aware
of.
So.
If
we
looked
and
said,
hey
we're
looking
for
this
type
of
annotation,
this
network
service
mesh
annotations
and
they
have
it.
Then
we
go.
Oh,
this
is
good
they're
doing
something
positive.
A
So
we
want
to
let
end
users
of
this
CNF
know
that
they're
doing
something
positive,
but
if
we
don't
find
it,
it
doesn't
mean
that
they're
not
doing
something.
We
didn't
recognize
since
there's
not
a
single
standard
yet,
but
if
there
is
something
that
we
can
show,
here's
what's
currently
happening
a
valid,
like
you
think
it's
a
valid
use
of
network
service
mesh,
that's
still
applicable,
like
whatever
they're
currently
doing,
and
we
can
write
up
here's
an
annotation
test
and
we
check
for
it.
A
A
B
Yeah,
not
that
definitely
makes
sense,
no
desire
to
propose
something
and
eventually
really
fine
or
foolish.
All
these
things
based
on
the
feedback
from
the
community
instead
of
like
not
mentioning
anything.
B
Yeah,
that's
that's
it.
Do
we
still
have
the
next
yeah
I,
don't
know
if
you
have
to
start
preparing
for
the
holidays
and
asked
if
they,
if
you
want
to
have
the
meetings
or.
A
Real
quick
before
we
move
on
to
that.
Looking
at
your
screen
right
there
for
the
open
issues,
I
would
the
link
between
non-root
best
practice
and
not
run
written
test,
Suite
that
one's
pretty
straightforward,
Tom
I
want
to
get
that
one
knocked
out
I'm
just
kind
of
looking
at
the
titles,
real
quick,
so
that
one
seems
okay.
We
have.
We
just
need
to
update
it
in
the
docs.
That
seems
pretty
straightforward
to
try
to
clear
some
of
these
out
and
have
momentum.
A
I
want
to
add
that
to
my
to-do
list.
Would
you
assign
me
on
that.
B
A
Maybe
Lucina
too,
let's
get
multiple
people
on
this.
This
one
is
straightforward
enough
that
let's
get
it
completed,
all
right
go
ahead
and
go
back
to
the
list
of
issues.
A
A
And
there's
also
a
test
or
test
or
multiple
versions
of
tests
in
the.
A
Inside
of
the
test,
Suite
there's
one
in
the
certification
enabled,
but
the
test
Suite
actually
has
multiple
types.
So
I
think
that
one
should
be
one
that
we
put
together
sooner
than
later,
since
we
already
have
content
and
having
more
best
practices.
I
think
will
motivate
people
to
get
involved,
and
it's
good
to
document.
A
One
thing
that
I'm
remembering
Lucina
so
I'm
just
trying
to
think
of
like
what
are
some
things
that
we
can
put
in
place
and
move
forward
on.
Lucina
had
mentioned
previously.
To
that
we
could
start
using
that
best,
CNF
Dev
document
we
had
held
off
because
we
didn't
have
any
best
enough
best,
maybe
no
best
practices
when
Robbie
created
it,
but
I
think
we
could
start
linking
them
in
there
like
the
non-root,
and
that
would
be
one
yeah
like
how
do
people
find
these?
Well,
you
can
go
in
GitHub
and
look
at
that.
A
I
just
realized
scroll
up
the
under
configuration
life
cycle
uh-huh
the
best
singing
after
applications
configured
via
standard
way;
I
guess
those
are
just
examples.
A
What
is
number
two
application
announced
Zone
membership
of
the
tier
to
its
peers
and
interesting.
Those
are
not.
Those
are
going
to
be
fake,
I
think
so
they
just
got
put
in
there.
A
A
Because
when
we're
trying
to,
we
want
to
be
able
to
get
more,
people
engaged-
and
you
know
in
2023,
get
this
going
again.
We
had
a
higher
number
of
folks
that
were
involved
for
a
while
and
it's
kind
of
fallen
off,
but
we're
towards
the
end
of
year,
so
I
think
in
like
2023
and
getting
people
engaged
and
contributing.
If
we
say
here's
what
we're
trying
to
do,
we're
trying
to
help
the
developers
and
the
con
and
the
end
users
of
those
developers
with
having
cnfs
that
are
following
best
practices
that
everybody
understands.
A
B
Yes,
kind
of
confused
the
other
content,
or
maybe
one
of
the
purposes
we
can
have
it
here
and
the
disease
could
be
sustainability.
Maybe
some
practice
is
best
practice
for
sustainable
ability
or
environment
care.
I,
don't
know
what
do
you
think.
B
No
yeah
I
was
thinking
like,
maybe
you
probably
like
11,
and
the
number
11
like
sustainability,
like
stupidity
or
things
that.
A
Impacting
the
environment
yeah,
that's
great!
That's
great
yeah
sustainability,
I,
don't
know
if
it's
just
environmental
sustainability
might
be
the
category.
If.
A
I,
like
it
environmental
sustainability
or
just
sustainability,
I,
don't
know
if
there's
any
other
sustainability
that
a
CNF
would
care
about,
but
yeah
what
Lucina
just
put
in
there
can
we
add
this
comments
to
the
if
it
hadn't
already
happened
to
the
The
Mating
Nets
place.
This
is
a
good
idea.
I
really
like
that.
A
Thanks
you're
awesome
all
right!
Yes
for
that,
adding
that
category
and
then
what
do
you
think
as
far
as
adding
best
practices
into
the
best
CNF
Dev
doc.
A
Since
we're
running
out
of
time
before
break,
let's
see,
let's
just
Mark
that
then
I'll
come
back
to
what
I
was
going
to
say:
December
26th,
let's
just
cancel
that
one
I'm
gonna!
No,
on
that,
let's
are
you
gonna
you
wanna
run
one
on
on
the
26
Vector.
No,
all
right,
let's
cancel
so
on.
The
second
sounds
good.
A
A
Yeah
looks
good
all
right,
so
are
you
available
this
week
for
maybe
some
working
sessions
to
get
through
some
of
this.
A
A
That's
something
that's
a
little
tedious
and
annoying,
but
if
we
get
the
categories
updated
or
decide,
if
we're
going
to
update
them
and
then
do
it
yes
or
no
will
make
it
better
if
we're
adding
tickets,
adding
new
best
practices,
sorry
so
ticket
228.
A
A
If
they're
not
responding
to
Readiness
checks-
and
this
is
after
download,
so
this
this
test
waits
for
the
CNF,
the
image
to
be
available
and
actually
initiate
container
startup
on
the
host
machine.
So
if,
if
it's
not
having
any
response
at
all
then
and
it's
indicative
of
a
monolithic
application,
so
that's
the
idea
and.
A
Even
if
it's
saying
I
don't
want
to
accept
new
Services,
don't
don't
have
the
proxy
or
whatever
put
me
in
service
yet
because
it's
waiting
on
multiple
other
things
to
come
up,
there
should
be
some
type
of
responsiveness
and
say
I'm
waiting.
You
know
if
I'm
thinking
like
restful
applications,
you
can
still
repo
respond
and
then
have
applications
that
are
intelligent
because
of
the
response.
A
That's
not
the
best
choice
but
it'd
be
better
than
nothing
like
no
response.
Anyways.
The
point
is:
if
we
go
to
categories
that
match,
then
I
think
it's
going
to
be
a
little
bit
easier,
but
we
need
to
look
and
see
if
it
makes
sense
for
what
we've
been
writing
over
there.
So
compatibility
and
solubility
upgradability
that
one.
A
A
Installability
and
life
cycle
management,
I'm,
saying
there's
no
space
here,
you
know
anything
all
right,
so
this
is
merging
two
categories.
A
Which
there
was
overlap
and
which
one
does
it
go
in?
Is
it
going
to
go
in
to
configuration,
or
is
it
going
to
go
into
configure
lifecycle,
or
is
this
part
of
the
initial
installation
will
upgrades
and
installation
I
mean
there's
configuration
items
that
you
could
say?
Well,
it's
important
to
do
this
so
that
you
can
do
deployments,
but
then
you
go
well.
Isn't
that
part
of
the
life
cycle
so
that
whole
discussion
around
where
it
should
go?
It
seemed
like
it
was
better
to
have
something
like
this,
so
that
was
the
decision
there.
A
B
A
A
Are
we
going
to
keep
them
separate
or
they're,
not
in
sync,
or
do
we
merge
them?
Okay,
got
it
I
just
realized.
We
had
this
configuration
test
here
and
we
have
compatibility
I
guess
it
is
split
all
right.
A
So
we
need
to
look
that
over
in
my
mind
and
then
that
kind
of
influences
how
we
think
about
best
practices
and
when
we're
communicating
when
we're
in
the
middle
of
it
you
know
Victor,
you
may
go
I
know
this
is
applicable
in
multiple
areas,
but
when
we're
trying
to
get
other
people
engaged
and
they
go
I,
don't
I,
don't
know
what
that
is.
All
I
do
is
help
over
here.
I'll
go
yeah,
it's
applicable,
but
more
less
categories
is
probably
easier.
A
It's
been
less
confusing
when
people
are
saying
a
best.
Practice
is
applicable
in
two
different
categories
and
those
categories
are
similar
enough.
So
then
you
just
go.
Here's
the
set
they're,
all
applicable
I
mean
in
the
context
of
a
specific
best
practice.
It
may
say
this
is
for
more
applicable
for
the
install
on
day.
One
and
another
may
be
well.
Upgrades
are
applicable
related
to
the
day
one,
but
they're
also
part
of
life
cycle
management.