►
From YouTube: CHAOSS.Community.April.14.2020
Description
CHAOSS.Community.April.14.2020
A
B
A
A
A
lot
of
people
day
so
I
have
a
fairly
light
number
of
things
that
I'd
like
to
just
talk
about
today.
Of
course,
there
are
other
things
that
we
can
put
on
the
list.
I
just
I
wanted
to
just
put
it
out
there
again
that
we're
in
the
process
of
hiring
a
pretend
community
manager
for
the
chaos
project
again,
I
just
want
to
keep
this
in
front
of
people
hey
Olli
Co,
and
we
have
a
group
of
people
who
are
putting
together.
I.
A
D
E
B
It's
gonna
lean
that
way.
Linkedin
is
pretty
popular
these
days,
I
think
regardless
of
work,
if
you
publish
it,
someplace
will
help
get
the
word
out,
I'm
already
primed,
to
send
it
to
Mary
thing
ball,
who
runs
like
a
Debra
Lynn
community
mailing
list.
So
there's
quite
a
few
people
to
get
it
in
that
right
away
and
then,
through
our
own
social
media,
I,
think
well
we'll
hit
a
pretty
solid
audience
right
away.
It'll.
A
C
D
A
A
A
D
C
D
C
B
E
A
D
D
A
A
A
D
F
D
F
F
A
B
A
I
guess
I
have
one
question:
I'm
sure
this
isn't
it
to
me
before,
but
all
right,
so
we've
got
common
and
evolution
who
have
new
metrics
that
are
ready
for
release.
Yes,
and
we
have.
We
have
the
Kaos
community
slash
metrics
page.
Yes
right,
it
was
the
current
release
that
was
in
association
with
Kaos
con
Europe
in
2020
right.
A
F
A
F
A
F
So
there
are,
there
are
some
other
considerations
as
well.
So,
for
example,
on
that
page,
where
the
the
metrics
are
listed,
we
we
will
then
point
to
the
to
a
static
version
of
the
the
metric
page,
all
right,
so
that
that
static
version
is
the
one
that
we
capture.
It's
a
snapshot
in
time
for
the
regular
release
and
then
again
it's
kind
of
a
snapshot
in
time
for
the
regular
release
right.
So
it's
it's
static.
We
grab
the
page
at
a
certain
time
and
that's
part
of
the
regular
release.
F
A
C
F
Is
where
we
add
the
label
for
regular
release
or
continuous
release?
However,
however,
that
labeling
occurs
when
you
click
on
activity,
dates
and
times,
for
example,
it
will
take
you
to
the
metrics
page
yep.
We
pull
these
metric
pages
directly
from
the
github
repo.
However,
we
pull
them
using
a
we.
Basically,
we
take
a
snapshot
of
it
at
the
time
of
the
regular
release.
So
this
is
not
the
dynamic
page.
This
is
this
was
this
is
very
specifically
the
release
page
on
github.
F
If
anything
changes
within
this
this
metrics
page,
it
will
not
be
reflected
in
the
regular
release
right.
So
one
of
the
things
that
I
was
working
through
on
this
release
is
whether
or
not
we
want
to
actually
take
that
that
static
snapshot
in
time
of
the
continuous
metrics
or
if
we
only
want
to
do
that,
when
we
do
the
regular
release,
it's
the
way,
I.
Have
it
written
right
now
in
the
edited
version
of
the
the
governance
chaos
metrics
release.
Is
that
the
snapshot
that
static
version
of
the
page
only
happens
during
the
regular
release?
F
D
F
D
F
It
so
the
page
will
look
exactly
the
same,
but
the
page
is
populated
based
on
data
from
the
working
group
repo,
so
we're
the
regular
release
that
data
that
it's
populated
is
a
static
set
snapshot
of
the
page
that
we've
grabbed
or
then
for
the
continuous
release.
It's
just
going
to
point
to
the
the
working
page
actually
where
all
the
work
is
done.
D
To
ask
a
navigation
question:
yes,
when
I,
when
I,
navigate
to
a
rolling
release
metric
I,
see
what
I
see
is
exactly
the
same
thing
as
what
I
see
in
our
least
metric.
It's
the
same
format,
the
same
link
structure!
It's
just
that
if
I
chip,
the
work
group
evolution,
changes
that
metric
during
the
time
between
formal
releases,
that
page
will
actually
also
change.
Is
that
what
I'm
hearing
right?
D
A
A
F
If
you
drop
down
to
list
number
four
under
the
continuous
metric
release,
so
listen
number
four
includes
include
inside
the
metric
markdown
file,
a
message
that
will
be
part
that
this
metric
will
be
part
of
the
next
regular
release.
Alright,
so
and
then
I
created
kind
of
a
format
that
might
be
helpful
and
like
this
metric
is
a
release
candidate.
F
The
30-day
comment
period
for
this
metric
begins
on
such
and
such
date
ends
on
such
and
such
date.
To
comment
on
this
metric,
please
see
issue
number
blah,
blah
blah
and
then
following
the
comment
period,
this
metric
will
be
included
in
the
next
regular
release
and
we're
missing
the
new
lines
in
that.
So.
D
A
F
The
message
to
so
the
but
either
way
there
would
be
a
message
on
the
metric
page
during
the
comment
period
and
then
there
would
also
be
a
message
that
would
be
there
until
the
regular
release
and
then
when
we
do
the
regular
release,
we
would
remove
the
message
and
then
create
basically
a
snapshot
of
that
page
as
it
is
and
and
then
it
would
go
to
the
website
like
that.
And
then
at
that
point
we
would
also
create
the
the
PDF
of
the
of
the
full
metric.
D
A
F
F
A
F
Yeah,
but
it
would
yeah
and
it
would
be,
it
would
have
to
be
a
message
on
the
it
would
be
a
message
on
the
so
there'd
be
two
messages:
there'd
be
a
label
on
the
the
previous
web
page
and
then
on
the
metric
web
page
itself.
There
would
be
a
message
there
as
well.
It
basically
says
what
you
just
said:.
A
F
A
F
F
C
F
Well,
so
there
are
two
messages:
one
one:
the
value
for
the
one
is
that
it
actually
it'll
connect
you
to
the
issue
so
that
you
can
make
a
comment
and
then
the
value
for
the
second
message
is
to
reinforce
that
it's
the
content
is
still
dynamic
for
the
for
the
for
the
list.
When
we're
here
the
value
is,
you
can
see
at
a
very
high
level
which
metrics
are
going
to
be
on
the
next
regular
release.
So.
C
A
Tea
tie
okay,
part
of
the
continuous
metrics
releases
that
we
enable
for
metrics
to
be
contributed
over
the
course
of
six
months
per
the
working
group,
and
so
to
me
that
mission
is
a
is
a
contribution,
so
in
the
case
of
common
and
they
have
the
types
of
contributors.
I
would
like
to
see
it
just
in
in
this
white
kitchen
right
here
in
this
page
I
believe
they
took
the
time
and
it's
not
it's
not
as
it's
not
different
from
any
of
these
metrics
right.
A
A
F
F
So
my
so
my
thought
on
the
release
notes
is
that
we
all
we
create
the
release,
notes
on
the
regular
release.
However,
we
need
to
have
a
way
of
capturing
the
release
notes
during
the
continuous
period
so
similar
to
what
we
did
in
this
last
release.
We
have
each
working
group
create
an
issue
that
is
release
notes
and
you
just
continuously
capture
your
your
release,
notes
within
that
document
or
within
that
issue,
and
then
at
the
regular
release.
We
can
just
go
into
that
issue
and
pull
all
of
the
release,
notes
out.
F
C
So
the
way
that
I
see
the
release
notes
is
this:
is
the
document
I
go
to
see
if
they
have
been
changes
and
as
we
are,
adding
new
items
here
on
the
metrics?
Yes,
even
if
they're
for
the
continuous
metric
contribution,
I
would
expect
the
release
history
to
state
that
update,
because
the
website
has
changed
so.
F
A
F
So
Gehrig
would
like
a
list
at
the
top
of
the
release,
history
that
has
a
date
of
all
of
the
all
of
the
new
metrics
that
were
released
during
the
continuous
release
period
and
then,
after
the
continuous
release
period
is
done
and
we
do
a
regular
release.
We
empty
that
list
and
create
the
release
notes
for
the
the
regular
version.
So
okay
did
I
say
that
correctly.
Yes,.
F
So
if,
if
we
look
at
a
if
we
look
at
all
of
the
stuff
that
we
have
in
the
release
notes
currently,
if
it's
a
continuous
release,
the
I
think
the
working
groups
need
to
need
to
make
some
of
these
some
detailed
notes
somewhere
within
an
issue,
so
that
we
can
populate
a
more
detailed
release,
notes
during
the
regular
release,
and
we
can
still
have
that
we
could
still
have
that
content.
His
release
list
at
the
top
of
the
release
notes
does
that.
Does
that
make
sense?
F
A
A
There
yeah
so
so
this
it
would
have
a
I'm
just
thinking
just
super
pragmatically
here,
so
it
would
have
the
the
top
title
would
be
release
history
still
like
like
H
1
would
be
release
history.
Yep,
h,
uu
would
be
continuous
metric
contribution
since
last
release,
like
that's
the
next
immediate
heading,
under
release,
history,
correct,
alright,
and
then
whatever
comments
go
in
there
like
any
new
metrics
that
were
released
and
then
the
next
h2
is
released.
20
2001
notes
is
that
correct,
correct
and
then,
when
we
do
a
20
2007
release.
E
F
F
So,
most
of
it
most
of
it
matches
the
edits
that
I
made
to
to
the
release
handbook.
However,
there
are
some.
There
are
a
few
details
that
would
that
would
change
a
little
bit
so
I
would
know
if
Gehrig
has
time.
I
would
appreciate
it
if
he
could
take
a
peek
at
that
document,
or
the
pull
request
and
I
did
I've
been
making
notes
in
the
pull
request
itself.
A
D
Spent
so
if
we
ex,
if
we
decide
to
add
a
couple
of
filters
to
a
pull
request
there
to
a
metric
definition
in
the
interim
period,
do
we
process
that
as
an
interim
release,
because
it's
already
released
metric
or
do
we
just
let
that
update
sit
then
wait
for
the
next
final
release
and
I
would
advocate
just
letting
it
sit
and
waiting
for
the
next
release,
because
it's
just
a
very
it's
a
change
to
an
existing
metric
and
that
would
break
the
process.
We
just
described
four
new
metrics.
C
D
And
then
ones
that
are
changed,
they
would
be
released
within
the
next
formal
releases,
because
literally
we
added
two
filters:
two
lines
to
one
of
the
evolution:
metrics
and
I:
don't
I
don't
want
to
break.
That
seems
fine
to
like
wait
until
the
next
formal
release.
Harry
I
agree
so
know
that,
let's.
D
A
F
D
F
C
A
F
C
F
C
Those
of
you
who
are
not
familiar
that
they're
scratching
under
this
we
just
to
in
a
little
bit.
It
came
out
of
the
diversity
and
inclusion
working
group.
They
were
ranking
different
metrics
and
then
it
was
picked
up
by
other
working
groups
to
do
similar
exercise
and
then
every
walked
into
managing
the
releases
and
keeping
track
of
the
on
the
release
cycle.
So
the
same
spreadsheet
has
seen
many
losses
as.
A
And
it's
in
sync
I
find
it
to
be
incredibly
helpful
across
all
working
groups
and
tracking
metrics
when
I'm
doing
the
release,
that's
primarily
what
I
work
from.
So
it's
a
great
document.
So
all
right,
cool
I
have
one
I'm
gonna
skip
this
issue
metric
thing
for
just
a
second
and
then
go
down
to
podcast,
just
because
I
think
Georg
has
some
updates
that
I
like
to
talk
about
so
Gary.
Do
you
want
to
talk
about
that?
Yeah.
C
I'm
happy
to
talk
about
the
podcast.
We
now
have
a
website
for
the
podcast,
and
this
was
something
well
before
that
you
I
assume
you
all
have
read
the
email
that
I
sent
with
twenty
million
thousand
updates
on
changing
the
name
back
and
all
the
process.
That
is
happening
in
the
background,
so
just
on
the
name,
real
quick.
C
C
Fire
side,
m
and
justin
suggested
that
we
use
our
own
sub
domain
and
use
a
cname
forwarding
so
that
in
case
we
want
to
move
the
podcast
somewhere
else
in
the
future
away
from
fire
side.
We
can
do
that
without
breaking
anything.
Well,
breaking
less,
that's
good,
and
so
we
own
this
space
for
the
podcast.
That's
why
we
have
the
subdomain
and
integrating
it.
C
A
A
C
B
D
B
Have
raw
audio
that's
already
sent
over
to
Justin
and
gang,
so
our
process
is
to
download
the
audio,
send
it
to
them
directly.
They
will
edit
it
and
send
it
back,
and
then
we
plug
it
into
this
page.
The
page
Auto
generates.
They
also
have
I
think
they
do
voice
to
text
so
that
we
have
all
that
information
in
there
and
we
will
eventually
also
have
subscription
links
for
you
know
for
all
the
different
pod
captures
in
the
world.
B
A
B
C
C
B
Can't
have
Garrigan
a
fuse
machine
on
organizing
the
stuff,
but
it's
been
really
fun
to
see
the
progress
and
I
think
we've
like
a
really
got
a
good
sustainable
system
that
once
we
get
rolling,
will
continue
to
be
rolling
and
it
will
be
easy
for
other
people
to
hop
in
and
and
be
on
the
panel.
So
how.
F
C
F
C
F
A
It'll
be
part
of
the
negotiation
process
like
depending
on
the
person,
to
be
honest
with
you,
one
question:
I
have
for
Matt
or
Georg,
it's
kind
of
more
Restatement
question,
but
thank
you.
What's
your
cadence
of
reviewing?
What's
your
cadence
of
doing
the
podcast,
you
know
like
actually
recording
them.
First
is
your
cadence
of
really
we'd
save
that
go.
C
Currently,
we
have
two
weeks
recording
and
one
month
release,
and
this
was
just
so
that
we
can
skipper
we
we
have
a
pipeline
and
we
we
don't
overburden
ourselves
in
the
beginning
as
we're
building
out
the
process,
but
I
think
you're,
very
close
to
having
the
repeatable
process
and
Matt
and
I
can
share
the
load
of
organizing
the
recordings,
and
we
will
also
look
to
onboard
more
hose.
So
we
were
thinking
of
having
four
hosts
one
for
each
week
of
the
month,
who
organizes
one
episode,
and
then
we
have
a
pool
of
a
large.
C
Panelists
and
then
each
episode
you
would
have
one
host
and
one
or
two
panelists
join,
and
we
can
do
one
recording
each
week
and
we
can
even
release
on
a
weekly
basis,
because
there
are
so
many
conversations
that
we
want
to
have.
If
we
look
at
the
list
of
ideas,
we
have
for
episodes
it's
two
years.
It's.
A
A
month
I
mean
I
was
just
thinking
the
other
day.
I'm,
like
I
mean
we
couldn't
talk
to
remember
how
chaos
Khan
in
Europe
was
a
lot
about
how
metrics
are
important
for,
say,
scientific
communities,
I
mean
there's
a
whole
group,
I
mean
all
that
we
could
talk
back
to
in
that
regard,
I
mean
I
was
even
thinking,
universities
you're
starting
to
look
at
this.
A
You
know
as
to
how
they
measure
software
outputs
from
research
initiatives,
like
you
know,
as
software
as
a
as
an
outcome
honestly,
just
because
of
the
world
I'm
in,
like
from
a
funding
perspective,
why
do
funding
agencies
care
about
metrics
on
the
projects
that
they
financially
support?
There
are
so
many
different
ways
that
we
can
go
on
this
to
not
to
give
a
right
now,
but
to
your
point
that
there's,
like
years
and
years
of
conversations
as
to
why
understanding
open-source
community
health
is
important.
C
So
one
one
thought
just
listening
to
you
that
came
to
my
mind
is
if
we
do
build
this
out-
and
there
was
another
conversation.
I
had
mentioned,
that
for
building
and
following
it's
really
good
to
have
some
consistent
people
on
the
podcast
that
people
can
identify
with
and
relate
to,
and
so
the
whole
changing
hosts
and
panelists
and
I.
Don't
think
that's
a
big
issue
here,
but
one
way
to
around
them
might
be
to
have
hosts
that
specialize
in
one
area
of
chaos
like
if
you
want
it
to
be
a
host.
C
B
I
think
we
could
ultimately
have
like
the
it's
like.
If
you
follow
the
changelog,
the
changelog
has
the
master
thread
like
you
subscribe
to
get
all
of
their
sub
podcasts
and
I.
Think
if
we
do
what
we're
what
we're
planning
to
do
and
we
can
keep
it
up
for
a
few
months,
we
could
look
at
ourselves
to
be
like
alright.
Maybe
we
do
have
basically
sub
podcasts
under
this
umbrella
of
chaos
cast.
B
So
it's
it's
actually
great
idea,
and
yes,
it's
way
too
soon
to
do
it,
but
we
certainly
have
the
ideas
to
get
us
there.
We're
and
yeah
I
would
happily
be
like
SPO
and
devorah
eccentric
as
a
topic
and
I
could
see
you
being
scientific
or
education
like
yeah.
Just
lends
itself
really
nicely
get
into
tooling
yeah
there's
so
many
people
looking
on
this
door
to.
A
C
C
B
C
B
A
per
episode
yeah,
which
I
mean
so
normally
it
would
take
you
to
have
at
least
twenty
plus
thousand
listeners
before
you
start
making
around
a
five
hundred
dollar
per
episode,
the
exact
on
a
charge
so
like
the
fact
that
we're
starting
from
zero
and
immediately
making
that
is
kind
of
insane.
That's
what
I!
That's
why
I
asked?
Oh
yeah,
yeah
I
know
it's
wild
all
right.
A
All
right
cool
all
righty.
Well,
thank
you.
That
was
a
great
update,
so
I
appreciate
it
the
thing
about
we'll
talk
about
this
next
week.
It
was
basically
somebody
had
brought
forward
a
way
to
think
about
all
of
the
metrics
associated
with
issues
and
how
we
think
about
issues
kind
of
a
collective
sense,
so
we
are
at
the
top
of
the
hour
it.
You
just
turned
12
noon
on
my
computer
12
noon.
Central,
so
thank
you.
Everybody.
This
is
great
good
to
see
y'all
soon,.