►
From YouTube: CHAOSS.D&I.Part2.Feb.19.2020
Description
CHAOSS.D&I.Part2.Feb.19.2020
A
C
B
D
So
just
for
those
of
you
that
don't
know
we
use
this
spreadsheet
as
a
way
to
one
track,
progress
with
respect
to
their
releases,
but
then
also
just
kind
of
capture
what
other
people
have
brought
up
in
the
past
so
like.
What's
on
Georg
screen
right
now,
for
example,
those
on
under
the
considering
that
first
column
under
considering
or
just
that,
we've
talked
about
them
and
actually
I.
Think,
okay,
where
we
can
mark
the
readies
as
released.
E
E
F
D
F
One
of
the
things
that
like
I
sort
of
open
issue
for
is
like
I,
feel
like
the
piece
that
is
at
least
missing
in
conversations
that
I
have
is
how
people
can
take
those
metrics
and
apply
them
like
you
know,
in
a
LDR
kind
way,
without
having
to
go
through
the
repo
and
even
like
understand
all
the
little
bits
that
make
up
the
metric.
Yeah
and
I
have
plans
to
kind
of
write.
F
Some
of
those
kind
of
like
almost
like
recipes
for
like
a
value
evaluation,
yeah
I,
think
that
that's
still
for
me,
missing
and
I
think
would
be
kind
of
I
mean
helpful.
Like
once
it's
released,
you
know,
people
saying
I'm
using
these
I
think
I'll
help
the
chaos
project
to
like
I'm,
using
these
they're
valuable
they're,
helping
like
or
they're.
You
know,
there's
this
thing
that
I
can
improve
on,
like
so
I'm
gonna
be
doing
that
kind
of
on
my
own.
E
Point
one
thing
out
that
I
was
just
it
was
just
hitting
me:
it's
almost
like
we,
we
want
those
who
use
the
metrics
to
write
a
medium
article,
how
the
chaos
metric
helped
our
project
and
then
they
would.
They
would
kind
of
write
this
like
we
went,
we
got
them.
This
is
what
we
did.
You
know
it's
kind
of
like
the
the
back
story
of
how
taking
the
metrics
led
to
the
results.
So
so
you
know
also
it's
kind
of
like
behind
the
scenes
that
shows
really
okay.
How
did
you
use
them?
E
How
to
roll
them
out?
How
did
you
sample
so
so,
just
just
the
narrative,
the
account
of
how
to
take
those
and
make
them
useful
and
and
and
I
think
it's
fair.
You
know
to
say
that
people
who
use
them
and
find
them
useful
would
want
a
co-author,
or
you
know,
maybe
author,
on
their
own.
Some
some
of
these
articles.
B
So
what
you're
saying
is
a
excellent
idea
and
it
goes
back
into
something
I've
been
working
on.
Sorry,
you
see
it
my
mess
here,
but
there
is
something
about
a
blog
post
series,
metrics
and
use
that
we
do
have
a,
and
this
idea
has
been,
we've
developed
this
idea
to
have
a
series
of
blog
posts
about
how
people
actually
use
the
metrics.
F
B
E
E
Obviously
there
will
be
a
back
end.
Some
data
going
somewhere,
but
just
just
to
try
an
experimental
implementation
with
client,
heavy
or
client
client
sorry
static.
We
served
front-end
that
they're
doing
they're
doing
a
lot
of
the
heavy
lifting
not
draining
battery
just
doing
doing
good
work,
yeah
I
think.
E
A
E
D
F
Yeah
I
think
I
think
so
I
mean
I
haven't
thought
you
were
too
hard
about.
Like
the
format
I
feel
like
like
we
created,
we
had
an
innovation
to
a
cut
that
we
created
at
Mozilla,
which
was
just
like
you
know.
There's
a
this
activity,
framing
Anna's
activities
almost
useful.
It
will
take
this
much
time.
It
will
take
these.
Yes,.
D
D
F
Yeah
yeah,
so
just
like
that's
our
thing,
because
I
think
that
feels
doable,
I
think
people
feel
overwhelmed
and
mm-hmm,
and
it's
also
their
entire
self.
For
myself
to
you,
it's
not
just
yeah,
because
if
some
of
it
is
fake
right,
like
some
of
it,
does
take
a
lot
of
time
and
some
of
it
not
all
of
it.
Does,
though,
like
the
tracklist
mate
for
loss,
it's
like
you
know,
some
of
our
metrics
are
like
kids
are
court
of
conduct.
Is
it
in
the
root
of
the
you
know?
The
repository?
F
D
F
F
E
So
I
don't
yeah
because
I
have
not
visualized
yet
the
the
rest
of
the
process
beyond
the
metrics
are
published
and
then
some
data
is
this
processed
I.
Didn't
you
know
the
disconnect
for
me?
Is
you
know,
okay?
Where
does
what
do
people
usually
do
to
go
from
like
okay
I
got
the
metric
as
a
markdown
and
I
do
magic?
Obviously
you
know
I
can
reason.
E
But
I
haven't
seen
the
process
of
okay.
This
is
how
I
rolled
it
out,
and
this
is
how
I
got
the
data.
Then
I
put
that
date
back
into
the
system.
So
so
what
I
was
asking?
If
it
is
a
web
app,
would
it
be
a
web
app
that
deploys
the
metric
to
collect
the
data
firsthand
or
you
know?
Would
it
be
more
of
a
okay
here's
what
you
need
to
go
do
and
when
you
come
back,
just
give
us
the
data,
and
this
is
where
I
have
a
complete
talking.
D
D
E
H
E
G
B
So
you're
you're
raising
an
excellent
point
right
now
we
have
on
our
website
on
the
chaos
website,
the
metric
page,
where
we
list
the
metrics
that
we
have
sufficiently
defined.
On
top
of
that,
we
have
published
blog
posts
in
the
past
to
get
the
word
out.
We
also
doing
conference
talks
about
this
so
at
the
open
source
at
the
Linux
Foundation
member
ship
summit,
for
example.
We
have
a
panel
about
this
topic
and
then
we
do
this
at
other
conferences
as
well.
So
there
are
several
ways:
we've
tried
to.
E
E
G
E
I
mean,
are
you
sorry?
No?
No,
it
was
a
conversation
with
someone
who
has
a
particular
position
and
get
up
about
accessibility
aspects,
and
they
were
well
positioned
to
you
know,
talk
to
me
one-on-one,
sometime
down
the
road,
and
that
is
when
they
mentioned
chaos.
As
being
you
know,
doing
very
important
work
that
I,
should
you
know,
seek
you
guys
out
so
so
I
know
otherwise,
but
that's
only
you
know
one
one.
One
way
of
you
know
how
you
could
come
to
know
if
acquiesce
so
the.
B
Other
part,
energy
that
I
think
you
lost
when
you
disconnected
was
that
we
have
on
our
website
the
metrics
page,
where
we
list
the
metrics
and
then
we
go
to
conferences
and
have
talks
and
sessions
and
panel
discussions
about
these
metrics.
Do
you
have
spread
the
word
and
we
have
also
published
blog
posts
in
the
past,
but
we
can
probably
do
better
at
getting
the
word
out.
Does
that.
G
E
I
think
it
that
was
a
great
segue
as
well,
because
while
you
were
saying
obviously
the
badging
in
the
back
of
my
mind
was
yes,
you
know
I
wish
the
badging
was
like
III
could
just
imagine
all
those
folks
are
all
those
projects
that
have
worked
with
chaos.
Metrics
putting
you
know
something
on
their
site.
That
says
you
know
we
are
proud
to
work
with
the
chaos
metrics
for
our
project.
E
You
know
that's
one
step
before
the
badging,
even
because
you
know
comes
in
and
can
play
it's
just
saying
that
we
are
not
like
business
affiliates
or
anything
we
are
just
proud
to.
You
know
say
that
we
are
using
those
metrics
and
you
are
seeing
you
know,
making
making
it
a
better
experience
for
everyone
involved
in
the
project,
and
so
so
it
is
not
meant
to
be
a
one-way
advertisement.
E
It's
actually
a
two-way
street,
so
you
know
that's
a
little
different
than
the
badge
that
they
would
get
you
know,
and
hopefully
they
would
get
the
gold
badge
you
know,
but
they
could
still
get
you
know
so
right
now
these
are
the
badges.
We
kind
of
think
will
will
will
end
up
being
the
options.
I'm
sure
other
metrics
we
may
as
well
have
badging,
and
that
goes
to
the
visibility.
But
this
at
least
is
a
starting
point.
E
So
I
guess
now
we
shifted
to
talking
about
badges
altogether,
so
I
guess
math
math
is
really
doing
the
bulk
of
the
work
here.
So
he
made
this
repo
I've
been
kind
of
slowly
joining
him
and
he
basically
wanted
folks
to
be
able
to
open
issues
and
basically
say
if
they
want
a
badge
for
an
event
or
a
project
and
then
when
they
say
okay,
it's
an
event,
then
they
would
fill
out
a
markdown
version
of
the
questionnaire,
and
you
know
it's
hard
to
work
with
this
format.
E
Obviously,
but
I
mean
one
of
the
key
one
of
the
important
things
is
that
we
stick
to
a
github
process.
We
don't
use,
you
know
a
third
layer
or
an
external
place
like
a
web
form
or
something
like
that.
So
I
guess
this
approach
means
every
badge
would
have
an
issue
and
that
issue
would
would
have
a
review
process.
E
E
B
Asked
a
question
sure
so:
I
understand
the
idea
to
have
a
hold
request:
workflow,
where
people
fill
out
a
form.
Maybe
they
are
at
a
markdown
thing
somewhere.
So
we
have
a
permanent
record
and
while
they're
getting
the
batch,
we
work
through
the
pull
request
model.
Now
the
you
use
that
there
are
two
different
batches
event
and
projects.
E
Yeah,
so
so
so
dni
of
an
event
versus
a
DNI
above
project,
so
you
get
a
badge
if
your
event,
if
your
event
is
receiving
a
bath,
you
know
you
fill
out.
That
particular
form.
So
let
me
let
me
backtrack
here
for
a
sec
that
doesn't
work
really
where
they
go.
Oh,
it's
here
all
right,
yeah,
so
I
can
open
the
two
templates.
E
E
B
Which
one
which
one
will
you
finish,
events
or
projects,
because
then
I
would
like
to
dive
into
that
batch
a
little
bit
more,
which
bags
yeah?
If
you
have
events
and
projects
I
assume
it
makes
sense,
maybe
to
focus
on
one
first
flush
that
out
before
we
start
spending
Oh
spending
too
much
time
on
both
at
the
same
time,
Oh
like.
E
I'm,
just
showing
them
generally,
because
I'm
not
sure
like
to
be
honest,
I
haven't
been
part
of
those
templates
at
all,
like
I
mean
those
were
kind
of
in
the
repo.
At
that
point
in
time,
I
was
just
gonna
show
the
workflow
that
bit
I
have
been
party
to
so,
but
but
do
you
think
what
we
want
to
do
is
revive,
was
or
review.
Those
was
that
was
that
what
you're
getting
at
I.
C
C
We
should
probably
review
them
and
just
make
sure
everything
is
good,
but
if
it's
matching
up
to
the
metrics
I
think
if
someone
does
pass
or
if
you
get
like
nine
out
of
it
of
tenure
of
this
a
silver
instead
of
a
gold
or
whatever
I
think
the
basic
work
is
there
I
mean
from
the
OpenStack
side
of
things
yeah.
We
would
try
to
get
the
project
to
get
a
badge
as
well.
C
E
E
B
For
the
kubernetes
process
that
there
is
some
some
process
done,
you
might
know
more
about
what
has
happening
kubernetes
but
as
far
as
I
understand,
they
have
a
conformance
program
where
you
have
to
fill
out
like
a
form
similar
to
this
and
then
submit
the
form
as
a
markdown
to
a
repository,
which
is
the
documentation
that
you
are
conforming
to
whatever
they're
conforming
the
API
access
whatever
and
is
done.
Do
you
know
something
about
this
yeah.
C
Yeah
they
do
have
to
pass
because,
like
OpenStack,
a
couple
of
the
projects
are
past
conformance
so
like
I,
know
a
little
bit
about
the
process.
So
basically
there's
you
know
the
basic
kubernetes
and
how
it
should
work.
And
then
you
have
your
offshoot
of
how
you're
using
it,
and
it
goes
through
conformance
to
make
sure
everything
works
and
is
proper.
Yeah.
I
But
it's
it's
different
I
would
say:
conformance
is
different
than
badging.
I
can
see
why
you
I
can
see
why
it's
similar,
but
conformance,
for
example.
Is
you
know
what
are
the
tests
that
I
need
to
pass
in
order
to
call
the
thing
that
I'm
shipping,
a
kubernetes
distribution
or
an
openstack
distribution,
so
you're?
Actually
using
you
know
it's
more
of
a
it's
more
of
a
technical
test
to
make
sure
that
if,
if
I
write
an
application
on
top
of
pivotal
scoober
Nettie's,
it
works
the
same
way
as
if
I
write
an
application.
B
So
I
understand
that
there's
a
more
technical
nature
to
it
than
what
we
have,
but
we
do
have
the
metrics
that
provide
several
ways
of
measuring
any
one
metric
and
the
badging
process
is
dynamic
enough
to
allow
someone
trav
to
make
an
argument
for
how
they
are
measuring
it.
That's
how
I'm
understanding
it
right
now.
B
The
part
where
I
think
we
can
learn
from
this
kubernetes
process
is
that
in
what
Salah
is
showing
here
is
just
adding
one
line
to
passing
or
not
passing,
which
is
good,
but
it
would
also
like
to
document
that
template
that
he
said,
and
rather
than
having
that
in
a
pull
request.
Discussion
have
an
actual
marked
on
page
somewhere,
where
it
becomes
part
of
the
repository,
because.
E
That's
a
that's
absolutely
part
of
this.
You
know
it's
possible
with
the
PR
approach,
because
once
once
they
fill
out
this
and
we
comment
and
they
correct
it-
we
can
copy
and
paste
that
markdown
and
push
a
commit
to
their
branch
that
puts
their
filled
out
version
in
a
folder
of
all
applications.
You
know
the
records
and
make
a
link
and
put
the
badge
in
the
in
the
table,
link
it
to
that
particular
record
and
when
we,
when
our
review
is
satisfactory
and
there
they
are
satisfied
by
our
review,
we
can
merge
the
PR.
E
B
I
think
something
along
those
lines,
so
we
have
a
pull
request
that
does
tooth
two
changes
to
the
repository
one
is:
it
adds
a
markdown
page
based
on
the
template,
with
all
the
answers
that
documents
exactly
how
an
event
or
project
is
following
the
DNI
metrics,
and
the
second
part
of
the
pull
request
is
adding
the
entry
in
a
list
of
passing
badges.
Yes,.
E
And
linking
them
right
so
and
I
think
we
can
use
github
actions
to
actually
take
the
body
of
the
PR
and
automatically
preserve
that
and
make
the
link.
So
so
I
see
that's
a
a
really
useful
process,
I
hope,
but
there
will
be
a
lot
of.
We
need
to
write
documentation
to
help
folks
who
hit
the
unexpected
I
will
uncover
some
of
those
usually
not
the
same
unexpected
that
other
people
do
but
yeah.
So
so
we
will
have
to
play
around
with
this
workflow
enough,
of
course,
getting
a
badge
is
you
know,
proving
too
difficult?
E
C
E
Question
great
for
us,
and
so
so
we
did
talk
about
this.
We
start
off
by
saying
we
have
those
PNG
images
made
from
shield
star
IO,
but
but
we
also
were
we're
keeping
in
mind
what
it
takes
to
actually
call
an
image
from
shields
thought
IO
is
that
it
knows
the
origin
or
the
the
which
you
know
if
the
cross
origin
basically
says
what
refer
you
know
asked
for
this
image.
E
So
when
we
say
a
particular
or
a
project
or
event
is
badged,
then
we
know
particular
referrers
that
will
be
white
listed
to
receive
that
particular
badge.
Now
the
technical
flipside
of
this
is
okay.
How
do
we
work
with
or
around
shields
that
I
owe
so
that
those
particular
DNI
badges
do
not
get
generated
using
the
same
magic
string?
E
You
know
if
the
URL
is
not
white
list
of
them.
I'm
sure
he'll
style
has
a
process
that
for
a
particular
tag,
a
particular
you
know,
webhook
gets
triggered
or
a
particularly
you
know.
Very
40
is
consulted
to
to
populate
the
shield
with
the
particular
data
needed.
So
so
we
will
have
to
explore
how
exactly
we
can
technically
get
this
implemented,
but
yeah,
you
know
if
you're
going
to
hand
out
you
know
full
mark
versus
you
know,
passing
most
people
will
say:
yeah
I
got
the
whole
mark.
B
So,
okay,
so
there's
the
technical
question
of
displaying
the
badge,
and
maybe
we
can
built
in
some
technical
check
that
they
are
actually
listed
on
our
passing
list.
And
then
we
have
the
legal
side
where
we
have
the
trademark
or
the
Linux
Foundation
on
the
trademark
to
the
Kaos
brand,
and
that
is
our
legal
leverage.
C
And
you
scroll
up
just
a
little
bit.
There
was
something
that
caught
my
eye.
Aha
I
am
miss
global
hey.
This
is
a
work-related
phone
call,
okay
yeah,
so
we
could
even
possibly
run
through
a
database
hosted
over
at
Linux
Foundation
I'm
thinking,
I
mean
they've
got
infrastructure.
We
don't
have
infrastructure,
let's
be
real
technology
wise.
It
wouldn't
be
real
hard
to
host
these
badges
over
there
and
run
checks
on
them.
We
would
just
need
by
internal
Enix
Foundation
I.
E
Think
the
trend
is
like
CloudFlare,
for
instance,
has
this
worker
idea
where,
on
a
network
request
going
to
your
your
your
domain,
you
can
basically
have
a
Middle
where,
or
you
know,
a
service
worker
per
se.
You
know
in
a
way
that
when
it
gets
a
particular
request,
it
knows
where
it's
coming
from,
you
know
refer,
and
it
knows
what
the
request
is,
and
then
it
can
do
a
network
request
that
is
different
from
what
the
static
server
is
doing
and
then
it
can
can
augment
or
redirect
or
mutate
the
returned
result.
E
So
at
this
point,
if
we
say
there's
a
github
repo
that
has
a
markdown
file
and
in
that
markdown
file,
if
the
query
is
not
matchable,
maybe
a
JSON
file.
If
that
query
is
not
found,
then
the
batch
should
be
not
not
authorized
or
you
know
illegal
or
something
you
know
go
to
jail,
something
like
that.
Yeah
I.
B
C
Edging
shouldn't
we
be
leveraging
it
versus
I,
mean
mind
you.
This
work
is
different
than
that,
but
if
there's
an
infrastructure
already
in
place
to
hand
them
out,
it
makes
sense
to
go
ahead
and
piggyback
so
that
anyone
else
who
then
has
their
own
badging
system
and
their
working
group
we're
not
duplicating
any
efforts.
So.
E
E
B
And
if
you
have
enough
check
marks
in
all
the
right
places,
then
you
automatically
get
the
passing
silver
or
gold
level
which
looks
like
this,
and
you
can
have
embedded
it.
You
get
a
URL
that
you
can
embed
in
your
repo
or
on
your
website,
and
this
is
dynamically
generated
badge
that
checks
against
this
website.
E
B
E
The
idea
that
they're
the
this
front-end
basically
like
I
I,
don't
like
the
idea
of
filling
out
the
markdown
template,
because
you
know
when
you
put
the
markdown
template,
people
are
very
inclined
to
change
the
structure
of
the
template
when
they
feel
that
the
template
doesn't
really
speak
their
mind.
Well,
I
do
that
sorry,
but
every
time
I
opened
an
issue
that
told
me
exactly
how
I
should
describe
my
problems.
My
problems
are
not
meeting
the
template.
I
was
frustrated
because
you
know
how
would
you
know
exactly?
E
B
E
And
and
that
can
automatically
trigger
opening
the
PR
and
starting
the
review
process,
because
I
don't
think
we
want
to
hand
out
the
badge
just
yet
we
want
to
collect
that
information
populate
the
PR
with
all
the
relevant
pieces,
because
that's
the
transparency
record
aside
from
the
record
of
you
know
that
will
be
checked
against
the
whitelist
of
getting
this
badge
from
this
yeah
right.
Just
to.
B
E
B
C
E
I
kind
of
visualize,
because
because
I've
done,
I've
opened
issues
for
some
software,
they
give
you
a
playground
and
they
tell
you
rep
reduce
the
process.
The
configuration
that
led
you
to
you
know
not
get
prettier
to
make
things
prettier,
for
instance,
and
so
when
I
do
that
and
I
click
OK
open
the
issue.
Now
I
don't
have
to
fight.
You
know
the
urge
to
change
the
template.
The
answer
is
there
and
nine
out
of
ten
times.
I
submitted
the
issue,
as
is
so
so
that
this
idea
that
there
is
a
PR.
E
So
so
I
I
really
feel
a
good
synergy
can
come
out
from
this.
You
know
where
we
have
this
front-end
that
is
already
tested
now
being
repurposed
by
adding
the
review
model
of
the
PR,
which
is
very
familiar
and
and
by
doing
that,
we're
minimizing
all
the
moving
parts,
because
if
you're
getting
a
badge
and
you're
now
diverted
to
a
full
request
and
you're
asked
a
question,
you
can
answer
that
question
and
you're
part
of
a
familiar
review
process.
E
And
after
that
there
is
a
permanent
record
which
I
beg
to
you
know:
I,
believe
that
the
markdown
approach
is
transparent.
Documentation
of
the
process
that
there
is
a
data
record
of
it
elsewhere
is
not
necessarily
the
invisible
component
of
transparency.
We're
talking
about
here,
you
know,
could
just
be
IP
address
or
URL
badge
number
or
you
know
bad
code,
and
you
know
so.
Those
are
my
kind
of
insights
here.
Okay,.
B
So
we're
almost
out
of
time
and
thank
you
for
working
on
this
and
giving
us
a
rundown
of
the
progress
Matt
and
you
have
already
made
this
is
really
great
well,
thank
you
at
one
point.
I
think
it
would
be
nice
Amy.
Maybe
you
said
it
makes
sense
for
OpenStack.
Maybe
we
could
sit
down
at
some
point
and
go
through
this
badging
approach
together
to
see
basically
as
a
prototype
or
early
feedback.
If
we
could
fill
this
out
for
OpenStack.