►
From YouTube: CHAOSS Evolution Working Group 8/9/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
It's
like
because
I'm
sharing
it,
the
the
but
the
nice
easy
to
see
button
becomes
one
of
20
things
in
a
drop-down
menu
right.
It's
never
in
the
same
place,
because
designers
got
to
change
that
stuff
to
make
it
easier
to
find
at
the
current
time,
record
is
actually
the
first
item
in
the
20
item
drop
down
list
moved
from
somewhere
in
the
top
middle
or
bottom
middle
over
time.
So
here
we
are,
and
we
have
uh
four
three
new
metrics
to
develop.
A
B
A
A
A
A
A
B
B
B
A
A
A
B
No,
I
see
it
as
a
separate
matrix,
because
you
know
time
to
close
the
there
are
humans
in
the
loop
and,
for
example,
you
can
start
reviewing
something
on
monday.
You
skip
tuesday
wednesday,
and
you
continue
on
the
next
days
of
availability,
then
to
really
know
the
active
period.
While
you
were
working
on
the
particular
let's
say,
file
or
task
that
we're
doing
it's
somehow
challenging
to
know.
But
when
a
build
process
starts,
it
spin
up
onto
the
moment
it's
really
close
and
then
for
for
some
other
interesting
reasons.
B
A
B
A
A
B
A
B
B
B
B
A
B
B
A
A
A
B
A
B
B
A
B
A
You're
going
to
have
yeah
tons
of
builds
every
day
because
it's
all
automated,
so
that
makes
that
makes
sense
to
me
that
they
would
have
that,
because
you've
got
probably
hundreds,
if
not
thousands,
of
developers
pushing
to
these
repositories
and
probably
triggering
builds
every
time
they
do
it
like
it.
Sometimes
I
imagine
on
a
project
of
that
scale,
it
gets
to
the
point
where
they
actually
don't
automatically
build
it.
Every
time.
B
No,
I
mean
that's
like
the
job
of
the
release
team
after
they
have
tested
everything
they
build
and
they
deploy
right.
So
so
it's
always
good
to
have
because
this
number
can
escalate
in
some
cases
why,
in
other
cases
the
number
might
be-
let's
say
low,
so
we
might
find
cases
of
outliers
and
if
we
don't
know
how
to
interpret
it
in
that
context,
then
we
might
represent
them
wrongly.
A
So
yeah,
I
think
I
hear
what
you're
saying
there's
I'm
just
gonna
go
to
the
auger
one,
because
it's
just
an
example
that
so,
for
example,
it
takes.
You
know
right
when
I'm
running.
If
I've
updated
a
bunch
of
files,
it'll
run
a
whole
bunch
of
them
and
that's
I
have
more
limited
resources,
and
so
it
takes
longer
for
each
of
them
to
run
so
augur
takes
like
15
16
minutes
at
the
outside
and
as
little
as
11
minutes.
When
there's
only
one
of
them
running.
Although
18.
B
A
B
A
B
B
A
The
metric
template
from
I
went
to
the
top
of
the
spreadsheet
okay
and
clicked
um
metrics
template.
Oh,
this
is
not
the
right.
Metrics
template
it's
very
close,
but
I
was
just
looking
at
the
the
main
one
because
I
was
going
to
fix
that,
um
but
it's
already
been
fixed.
So
then
I
was
like.
Oh
no,
and
I
noticed
too
that
the
ethics
document
was
not
linked
and
that's
also
linked
in
the
metric.
So
I
think
those
are
the
only
real
changes
that
I
see
yeah.
B
A
A
A
B
A
A
You
know
the
only
dei
effect
is
if,
if
like,
uh
for
example,
one
of
the
things
I
can
see
from
working
with
our
chaos,
africa
folks,
is
that
they
have
less
bandwidth
than
I
do
at
my
gigabit,
fiber,
home
and
so
building
auger
takes
longer
because
auger
has
to,
and
it
would
auger
is
not
special
like
any
of
the
chaos
software
projects
will
take
longer
because
they
all
are
downloading
python
libraries
uh
over
the
internet
as
part
of
the
installation
process,
and
so
anytime.
Somebody
with
a
low
bandwidth
connection
is
installing
auger.
A
It
takes
them
considerably
longer
or
for
more
lab
or
whatever
any
piece
of
any
piece
of
software.
In
our
chaos,
universe
takes
longer
because
they
have.
If
your
bandwidth
is
lower,
it
takes
longer
to
download
stuff
um
mm-hmm
things.
I
learned
back
when
I
had
a
modem,
although
I'm
not
old
enough
to
have
had
them.
B
A
A
It's
the
small
knit
but
yeah
it's
it's
like
any.
It's
like.
So
it's
I'm
not
entirely
because
when
I
think
about
build
times
and
I
think
about
its
effect
on
community
service
and
support,
I
think
that
that's
part
of
it
that
might
be
a
factor.
So
we
can
check
with
the
asia
pacific
group
on
wednesday
morning
to
sort
of
get
a
sense
of.
A
A
B
B
Because
those
kind
of
things
I
was
thinking
that,
uh
after
a
while,
like
in
the
evolution
working
group,
we
can
try
to
see
how
we
could
put
resources
together
even
to
make
some
good
publications
on
how
the
evolution
of
the
metrics
and
how
we
have
been
consumed.
We
can
always
have
data
to
to
publish
our
work
within
the
working
groups
themselves.
A
Like,
for
example,
um
let
me
see
if
I
can
find
it
here
or
if
I
got
logged
out
um
oh
here,
it
is
I'm
just
gonna,
we're
kind
of
near
the
end
of
time,
so,
okay
I'll
just
um
so
there's
a
like.
We
could
like,
for
example,
in
auger.
Let
me
just
uh
I'm
going
to
take
a
side
trip
here
for
just
a
second
excuse
me,
allergies.
A
Yeah,
so
this
is
like
a
third,
a
third
of
a
gigabit
that
it's
getting
on
a
server
where
it's
not
on
full
duplex
on
my
local
network.
That's
actually
making
a
ton
of
calls
to
the
internet,
and
so
this
speed
test
library
could
be,
for
example,
included
in
all
implementations
of
chaos.
Software
and
we
could
execute
it
as
part
of
a
of
an
install
and
ask
people
to
optionally
share
their
network
performance
information
with
us
and
then.