►
From YouTube: 20210527 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
A
Just
as
a
reminder,
we
are
under
the
cncf
kubernetes
code
of
conduct
so
be
good
to
everyone
and
if
you
ever
have
any
problems,
just
let
me
know
we're
going
to
start
today
with
the
agenda.
We
have
a
couple
items
so
we're
going
to
start
with
anna
the
second,
let's
start
with
the
the
second
topic
on
the
list.
If
you
want
to
take
it
away,
anna
sure.
B
It's
actually
related
to
the
first
one.
So.
B
Well,
I
guess
let's
just
talk
about
it,
then
so
I
guess
well,
okay,
so
I'm
just
gonna
talk
about
the
first
one,
because
it's
related
okay.
A
A
C
A
B
Yeah,
so
there
was
a
discussion,
a
thread
that
jeremy
posted
on
slack,
asking
us
feedback
on
the
current
receipt
cab
and
asking
feedback
on
whether
we
should
close
it
or
keep
it
open,
and
I
think
a
lot
of
us
said:
let's
close
it,
because
it
doesn't
actually
meet
the
current
goal
or
we
should
rethink
the
process
a
little
bit
and
I
think
that's
where
the
survey
came
from.
B
So
that's
the
second
bullet
point
on
whether
how
we
should
gather
feedback,
because
I
do
agree
that
we
probably
need
more
end
user
feedback
to
figure
out
the
focus
of
what
we
should
improve
on.
So
I
think
that
should
be
our
focus
right
now.
I
don't
know
if
everyone
agrees
with
that,
but
I
just
wanted
to
start
a
conversation
on
how
we
might
go
about
doing
that.
So.
C
One
quick
question:
did
you
mean
end
users,
end
users
or
end
users,
as
in
contributors
in
the
kep
process,
contributors.
A
I
guess
for
me:
there's
there's
two
things
like:
I
thought
that
he
was
gonna,
send
an
email
for
the
current
receipt
kept
just
to
get
like
broader
thumbs
up
thumbs
down
on
that.
So,
oh
wait
is
anybody
taking
notes?
Sorry.
A
Okay,
so
maybe
the
action
item
would
just
be
to
find
out
for
that
one
to
find
out
if
he's
gonna
send
out
an
email
before
we
formally
close
it
or
make
like
a
formal
decision
about
that,
because
they
know
that
he
said
that
he
was
going
to
to
do
that
just
to
just
because
maybe
slack
isn't
the
only
forum
for
that.
A
The
survey
that
you're
asking
for
should
really
be
done
through
sig
release,
especially
because,
like
they
own
the
opt-in
process
and
their
spreadsheet
and
everything,
and
potentially
I
mean
there-
is
such
a
thing
as
like
feedback
fatigue,
and
I
feel
like
you
know,
if
sig
release
does
the
questionnaire
and
they
can
share
some
of
their
survey
results
with
us.
A
That
would
be
great,
but
also,
I
think,
like
jeremy
and
nabaru,
and
the
rest
of
enhancements
might
have
some
ideas
about
whether
or
not
a
receipt
process
makes
sense,
or
you
know
like
the
direction
to
go
in.
I
guess
the
one
thing
that
I'm
worried
about
is
just
gathering
feedback
just
to
gather
feedback
without
sort
of
a
targeted
and
focused
point
that
we're
trying
to
get,
but
also
that
this
really
on
the
current
process.
It
would
really
be
like
a
sig
release,
type
feedback
since
they
own
that
current
process.
D
Yeah
so
two
comments
what
I
wrote
on
slack,
so
I
don't
think
we
need
to
send
an
email
to
close
it
because
it
was
again
a
provisional
discussion
and
closing
also
does
not
mean
like
close
permanently.
It's
just
pr,
so
these
are
just
like
housekeeping
things.
D
On
the
second
point,
we
do
need
to
send
a
survey
who
that
who
and
what
that's
what
we
can
discuss,
but
I
feel
like
it's
just
not
on
sic
release
in
the
release
team.
It's
also
on
us.
This
is
a
project
who
have
like
deep
stakes
into
the
enhancement
process,
as
in
the
whole
thing
is
kind
of
formed
by
a
sick
release
and
the
release
teams.
Enhancement,
sub
team
just
facilitates
it
on
our
behalf
in
the
release.
D
So
we
do
need
to
find
some
questions
on
the
survey
now.
Where
should
we
discuss
not
sure,
because
I
feel
like
enhancements
of
project
people
release
team
announcement,
steve
people
from
the
recent
few
releases
and
the
current
review
should
be
part
of
the
discussion,
and
those
are
my
thoughts.
A
Well,
for
the
first
point:
how
about
then
our
action
item
would
just
be,
let's
verify
with
jeremy,
that
we
don't
need
to
set
that,
like
he's
not
going
to
send
the
email,
you
know
just
to
give
him
the
space.
If
he
wanted
to
do
that,
to
like
ack
or
knack
that
and
then
depending
on
what
he
says,
we
can
close
it.
A
We
really
need
to
figure
out
what
we're
trying
to
get
from
that
other
than
just
like
general
general
thoughts,
because
I
just
think
that
there
is
such
thing
as
survey
fatigue
and
it
does
need
to
be
targeted
to
whatever
our
goals
are
and
as
of
right
now.
I
don't
think
that
we
have
any
particular
goals
other
than
just
like
sending
a
survey
which
I
don't
think
is
going
to
like
facilitate
a
lot
of
actionable
information.
D
We
do
have
a
goal.
The
main
question
is:
are
you
happy
with
the
current
enhancements
process?
If,
yes,
why?
If
not,
why
and
should
not
be
this
simple
just
that
if
you
are
not
happy,
there
should
be
some
more
objective
questions
as
to
understand
more
metrics,
but
I
think
we
do
have
a
goal.
The
whole
receipts
process
discussion
started
with
enhancing
the
enhancements
process.
Just
that
I
don't
think
we
all
agree
right
now
that
that
is
good
thing.
D
I
myself
don't
think
like
adding
one
more
artifact
as
a
burden
for
the
contributors
without
even
asking
for
feedback
is
good.
So
that's
where
this
discussion
came
in
for
a
survey
and
the
survey
does
have
a
goal.
Is
that?
Are
you
happy
with
the
current
current
enhancements
process,
adding
doing
whatever,
like
filing
caps
and
doing
processes
on
that
and
then
the
opt-in
thing?
So
what
anna
wrote
soliciting
feedback
on
the
opt-in
process.
B
Yeah,
I
actually
agree
with
that,
because
once
we
close
the
receipt
process
or
receipt
cap,
it's
like
what
is
this
group
trying
to
do
right
like
I
want
us
to
focus
on
something
and
that
something
will
come
from
feedback
from
users
who
you
know,
creates
the
enhancement
cap,
so
I
think
we're
trying
to
understand
what
do
they
need
help
help
with
like
what
should
we
improve,
and
I
think
we
will
get
that
from
the
survey.
D
Yep
also,
like
I
have
seen
like
people
dissenting
against
the
process,
so
I
feel
like
we
really
should
like
send
out
something
to
the
contributor
community
to
understand
like
where
people
feel
that
the
process
is
hectic.
I.
A
Would
just
I
would
just
say
that
we
really
have
to
work
with
sig
release
on
this,
because,
like
half
three
quarters
of
the
complaints
are
probably
going
to
be
about
the
collection
process,
as
opposed
to
like
actual
kept
stuff.
A
So
that's
part
of
my
concern
is
just
like
getting
the
right
people
involved
in
a
survey
and
getting
the
right
questions
asked
in
the
survey
because,
like
sig,
release
owns
the
opt-in
process
and
if
we're
gonna
get
a
lot
of
feedback
about
that,
and
they
kind
of
need
to
own
that,
but
also
the
idea
that
you
don't
want.
D
A
People
like
50
surveys
about
different
things
and
the
surveys
should
be
focused
and
tight,
and
you
don't
want
to
overburden
people
with
surveys
and
since
sig
release
is
probably
also
interested
in
this,
and
the
release
team
is
also
interested
in
this.
There
should
probably
be
some
tight
coordination
on
this
so
that
we're
not
like
sending
out
50
surveys
to
people
and
they
just
start
sort
of
not
responding
or
giving
us
information.
That's
not
necessarily
relevant
to
us
and
would
be
relevant
to
state
release.
A
C
Yeah
I
just
wanted
to
go
back
and
like
talk
about
sort
of
the
like
briefly
go
over
the
sort
of
like
breakdown
of
what
enhancements
is,
as
far
as
a
cigar
sub
project
versus
release
itself.
I
think
you
actually
covered
that
pretty
well.
The
the
last
statement
like
and
the
enhancement
sub
project
does
not
cover
the
actual
collection
or
sort
of
the
facilitation
of
the
process
they
own.
The
sort
of
you
know
the
various
metadata
things
we
need
to
track.
C
Sorry
about
that
and
sort
of
the
the
overall,
how
you
know
it's
just
like
what
we
need
from
caps
to
drive
things
forward
and
how
it's
sort
of
like
how
I
also
see
like
steering
and
control
backs
where
steering
serve,
decides
the
policy
and
contributes
as
the
executors
of
the
policy
and
it's
sort
of
that.
The
way
I
see
that
for
like
enhancements
and
the
enhancements
release
team
does
that
sort
of
make
sense.
A
Actually
can
I
I
was
wondering,
because
I
was
thinking
about
this
a
lot,
but
could
I
bring
up
my
my
last
bullet
point
because
it's
semi-related
this
bullet
point
that
we're
discussing
now
and
the
thing
that
I
was
thinking
about
was
in
general
like
I
want
to
have
a
kept
template?
Oh
wait.
Did
I
just
delete
it.
C
I
moved
it
up
because
we're
talking
about
it.
Oh.
A
Cool
thanks
something
that
I
I
wanted
to
us
to
explore,
which
is
more
closely
related
to
the
actual
kept
instead
of
the
process
with
kept
versioning,
because
one
of
the
problems
that
I
think
that
we're
having
we're
going
to
have
is
that,
like
tooling
and
other
things
we
currently
don't
have
a
way
to
have
a
version
of
a
template.
So
we
can't
tell
the
release
team.
A
Hey,
like
everybody
needs
to
be
on
this
version,
especially
as
time
goes
on,
and
also
that
I
think
we
want
to
stop
making
incremental
changes
to
the
kept
template
like.
I
think
that
it
would
be
a
lot
easier
if
we
say
hey
like
this
is
the
whatever
I
don't
know
what
time
period
I'm
going
to
try
to
write
up
something
for
this,
but
some
kind
of
time
period
or
you
know,
then
you
should
be
updated
to
the
may
2020
template
version
and
as
such
I
was
going
to
say.
A
Well,
maybe
we
should
have
a
sort
of
a
different
directory
where
it's
like
the
sort
of
in
progress
kept
template
where
we
would
be
merging
changes
and
can
get
feedback
on
that.
But
I
I
guess
I
was
thinking
if
the
sub
project,
like
bob
is
saying,
is
more
focused
on
the
actual
cast
like
once,
we
can
more
like
can
better
organize
the
actual
like
kept
change
process
and
kept
versioning
process.
A
A
Sig
leads,
maybe
the
release
team,
prr
people,
api,
reviewers
performance,
test
people
and
try
to
like
get
the
test
to
be
tighter
and
more
efficient
for
everybody,
and
so
that
was
something
that
I
was
thinking
about
for,
like
an
enhancement,
related
survey,
as
opposed
to
like
a
more
process,
related
survey
that
I
was
interested
in
doing,
but
that
would
require
like
a
little
bit
of
pre-work,
just
because
I
want
to
be
able
to
have
a
way
to
get
feedback
from
people.
A
That's
also
actionable
and
to
have
things
like
done
in
a
more
organized
fashion.
So,
just
on,
like
the
survey
tip
like
that's,
like
an
enhancement
for
project
survey,
that
I
was
interested
in
doing
not
like
super
ad
sap,
because
I'd
like
to
get
it
organized
a
little
bit
better
and
get
all
of
our
thoughts
and
a
process
set
up
for
sort
of
iterating
on
the
template
in
a
more
organized
way.
So
those
are
just
my
thoughts
and
it
seemed
like
somebody
related
to
the
above
above
point.
A
C
So
I
am
very
much
in
plus
one
towards
versioning
the
kept
template
like
that
was
actually
sort
of
what
I
visioned
a
long
time
ago,
versioning
both
the
template,
along
with
the
kep
metadata
itself,
because
that
would
be
really
easy
to
like
attach
a
version
just
like
we
do
in
our
normal
kubernetes
apis.
C
To
then
like
see
like
hey.
This
is
this
state
and
you
know
we
do
need
to
plus
one
it
or
you
know
this
is
the
validation
criteria
at
this
point
in
time.
This
is
the
validation
criteria.
Now
it
becomes
easier
to
see
what
must
be
changed
and
then,
as
far
as
like.
A
Yeah,
I
was
also
thinking
like
if
there
are
changes
to
the
kept
template.
It
would
also
be
a
little
bit
easier
to
get
feedback
on
that
because
we're
not
doing
pr's
directly
to
the
like
active
template.
Like
say
we
have
a
totally
words
are
escaping
me
right
now,
but
let's
say
we
had
a
like
whatever
work
in
progress
or
perspective
like
kept
template
directory
and
say,
like
people
did
some
pr's
to
that,
and
we
thought
hey.
A
These
look
pretty
good,
like
let's
merge
them
in
then
that's
something
that
we
can
also
send
to
like
a
semi-broader
group
of
people
and
say:
hey
like
this
is
these
are
some
of
the
changes
that
we're
thinking
of
what
do
you
think
of
these
changes?
Are
there
any
changes
that
would
help
like
facilitate
you
filling
out
the
caps
in
a
more
workable
way,
and
they
can
look
at
this
version
like
still
use
the
old
version
and
comment
on
it
prs
to
it,
and
then.
A
C
It
it
reminds
me
of
like
staging
or
release
yeah
if
season.
A
A
Yeah,
no,
I
because
I
know
that,
like
navaroon,
like
is
very
like
always
reminds
me,
like
he's
interested
in
getting
community
input
and
I'm
thinking
like.
I
see
a
lot
of
problems
with
the
kept
temple
clip
being
workable
or
what
kind
of
ways
can
you
actually
get
feedback
that
makes
sense
and,
like
sometimes,
questions
like
general
questions
are
great,
but
it's
also
really
effective
when
you
have
something
to
refer
to,
and
you
have
something
to
say,
this
is
the
thing
that
we're
all
talking
about.
A
A
It
is
like
to
anchor
it
in
this
artifact
I
think,
could
be
like
super
helpful,
so
I
kind
of
like
I
want
to
have
like
a
versioning
policy
and
work
on
that,
but
I
also
more
immediately
kind
of
want
to
build
a
little
bit
of
consensus
and
I
can
like,
I
guess,
bring
this
up
in
slack
as
well,
about
like
having
a
sort
of
staging
directory
for
the
kept
template
and
that
that's
where
pr's
to
the
template
should
go
into
so
that
those
changes
are
visible
and
difficult
right,
they're
difficult
against
the
current
version,
so
that
we
don't
just
roll
them
out
randomly,
and
we
can,
you
know,
sort
of
get
feedback
on
them,
especially
if
they're
like
more
substantive
changes
and
articulate
those
changes
a
little
bit
a
little
bit
better,
instead
of
just
merging
straight
into
the
template
all
the
time.
A
So
I
guess
that
would
be
step,
one
just
making
the
new
staging
directory
and
then
working
on
like
some
sort
of
versioning
policy.
If
other
people
think
that
that's
interesting,
that
was
an
idea.
I
was
kicking
around
my.
B
Head,
I
mean,
I
think,
that's
a
great
idea,
but
I
also
want
to
just
like
go
back
to
like
the
whole
receipt
cap
like
so
that's
process
related,
so
is
that,
like
sig
release
should
not
have
been
more
focused
on
secrets,
really
speak,
I'm
only
asking
because
I
don't
want
to
lose
track
of
what
we
were
trying.
D
B
C
Sorry
don't
mean
to
interject
without
reason
my
hand
the
like.
I
do
think
that
the
cap
does
sort
of
cover
both
groups.
I
think
it's
it's
technically
owned
by
an
enhancements
team
they're
not
by
enhanced
by
sig
arch
just
because
and
then
the
participating,
sega,
sig,
release
and
sig
release
would
own
the
process
part
and
the
or
sorry
too
many
process
parts.
B
I
guess
from
our
point
of
view,
then
the
enhancements
of
projects
group
was
there
something
from
that
cap
that
we
should
keep
focusing
on
or
like
do
you
think
we
can
just
it
was
more
process
based,
and
it
was
more
like
sick
release
thing.
A
I
mean,
I
think,
that
the
tooling,
like,
I
think
that
it's
also
the
idea
that,
if,
if
the
enhancement
subproject
wants
to
create
tooling,
which
then
becomes
the
new
collection
process,
then
like
the
enhancement,
sub
project
is
able
to
do
that.
But
I
think
at
least
for
me,
the
opt-in
process
solves
a
lot
of
the
initial
pain
points
from
that
that
the
receipts
process
was
hoping
to
create.
A
So
that's
why
I'm
kind
of
interested
in
seeing
what
kind
of
feedback
she
release
gets
about,
the
actual
like
release,
process
from
people
and
if
it's
something
where
it's
like,
streamline
the
opt-in
process.
A
But
people
think
that
it's
working
well
versus
like
hey
this
sucks
and
we
need
something
else.
That's
that's
kind
of
like
where
I'm
at
for
that,
but
I
do
think
that
the
tooling
is
really
valuable.
But
I
also
think
that
the
tooling
would
be
would
benefit
from
having
like
these
version
kept
and
other
things.
D
A
Yeah,
but
I
think
maybe
an
action
item
could
be
like
if
anna
maybe
wants
to,
like.
I
mean
she's,
on
sick
release
as
well
like
on
the
release
team,
but
kind
of
wants
to
bring
this
up
and
sing
release
about
whether
or
not
they're
going
to
be
collecting
any
information
about
feedback
for
the
enhancements
process
and
like
when
they
plan
on
timing.
That
and
maybe.
D
A
C
You
know
I'm
sorry,
the
other
like
little
thing
I
wanted
to
mention,
would
be
to
like,
I
don't
want
to
like
add
more
hands,
but
there
are
some
people,
and
I
just
want
to
call
it,
especially
like
josh,
burkus
and
contrerbex,
who
essentially
like
specialize
in
refining
surveys,
to
get
like
what
you
actually
want
out
of
them.
So
it
might
be
worth
just
like
when
this
does
start
to
come
together.
Plusing
him
in
on
the
the
conversation.
A
That
sounds
great
anna.
Is
that
something
that
you
could
kind
of
touch
face
with
big
release
for
because
I
I
know
like
the
release
team-
doesn't
really
send
out
surveys
because
it's
like
a
more
transient
team,
but
is
that
something
that
you
could
follow
up
on
just
to
get
information
about
their
plans
for
a
survey
yeah
sure
it
can
get
cool?
A
A
So
yeah
and
then
there's
two
small
pr's
ready
for
review.
I
think:
are
these
your
pr
center.
A
Yeah,
I
meant
to
get
to
them,
but
I
was
like
in
a
semi
crazed
state
this
week,
so
I
didn't
get
to
re-review
them,
but
I'll
do
that
later.
Today,.
D
A
And
then
I
see
luke
and
eddie
are
here.
So
are
there
any
sort
of
topics
that
either
one
of
you
want
to.
D
A
A
E
I'm
just
absorbing.
A
Okay,
cool
yeah,
so
cool.
I
guess
I
should
make
an
act,
so
we
have
one
action
item
to
just
verify
that
we're
with
jeremy
that
we're
not
necessarily
gonna
send
an
email
before
that's
closed.
The
receipts
process
is
closed.
That
doesn't
mean
that
any
of
that
will
not
be
used
in
the
future,
but
just
that.
That's
not
something!
A
A
For
the
cad
template,
because
that's
something
that
we
can
just
do
sort
of
pretty
quickly
and
and
put
some
clarity
into
that,
and
then
I'm
going
to
try
to
work
on
like
a
proposal
for
a
cap,
template
sort
of
feedback,
versioning
thing,
hopefully
in
the
next
couple
weeks
and
I'll
share
that
with
everyone.
I
don't
I
mean
I
guess
it
would
be
a
kept,
but
I'm
not
sure
I
might
just
do
like
some
kind
of
draft
document.
A
First
just
to
get
some
feedback
before
I
do
anything
more
formal,
but
I
will
hopefully
have
an
update
on
that
next
week,
and
I
also
the
other
thing
just
to
pitch
my
kept
versioning
is,
I
think,
like.
If
we
get
a
good
handle
on
the
actual
normal
cat
template,
then
it
becomes
a
little
bit
easier
to
think
about
other
kinds
of
templates
that
we
have
like.
A
If
we
have
a
process
template-
or
we
have,
you
know,
sort
of
templates
that
have
a
little
bit
less
of
a
bar
because
they're
not
necessarily
like
major
feature
work.
I
do
think
that
we
need
like
a
way
to
easily
iterate
and
control.
A
What
that
looks
like
and
talk
about
it
as
well,
so
that's
that
was
my
other
idea
of
why
having
having
some
sort
of
versioning
your
versioning
process
would,
I
think,
be
overall
net
positive
just
for
all
of
our
future
plans,
because
I
don't
think
that
we
really
thought
about
that
very
much
so
yeah,
sorry,
I
I'm
so
tired,
like
I'm
babbling,
so
I
apologize
no
worries.
A
Yeah,
I
I
think
that'll
be
cool,
though
I
I
don't
think.
The
one
thing
that
bothers
me,
though,
is
like
I
kind
of
wish
that
if
you
have
like
this
okay,
I'm
just
talking
out
loud
again.
If
you
have
this
staging
directory
that
has
like
this.
This
work
in
progress,
kind
of
kept
template
and
we're
saying
hey
like
we
have
some
feedback
on
this.
A
One
of
the
things
is
like.
If
we
did,
let's
say
we
did
send
out
a
targeted
enhancement
survey
about
the
kept
template
yeah.
I'm
just
also
brainstorming
like
what
would
be
some
of
the
better
ways
to
get
feedback
on
that.
Would
it
be
pull
requests?
Would
it
be
using
like
a
hackmd
file?
Would
it
be
like
using
something
that
allows
people
to
sort
of
add
notes,
like
I'm
not
sure,
but
I'm
kind
of
I
actually
think
that
it's
gonna
help
us
get
a
little
bit
better
communication
and
transparency
with
the
community.
A
So
I'm
gonna
write
something
off
and
like
put
it
in
the
slack,
and
hopefully
we
can
get
the
directory
thing
going
soon,
but
yeah
I'm
like
super
interested
in
everybody
like
giving
some
feedback
and
thinking
about
like
what
kind
of
cadence
do
you
want
the
versioning
to
take,
like
all
sorts
of
things
like
that,
so
I'll
probably
try
to
get
that
sort
of
up,
hopefully
before
the
next
meeting.
C
Actually,
if
if
this
is
a
little
bit
of
a
rush
job,
but
with
the
chairs
and
tls
meeting,
I
think
it's
next
week.
Okay,
that
might
be
a
good
time
to
you,
know,
ask
for
yeah
feedback
on
the
idea.
Let
me
look
at
the
calendar
really
quick.
It
might
be
well.
A
A
C
That
that's
you
know,
give
folks
a
preview
or
yeah
talk
about
it.
There.
A
Yeah,
I
think,
like
I
definitely
have
like
a
paragraph
blurb,
if
not
something
for
them
to
actually
comment
on,
but
just
to
kind
of
raise
some
awareness
that
that's
an
improvement
that
we're
going
to
be
making
and
seeking
feedback
on
it
so
that
it
doesn't
come
as
like.
A
super
surprise,
and
I
think
people
will
be
will
be
interested
because
it
also
solves.
A
C
Sorry,
I
don't
want
to
scroll
too
much
and
we're,
I
think,
we're
technically
over
time.
No.
A
C
The
one
thing
we
might
want
to
do
too
is
at
least
give
people
a
way
to
provide
anonymous
feedback
either
on
the
survey
form
or
something
else.
Just
so
people
don't
you
know,
you
know
what
I
mean
like.
Sometimes
people
will
be
concerned
about
that
sort
of
thing,
but
if
we
want
the
like
people's
real
thoughts
on
it,
yeah.
D
C
C
A
B
Well,
I
think
one
thing
that
I
think
we
talked
about
in
the
past
is
the
pr
emo
file
like
if
we
could
automate
that
I
don't
know.
I
remember
like
somebody
mentioning
something
that
they're.
B
It
or
something
is
that
something
that
anyone
knows,
because
that's
something
that
is
really
visible.
Everyone
like
forgets
to
make
thoughts,
sometimes
and
then
like
it's
something
that
could
easily
be
automated.
So
I
don't
know
if
that's
on
us
or
prr
team,
I
I
don't
know
what
the
relationship
from
so
you
mean.
B
A
So
right,
so
the
question
would
be
like.
Is
that
something
that
we
want
to
have
sort
of
living
in
the
template
or
somehow
give
it
more
visibility?
I
can
follow
up
with
the
pr
people
and
see
what
they
think
and
then,
depending
on
what
they
say
like
get
a
get
in
get
a
card
up,
and
maybe
we
can
just
add
it
to
the
template.
I
just
wanted
to
like
double
check
like
their
thoughts
on
it,
but
that
could
be
cool.
A
I
agree
yeah,
okay,
so
that
would
be
my
I'll
follow
up
with
them
just
to
see,
like
maybe
there's
a
reason.
Maybe
they
don't
want
everybody
having
a.
A
E
A
Always
so,
just
for
a
summary,
your
cap
didn't
get
into
122,
because
I
don't
think
that
you're
sick,
like
chimed
in
for
your
exception,
approval
right,
correct.
E
A
E
But
we'll
we'll
see
they
may
change
their
mind.
E
A
We're
doing
good
we're
doing
good,
but
yeah.
If
you
I
mean
I
think,
for
that
enhancement.
If
you
get
the
approvals,
then
just
let
the
release
team
know
in
the
same
release
channel.
I
think
that
there's
a
thread
already
and
you
can
kind
of
try
to
push
your
stick
but
yeah
that
should
be
cool.
That
happens
and
is
there
anything
else,
luke
luke
is
just
listening.
Anna
nubber
bob
well
good,
all
good
albert
you're,
good
yep,
okay,.
D
Cool
yeah,
the.
E
The
the
process,
the
I
say,
a
quote,
there
was
a
question:
what
about
the
opt-in?
The
process
seems
fairly
usable,
it's
just
it
every
time,
there's
a
change
to
it.
It
is
a
little
confusing
to
the
you
know
to
the
older
caps.
What
do
I
need
to
change
now
and
yeah?
We're?
Not
all
you
know
imbued
in
the
in
the
changes
that
are
happening,
so
we
will
find
out
about
them
later.
E
E
Let's
just
wait
a
minute
and
it's
hard
for
when
you're
coming
in
from
the
from
the
other
side,
to
know
why
the
changes
happen,
because
usually
it's
just
no
here's
the
new
process
and,
oh
you
need
here's,
how
you
file
an
exception
this
time,
you
know
it
just
it
seems
like
it's.
It's
a
little.
You
know
it
it's
it's
it's
a
it's
a
living
process
right
as
things
are
moving
along
and.
A
Well,
the
exception
process
is
basically
the
same.
The
opt-in
process
is
a
bit
different,
but
if
you
have
any
like
feedback
for
the
opt-in
process,
there
is
a
release
team
retro,
where
I
think
you
can
add
your
feedback
as
well.
I
can
find
that
and
send
that
to
you
on
slack
just
like.
If
there
are
some
specific
points
to
that
that
you
like
find
to
be
for
points
of
friction,
then
that's
something
I
wouldn't.
E
Say
it's
not
friction.
It's
just
there
are
changes.
I've
been.
I
was
very
pleased
with
a
lot
of
the
help
I
was
getting.
You
know
from
the
various
teams,
the
pr
reviewers
and
things
like
people
were
involved.
You
know
and
that's
good
and
there's-
there's
there's
always
too
many
features
that
want
to
need
to
get
in
or
want
to
get
in.
So
so
that's
all
understandable,
but.
A
Well,
we're
working
on
like
bettering
our
communication
in
general,
so
that
was
actually
what
we
talked
about
a
lot
in
this
meeting,
and
I
know
that.
That's
also
something
that
sig
relief
is
thinking
about
a
lot
as
well,
how
to
better
sort
of
articulate
changes
and
let
the
community
know
in
advance
of
what
the
expectations
will
be.
So
I
think
it
would
definitely
hear
you
and
that
that's
something
that
we're
all
like
very
focused
on.
E
E
There's
a
cap,
pr,
there's
right
the
pr
itself
so
and
then
there's
the
email,
for
you
know
chain
that
you
need
to
track
and
manage
as
well
for
the
sig
node
and
then
and
then
there's
the
slack
communities
that
you
have
to
be
involved
in
I'm
running
out
of
fingers
right
on
the
places
that
you
need
to
be
involved
in
if
you're
just
trying
to
get
a
fee.
You
know
a
feature
in
it's
it's
it's
it
it
it's
intimidating.
Let's
put
it
that
way.
You
know
it
makes
you
want
to
jeez.
E
C
E
A
But
luckily
I
mean
sig
node
especially
has
like
really
taken
a
lot
of
control
over
their
feature
and
kept
process,
and
I
know
that
it's
still,
which.
A
Well,
some
of
those
you
don't
you
personally,
don't
have
to
worry
about.
That's
for
the
thing
to
you,
know,
fill
out
and
and
worry
about,
and
that's
really
up
to
you
to
just
you
know,
try
to
get
their
attention
and
their
priority
for
your
enhancements.
Like
they've,
been
doing
a
lot
of
really
good
work
to
try
to
bring
some
sort
of
order
to
the
the
chaos
because.
D
E
A
C
E
A
Well,
I
mean
you
really
have
to
just,
I
think,
communicate
with
your
sig
and
communicate.
However,
they
you
know
they
prefer.
So
if
that's
going
attending
the
fig
meeting,
if
that's
talking
to
those
because
they're
the
ones
who
own
the
cap
and
they're
the
ones
who
shepherd
it
through
the
process
and
sort
of
prioritize
it
within
all
of
the
other
things,
and
once
they
do
that
and
they're
able
to
give
it
enough
energy
and
time,
then
it
goes
through
pretty
quickly.
E
A
I
mean
in
general,
if
a
fig
gives
your
enhancement,
a
green
light
and
you're.
Getting
all
of
the
reviews
that
you
need
on
your
test,
then
that's
going
to
facilitate
the
process
and
then
you're
going
to
get
your
prr
done
and
that's
part
of
the
process,
and
then
it's
just
going
to
be
kind
of
shepherded
through.
If
there's
any
sort
of
I
mean,
but
then
they
also
have
a
limited
capacity.
So
they
have
to
kind
of
pick
and
choose
like
what
they
can
do.
B
A
Well,
I
mean
we
defer
to
the
things
subject
matter
expertise
on
all
of
it.
So
if
that's.
E
A
But
we
actually.
E
D
D
A
To
end
at
10
45,
and
I
think
we
had
a
really
productive
conversation
today
with
a
bunch
of
action
items,
so
I
guess
let's
reconvene
in
two
weeks
and
hopefully
we
have
some
updates
for
that
and
I
hope
everybody
has
a
great
long
weekend
if
you
have
a
holiday
on
monday
and
it's
just
always
a
pleasure
talking
to
everyone
so
bye,
I'm
gonna
stop
recording
now.