►
From YouTube: CHAOSS.Common.April.30.2020
Description
CHAOSS.Common.April.30.2020
B
Most
of
it's
based
on
kind
of
iterations
of
stuff
we've
been
working
on
for
the
past
couple
of
weeks.
So,
let's
just
start
with
that.
First
one.
So
we
had
the
the
types
of
contributions
metric
and
we
we
finalized
it.
For
the
rolling
release
did
that
ever
actually
get
released,
I
sort
of
lost,
I
got
busy
and
I
had
lost
track
of
it.
I
know:
Kevin
was
working
on
some
stuff,
but
I
also
make
sure
that
we
did
indeed
actually
release
that
or,
if
not
follow
up
with.
D
C
D
D
C
C
B
B
B
C
B
B
B
B
And
then
we
also
kind
of
standing
thing.
Look
at
the
progress
on
the
metrics
spreadsheet.
D
The
time
all
the
constantly
yeah
it's
it's
like
why.
B
A
B
B
F
B
F
F
B
Okay,
so
the
next
and
I
actually
really
like
the
idea
of
working
out
one
of
the
space
metrics
next,
because
that's
the
one
that
we
don't
have
anything
in
right
now
right.
So
we
have.
We
have
things
now
released
in
three
of
our
four
focus
areas,
so
it'd
be
nice
to
get
something
released
and
in
the
where
category.
A
B
From
my
standpoint,
probably
the
the
two
that
I
I
would
care
about.
The
most
are
probably
the
top
to
the
collaboration.
Platforms
is
always
interesting,
because
a
lot
of
the
community
interaction
happens
in
loads
of
different
places,
depending
on
the
type
of
you
know,
the
type
of
project,
and
so
that's
something
that
I
think
I
think
is
important
and
I'm
also
I've
been
spending
a
lot
more
time
recently.
Thinking
about
where
software
is
released.
B
Interestingly
enough,
because
I've
been
counting
releases
on
github
and
realizing
that
a
lot
of
projects,
don't
don't
put
their
releases
on
github,
so
you
have
things
like
like
helm,
charts
which
are
released
somewhere
else
or
you
have
packages
which
are
released
in
distributions.
You
have
all
of
these
places
that
things
can
be
released.
Yeah.
D
So
we
early
on
Matt's
team
kevin
and
I
and
matt
cameron,
burt
others
were
involved.
That
thought
was
the
main
group
we
looked
at
with
it
pretty
deeply
in
the
libraries
I,
oh
and
with
the
median
number
of
libraries
that
come
out
of
github
repo
where
that
library
comes
from
is
40
so
and
there's
as
many
as
500
is
the
is
the
max.
So
the
a
lot.
G
I
would
agree,
I
think
I
think
both
of
those
first
two
are
really
interesting.
They're
released,
yeah
I
could
say
that
has
just
so
many
different
angles.
I
mean
there's
the
github
angle.
There's
you
know
people
using
like
NPM
or
like
that
and
I
think
there's.
Probably
some
interesting
correlation
is
how
it
also
maps
out
to
the
larger.
You
know
language
communities
as
it
goes
to
so
I
think
this
first
she
makes
sense.
The
third
one
would
have
made
sense.
G
D
G
But
I
think,
and
actually
maybe
maybe
that
parlays
into
something
interesting
there
of
like
how
communities
balance
between
physical
and
virtual
I,
don't
I,
don't
know
if
that's
inherent
in
that
that
metric.
But
it's
maybe
something
to
think
about
the
first
one
I
think
that's
kind
of
interesting
I
mean
I,
guess
I
think
all
four
are
very
interesting:
I
mean
I.
G
I
would
say
that
it
definitely
comes
after
the
first
one
and
you
could
make
an
argument
between
the
second
and
the
fourth
one
to
me
very
interestingly,
because
infrastructure
is
kind
of
like
I
mean
we
hear
all
the
anecdotal
stuff
of
you
know:
people
shifting
to
github
actions,
people
who
are
hosting
their
own
Jenkins
people
who
were
you
know
using
Travis,
CI
and
and
I,
don't
and
I
think
some
sort
of
concept
around.
Some
of
that
might
be
interesting.
G
Yeah
I
mean
that's
sort
of
an
interesting
one.
There
it's
a
little
bit
different
in
a
way
of
that
where
we've
seen
like
some
of
the
other
metrics
was
I
feel
like
if
I
look
at
like
the
people,
winds
below
it's
very
project,
centric
and
I
feel
like
those
there
are
kind
of
going
out
in
the
space
when
you're
almost
doing
analysis
across
or
analyses
across
the
entire
open-source
community
and
breaking
it
down.
G
B
Having
the
same
I'm,
something
same
thought
that
I
think
that
these
are
more
of
categories
of
metrics,
and
maybe
there
are
some
specific
metrics
that
we
need
to
define
within
each
of
these,
because
these
do
feel
they
feel
bigger.
They
feel
more
like
more
like
categories,
then
maybe
specific
metrics,
so.
D
Like
in
the
case
of
the
last
one
where
infrastructure
and
the
project
is
hosted,
there's,
where
is
the
git
repository?
You
know
what
platform
is
that
on,
but
I
and
in
the
risk
working
group
we
started
to
talk
about
what?
What
is
the
need?
What
is
the
configuration
at
a
very
detailed
level
of
the
machine
that
compiled
that
code?
That's
gonna
run
it,
and
so
that's
a
piece
of
infrastructure
so,
depending
on
how
you
define
what
a
project
is
and
I
think
it's
likely.
D
C
B
B
D
Like
when
you
mentioned,
kubernetes
and
I
immediately
thought
somebody's
got
to
have
a
pretty
big
data
center
of
hardware
to
do
testing
yeah
an
extra
technical
location
yeah
like
there
has
to
be
if
there
has
to
be
a
lot
of
physical
equipment
if
you're
gonna
actually
test
something
that
does
what
kubernetes
does
I
don't
know
who
I
have
no
idea
who
owns
that
or
where
that
runs,
but
I'm
pretty
sure
it's
not
a
Travis
I'm,
pretty
sure
it's
not
a
Travis
build
I'm.
Also
in.
D
F
Also
sponsorship
or
ownership
of
the
infrastructure,
for
example,
if
if
the
Linux
Foundation
is
providing
the
infrastructure,
so
it's
like
physical
space
and
and
who
is
providing
it
in.
F
F
B
Think
we've
I
think
we've
solved
that
and
given
more
people
access
to
whatever
it
was
and
I,
don't
remember
any
of
the
details,
but
but
that
was
a
case
where,
like
theoretically
everything's
hosted
by
the
CN
CF,
because
it's
a
CN
CF
project
but
in
reality
there
were
key
bits
of
the
infrastructure.
There
were
actually
kind
of
owned
and
hosted
by
other
people.
Things
like
things
like
domain
names
were
like
you
know,
somebody
purchased
the
domain
name
and
never
bothered
to.
B
F
A
from
a
chaos
perspective
our
website
is,
is
hosted
and
run
by
the
Linux
Foundation
and
within
within
our
project.
There
are
two
or
three
of
us
that
have
the
ability
to
do
things
on
the
website,
but
no
one
on
this
project
has
administrative
access
right.
It's
completely
under
the
control
of
the
Linux
Foundation
yeah
I
wouldn't
give
anyone
on
this
project
a.
B
G
Here's
where
my
builds
are
yada
yada
yada,
and
it
sounds
like
here
it's
more
of
an
intent
of
how
could
I
compare
like
a
kubernetes
infrastructure
to
a
Prometheus
infrastructure.
Something
I
got
I,
don't
know,
maybe
that's
not
even
the
right
apples
to
apples
like
it
I
guess,
I'm,
just
trying
to
think
in
my
head
like
how
would
one
apply
these
metrics
because
it
feels
different
than
the
other
ones
to
me,
but
I
am
also
still
I
can't
act
myself
as
the
newbie
here.
So
I
could
be
I.
D
D
B
Okay,
well
in
just
considering
time
so
it's
half
past
the
hour
and
we're
gonna
try
to
end
meetings
10
to
15
minutes
early,
so
the
people
up
a
break
between
same
meetings.
So
we
don't
have
a
ton
of
time,
but
matt
has
taken
the
action
item
to
start
building
some
of
these
out
for
the
next
meeting,
so
I
assume
that
means
creating
the
Google
Docs
that
we
can
use
to
collaborate
on
these,
or
at
least
some
element
of
these.
For
for
the
next
meeting.
B
A
C
B
A
B
B
B
Okay
and
then
the
other.
The
other
thing
that
we
wanted
to
do
is
sort
of
finalize
the
time
to
close
metric
join
me
to
Matt,
since
you've
been
working
on
that
join
me
to
stop
sharing,
and
you
want
to
share
that.
B
C
A
A
A
A
A
G
I
think
I
resolved
it
just
rewording.
It
I
think
it
was
I
was
just
trying
to
make
sure
I'm
wrapping
my
head
on
objective
2.
It
was
more
of
just
trying
to
see
like
what
are
the
characteristics
that
impacts,
whether
something
closes
quickly
or
slowly.
I
think
that's
where
you're
after
I'm,
just
the
wording
threw
me
off
but
I
think
what
sounded
like
two
or
three
words:
it
helped
I,
don't
know
if
that
if
I'm.
A
A
A
So
I
am
on
the
tools
providing
the
metric.
It
was
kind
of
messy
through
there.
So
I
got
rid
of
I'm
suggesting
to
get
rid
of
these
examples,
because
we
have
our
implementation
and
Gomorrha
of
implementation,
which
our
examples-
and
there
was
even
some
duplication
there.
So
everybody
really
just
removing
those
I
didn't
I
mean
it's
still.
A
C
C
C
D
A
B
D
D
Did
I
not
succeed,
yeah,
okay,
all
right,
so
we
just
did
a
new
release
and
I
have
the
new
and
the
new
I
guess
the
documentation.
End
point
changed
slightly
the
repo
the
actual
end
point
didn't
but
where
the
docs
are
did
and
this
Ellucian
issue
closed
issued
resolution
duration,
all
right,
I'm,
gonna
fix
so
okay,.
A
G
B
C
B
G
G
D
There's
some
reason
in
the
Google
Doc
I'm,
the
initial
click.
It
still
takes
you
to
the
top
of
the
document,
but
when
I
refresh
it,
it
goes
to
the
right
place,
so
I'm,
not
quite
sure,
I'll
check
it
out
and
it
should,
when
it
yeah
when
it
lives
in
the
markdown
I
think
it
probably
should
be
fine.
I
think
there's
some
kind
of
weird
ask
Google
thing
happening
here:
okay,.
A
F
Yeah,
just
as
a
as
a
data
collection
strategy,
I
think
that's
kind
of
important
to
address,
and
it's
it's
kind
of
counter
to
that.
The
line
we
just
deleted
right.
So
the
the
previous
line
had
said
that
something
to
the
effect
of
faster
time
means
that
your
development
is
better
or
something
some
such
thing,
but
but
I
think
the
the
collection
strategies
are
contextually
different.
Based
on
what
you're
looking
at
like
bug.
C
F
F
If
you're,
if
you're
exploring
issues,
you
might
collect
it
based
on
tags
or
labeling
right,
so
you're
testing
the
time
to
close
of
issues
that
are
labeled
as
bugs
versus
issues,
they're
labeled
as
feature
requests.
So
in
that
sense,
that
would
be
that
would
be
a
data
collection
strategy
to
separate
them.
At
that
point,.