►
From YouTube: 20200901 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
B
A
So
I
have
some
updates.
I
I
did
submit
a
couple
pr's
which
got
merged.
It
looked
like
one
of
them.
Although
I
had
questions,
I
wasn't
sure
if
we
should
merge
it,
the
the
oh
no
one
of
them
needs.
I
think
one
of
them
still
has
a
conflict.
I
need
a
result.
I
don't
remember
if
I
fixed
it
or
not,
but
anyway
I
just
added
pr
approver
as
something
we
can
filter
out
in
the
query,
and
I
added
the
ability
to
search
across
multiple
cigs.
A
So
in
order
to
do
that,
latter
one
I
had
to
pull
the
six
the
validation
module
in
which
has
load
six
from
the
net
from
the
net.
So
that
means
that
you
can
no
longer
run
it
at
all
unless
because
it's
done
in
the
init,
unless
you
have
internet
connectivity,
so
that
was
the
one
I
wasn't
sure
if
we
should
merge,
I
guess
if
people
have
any
thoughts
on
that,
we
can
fix
that
did.
Did
we.
C
Would
you
mind
actually
popping
open
the
the
repo
and
we
can
go
through
some
things
that
are
tagged
yeah?
I
thought
it
was
still
outstanding.
C
You
mind
linking
that.
G
H
A
C
What
is
it
for,
it
would
be,
is
closed.
Is
closed
authority
is
the
first.
B
E
I
I
would
probably
I
would
not
pull
it
out
and
I'd
work
local,
because
if
a
sig
you
know
retires
or
is
you
know
archived,
there
are
still
things
that
could
potentially
be
in
there.
C
So
so
I
think
that
we
need
a
map
of
current
sigs
right
if
we
just
have
a
listing
of
what
the
current
cigs
are,
that
kind
of
solves
the
problem
right
assuming
that
you're
building
locally,
assuming
that
your
local
is
up
to
date,
then
it
should
not
be
an
issue
right.
A
E
No,
when,
when
a
sig
or
working
whoever
is
removed,
their
entries
are
removed
from
there
and
all
their
stuff
is
moved
to
the
archive
directory.
C
A
Okay,
I
mean
we,
don't
do
it
that
often
so
it's
just
like
this
means
another
place.
We
have
to
keep
something
up
to
date,
that's
all,
but
whatever
it's
not
that
big
of
a
deal.
C
Yeah,
I
think
until
we
solve
like
sinking
owners
or
sinking
sigs
across
across,
like
the
project
or
across
orgs,
we'll
continue
running
into
kind
of
yeah
duplicated
data,
but
but
yeah
it's
it's
updated
infrequently
enough
that
I
don't
think
we
need
to
care
too
much
about
that.
Yeah.
I
Yeah,
okay,
that's
fine,
then.
So
we.
A
C
So
question
for
you,
john:
have
you
seen
people
using
this.
A
So
in
the
pr
group
so
which
is
right
now,
just
me
and
david
eve
and
voice,
we
have
this
issue
of
trying
to
figure
out
whether
we
need
to
do
you
know
whether
we
have
reviews
open
for
pr
approval,
and
so
this
was
we
have
this
in
the
cap,
dot
yaml,
and
this
was
a
way
to
be
able
to
figure
out
whether
we
have
that
or
not
you
know
in
other.
A
A
C
We
and
then
we,
you
know,
tighten
it
up
later.
So
I
think
that's
that's
fine.
I
I
think
what
I
would
want
to
see
is
the
let's
lay
out
what
the
road
map
looks
like
overall,
because
again
going
back
to,
like
the
I
think,
those
mentioned
in
the
july
7th
meeting.
While
I
was
kind
of
like
just
postulating
about
all
the
possibilities,
it's
people
process
tools
right.
So
I
think
we
need
to
make
sure
that
the
process
that
we
we
want,
like
the
tool,
serves
the
process
that
we
want
right.
C
So
we
have
some.
You
know.
Keps
are
considered
to
be
in
quote-unquote
beta
right
now
and
we
should
look
at
you
know.
What
does
our
you
know?
V2
beta
1
look
like,
or
what
does
our
moving
to
ga
for
caps
mean
right.
C
So
one
of
the
things
that
I
mentioned
was
the
receipts
process
right
and
I
don't
know
if
we
have
time
for
it
this
cycle,
but
it's
something
that
we
could
try
for
the
idea
being
that
people
would
submit
receipts
about
the
their
intentions
for
the
cycle
right,
so
that
becomes
a
way
of
helping
the
sub-team
for
the
release
team
kind
of
divest
of
having
to
do
the
cat
herding,
which
is
a
big
portion
of
their
their
day-to-day
having
to
figure
out
what
statuses
certain
things
are
in.
C
If
a
sig
has
committed
to
the
work,
then
it
is
in
the
form
of
a
receipt
right.
It
could
be
in
the
form
of
a
receipt,
and
that
way
we
can
apply
automation
to
that
right.
We
have.
We
have
something,
come
in
scrape
the
receipts
and
say
hey.
This
is
what
is
planned
for
the
cycle
right
and
it's
it's
no
is
it
in.
Is
it
out?
We
have
to
update
the
spreadsheet.
C
This
is
at
risk
right,
there's,
there's
quite
a
bit
of
back
and
forth,
and-
and
I
think
that
you
know
we
have
a
bunch
of
you
know,
including
myself.
Former
enhancement
leads
on
the
call
where
I
would
say
that's
one
of
the
hardest
things
to
do
just
keep
track
of
where
something's
at
across.
C
Of
of
issues,
while
you
know,
while
also
being
kind
to
the
fact
that
people
are,
are
trying
to
execute
on
the
enhancement
delivery
as
well
as
keep
us
surprised.
So
if
we
can
remove
that
barrier,
I
think
that
that
would
be
a
huge
step
even.
E
E
G
Yeah,
I
mean,
I
think,
where
we're
going
with
this
is
that
we
don't
really
have
a
roadmap
yet,
and
so
we
don't
really
know
what
the
120
delivery
goals
would
be
for
this.
So
before
we
would
project
you
know,
majorly
ambitious
parts
of
this
project.
We
we'd
want
to
know
what
what
we
could
actually
do.
So
I
don't
think
there's
any
pressure
in
delivering
any
specific
aspect
of
it.
C
And
over
and
over
all,
I
I
find
this
is
potentially
like
it's
a
smaller
change
in
process
that
I
think,
has
a
huge
net
benefit.
I
don't
think
it
would
be
hard
to
implement,
but,
given
that
we're
in
between
the
cycle
boundaries,
I
would
have
wanted
to
give
more
notice
before
trying
to
yeah.
G
G
So
we
have
a
bunch
of
user
feedback.
You
know
the
user
group
I'm
talking
about
meaning
the
enhancements
sub
team
from
119.
So
when
we
were
doing
those
prioritization
breakouts
and
if
you
weren't,
you
know
we
did
about
five
or
six
prioritization
breakouts
with
all
members
of
the
team
on
on
the
backlog
of
items
for
the
release
team
and
what
was
highest
importance
and
lowest
importance.
G
There
was
a
lot
of
interest
in
this
tool,
but
there
was
also
a
lot
of
ambiguity
around
how
people
they
had
heard
of
a
tool,
but
they
weren't
sure
what
the
tool
was
or
if
it
existed
already,
what
the
tools,
ultimate
goals
or
span
of
goals
might
be
in
terms
of
helping
that
process
along.
So
the
fortunate
thing
is,
I
think
there
is
a
very
clearly
fairly
clear
vision
for
this.
G
I
G
So
I
think
yeah
I
mean
we
had
617,
and
so
that
was,
I
think,
the
initial
kickoff
umbrella
like
we
want
to
have
some
sort
of
tooling
and
there
are
six
sub
themes
or
goals
within
that.
And
so
I
think
what
we
wanted-
and
we
talked
about
doing,
was
just
like
taking
a
look
at
that
again
and
what's
already
been
written
and
then
just
updating
it
and
then
so
you
already
have
work
done
and
we
just
need
to
refresh
it.
And
what
are
the.
C
G
C
Yeah,
so
I
that's
yeah
lori
took
the
words
out
of
my
mouth,
the.
What
john
is
looking
for
is
a
meta-cap
about
caps
and
617.
Is
that
that's
exactly
why
that's
exactly
why
we
wrote
it
up,
so
I
think
it
sounds
like
the
work
for
120
is
to
refresh
617,
primarily
the
to
to
go
to
the
tool.
The
tool
is
not
useful
to
end
users
to
paris,
comments
and
zoom.
The
tool
is
not
useful
to
end
users.
What
would
be
useful
to
end
users?
C
Is
this
receipt
system
having
because
if
the
receipts
in
the
same
way
that
we
do
release
notes
and
release
notes
has
relnotes.kates.io
having
those
receipts
would
allow
us
to
have
metadata
about
what
is
in
the
current
cycle
or
what's
in
an
upcoming
cycle,
and
and
it's
the
same
with
the
part
of
the
reason
that
we
added
new
fields
and
the
structs
for
for
the
the
kept
metadata
right.
So
the
proposed
the
milestone.
All
of
that
information.
A
C
G
I
mean
you
have
different
users
here
right
and
so
it's
sort
of
like
who
are
the
users
that
we
need
to
satisfy.
First,
I
mean
you
want
to
satisfy
all
of
them
right,
but
finishing
part
of
the
job,
for
a
specific
set
of
users.
To
then
be
able
to
help
those
other
users
would
be
a
good
idea.
So
getting
the
part
for
the
release
team,
I
think
really
solid
and
getting
that
team
to
be
able
to
use
this
tool
and
then
making
sure
that
the
other
types
of
users
will
benefit.
G
You
know
that
they're
not
like
siloed,
that
the
goals
aren't
siloed
but
are
building
like
like
a
story
in
a
book.
You
know
you
have
chapters
you
finish
first
chapter,
then
you
move
to
the
second.
C
G
C
Yeah,
so
what's
important
to
me
is
especially,
as
you
know,
you
know,
all
of
the
sub-project
owners
have
multiple
hats
right
right.
So
you
know
bob
has
focuses
and
contributor
experience
jeremy's
taking
on
120
as
the
release
team
lead.
John,
is
a
sick
architecture
lead.
I
had
mentioned
this
in
my
previous
meeting,
but
like
we
want
to
do
less
stuff
right,
so
so
being
able
to
activate
the.
C
C
So
I
would
love
to
be
able
to
shed
some
of
that
work,
toss
it
to
the
enhancement,
sub
team,
for
the
release
team
and
have
them
also
work
on
some
of
those
pro
proactive
activities,
as
opposed
to
you
know,
as
opposed
to
trying
to
serve
all
these
users
simultaneously
right,
we
build
a
bigger
squad
and
then
we
all
go
forth
for
the
the
end
users
and
and
the
other
people
looking
at
caps.
G
A
Well,
I
think
that
would
be
useful.
I
think,
though,
that
the
next
step
is
like
we
need
to
pick
somebody
on
this
call
to
sit
down
and
revamp
the
cap
and
write
down
revise
the
goals.
Take
the
things
from
the
doc
you
put
together,
lori
and
and
and
put
that
in,
you
know,
move
those
user
stories
into
the
cap,
and
then
you
know,
I
think,
maybe
simultaneously
we
can
have
that
conversation.
G
I
don't
actually
understand
what
this
does
yet
and
I've
looked
at
the
docs
and
I
don't
get
it
so.
I
will.
G
B
A
First
goal
eliminate
the
enhancement
sub
team
of
the
release
team,
eliminate
the
spreadsheet
right
then
allow.
A
Tooling,
to
do
everything
they
do
or
is
it
you
know,
address
discoverability
of
tabs
for
other
people
or
the
receipt
system
like
what
goals
are.
What
use
that
service.
G
G
Yeah,
so
I
know
that
you
want
to
get
rid
of
the
spreadsheet
but
like
in
terms
of
like
technically
what
this
thing
is
doing
right
now
are
capable
of
doing
right
now
and
then
how
it
does
it.
So
you
know
so
that
you
can
actually
build
on
this
tool
to
start
serving
paris's
needs
and
other
people's
needs
as
you
go
along.
So
that's
what
I
would
like
to
see
like.
How
does
this
thing
work?
G
That's
not
clear
to
me
right
now,
and
so,
if
we,
if
we
have
that
conversation
together
in
a
small
group
so
nabarro
and
you
jeremy,
we
can
figure
that
out
quite
quite
quickly.
I
think
it's
all
written
down,
it
just
needs
to
be
tweaked,
and
then
I
think
you
have
your
users
and
that
needs
to
be
kind
of
structured
in
a
flow
so
like
what
are
your
next
immediate
goals?
G
For
this
thing,
what
are
the
you
know
the
increments
of
value
and
then
and
then
we
have
to
figure
out
like
who
actually
does
the
work,
because
you
know
just
that-
maybe
that's
answered,
but
just
like.
How
can
we
even
have
other
people
help
out
because
it
seems
like
the
two
of
you
are
basically
doing
most
of
the
work?
Is
it
possible
to
get
contributors
to
support
that?
I
don't
know.
C
Right
so
the
the
contributors
that
would
be
in
the
best
place
to
help
out
with
that
are
people
who
have
been
on
the
enhancement
sub
team
are
currently
on
the
enhancement
sub
team.
So
the
when
you
say
this
thing
are
we
talking
about
the
tool?
Are
we
talking
about
caps?
Are
we
talking
about
enhancement,
subproject
overall.
C
Forget
the
tool
for
a
second
okay.
I
say
that
to
say
we're
right
now:
we
have
built
a
tool
for
a
very
specific
purpose
that
does
not
serve
as
many
people
as
we
would
want
like.
We
are
not
like.
I
don't
think
we're
going
to
get
to
the
place
where
we
build
the
tool
that
serves
everyone
right.
The
what
we
need
to
do
is
build
a
process
that
can
serve
everyone
right
and.
A
C
Some
of
the
skeleton
for
that
process
in
place
we've
been
running
with
it,
so
I
think
that
the
so
we
have
a
the
ability
to
get
a
reasonable
amount
of
feedback
from
people
about
this
process,
and
we
do
have
some
of
that
already.
There
is
an
issue
opened
that
says,
like
iterate
over
cap
feedback
or
something
right
that
I
opened
when
we
were
doing
the
second
iteration
of
like
the
medicap
right.
A
G
G
C
G
G
We
have
the
tool
itself
and
development,
and
then
we
have
the
process
and
we
want
to
revise
that
to
update
it,
but
everything
does
talk
to
each
other
in
the
end.
So
how
you
know
we
have
a
delivery
path
on
this
tool
itself
and
then
we
have
the
process.
So
do
you
want
the
two
to
run
in
parallel
to
have
the
tool
serve
the
optimizations
for
the
process.
C
I
don't
believe
the
optimizations
of
the
process
can
be
served
by
the
tool
immediately.
I
think
that
an
optimization
for
this
process-
and
this
is
why
I
go
back
to
the
release
team.
The
first
part
of
the
cycle
is
enhancements
collection
right,
so
removing
the
bottleneck
at
enhancements
collection
time
is.
A
G
C
So
so
well,
the
receipt
process
wasn't
necessarily
doesn't
necessarily
need
to
be
part
of
the
tool.
B
A
There-
and
I
just
don't
remember,
I
know
there
was
discussion
of
it.
I
don't
remember
if
it's
written
down,
but
we
have
a
document.
What
the
receipts
process
looks
like
and
then
we'll
see
is
the
tool
useful
or
is
it
simply
something
something
people
can
do
with
pr's
manually
for
now
or
or
if
we're
talking
about
121
anyway,
maybe
we
define
the
receipts
process
and
we
see
if
the
tool
is
useful
and
we
build
it
for
that,
but.
B
A
G
A
Yeah,
whether
it's
a
different
tool
or
it's
different
aspects
of
the
same
tool
like
there
may
be
things
like
like
this
little
pr
that
I
did
that's
just
particularly
useful
for
me,
it's
not
even
part
of
that
process.
It's
a
different
process
that
the
tool
is
serving
and
we
just
have
to
not
necessarily.
A
G
A
C
So
I
would,
I
would
expect
again
we
given
this
stage.
We
don't
want
to
introduce
any
any
weird
changes
for
the
enhancement
scene
moving
into
one.
So
I
would,
I
would
say,
to
dean,
hansen's
team
that
it's
business
as
usual
right.
Anything
that's
in
already
documented
in
the
enhancements
handbook
is
what
you
should
follow
this
tool,
this
tool
process
updates
all
that
stuff
will
come
in
in
a
parallel
track.
C
The
so
it
sounds
like
it
sounds
like.
I
need
to
define
the
receipts
process
and
I
would
request
who
is
the
lead
for.
C
G
Mean
a
lot
of
it
came
in
those
prioritization
sessions
and
kirsten
was
pretty
vocal
and
and
knows
about
the
enhancements
process
and
what
could
be
optimized,
and
I
have
the
item
actually
on
the
agenda
here.
These
recently
prioritize
items,
there's
a
there's,
a
bunch
of
information
there
and
then.
G
C
Yeah,
so
let's
go
into
that
next
before
we
do,
though,
paris
you're
chatting
a
bunch
on
the
chat,
but
it
is
not
recorded
paris.
Would
you
like
to
give
some
feedback
about
the
tool
expectations
as
an
end
user.
K
Hey
miss
y'all
yeah.
No.
I
actually
was
talking
to
him
recently
and
I
told
dims
that
it
would
be
so
cool
if
I
could
have
a
tool.
I
mean
I've
said
this
before
in
the
past,
but
it
would
be
so
cool
if
I
could
have
a
tool,
instead
of
digging
through
the
repo
to
find
out
every
like
every
single
cap
like
if
I
wanted
to
and
then
ultimately
query
things
like
its
status
and
other
details
and
then
that's
when
he
said.
Oh
well.
K
I
look
at
this
cool
kept
ctl
thing
this
little
screenshot
of
it
and
I
was
like
that's
it.
I
was
like
that's
it
if
I
could
get
that
on,
like
a
static
site
and
like
refresh
every
six
hours,
I've
I'm
like
yeah,.
C
K
Yeah
yeah,
like
ultimately
like
I
mean
ultimately
like
my
first
thought,
was:
oh,
let
me
go
to
dev
stats
and
I
was
like.
Let
me
I
was
like
yeah.
I
know
trust
me.
I
know
I
I
I
like
trust
me
of
all
people
here.
I
know
I
understand
what
you're
thinking,
but
not
as
an
I'm
at
an
end
user
and
end
users
were
like,
oh,
like
what
features
are
coming
up.
What
features
are
this?
What
features
are
that?
What's
this
and
it's
like?
K
Oh,
let
me
go
to
a
dev
stats
right.
Let
me
go
to
a
dev
stats.
That's
totally
note
my
quotes
and
like
let
me
query
the
repo
and
do
a
bunch
of
things
that,
like
I
could
figure
that
out
and
it's
like.
No,
we
don't
really
have
that
and
it's
like
yeah
well,
we
have
like
the
release.
Team,
has
the
spreadsheet
and
then
so,
like
obviously
keeping
my
own
spreadsheets
and
then
all
of
a
sudden,
it's
like
spreadsheets
and
yeah,
and
then
it's
like
just
so
much
work.
G
I
see
it
for
this
kind
of
work
in
this
process
and
or
the
tool,
and
then
maybe
you
know
the
tool
or
we
have
different
tools,
but
it
sounds
like
you
need
roughly
the
same
tool
as
like
checking.
C
A
C
C
This
website
is
going
to
be
super
useful
for
end
users,
or
maybe
someone
who
doesn't
need
to
care
about
caps
or
doesn't
want
to
care
about
caps
and
only
cares
about
like
what's
happening
this
cycle.
Why
is
it
happening?
Is
it
something
being
deprecated?
Is
it
something
that's
going
to
mean
that
I
have
to
upgrade
my
cluster
downgrade?
My
cluster
disappear.
My
clusters
right,
like
that's,
that's
the
question
that
an
end
user
wants
to
answer
right
now.
G
C
Just
yeah
I'm
just
saying
that
the
metadata
is
what
we
want
right
and,
and
that's
that
was
the
first
thing
that
we
we
went
after
so
I
think
we
have.
I
think
we
have
most
of
the
fields
that
we
want
to
massage
at
this
point
so
yeah
the.
C
However,
we,
however,
we
do
it
website
tool
both
the
website
as
an
end
goal
is
nice,
but
I
think
I
think
that
the
website,
as
a
sooner
goal,
is
easier
to
execute
on
easier
only
because
we
kind
of
have
a
framework
for
it
with
the
rel
notes,
type
bob
I
will.
I
will
reserve
more
speaking
for,
like
I
think
you
have
been
closer
to
rail
notes
than
I
have.
E
Yeah,
so
the
the
big
thing,
if
all
you
want
to
serve
up,
is
like
the
kept
name
linked
to
it
and
at
status
that
isn't
a
big
deal,
because
you
can
like
get
the
one
json
blob
where
I
think.
If
we
want
to
present
and
be
able
to
filter
out
more
information,
we
really
need
to
lock
down
the
schema
and
then
like.
E
This
is
sort
of
like
the
first
action
items
and
then
go
through
and
update
all
the
caps
like
convert
them
to
the
new
format
and
get
them
in
like
if,
if
we
can
achieve
that
under
like
1.20
like
that,
that
sets
things
up
for
you
know
many
better
things
down
the
line.
C
So
so,
this
is
something
that
I
see
as
a
task
that
we
could
totally
have
the
the
enhancement
sub
team,
help
out
with
right.
Yeah
the
yeah
pruning
pruning
the
data,
because
we've
done
some
of
it
right,
at
least
with
incoming
caps,
but.
E
Yep,
the
other
thing
like
it's
honestly,
it's
a
great
opportunity
for,
if
sigs
want
to
onboard
people
into
like
you,
know,
new
people.
This
is
a
great
task
to
start
with,
especially
if
they
want
to
get
a
little
bit
more
familiar
with
that
specific.
You
know
kept
or
thing
that
it's
touching,
if
we
want
to
like
try
and
have
them
like
updated
a
little
bit
more
too,
because
a
lot
of
the
the
caps
are
missing
sort
of
the
final
implementation
history.
E
C
A
A
A
C
Without
blocking
duplicate
job
running
in
a
strict
flag
or
something
right
that
spits
out
the
warnings,
as
opposed
to
spits
out
yeah
spits
out,
the
warnings
are
outright,
fails
right
with
bad
metadata
right
and
then
we
do
something
the
same.
As
you
know,
the
the
lints
that
we
skip
on
kubernetes
kubernetes
right,
yeah,
okay,
and
then
that
way
we
can
provide
a
list
to
whoever
is
going
to
be
working
on
this
and
they
can
knock
them.
G
Out
so
going
back
to
the
kep
revision,
I
would
say
we
could
do
that
in
an
hour
if
we
keep
it
to
the
high
level
goals
and
don't
get
into
details
like
you
can
get
into
details,
but
maybe
not
in
that
meeting,
because
otherwise
I
don't
think
we
would
finish,
but
if
we
can
gain
the
create
the
overall
vision
for
this,
I
think
it
would
just
take
an
hour.
G
Sure
so
here's
how
I
would
structure
this
like
we
have
an
existing
cut,
so
we
come
in
with
that
updated.
We
can
do
that
asynchronously
and
we
try
to
prepare
ourselves
as
much
as
we
can
beforehand
for
like
what
we
would
actually
like
this
process.
What
are
the
main
outcomes
we're
looking
for
with
this
process
now,
and
then
we
can
get
alignment
on
what
those
outcomes
might
be
and
talk
about.
C
G
And
then
maybe
we
have
the
owners
that
will
take
parts
of
those
take
some
of
those
outcomes,
because
you
know
they're
working
with
different
end
users
more
closely
or
they're.
You
know
in
the
enhancements
team
whatever,
but
we
we
would
have
that
achieved
in
that
in
that
hour-long
session,
and
then
we
would
also
have
a
way
to
message
the
outcome
to
the
stakeholders.
G
So
that's
a
couple
of
things.
The
messaging
part
is
easy.
Basically,
like
we
have
these
outcomes,
we
all
signed
off
on
them.
Here's
what
we
do
now,
but
it's
just
getting
alignment
on
the
outcomes
and
how
we
want
to
achieve
them.
C
Okay,
yeah,
that's
that's
fine.
We
can
do
that
for
the
next
meeting
when
we
can
think
about
it.
Until
then,
do
you
want
to
put
that
up
for
topics
for
the
next
one.
G
C
Yeah,
okay,.
C
I
just
have
back-to-back
meetings
today,
all
right
so
yeah,
I'm
gonna,
do
more
thinking
about
the
receipt
system,
because
this
is
carry
over
from
what
I
was
thinking
of
like
this
carryover
is
like
caleb's
baby.
So
there
are
some
thoughts
already
kind
of
strewn
across
the
repo.
I
guess
we
need
to
drag
them
together.
They're
a
bunch
of
issues
opened
around
617
as
well.
A
C
G
C
G
C
Cool
cool
should
we
get
into
the
the
prior
prioritized
items.
A
G
So
that
is
actually
relating
to
so
sig
note
has
taken
a
look
at
their
cups
and
yeah.
It's
a
request,
access
doc,
but
I
can
share
a
screenshot
if
you
can't
access
it,
but
they
ran
through
their
caps
and
they
just
basically
said.
Okay,
here's
what
we're
gonna
push!
Here's,
what
we
are
not
gonna
push
it's
kind
of
like
a
high-level
triaging
and
so
then
in
the
chairs
and
leads
channel,
I
posted
it
and
then
jordan,
liggett
and
others
bob
as
well,
weighed
in
and
said
hey.
A
G
A
sig
wants
to
push
forward
or
not,
and
it's.
G
Taking
the
temperature,
like
catching
up
with.
A
G
A
Oh,
I
I
was
just
gonna
say
this
might
feed
into
that
receipts
process.
Right,
like
I,
don't
know
the
receipts
process
in
detail,
but
I
wonder
it's
a
it's
a
way
to
signal
intent
right.
So
you
know
that
would
seem
to
be
a
similar
thing,
but
anyway.
C
So
so
yeah
what
I
am
a
little
hesitant
going
down
this
path.
I
think
that
there
are
a
lot
of
instances
where
it's
clear
that
a
sig
needs
to
do
triage
and
the
triage
ends
up
in
a
perfect
example
is:
is
the
bug
triage
sub
team
on
the
release
team
right
where
issue
npr
triage
is
happening
there,
sometimes
when
it
should
be
in
a
sig's
hands?
C
I
think
that's
caps
are
part
of
your
delivery
for
the
cycle,
as
well
as
the
you
know,
as
well
as
the
actual
code
process
content
as
a
result
of
of
those
caps.
So
I
think
that
should
fold
into
your
triage
process.
I
don't
believe
that
triage
is
something
that
we
should
appear
to
be
handling
for
people.
E
A
E
One
thing
that
had
like
I
have
personally
noticed
in
the
past:
oh
quite
a
few
sigs,
don't
necessarily
know
everything
that's
going
on
with
within
their
own
sort
of
like
enhancements
of
tracking
there's,
there's
potentially
too
many
people
in
milestone,
maintainers
to
sign
off
on
some
of
this
stuff,
and
so
it
sort
of
serves
as
just
as
a
good
way
to
keep
tabs
on
on
everything.
That's
going
on.
C
C
Yeah,
so
we
have
it's
it's
a
problem
of
too
few
and
too
many
simultaneously
right
for
having
multiple
milestones.
The
the
point
of
the
milestone
maintainers
group
is
to
maintain
the
milestone,
and,
and
primarily
we
mean
that
in
a
very,
very
github-centric
manner,
right
actually
being
able
to
apply
the
milestone
label
right.
But
what
goes
into
the
milestone?
C
We've
previously
had
a.
There
is
a
features,
I
think,
there's
a
features:
approvers
owners
list
within
eddie's
kubernetes.
There
was
a
features:
maintainers
github
team,
a
various
teams
that
were
kind
of
coalesced
around
the
idea
of
like
maintaining
your
caps
or
maintaining
your
things
for
the
milestone.
C
I
don't
think
that
I
believe
that
we
have
too
few
milestone
maintainers,
which
is
leading
to
instances
where-
and
we
had
talked
about
this
a
little
bit
on
the
the
release
engineering
meeting
just
now,
but
there
need
to
be
more
people
who
understand
what
it
means
to
be
a
milestone.
Maintainer
also
maintainers
do
not
need
to
be
just
chairs
and
technical
leads
for
cigs.
C
They
can
be
potentially
anyone
in
the
sig
who
knows
how
to
to
kind
of
get
a
pulse
on,
what's
happening
for
the
milestone
and
is
willing
to
take
on
that
duty
right.
I
think
you
know
in
the
opening
the
120
milestone
work
that
I've
been
doing.
C
I've
seen
prs
come
by
for
people
updating
their
milestone
maintainers,
but
it
was
primarily
to
update
stale
milestone
maintainers
for
the
chairs
and
technical
leads,
not
add
new
non-share
technical
lead,
milestone,
maintainers.
I
would
personally
like
to
see
more
of
that
the
because
that
goes
into
that
then
goes
into
issue
and
pr
triage
work
for
kubernetes
kubernetes.
If
they're
doing
less
of
that,
they
have
more
time
to
look
at
the
caps.
E
C
Yes,
paris,
that
would
be
a
good
idea,
so
the
idea
for
the
recording
is.
Can
we
have
this
topic
as
a
topic
for
the
next
chairs
meeting,
and
I
think
that's
super
important.
I
think
the
a
lot
of
the
chair
meetings
for
those
who
are
not
in
attendance
are
have
been
geared
around
triage
right,
how
people
are
doing
triage.
What's
what's
been,
what
has
and
hasn't
been
effective?
C
I
I
do
think
that
keps
land
right
in
that
bucket-
I
just
I
sorry
to
be
so
vehement
earlier
like
I
was.
I
just
want
to
be
very
clear
that
we're
not
taking
on
triage
for
anyone.
G
C
G
G
And
don't
worry,
a
hundred
percent
of
my
messages
have
been
like
we're
not
doing
that
like
this
is
your
work
so
because
it's
not
sustainable
otherwise,
and
it
won't
really
build
the
kind
of
ecosystem
that
we
need
to
have.
Where
everybody's
doing
this
kind
of
work
and
running
their
own
process,
just
to
clarify
is
the
idea
for
the
chairs
meeting
this
health
check
or
just
the
whole
topic
of
caps
being
with
the
health
check.
Being
you
know
a
tactical
tool
that
things
could
consider
using.
C
C
What
is
the
definition
today
right
like
having
that
conversation,
because
I
think
that
you
know
we
we're
going
to
have
that
discussion
as
well
in
the
next
sig
release
meeting
and
expand
contract
make
wide
more
widely
known
the
definition
of
milestone
maintainer
in
several
email.
I
think
it's,
it's
partially
an
outreach
thing,
but
it's
also
a
execution
post
outreach
right.
There
have
been
several
calls
to
update
your
milestone.
Maintainers
update
your
reviewers
and
approvers.
G
G
Your
feature.
Health
check
is
basically
your
big
ticket
triage
party
and
then
your
bugs
is
your
small
ticket
smaller
ticket
one,
but
there's
still
it's
not
intuitive
for
all
people,
so
I
think
helping
them
along
is
is
useful.
C
And-
and
I
think
that's
definitely
like
the
putting
on
the
hat
of
a
of
a
product
team
or
a
product
owner
right,
there's
a
different
investment
and
incentives.
C
If
you're
doing
this
internally
right,
the
the
goal
would
be
very
clear
right
that
you
would
be
expected
to
deliver
on
kind
of
road
map
items
or
even
understanding
what
the
road
map
is
overall
right.
So
I
I
think,
taking
some
of
that
corporate
focus
and
bringing
it
into
the
community
could
be
useful.
G
Map
and
let's
just
do
a
bunch
of
other
things,
it
happens
but
yeah
absolutely.
We
would
like
to
see.
I
mean
it's
about
helping
caps
cigs
rather
be
successful
and
feeling
productive
and
and
staying
connected
to
their
purpose.
Getting
stuff
done.
C
Yeah,
I
think
anything
that
we
can
do
to
remove
load
from
our
you
know
our
collective
chairs,
technical
aids,
sub-project
owners,
yada
yada,
is
going
to
be
useful
because
I,
I
think
that
one
of
the
underlying
problems
for
even
executing
on
some
of
the
stuff
is
not
the
it's,
not
the
lack
of
willingness
to
execute
on
it.
I
think
it's
the
time
right.
G
G
Well
right
and
what
I
like
about
the
signoid
health
check
is
that
they're,
basically
saying
like
here's,
a
bunch
of
things
that
we've
said
we
needed
to
do,
but
then
let's
dig
into
that
like
or
it's
a
template
for
having
that
kind
of
conversation,
and
you
know,
I
think
there
is
kind
of
this
expectation
that
we
put
on
ourselves
like
all
right.
You
know
this
issue
exists.
Now
these
things
exist.
C
Yeah-
and
I
think
you
know
dovetailing
I
don't
know
if
I,
since
I
can't
see
the
dock-
I
don't
know
how
it's
modeled,
but
dovetailing
into
steering's
request
for
annual
reports
moving
into
the
next
year.
Seeing
what
the
annual
report
format
looks
like
everyone
taking
a
look
at
that
and
just
getting
an
idea
of
like
oh
this
is.
This
is
a
place
where
you
know
some
tool
or
process
that
we're
thinking
of
might
be
helpful
right.
C
A
Okay,
well,
I
think
that
pretty
much
covers
our
agenda,
so
does
anybody
else
have
anything
they
want
to
discuss
in
the
last
five
minutes
we
have
here.
G
G
D
A
H
D
I
C
All
right,
then,
oh,
hang
on
sorry
we
have
a
new
attendee,
maybe
new.
I
don't
know
if
you
want
to
say
anything.
C
Sure
did
you
have
questions
anything
specific
you're
looking
to
get
out
of
this
group?
No,
I'm
just.