►
From YouTube: CHAOSS.Weekly.February.12.2019
Description
CHAOSS.Weekly.February.12.2019
C
D
C
C
E
F
A
So
that's
great
I
mean
it
sounds
like
there's
gonna
be
a
handful
of
chaos
related
or
chaos
mentioned
talks,
alright,
which
is
super
cool,
well
good
job.
Everybody
thanks
for
getting
all
those
in
so
that
was
that
and
then
are
we
I
think
that's
that's
gonna,
be
it
I,
don't
think,
there's
anything
else.
Chaos
planned
at
the
Leadership
Summit.
Is
that
right?
It's
mostly
just
the
talks.
There's
no
way
well.
E
A
C
A
G
E
E
A
H
A
E
E
A
E
A
E
B
A
G
A
A
B
B
B
A
G
The
update
on
that
is
that
Sarah
is
going
to
connect
with
Wright,
who
is
here
and
talk
internally
with
aperture
what
their
goals
are,
so
that
we
can
figure
out
what
DNI
metrics
are
good
place
to
start
with,
because
using
all
of
them
at
once
is
going
to
be
too
much.
And
so
we
want
to
start
a
small
pilot
and
yeah
conversations
are
ongoing.
Okay,
Dee.
A
Have
you
do
you
have
thoughts
on
how
to
get
this
work
done
right?
Because
if
it's,
let's
just
say
it's
around
one,
one
of
the
focus
serious
whatever
that
might
be,
it's
you're
just
going
to
take
time
right,
there's
just
a
human
effort,
it's
going
to
be
involved
and
how
we
as
a
community,
can
help
in
that
process
and
how
the
community,
like
hyper
ledger,
can
help
in
that
process.
We're
just
asking
for
more
time
somewhere
and
I.
A
G
A
A
A
A
E
C
E
B
C
C
C
A
A
A
C
A
C
Because
I
don't
want
to
work
on
ones
that
GMD
are
using
or
ones
that
D&I
are
using,
and
if
we
have.
If
we
have
that
indicator
in
the
list,
then
it
makes
it
easy
for
us
to
sort
of
cherry
pick.
Some
new
ones
to
work
on
candy,
that's
gonna,
be
part
of
our
discussion
next
week
is
getting
some
people
to
to
take
on
some
of
the
other
I
want.
B
A
A
C
Exactly
yeah,
we'll
probably
just
create
some
kind
of
directory
structure
for
the
ones
that
were
sort
of
focused
on
something.
Well,
we
haven't
gotten
quite
that
far
to
decide
exactly
what
that
should
look
like.
We'll,
probably
just
do
something
similar
to
what's
being
done
in
DNI
and
GMD,
where
we
have
some
some
focus
areas
and
we
work
on
the
detailed
markdown
files
for
exactly
what
definitions
go
with,
which
which
ones
and
probably
probably
do
something
like
that.
Right.
A
On
okay,
cool
for
that
column,
for
the
column
that
I
had
I
had
like
different
notes
that
take
me
in
different
directions,
so
obviously
I'm
adding
the
name
in
whatever
like
and
then
do
I.
Do
you
want
me
to
link
it
to
the
focus
area
where
this
is
being
like?
I
could
just
link
it
right
to
the
to
the
DNI
repo,
which
obviously
is
not
very
fine-grained.
C
I
would
say,
I
would
say,
sort
of
in
that
reverse
order,
if
there's
a
page
that
describes
the
metric
linked
to
that,
if
there's
not
linked
to
a
focus
area
and
if
there's
not
any
of
those
just
link
it
to
the
DNI
repository
and
it'll
sort
it
out
from
there
that'll
work
does
that
seem
reasonable
to
other
people.
I.
B
A
C
A
B
Lost
the
the
the
GMD
group
is
is
when
we
meet
next
going
to
kind
of
start
to
take
on
a
list
of
the
metrics
that
we
want
to
release
by
the
Leadership,
Summit
and
I.
Think
that
dovetails
with
gear
gone
off.
If
we
want
to
update
in
this
call
about
the
conversation
that
you
and
I
and
Toby
had
after
the
calls
I
bring
that
up
with
one
point,
so
I
think
I
think
what
we're
working
on
is
identifying
the
metrics
that
we
want
to
release.
B
G
G
Our
primary
goal
was
to
have
one
page:
let's
say:
chaos
top
coming
t
/
metrics,
that
has
the
list
of
all
metrics
and
Katie
had
shown
us
the
SPT
X
license
list
last
week,
and
so,
based
on
that
idea,
we
now
have
a
proposal
and
I
have
sent
that
to
the
mailing
list,
so
you
might
have
seen
it.
The
idea
is
to
have
this
page,
this
slash
metrics
page,
that
is
a
manually
curated
list
of
the
metrics
that
we
released
from
this
list.
G
We
linked
to
the
description
of
each
metric
and
those
live
within
the
working
groups,
so
they
are
maintained
directly
in
the
working
group
repositories,
which
means
we
have
three
different
repositories
that
have
metrics
but
each
responsible
for
their
home
and
because
we
don't
want
to
link
to
markdown
files.
We
are
going
to
build
a
github
pages
templating
engine
that
will
convert
the
markdown
file
into
nice
HTML
files,
and
so
we
have
two
components.
One
is
the
website.
A
G
E
G
E
G
A
You're
saying
yes
and
I
think
that's
also
then
consistent
with
the
work
group.
Names
really
is
consistent
across
all
this
okay
I
agree
and
then
the
it'll
link
the
descriptions.
How
does
the
templating
work
so
GMB,
obviously
or
whatever
DNI?
Has
your
your
focus
areas
and
then
I
clicking
on
in
the
repository
right,
if
I'm,
just
in
the
repository
I
click
on
the
conference,
one
right
and
obviously,
then
it
shows
me
the
stuff,
that's
the
metrics
that
are
used
to
inform
DNI
with
respect
to
conferences.
A
G
So
it
it
is
a
HTML
page
that
github
creates
for
us
mm-hm
and
there's
a
separate
URL
to
access
it
and
whatever
template
I
intend
to
use
the
same.
Template
is
for
the
website
that
will
be
put
around
the
content
similar.
Alright.
Now
we
have
on
the
website
content
from
the
repository
displayed
on
our
website.
Ok,
so
that's
what
it
should
look
like.
So.
A
Then
so
then,
if
I'm
in
the
repository,
it
still
looks
like
it
does
today,
because
just
nothing
changes
there,
the
the
templating.
So
then,
if
changes
do
occur
within
the
DNI
work
group
or
a
new
focus
area
or
for
new
metrics
within
a
focus
area,
there's
there's
no
change.
There's
no
effort
by
the
work
group
to
represent
that
new
information
that
would
be
displayed
via
web
page
is
that
correct.
I
say
that
right,
yes,.
G
A
G
C
E
I
A
C
A
B
The
discussion
in
the
conversation
that
we
had
Toby
was
fairly
I,
don't
know
if
he
felt
pretty
strongly
about
the
the
idea
that
he
would
not
try
to
formalize
the
release
process
as
much
in
slowed
it
down.
We
did
discuss
this
idea
that
we
don't
want
particular
for
tool
builders
to
have
a
shifting
or
changing
set
of
requirements
for
these
metrics.
B
So
it's
a
little
difficult
for
me,
but
tell
me
if
I'm
misrepresenting
anything
here,
gear
I
think
Toby
thought
that
at
the
end
of
the
discussion
in
this
meeting
last
week,
we
were
maybe
ok
with
periodic
release
with
the
sort
of
an
ongoing,
steady
release
state
with
the
understanding
that
we're
not
going
to
be
changing
things
much
once
they
are
released,
but
I
think
there
may
have
been
different
perspectives.
And
that's
that's.
Why
I
think
it's
an
important
topic
for
this
meeting,
so
we've
arrived
at
what
we
want
it
to
look
like
the.
G
C
G
G
E
E
A
E
E
H
A
E
E
E
C
I
mean
if
we
did
this
as
a
if
we
do.
This
is
a
regular
release
process
right
and
we
do
this
sort
of
quarterly.
That
would
just
be
part
of
the
release
process.
Right
Kevin
creates
the
page
we
you
know,
we
make
sure
that
everything's
ready
to
be
pulled
in
you
know,
whatever.
Whatever
we
decide,
the
release
process
is,
but
I
think
I.
Think
fundamentally,
I
think
we
need
to
step
back.
C
Think
the
governing
board
needs
to
decide
whether
they
would
they
want
rolling,
updates
the
website
or
periodic
releases.
And
if
so,
how
often
are
the
releases.
And
then
we
need
to
also
I
think
at
the
same
time,
better
understand
any
technical
limitations
that
we
might
run
into
based
on
the
choices
that
we're
making.
J
G
A
A
Think
this
is
really
great,
no
matter
what
because
I
think
we're.
You
know
the
likelihood
that
you're
gonna,
that
we're
gonna
start
just
a
conversation
about
releases
and
technical
ways
to
handle
releases
and
the
first
pass
is
pretty
pretty
low.
So
I
appreciate
that
we're
having
this
discussion
and
circling-
and
it
sounds
like
maybe
on
the
board,
we'll
start
finding
that
that
resolution,
based
on
all
the
good
work
that
everybody's
doing
so
far.
G
C
A
C
Just
I'm
curious
what
our,
what
our
options
are,
what
he
thinks
about
doing
doing
releases
cuz.
You
know,
regardless
of
what
we
decide
and
the
in
the
governing
board
meeting.
What
are
our
technical
options
if
we
did
rolling
releases
like
what
it
sounds
like
Toby,
Shawn
and
Guerra
kind
of
talked
about,
and
what
are
our
technical
options
if
we
do
like
quarterly
releases
website,
we.
B
Can
follow
the
same
technical
options
for
either
one?
It's
a
question
that
when
we
read
in
the
new
changes
so
and
they're,
really
the
the
process
difference
more
than
a
technical
difference,
I
think
at
the
end
of
the
day,
it's
whether
or
not
when
the
working
group
makes
changes
it
gets
pushed
to
the
website
right
away
or
all
that
gets
sort
of
put
through
some
sort
of
before
it
gets
pushed
out
to
the
world
to
consume.
Yeah.
C
A
C
Even
because
even
doing
them
a
separate
like
if
we
used
the
github
pages,
instead
of
instead
of
our
WordPress
site,
that
also
that
still
creates
overhead
for
Kevin,
because
we
have
to
do
things
like
keep
the
templates
up
to
sync
it
when
we
add
something
what
happens
and
how
do
we
handle
like
headers
and
footers
and
stuff
like
that.
That
creates
a
little
more
complexity
on
his
side.
No.
H
A
That's
TBD
a
little
bit
and
against
to
be
determined
as
to
what
we
mean
by
that
and
I.
Think
honestly,
it
seems
like
it
comes
about
as
to
whether
or
not
feels
like
there
was
a
few
questions
in
there.
It
does
sound
like
there
seems
to
be
general
consensus
around
the
chaos
community,
slash
metrics
page
as
representing
a
release.
Whatever
that
release
might
be,
nobody
seemed
to
really
push
back
on
that
mm-hmm.
F
C
You
could
bring
up
a
good
point,
I
think
at
its
core,
we've
been
talking
about
releases
for
quite
a
while
and
I.
Think
as
we
talk
about
them
that
we've
had
different
people
have
had
different
definitions
when
they
say
release
and
I.
Don't
think.
We've
realized
quite
to
the
extent
that
that
was
true
until
recently
mm-hmm.