►
From YouTube: 20200213 SIG Arch Community Meeting
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
A
We
probably
could
as
I
as
I
went
through
it
afterward
as
sometimes
happens
realized
we,
we
didn't
ask
which
releases
people
rolled
back.
So
if
we're
gonna
try
and
use
this
for
quality,
we
need
to
ask
that
question.
We're
not
going
to
know
which,
whether
whether
fewer
or
more
people
have
had
two
rolls
in
the
back
again.
It's
also
a
very
self
selected
crowd,
so
that
also
limits
the
utility.
A
A
We
got
about
30,
other
people
said
they
were
willing
to
have
a
one-on-one
conversation
about
about
the
specific
failures
they
had,
and
you
know
what
we
might
be
able
to
do
to
make
things
better,
so
definitely
we'll
be
following
up
with
them,
but
I
don't
want
to
show
the
raw
results
because
of
those
emails.
What
I'll
do
is
take
the
the
results
and
put
together
a
deck,
and
we
can
go
over
the
highlights
at
another
time
and.
A
B
B
B
B
There
are
there's
a
transitive
recursive
dependency
and
a
dependency
on
the
CRI
API,
so
we're
trying
to
figure
out
ways
to
give
that
component,
what
it
needs
and
avoid
entangling
ourselves.
So
that
was
one
set
of
conversations
we
had
over
the
past
couple
weeks.
The
other
set
is
trying
to
think
through
how
we
measure
the
health
of
our
code
base
and
specifically
around
dependency
graph
stuff
as
we're
pulling
in
updates,
and
sometimes
those
updates
pull
in
additional
transitive
dependencies.
B
We
have
in
the
past,
it's
kind
of
been.
You
know
you
squint
at
a
proposed
change
and
say:
oh,
this
looks
better
or
worse
or
way,
worse
or
way
better,
and
it
was
sort
of
a
gut
feel
type
thing
and
so
we're
trying
to
think
of
ways
to
measure
what
we
have.
So
we
can
track
it
over
time
and
actually
understand
if
a
particular
change
is
going
to
make
things
way
worse.
So
we
we
don't
do
that.
B
C
C
A
A
C
The
parts
that
weren't
contentious
on
the
discussion
and-
let
us
say,
Caleb
Steven
Steven
Augustus,
had
point
out
that
he
had
a
cap
that
actually
covered
half
of
it
already,
so
we
merged
those
two
and
if
people
are
interested
in
reviewing
caps
and
the
structure
around
caps,
please
go
take
a
look
at
that.
Pyaare.
A
A
You
know
tooled
and
it
would
be
nice
to
have
how
to
wait
something
to
tie
them
all
together
and
if
the
cap
conserve,
but
this
this
allows
some
more
structure,
structured
metadata
and
some
things
like
that.
That
might
sound
silly
make
that
more
feasible
all
right.
If
that's
it
point
once.
Ok,
we
get
back
49
minutes
nice.
Alright!
Thank
you.
Everybody.