►
From YouTube: 20210401 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
All
right,
hello,
everybody
welcome
to
our
enhancement,
subproject
meeting.
My
name
is
laurie
apple
and
I
will
be
your
host
and
facilitator
today.
If
you
could,
please
add
your
names
here
for
our
list
of
attendees.
We
just
like
to
keep
track
of
that.
We
follow
the
kubernetes
code
of
conduct,
which
means
to
please
show
respect
toward
each
other.
A
Please
be
kind
everything
that
we
say
here
is
recorded
and
goes
online,
so
be
mindful
of
that,
and
with
that
do
we
have
a
note
taker
for.
B
A
A
A
D
D
A
Welcome
and
we
can
hope,
we
hope
that
we
can
provide
something
for
you
to
feel
engaged
and
and
get
involved.
If
that's
what
you're?
Looking
for
cool.
A
No
problem,
so
I
put
a
bunch
of
things
on
the
agenda
because
I
was
collecting
different
topics
from
the
chat
and
things
that
we're
also
tracking.
A
A
Yeah,
okay,
maybe
this
from
kirsten
also
is
receipts
related.
So
I'll
put
it
next
to
the
cap.
Part
cup
item.
E
A
Everything
covered,
so
I
would
just
like
to
run
through
mine
real
quickly
so
that
we
have
more
time
for
other
folks
topics.
So
I
think
we're
all
fairly
aware.
A
Maybe
james
is
not
because
he
hasn't
been
part
of
this
direct
discussion,
but
given
the
feedback
from
this
group
and
others
about
responsiveness
during
the
release
cycle,
when
it
comes
to
updates
from
sigs
about
caps
dems-
and
I
were
actually
talking
it's
his
idea
to
think
about
an
enhancements
liaison
and
this
person
would
work
in
a
sick,
so
they'd
be
embedded
in
a
sig
there's
not
like
a
secondary
release,
team
or
anything,
really
brand
new.
A
Just
think
of
this
as
a
very
communicative
member
of
the
sake
ideally,
and
they
would
be
the
contact
for
the
release
team
from
netsig
for
the
release
cycle.
So
they
would
be
coordinating
communicating,
responding
to
requests
going
back
to
their
homesig
and
giving
updates
working
with
their
sig
chairs
and
leads
to
get
the
information
about
what
cups
will
go
into
the
cycle
and
make
sure
everybody's
aware
of
what's
going
on
and
reduce
some
of
the
back
and
forth
and
the
cat
hurting.
A
And
then
the
swirl
was
also
identified
as
helpful
on
the
clown
side
as
well.
So
xander
had
mentioned
this,
so
we
could
expand
it,
but
it's
just
it's
right.
Now,
it's
a
pilot,
it's
an
official.
We
want
to
try
it
out,
but
we
have
a
few
volunteers
that
have
expressed
interest
and
some
sigs
that
have
also
met
them
online.
To
say:
hey,
let's,
you
know,
let's
try
this
out.
E
So
you're
right,
it
wasn't
fully
aware
I'd
have
vaguely
heard
of
it,
but
not
in
a
angry
deal.
So
thanks
for
that
is
the
intent
that
this
would
be
in
place
for
122's
enhancement
cycle
or.
A
F
So
I
guess
I'm
wondering
how
do
these
liaisons
really
fit
in
for
the
enhancements
part
of
the
release,
because
I
could
see
how
they
would
probably
make
sense
like
in
especially
coms
and
docs
things,
because
that's
where
things
get
like
pretty
stuck
like
consistently
but
for
the
enhancements
process.
I
guess
I'm
wondering
like
what
this,
what
this
role
actually.
A
A
Yeah,
so
what
I'm
saying
is
that
this
component
of
interacting
with
the
release
team-
because
it's
now
already
opt-in,
may
maybe
much
less
than
in
the
past
so
but
it's
still
good
to
have
somebody
who
can
speak
to
what's
going
on
with
basic
status.
Here's
what's
happening
and
then
communicate
with
other
members
of
the
release
team.
If
need
be.
E
So
from
from
my
kind
of
experience
in
121
on
enhancements,
there's
been
a
couple
of
occasions
where
we
were
trying
to
get
information
about
a
particular
enhancement
and
the
like
enhancements.
Author
was
relatively.
You
know
they
were
busy
but
ultimately
were
non-responsive
to
us
in
some
way,
and
that
might
not
be
anything
that
thought
of
her
own.
Having
someone
in
particular,
I
guess
to
go
like
poke
from
the
owning
sig.
I
can
see
that
being
quite
useful
and
I
I.
A
A
Yeah,
so
I
mean
we
can
define
this
based
on.
However,
we
want,
but
I
think
enhancements
is
a
good
broad
topic,
because
it's
what's
the
focus
of
the
releases
and
there
are
more
needs
than
just
communicating
with
the
enhancements
teams
alone,
but
that
person
can
still
serve
as
a
point
of
contact.
It
might
just
be
less
taxing
than
it
was
in
the
past
because
because
things
have
changed.
A
It's
a
it's
a
new
process
and
we
we
might
want
to.
We
might
find
things
out
right
that
we'll
still
need
this
contact
person.
For
so
I
would.
I
would
define
some
areas
for
this
role
on
the
cons.
Doc's
other
side
related
to
the
cups
be
on
watch
for
how
the
new
process
rolls
out
in
its
next
iteration,
and
then,
if
we
see
that
this
person
needs
to
be
more
involved,
you
can
take
an
action.
F
Sense,
carson,
I
think
I
I
think
I
would
have
to
see
what
the
responsibilities
are
like
it.
This
kind
of
feels
like
more
of
a
sig
release
thing
than
a
straight-up
enhancement,
subproject
thing,
but
it's
I
guess
I
I
would
just
say
that
I
would
be
worried
about
adding
a
lot
of
process.
I
can't
like
fully
envision
what
what
this
ends
up
being.
A
F
Think
that
this
sigs,
a
lot
of
them
are
very
wary
of
like
extra
process.
So
if
this
is
a
person
who
really
wants
to
be
a
part
of
the
fig
is
maybe
somebody
because
I
I
actually
think
of
people
who,
like
instincts,
that
I've
seen
they've,
contributed
a
couple
pr's
but
they're,
not
necessarily
in
this
egg,
like
they?
Don't
they
don't
feel
like
they're,
a
part
of
this
egg,
but
they'd
like
to
get
a
foothold
in
it
like
something
like
this
could
really,
I
think,
help
them
move.
B
F
Being
a
part
of
a
sig
being
a
like,
even
like
getting
enough
buy-in
from
other
members
where
they
could
eventually
be
a
reviewer
or
an
approver,
because
they've
clearly
demonstrated
that
they're
like
active.
F
But
I
think
that
that
could
be
a
cool
opportunity.
If
it's
just
people
who
have
never
ever
contributed
to
the
sig,
I
think
it
can
get
potentially
a
little
more
iffy
because
they
don't
necessarily
understand
like
what's
going
on,
but
we
do
have
a
problem
with
like
sigs:
don't
have
enough
reviewers,
they
don't
have
enough
active
non-chairs.
A
F
A
So
yeah,
so
I
would.
I
would
recommend
that
we
take
this
offline
for
yeah.
A
Because
I
yeah,
I
do
think
that
this
is
more
like
outside
of
the
I
wanted
to
just
mention
it
because
it's
enhancements
related,
but
I
I
face
that
wariness
every
day
as
a
program
manager.
So
I'm
fully
aware
of
the
wariness
of
process-
and
I
hear
all
of
your
points
about
onboarding
new
contributors
as
code
contributors
moving
up
the
ladder
and
getting
a
foothold
in
the
project
this
way.
So
all
of
that
is
in
mind
right,
so
we
will.
We
can
define
a
role
that
keeps
all
of
those
concerns
front
and
center.
A
A
A
So
this
was
the
last
input
on
the
thread
and
it
was
a
week
ago.
So
I'm
also
wondering
what's
what's.
A
I
guess
if
someone
wants
to
ping
nabarron
and
jeremy
right
now
to
ask
we,
can
I
will
cool.
C
F
Because
I
like,
I
think
that
we
both
feel
like
it's
kind
of
unclear,
of
the
timing
of
the
of
the
rollout
for
the
receipts
process.
F
Like
I
remember
a
release
ago,
we
were
talking
about
122,
but
I
I
think
that's
clearly
not
going
to
happen,
and
I
think
that
there's
a
lot
of,
I
guess
my
main
concern
is
that
it's
another
process
change
and
I
think
that
as
people
know,
that's
really
hard
on
authors
and
stakes
to
understand
what's
happening,
but
also
we're
in
the
middle
of
helping
cigs
get
more
ownership
of
their
like
of
their
caps
just
in
a
general
way.
F
So
I
was
like
worried
that
we
were
going
to
try
to
roll
out
some
new
process
when
they're
just
trying
to
get
their
their
like
feet,
like
you
know
like
try
to
get
their
footing
right
now,
but
then
I
also
had
concerns
that
the
cap
doesn't
merge.
There's
like
a
lot
of
questions
on
the
cap
ctl,
and
I
really
wanted
to.
F
I
guess-
say
that
we
would
need
a
rollout
plan
for
it,
like
the
more
I
think
about
it.
The
more
I'm
like
there
needs
to
be
like
a
pilot
program,
or
some
testing
like
have
some
authors
volunteer
to
use
it
and
then
get
feedback
on
that
because,
like
this
is
our
this
is
this,
is,
I
guess,
enhancement,
sub
project
idea
of
what's
going
to
work
best,
but
we
also
need
that
feedback
to
see
like.
Does
this
really
make
sense
for
people
like?
Are
there
issues
with
this
tool?
F
Like
does
anything
need
to
be
changed
and
then
probably
some
iteration
on
that
before
it's
something
that
we
actually
tell
people
you
have
to
use,
because
if
it
doesn't,
I
guess
if
it
doesn't
work
or
if
people
find
it
very
hard,
I
it
could
really
affect
the
release.
You
know
like
so,
and
I
think
that
there
also
needs
to
be
like
training.
If,
like
say
you
pilot
it
and
it
works
really.
Well,
you
still
have
to
communicate
that
there's
a
new
process.
F
Do
some
training,
have
some
material
and
like
have
probably
like
a
phased
rollout
of
it,
where
it's
like,
not
required,
but
you
can
use
it
and
then
you
know
eventually
be
required.
So
I
did
really
see
that
in
the
kept-
and
I
just
kind
of
wanted
to
get
that
like
those
thoughts
on
the
record,
because
I
think
that
it's
like
we
have
to
be
extremely
sensitive
to
the
people
that
are
affected
by
it
and
and
make
sure
that
it
actually
works
for
them.
A
Yeah,
that's
all
excellent
points,
so
I
can
volunteer
for
this
because
I
think
it's
really
important
for
a
variety
of
reasons.
How
about
how
about
others
here
like
do
you
want
to
actually
play
a
role
in
this
rollout
plan?
A
F
Like
like,
I
I
yeah
I,
I
definitely
would
like
to
see
that
I
think
that
that
probably
should
be
included
in
the
cap.
I
think
the
the
rollout
plan,
because
that's
something
that
we
require
of
all
caps,
is
like
alpha
beta
ga,
and
I
think
we
could
totally
brainstorm
for
that
and
potentially
just
take
it
over
to
the
cap
as
well.
A
A
A
A
E
Christian,
do
you
see
us
like?
Do
you
see
like
none
of
this
making
into
22,
or
do
you
see
like
a
part
of
this
personally.
F
Personally,
what
I
would
do
is
spend
122
like
assuming
that
the
tool
is
finished,
which
I'm
not
sure
if
it's
finished.
I
would
like
to
see
some
like,
inter
internal
review
and
testing
of
it
and
then
potentially
some
just
like
very
light
testing
from
authors
and
then
potentially
for
me
in
123,
you
could
have
a
non-mandatory,
offering
and.
B
F
F
A
tool
use
it
like
it's,
it's
yeah,
you
know
like.
I
think
that
we
should
really
focus
on
getting
it
right,
not
doing
it
fast
like
because
if
you
roll
it
out
too
quick,
if
you
roll
things
out
too
quickly
or
add
too
much
process,
people
reject
it,
rightly
right
because
their
life
is
made
harder.
So
I
think
that
we
really
have
to
like
verify
that
this
works
well
like.
I
would
also
love
to
see
some
of
the
people
who've
been
involved
in
enhancements
before
trying.
A
F
And
saying
and
like
giving
some
feedback
on
the
actual
tool,
which
I
don't
think
that
we've
really
done
and
then
like
kind
of
collecting
that
and
then
probably
iterating
a
little
bit
and
then
trying
to
figure
out
like
how
can
this
be
broken
up
for
a
roll
out
like
is?
Is
it
being
constructed
so
that
everybody
has
to
use
it
all
at
once
or
is
there
like
is?
F
To
actually
like
really
understand
what
this
is
along
with,
I
would
say,
like
we
are
going
to
need
docs
we're
going
to
need
nice
stocks,
we're
going
to
need,
like
probably
like
a
webinar,
we're
going
to
need
a
lot
of
stuff
to
make
it
as
easy
as
possible
for
people
to
see
the
value
of
the
tool
after
we
already
let
people
try
it
and
get
feedback.
F
A
Is
quite
heavy,
you
don't
want
to
push
people
further
away
yeah,
so
I
think
you've
basically
articulated
a
very
detailed
argument.
F
A
E
So
one
thing
that
comes
to
mind
is
when
so
during
121,
because
because
we
had
this
new
process
around
opt-in
and
we
had
some
feedback
during
the
cycle,
I
think
there
was
a
particular
incident
from
let's
say
incident
particular
instance
from
from
tim
hawkin
talking
about
you
know
how
they
felt
it
was
quite
there's
quite
a
lot
to
make
sure
they
got
right
so
to
speak,
and
I
think
one
of
the
things
again
if
memory
serves-
or
we
said
at
the
time-
is
that
you
know
well,
you
know
a
lot
of
this
will
be
addressed
with
receipts.
E
E
E
E
F
D
F
D
F
That
ship
kind
of
sailed
like
with
with
this
with
the
existing
status
of
it
like,
but
I
also
think
that
we
can
say
it
should
be
122,
but
I
think,
as
we
think
about
how
does
this
look
being
rolled
out
to
users
and
what's
going
to
be
disruptive
and
what?
How
can
we
deliver
the
best
tool
possible?
That's
going
to
actually
give
value
when
there's
a
lot
of
churn
and
process
already.
F
I
think
that
that's
more
important
and
I
don't
think
that
anybody's
going
to
be
disappointed
that
we're
not
giving
them
something
brand
new
to
use
in
the
next
like
few
weeks.
I
think
that.
F
B
Something
new,
but
I
think
I
don't
think
that's
what
james
is
saying.
I
think
it's
just
saying
that
we
need
to
communicate
more
that
if
we
did
give
an
impression
that
the
receive
process
was
going
to
roll
out
in
1.22,
like
that's,
not
gonna
happen,
and
I
don't
exactly
know
whether
we
specified
1.22
like
I
am
kind
of
in
agreement
with
kirsten
there.
B
I
think
we
carefully
made
sure
that
we
never
promised
anything,
but
I
think
the
point
is
to
just
make
sure
that
people
are
aware
if
we're
we're,
if
we're
not
planning
on
rolling
it
out
that
people
are
aware
of
that
is,
I
think,
what
we're
trying
to
say.
F
Yeah
I
I
would
just
worry
that
that
communication
will
actually
be
a
little
more
confusing,
because
I
don't
know
that
anybody
had
the
impression
that
it
was
going
to
be
122..
I
feel
like
we
always
kind
of
punted
and
said
this
will
be.
This
would
be
covered
by
the
new
receipts
process
in
the
future,
and
I
kind
of
feel
like
we
can't
like
if
you
want
to.
F
If
we
want
to
mention
this
receipts
publicly
to
everybody,
then
they
kept
and
everything
else
should
be
open
for
discussion,
since
it's
not
merged
and
it's
still
there
and
you
might
get
a
lot
of
discussion
and
feedback
at
a
time
that
you
don't
necessarily
want
it.
So
it's.
I
guess
I'm
not
good
at
thinking
about
this,
but,
like
maybe
somebody
like
laurie,
can
think
about
this,
because
she's
probably
better
than
this
but
like
if
we
communicate
something-
and
we
really
don't-
have
good
answers
for
any
of
it,
then
that's
also
like
potentially
problematic.
F
A
F
F
Try
to
put
together
those
like,
I
guess,
questions
that
I
have
like
in
a
more
cohesive
way
and
then
either
bring
them
to
the
cap
or
bring
them
to
the
channel
and
eventually
to
the
cap
and
try
to
get
that
like
more
or
less
memorialized.
Because
I
think
that
that's
that'll
be
important.
If
we
actually
try
to
have
more
detailed
conversations
about.
D
A
A
Cool,
I
would-
and
I
would
try
to
do
it
soon
like
if
you
need
support
here.
This
is
a
top
priority,
because
you
want
to
buy
time
right.
You
want
to
know
exactly
as
early
as
you
can.
B
A
A
Oh,
it's:
okay,
we're
just
gonna,
say
put
together
a
plan
based
on
these
notes.
Do
it
asap
to
buy
time
to
get
ahead
of
the
steps
and
needs
yeah?
A
E
E
A
Now
go
ahead,
he
was
oh,
he
was
one
of
the
users
for
the
whole
process
that
we
brought
into
the
conversation,
so
he
and
alana
hoshman,
who
also
had
expressed
that
folks
were
finding
the
process
unwieldy.
We
want
to.
We
want
to
think
of
them
as
users
for
the
process.
That
was
the
discussion
that
we
had
about
it.
A
A
All
right,
let's
jump
down
to
kristen's
item,
just
because
it's
also
timely.
F
Oh
yeah,
I
was
just
thinking
that,
since
we're
making
changes
and
changes
are
extremely
difficult,
I'd
like
to
sort
of
try
to
get
feedback
on
the
changes
to
the
enhancement
process
that
we
have
and
maybe
a
little
bit
just
a
little
bit
more
formally,
because
I
feel
like.
A
F
Know
like
we're,
designing
tools
and
we're
thinking
about
how
to
make
things
better,
and
I
think
that
we
try
to
empathize
a
lot
with
the
authors
and
sigs,
but
I
also
think
that
we
might
want
to
think
about,
like
talking
to
sig,
leads
to
get
a
little
bit
more
feedback
on
the
process
for
enhancements
and
not
not
on
the
release
side.
F
Really
because,
like
that's
more
release
team,
but
just
like
their
thoughts
and
kind
of
make
that
a
a
regular
thing
for
the
release
cycle
to
make
sure
to
like
check
in
and
see,
what's
working,
see,
what's
not
working
see.
What
like?
Is
there
a
problem
with
the
enhancements
like
do
they
have
concerns
about?
F
It
are
some
of
their
use
cases
not
covered
whatever
it
is,
but
just
to
make
that
a
more
regular
thing,
because,
as
things
change,
we
kind
of
have
to
make
sure
that
we're
all
talking
about
the
theme
thing
you
know
like
like
not
like.
Oh,
I
remember
a
1.15
when
it
was
like
this.
It's
like
okay,
but
that
that
was
a
long
time
ago,
like,
let's
all
like
sort
of
have
like
a
shared
foundation
of
the
current
process
and
the
current
sort
of
you
know
vibes
surrounding
it.
A
A
Yeah,
no,
I
I
get
the
point.
I
just
want
to
clarify
the
real
basic
information.
So
like
your
users,
because
this
sounds
like
you
could
tee
this
up
as
part
of
the
conversation
that
we
just
had
about
the
process
changes,
you
can
yeah
use
this
as
an
opportunity
to
fact
find
and
get
some
feedback
already.
Yeah
yeah.
Oh
that's
so
this
is
yeah
like.
F
I
think
I'm
gonna,
I
just
thought
of
this
like
before
I
went
to
bed
last
night,
so
I'm
like
still
trying
to
get
my
head
around
it,
but
I
think
I'm
gonna
probably
just
get
like
a
google
doc
going
like
in
the
next
day
and
just
kind
of
maybe
pass
around
to
the
other,
like
people
in
a
meeting
and
just
sort
of
get
some
ideas
down
and
then
try
to
maybe
potentially
reach
out
to
the
sig
leads
and
send
some
have
something
to
send
to
the
sig
leads.
F
A
F
A
F
D
A
Okay,
is
there
anything
more
we
want
to
talk
about
there?
Are
there
questions
about
the
retro.
B
F
B
B
F
A
Okay,
so
we
don't.
I
have
six
minutes
left
and
a
few
more
topics,
so
I'm
gonna
try
to
go
through
some
of
these
quickly,
so
the
enhancements
process
recapped
miro
board,
and
we
were
having
a
pretty
lively
discussion
about
the
release
impacting
on
impacting.
So
we
still
need
to
do
work
on
that
right.
There's
a
lot
of
other
parts
of
the
process
that
we
haven't
gotten
to.
A
But
what
would
be
our
next
week
goal
or
like
by
the
next
meeting?
Do
we
have
a
goal
outcome
we
would
like
to
achieve
with
that
diagram
and
what
it
says
to
us
right.
It's
just
describing
our
process.
What
question
would
we
like
to
solve
as
our
next
step?
F
I
kind
of
I
was
thinking
about
that.
One
question:
that's
right
there,
the
sort
of
like
I
want
you
to
track
it,
but
I
want
it
to
be
as
lightweight
as
possible
and
I
kind
of
feel
like
it's
almost
like
a
deep
white
like
can
also
almost
be
deprioritized
because
it's
like
well,
you
know.
F
If
you
want
to
be
a
part
of
the
release,
you
can
just
participate
in
the
entire
release
process
right
like
that's
the
default,
and
then
that,
like
this
lightweight
option,
is
sort
of
an
optimization
where,
if
I
guess
we
don't
feel
like,
if
we
feel
like
we
have
other
things
that
we
have
to
focus
on,
then
I
think
that
the
optimization
can
potentially
be
left
for
a
later
date.
A
B
So
I
don't
think
so
I
don't
think
we
actually
answer
the
question
not
of
my
cup
is
really
impacting,
but
I
want
a
lightweight
process
right
like
what
is
that
lightweight
process,
and
I
don't
think
we
have
decided
that
so
like
that's,
why
we
were
defining.
Oh.
Is
that
an
api
change?
Is
it
a
bug
or
whatever?
B
And
I
think
when
elena
joined
our
meeting
like
two
weeks
or
three
or
some
time
ago,
I
think
that's
what
one
of
the
things
that
she
brought
up
as
the
end
user
is
like.
Oh,
I
have
this
bug
and
I
had
to
like
make
a
change
to
cab.
Just
to
get
this
bug
in
or
something
you
know
and
like
is
there
a
light
lighter
weight
process
for
her
to
you
know,
go
through
the
release
process.
B
A
That
was
kind
of
the
starting
question,
like
the
whole
goal
is
to
make
the
whole
outcome
of
the
entire
exercises
make
the
entire
process
like
as
lightweight
as
possible.
So
if
we've
solved
that
core
question
up
front,
I
think
what
you're
saying
is
like
okay,
what
happens
next
right
yeah
for
okay?
If
it's
not
release
impacting?
What
do
we
do
with
these
folks?
How
do
we
make
sure,
but
first.
F
F
B
A
So
yeah,
why
don't
we
do
that?
First,
total
makes
total
sense,
yeah
dude
fancy.
So
if
we
define
that
by
the
next
meeting,
that's
pretty
good,
you
know
we'll
have
a
good
idea
for
what
that
could
look
like
does.
B
A
F
Actionable,
I
think
it's
reasonable.
I
think
that
focusing
on
all
of
the
potential
release
impacting
use
cases
is
probably
the
priority,
especially
as
we
go
into
the
next
release
and
to
have
that
defined
so
that
we
can
either
say
hey
like
these
things,
don't
require
an
enhancement
or
they
require
this
lighter
weight
thing
is
going
to
be
taking
a
lot
of
burden
off
of
people
and
they're
probably
going
to
be
really
happy
and
relieved.
So
I
think,
defining
that
up
front
is
going
to
be
probably
the
biggest
payoff.
F
Focusing
on
those
flows
in
the
chart
and
making
sure
that
we
kind
of
understand
the.
A
A
A
Yep,
okay,
so
we're
out
over
time
now
I
just
want
to
ask
if
james
is
willing
to
work
on
this
with
us
if
you're
willing
to
join
this
discussion.
E
Looking
for
the
mirror
board,
but
I
guess
I
will
read
through
that,
so
this
is
a
proposal
for
how
it's
going
to
look.
Is
that
correct,
yeah.
A
A
Cool,
I
mean
we're,
basically
brainstorming
the
approach,
and
then
you
saw
some
of
the
slack
threads
like
kicking
around
ideas
back
and
forth.
I've
been
facilitating,
sometimes
late
on
friday
nights,
and
then
we
come
with
a
decision
around
one
o'clock
a.m
so
or
one
a.m.
O'clock.
E
F
Like
don't
feel
like
we're
like
pushing
you
into
something
like
as
an
enhancement
lead,
I
think
that
you're
gonna
also
have
a
lot
of
ideas
and
feedback
and
you're
a
shadow,
so
you
also
hopefully
can
share
some
of
your
feelings
about
like
what
you
saw
in
these
sort
of
buckets
of
of
caps
that
may
or
may
not
have
needed
the
entire
process.
It
very
well
may
be
like
hey
like
these
should
stay
in
the
process
for
these
reasons
and
it
kind
of
sucks,
but
maybe
we
can
make
the
process
easier.
A
A
Brainstorm
activity
offline,
but
I
would
really
like
us
to
get
going
on
this
in
the
next
meeting,
because
I
have
a,
I
think
we
can
do
it,
we'll
get
a
lot
done
in
five
minutes
if
we
just
work
asynchronously.