►
From YouTube: 20220915 SIG Arch Enhancements
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
Towards
you,
but
okay,
I'm
just
gonna,
say
it
one
more
time
today
is
thursday
september
15th.
This
is
the
sig
architecture,
enhancement
sub
project
meeting,
I'm
kirsten
your
host
and
and
the
sub
project
owner.
I
work
at
red
hat
and
we're
just
going
to
get
started.
I
guess
and
we're
I'm
recording
so
no
pressure
to
turn
on
your
camera
or
do
anything
that
you're
uncomfortable
with
and
if
there's
anything
you
want
to
say
after
the
meeting.
Also
that's
you
know
something
that
you
don't
want
recorded.
That's
fine,
too
yeah.
B
Oh
yeah
yeah
I'd
like
to
introduce
myself
with
astors
or
devops
engineer
from
india
and
yeah,
so
I
joined
the
call
because
I
applied
for
the
release
team
and
I
got
rejected
in
the
mail
because
suggested
that
it's
better
if
you
join
the
calls
and
give
more
contributions,
so
it
will
come
into
their
notice
and
next
time
they
may
allow
so
yeah.
B
A
Yeah,
of
course,
thank
you.
Thank
you
for
coming,
just
as
a
little
bit
of
background
for
you
and
I
guess
it
introduces
the
discussion
in
kubernetes.
We
have
this
thing
called
kep,
a
kubernetes
enhancement
proposal,
which
is
how
new
features
get
into
kubernetes.
So,
basically,
if
joe
decides,
he
wants
to
make
some
big
change,
he
has
to
fill
out
what
is
essentially
a
design
document
that
sort
of
tells
us
the
technical
details,
the
motivation,
you
know,
risk
factors
and
everything,
and
also
how
he
plans
on
rolling
out
the
future.
A
So
we
go
usually
through
alpha
beta
and
ga,
and
so
for
the
first
part
he
might
say.
Okay,
this
is
going
to
be
alpha.
You
know
only
parts
of
it
are
going
to
work
and
this
basically
it
this
kept,
which
is
this.
This
meeting
is
essentially
about
enhancements.
A
This
enhancement
is
the
document
that
you
know
anybody
can
look
at
to
understand
the
design
and
you
know,
maybe
even
just
the
state
so
hey
like
joe
did
this
thing
that
in
in
1.25
and
it's
beta,
I
wonder
what
that
includes,
and
you
can
go
and
look
at
the
document
to
also
see
the
state
of
the
enhancement.
If
it's
finished,
then
you
can
also
go
and
it'll
say
it's
ga
as
a
xyz.
A
So
basically
it's
like
a
record
of
a
let's
just
say
a
feature,
but
it's
also
the
design
of
the
feature.
So
it's
like
this
one
one-stop
shop,
that's
the
place
where
you
go
to
talk
about
and
also
track.
The
progress
of
you
know
any
feature
in
well
feature
feature
using
feature
loosely
in
kubernetes.
A
We'll
assume
it
makes
sense,
so
one
of
the
things
is
background
that
we've
had.
We
have
them
very
occasionally
and
they're.
They
don't
really
actually
happen
that
often,
but
we
have
people
who
want
to
document
something.
That's
not
a
technical
feature
with
a
cap,
and
the
problem
is,
is
that
a
cap
is
very
focused
on
technical
details
and
you
know
like
feature
gates
and
production
readiness,
review
type
things,
and
so
it
can
be.
A
You
know
just
kind
of
a
drag
to
have
this
really
long,
essentially
template
that
you
have
to
fill
out
when
you
want
to
make
more
of
a
policy
change
now
it
might
be
a
technical
policy
change
and
it
might
make
some
other
policy
change,
but
you
know
so
that's.
Why
there's
this
idea
of
what
we're
discussing
today,
which
is
a
process
cap
which
would
be
taking
that
enhancement,
template
that
we
already
have
and
tailoring
it
to
basically
a
whole
other
set
of
use
cases
where
people
don't
need
a
zillion
parts
of
you.
A
Discussion
of
it,
but
on
the
other
hand,
there
are
other
things
within
that
process.
Cap
template
that
we
probably
that
we
also
want
to
think
about
like
communication,
and
you
know
really
understanding
what
the
motivation
is
and
other
things
that
maybe
we
don't
care
as
much
about
in
sort
of
a
more
technical
cap.
So
it's
kind
of
a
balance
and
what
we're
discussing
is
kind
of
like
how
can
we
start
to
think
about
this?
Other
new
template
that
accommodates
these?
A
This
other
set
of
use
cases
without
excluding
use
cases
for
a
process
cap,
so
I
think
joe
yeah.
I
I
would
just
love
to
hear
your
motivation
because
I
feel
like
in
my
head,
like
your
your
process.
Cap
is
squarely
like
in
like
one
of
the
sort
of
like
use
cases,
but
it
doesn't
necessarily
cover
all
of
them,
but
I
would
I'd
just
love
to
hear
kind
of
like
your
perspective,
because
you
said
you
were
in,
I
think,
sick
api
machinery
and
at
cd.
A
So
I
I'd
love
like
from
a
perspective
of
like
a
sort
of
sig.
I
don't
know
if
you're
a
leader
just
like
a
really
active
member,
like
what
you'd
be
looking
for
in
a
process
cap.
B
Yeah,
it's
a
really
good
question,
so
I
I
kind
of
tim
hawking
kind
of
challenged
me
with
this
idea
that
this
was
something
missing
and
so
I
went
through
and
I
looked
at
some
some
caps
that
are
either
self-declared
or
are
kind
of
implicitly
a
process
cup,
and
I
found
you
know:
there's
a
bunch
around
kind
of
feature
life
cycles.
So
there's
you
know
one
about
preventing
perma-beta
features
of
features,
there's
one
about
beta
apis
going
off
by
default,
which
is
just
going
in
now.
B
There
was
another
one
to
introduce
the
concept
of
prod
readiness
and
they
all
had
a
couple
properties
in
common,
which
was
they
didn't.
They
didn't
require
any
code
changes
into
the
core
repos
of
kubernetes
right.
So,
like
no
code
changes
at
all,
it's
literally
entirely
about
process,
and
you
can
you
can
enact
that
process
at
like
a
reasonable
time,
but
it's
not
really
bound
to
the
release
cycle.
So
you
know
like
prod
readiness
you
just
pick
hey
in
the
126
release
or
123
release
or
whatever
it
was.
B
And
so
I
thought
those
were
all
kind
of
like
some
of
the
interesting
constraints
about
like
how
you
differentiate
a
process
coming
from
like
a
more
like
typical
cap
and
then
also,
if
you
just
go
through
like
how
the
the
the
de
facto
process
people
have
kind
of
like
found
for
themselves
to
do
this.
B
They
trimmed
off
a
ton
of
sections
on
the
cat
and
that's
super
useful,
because
it's
like
right
now.
Everybody
is
kind
of
individually
trying
to
figure
out
which
ones
to
trim
off
whenever
they
do
this.
But
if
we
just
show
them
like
no,
these
are
all
the
ones
that
don't
apply
for
sure
that
I
think
that
makes
a
life
easier.
I
so
there's
kind
of
this
reduction
stuff
that
you
can
do
where,
like
you
just
take
out
a
bunch
of
stuff,
but
then
I
also
started
to
notice.
B
There
was
like
a
misalignment
to
like
where
some
of
the
sections
kind
of
applied,
but
it
wasn't
quite
the
same
yeah.
A
A
It's
kind
of
different,
like
yeah,
because
I
actually
had
started
working
on
like
thinking
through
the
process
cap
and
started
on
like
a
template,
and
that
was
the
thing
is
like,
like
yeah
totally
agree
like,
we
should
have
a
process
gap
but
also
think
that
it
has
to
be
kind
of
opinionated
about
what
we're
looking
for,
because
otherwise
right
like.
If
we
just
like
take
out
parts
of
a
template,
then
it's
kind
of
leaving
like
certain
sections
up
to
the
person
where
it's
like
yeah,
give
me
some
details.
A
B
A
Actually
kind
of
like
once
you
go
through
the
reducta
reduction
reduction
step,
then
there's
like
I
started
like
doing
this
like
edition
step,
and
then
I'm
like
okay
well,
this
is
just
like
a
this
is
like
this
isn't
equally,
not
equally
long,
but
it
becomes
equally
long
because,
at
least
to
me,
like
part
of
the
process,
cap
is
communication
and
like
how
can
we
and
tell
me
what
you
think
right,
but
I
already
talked
about
this
in
another
video.
A
Yeah
so
so,
for
me,
part
of
it
is
communication,
because
we
also
have
a
process
kept
like
the
cadence
cap,
which
you
know
like
that's
like,
because
there's
different
levels
of
how
does
this
kept
affect
people
and
then
how?
Much
do
you
want
to
rely
on
the
thoughtfulness
of
the
author
versus
like
a
sort
of
a
framework
in
how
you
have
to
communicate
decisions
or
changes
like?
A
I
think
that,
for
you
know
like
the
no
perma
beta
thing
like
that
was
all
like
announced
well
in
advance-
and
you
know,
like
the
authors
of
that,
like
had
a
good
idea
of
the
impact
of
their
of
their
change
right,
but
you
could
also
foreseeably
have
people
who
make
a
big
process
change.
That's
actually,
like
you
know,
has
a
high
impact,
as
opposed
to
like
a
lower
impact,
and
they
don't
give
anybody
any
advance
warning.
A
They
just
write
their
cap
approve
it,
and
you
know,
even
I
could
even
see
like
within
a
sink
or
something
they
don't
really
give.
A
lot
of.
You
know
heads
up
for
that
and
it
could
be
really
disruptive
to
contributors
or
users
or
you
know,
downstream
projects
or
anything
so
like
yeah,
it's
kind
of
a
rabbit
hole
when
you
start
like
to
classify
kind
of
the
types
of
types
that
you
could
have
and
their
impacts.
A
A
You
to
comment
on
like
this
idea
of
like
tracking
impact
and
and
scope
of
the
cap
right,
because
it's
like
it's
something
impacts.
You
know
just
your
sig
and
it's
not
even
that
disruptive.
For
your
sake,
there's
no
reason
why
you
can't
just
say
like
hey.
Maybe
this
goes
into
effect
like
right
right
now,
maybe
you're
using
your
process
cap
to
document
something
that
already
exists
right,
like
you're
just
like.
A
Where
you
know,
we
kind
of
need
that
handbrake
in
there,
where
it's
like
okay,
but
this
impact
is
really
high
and
you
want
to
make
sure
that
you're
going
to
like
adequately
get
commentary
on
these
changes
from
whoever's
impacted
and
also
give
them
plenty
of
time
to
understand
what
the
change
is,
because
we've
been
relying,
I
think,
for
a
lot
of
their
processes
on
kind
of
just
like
the
knowledge
of
the
authors,
which
you
know
cig
architecture,
they
are
very
like
understanding
of
that,
but
it
doesn't
necessarily,
you
know,
I
think,
apply
for
everyone,
so
yeah
there's
like
all
of
these.
B
A
B
If
this
process
goes
through,
we
need
to
really
understand
who
you're
going
to,
and
that
makes
it
so
much
easier
for
the
next
process
kept
author
because
they
can
look
at
a
previous
process
cap
and
look
at
the
communication
plan
that
was
was
was
established
and
they
can
just
kind
of
incrementally
improve
on
that.
If
we
don't
do
that,
everybody
has
to
figure
it
out
from
scratch
all
over
again.
A
A
Cap,
the
proof
that
you're
kept
is
done
and
that
the
thing
happened
is
that
you
know
like
all
of
the
associated
prs,
close
right
and
somebody
looks
and
they're
like
all
of
the
pr's
closed,
or
they
didn't
they're
getting
backed
out
or
whatever.
So
this
is
officially
now
this
right
and
you
did
your
documentation
and
you
might
have
done
xyz
else
well,
the
process
kept
it's
kind
of
like
there
is
that
that
kind
of
risk
of
like
yeah
yeah
yeah
like
this,
is
a
big
change
and
we're
totally
gonna.
A
You
know
do
so
much
communication
and
then
they
don't.
You
know,
or
it's
like
super
janky
and
then
you're
like
wait,
but
you
actually,
like
you,
sent
out
one
email
like
the
day
before
holiday
and
nobody
saw
it
or
something
you
know
like
a
week
before
this
thing
takes
place.
I
don't
know
so
yeah
there's
definitely
like
that,
like
I
think
the
cap
is
kind
of
powerful,
because
there's
that
follow-up
action
to
verify
that
the
thing
happened
that
you
said
was
gonna
happen.
B
Yeah,
I
think
we
can.
We
can
basically
encode
the
expectations
and
kind
of
like
the
normal
process
here,
and
I
I
mean
if
I
was
going
to
write
a
process
cap,
I
would
be
super
thrilled
to
have
that
because
it's
like
okay,
so
first
I
propose
it
and
then
you
know
everybody
agrees
on
what
we're
gonna
do
when
it
gets.
B
Probably
I
don't
know
we
pick
words,
maybe
the
word
for
that
is
ratified
and
then
like,
and
then
you
go
through
the
process
of
like
enacting
it,
which
is
like
you
do
all
the
communication
you
mark.
That's
all
coming
in
you.
Can
you
probably
then
have
to
transition
the
cup
once
more
to
like
now
it's
fully.
A
Exactly
yeah
so
that
that's
totally
like
what
like
in
my
janky
draft
so
far
like
that's
what
I
was
doing
because,
like
that's
kind
of
the
part
that
actually
because
it's
like
really
tempting
to
just
like
strip
out
the
annoying
parts
of
the
kept
template
and
then
be
like
oh
here
like,
but
then
that
also
like
potentially
creates
a
lot
of
a
lot
of
unintended
consequences
like
because
it's
like.
Okay,
that's
why,
when
I
saw
yours
I
was
like
yeah.
A
I
think
this
accidentally
creates
like
a
lot
of
policies
that
we
don't
want
to
like,
actually
create
so
yeah
I
mean
I.
I
think
that,
like
I
think,
maybe
what
I
need
to
do
is
like
de-jankify,
my
draft
a
little
bit
and
put
it
up
it's
like,
but
the
thing
is.
I
don't
know
that
it's
like
great
for
a
pr
I
mean
I
could
just
do
like
a
google
doc
for
now
or
something
just
to
have
like
a
conversation
with
people
about
it.
But.
B
B
Going
to
be
messy
and
complicated,
and
then
one
of
the
nice
things
about
that
is
then,
like
once.
I
feel
that
people
like
people
are
starting
to
like
narrow
down
on
the
key
topics
and
I'm
getting
the
sense
of
like
where
the
final
shape
of
this
might
start
to
trend.
Then
I
can
then
like
write
a
cap
where
I
sometimes
copy
paste
sections
over
and
sometimes
rewrite
sections,
but
I
kind
of
like
I
kind
of
recreate
a
new
document.
Yeah.
A
Okay,
yeah
because,
like
that's,
that's
what
I
was
struggling
with
like
okay,
like
I
am
working
on
this
template,
but
there's
like
all
of
these
conversations
and
like
input
from
people
that
I
want,
but
I
don't
actually
want
to
put
up
the
template
because
that's
kind
of
not
the
point
right.
You
know.
A
It's
kind
of
like
no
like
there
needs
to
be
like
a
sort
of
semi
discussion
or
just
feedback
about
like
certain
ideas
and
sometimes
like
a
pr
is
not
the
best
place
for
it,
which
is
why
I
really
wanted
you
to.
A
B
Yeah
so
because
that's
all
going
to
have
to
happen
we're
going
to
be
in
this
kind
of
silly
flow
where,
like
we're,
we're
going
to
be
defining
something
not
using
the
process
that's
proposing
but
which
it
clearly
should
adhere
to.
So
we're
going
to
just
have
to
have
some
mess
somewhere
until
yeah.
A
B
A
A
I
feel
so
much
better
that
someone
else
like
felt
this
pain
because
I
was
like
I
almost
got
sidetracked
by
it
because,
like
I
like
when
I
was
when
I
was
doing
the
template,
I
actually
started
writing
like
just
comments
in
there
and
like
pros,
because
I'm
like
well
like
you
know
like
this-
is
what
I
think
about
this
and
that
and
this
I'm
not
necessarily
like
wedded
to
this
specific
wording.
But
this
is
my
intention
so.
B
A
Maybe
maybe
I'll
that'll
be
on.
My
big
to-do
list
is
to
kind
of
dump
it
all
into
a
document
and
share
it,
because
I
think
that
that's
a
better
kind
of
venue
for
like
discussion
and
not
even
thinking
about
the
final
form.
But
to
me
it's
like
goal
oriented
right.
It's
like
you,
want
a
clarity
of
why
people
are
doing
it,
what
they're
doing
like
the
impact
of
it
who
it
affects
and
then
how
they
plan
on.
I
mean
the
biggest
part
of
it.
B
Yeah
the
communication
communication
is
huge
and-
and
the
other
thing
that
I
noticed
is
right
now
people
are
individually
figuring
out
how
to
do
this
from
scratch,
and
I
mean
they
kind
of
converge
a
little
bit
on
certain
things.
But
it's
a
lot
of
work
for
people
to
like.
Oh
I'm,
I'm
trying
to
introduce
a
process.
People
are
recommending,
but
kept
for
that.
B
So
I'm
individually
just
trying
to
like
trying
to
like
restructure
the
cups
into
this,
but
I'm
not
really
sure
what's
right
and
then
I
go
over
to
like
the
yaml
file,
and
I
don't
know
what
the
states
mean
and
I
don't
know
which
ones
to
strip
about.
So
I
think
there
it's
like,
there's
kind
of
like
two
or
three
parallel
goals
here.
One
is
to
collectively
decide
how
this
works
instead
of
individually
deciding
how
it
works.
A
A
A
Really
good,
like
I
hadn't
even
considered,
I
was
like
stuck
on
like
kind
of
like
two
a
lot,
but
I
think
three
is
actually
like.
This
is
a
it's
kind
of
a
record.
You
know
like
this
is
because
even
like,
if
you
look
at
some
of
the
existing
process,
cups,
they're
kind
of
like
you
kind
of
understand
it,
but
then
you
kind
of
just
don't
necessarily
have
like
all
of
the
context,
sometimes
too
so
yeah.
I
think
this
is
yeah.
That's
actually.
B
Really
a
huge
time
saver
and
somebody
comes
in
like
why
did
we
do
this
and
then
like?
If,
if
the
cap
is
completely
an
unconvincing
reason
on
why
we
did
this
then,
like
we
need
to
update
the
crap?
Well,
I
mean
we
will
update
it.
So
what
will
probably
happen
is
we'll
we'll
have
a
set
of
big
kind
of
messy
ideas
and
we'll
all
kind
of
like
collab
on
that
for
a
while
yeah.
A
A
A
A
I
feel
like
it's
like
there's
there's
like
a
good
set
of
people
where,
if
you
give
them
just
like
the
headings
and
the
guidance
they
give
you
like
a
lot
of
information,
and
so
like
those
people,
I'm
not
worried
about
it's
more,
just
like
the
outliers,
where
you're
like
yeah,
but
this
is
a
process.
So
I
really
have
to
make
sure
that
these
outliers,
who
only
write
like
one
sentence,
have
the
right
sentence.
At
least
I
don't
know
like
but
yeah.
I
I
like
those
three
points
and
kind
of
figuring
out
like
yeah.
A
I
mean
I
do
think
that
part
of
the
final.
I
think
the
part
of
the
final
template
too,
though,
will
have
some
it'll
it.
I
like,
because
I
kind
of
looked
at
it
also
through
like
impact
like
how
many
like
how
many
like,
not
how
many
people
but
like
what
is
the
general
impact.
Like
is
it
just
like,
you
know,
just
memorializing
something,
or
you
know
this
isn't
a
big
deal
like
it's
like
a
low
impact
to
the
contributors
or
whoever
it
doesn't
affect
any
users.
It
only
affects
the
same.
A
The
cigar
already
talked
about
this
like
a
thousand
times
or
is
it
something
where
it's
like?
We
need
like
five
six
talking
about
this.
We
need,
like
you
know
we
need
like
all
like.
So
it's
also
like
kind
of
like
a
scale
question.
So
they'll
probably
be
more
like
not
optional
sections,
but
I
feel
like
you
need
more
detail.
The
greater
the
impact
is,
you
know,
especially
for
communication
and
and
probably
like
rollouts
and
things.
It's
like.
A
The
rollout
of
the
idea
really
is
the
one
that
starts
to
get
kind
of
complicated,
because
if
it's
like
a
sig
and
a
sig
is
like
yeah,
I
decide
not
architecture,
but
somebody
else
like
I
decided.
I
decided
this
and
everybody
in
the
sig
agrees
and
we're
all
gonna
do
this
from
now
on,
and
it's
totally
fine
like
I
mean
you
know
like
that's,
that's
pretty.
That's
a
pretty
like
standard
like
thing
to
decide
to
do
and
then
then
do
it.
A
But
if
it's
like
you
know,
hey
we're
changing
the
kubernetes,
cadence
or
hey
like
we're,
we're
changing
how
we
do
apis
and
things,
and
I
think,
like
sig
architecture,
did
a
really
good
job,
like
you
know,
making
sure
to
like
space
those
things
out
by
letting
people
know
a
good
period
of
time
in
advance
and
then
kind
of
like
cranking
it
to
like.
Okay.
Well
now
it's
this,
but
how
do
you
kind
of
memorialize
that?
But
that's
like
a
high
impact
change
as
well?
A
You
know,
so
I
think,
like
impact,
plays
sort
of
a
big
role
in
the
expectations
of
like
the
rollout
and
how
long
that
might
take
and
the
notice
that
needs
to
be
given
to
people.
You
know
like
notice,
it's
like
it's
like
the
impact
is
kind
of
the
core
of
like
you
know,
or
scope
is
kind
of
the
core
of
like
well,
how
much
notice
do
you
have
to
give
people,
and
I
don't
think
there
are
rules,
but
there's
there
should
be
guidance.
A
You
know
how
much
feedback
do
you
need
right
like
if
you're
going
to
change
everything,
then
maybe
your
kept
needs
to
be
open
for
you
know
x
period
of
time,
and
you
have
to
solicit
some
feedback
from
a
point
from
all
of
the
disparate
groups
where
like
if
it's
just
you're
sick,
it's
a
little
bit
more
straightforward.
So
yeah,
I'm
going
to
put
this
in
my
document
in
my
messy.
B
It's
tricky
because
some
of
them,
some
of
them
are
some
of
them,
are
very
procedural,
and
it's
like
we're
going
to
have
this
process
and
it's
not
super
contentious,
but
I
also
noticed
that
some
of
the
some
of
the
things
that
I
had
listed
as
being
an
example
of
a
process
cap
were
almost
more
of
a
policy
cap
yep
and
some
of
those
you
could
imagine
some
of
those
getting
incredibly
contentious
like
where
you
have
like
two
sides,
both
with
a
strong
perspective
yeah,
and
so
I
don't
like.
I
don't
know,
yeah.
A
A
Kepp,
isn't
like
I
feel
like
it's
like,
are
kept
not
telling
people
how
to
make
a
decision
right,
like
I
don't
tell
I
like
I'm
a
sub
project
owner
for
the
template,
but
I
don't
tell
people
like
this
is
how
this
is,
how
you
decide
that
you're
doing
this
teacher
right
like
it's
like,
I
can't
tell
you
how
you
agree
upon
something
or
not
or
how
you
resolve
your
disagreements
or
not,
but
I
do
say
that,
or
we
do
say
that
you
have
to
have
an
agreement.
You
know.
B
A
You
have
to
like
have
these
people
from
the
sig
or
the
other
thing.
There's
like
five,
maybe
there's
three
things
involved.
They
all
have
to
approve
this,
whatever
approved
means
to
them
so
yeah,
I
think
that's
like
a
kind
of
like
you
want
the
space
to
do
that.
A
That
was
why,
even
just
when
you
open,
when
you
open
a
a
new
cap
and
you
open
an
issue,
but
you
didn't
do
this
actually
joe,
but
when
you
open
a
new
issue
like
the
you're
supposed
to
put
a
discussion
link
where
someone
from
this
stage
said
like
this.
A
But
the
idea-
and
it
actually
just
as
background
it,
helped
us
a
lot
because
you
previously
just
had
tons
of
people
opening
kept
in
the
repo
and
never
talking
to
the
sig
and
then
having
this
awful
process.
So
it's
like.
I
don't
tell
them
like
what
I
don't
say
like
what.
What
do
I
need
to
see
in
that
discussion?
I'm
just
like
you
need
to
discuss
it
and
somebody
needs
to
say
yeah
do
that
right.
A
So
I
think,
like
we
can
lightly
make
space
for
those
agreements
and
discussions,
but
I
don't
think
we
have
to
say
like
what
agreement
is
right
like
or
like
what
that
has
to
really
look
like,
because
there
is
like
an
approval
process
on
a
cap.
Just
a
process
cap,
just
like
a
regular
cap
right
like
so.
B
A
You
know
maybe
it's
like.
If
you
have,
if
you
enumerate
the
impact,
then
you
know
different
people
need
to
also
approve
that
cat
like
different
cigs,
maybe
or
different
whoever's
like
if
it's
going
to
require
a
lot
of
communication.
Maybe
you
need
a
sign
off
from,
I
don't
know,
say,
contributor
experience
or
something
that
they're
going
to
help
you
do
whatever
you
know
something
like
that.
So
I
don't
think
we
have
to
say
what
approval
looks
like.
I
think
we
just
have
to
make
space
for
that
actual
approval
to
happen
in
a
way.
B
Yeah
I
gotta
jump
to
another
yeah.