►
From YouTube: CHAOSS.Community.August.13.2019
Description
CHAOSS.Community.August.13.2019
A
A
A
Stephanie
is
gonna
reach
out.
She
should
be
reaching
out
if
Oh
again,
to
get
out
on
that,
but
she's
gonna
give
all
attendees
kind
of
logistics.
You
know
cuz,
they
want
what
they
want,
is
attendees
to
go
to
the
main
Linux
Foundation
registration
boots,
and
that's
where
you
can
pick
up
your
kiosk
on
badges,
so
we're
not
gonna
actually
have
the
badging
at
the
site,
but
everybody
should
be
notified.
So
we
should
be
all
good
there
and
then
also
at
the
main
registration
site
will
be
things
like.
A
You
know
the
pronoun
stickers
and
you
know
those
stickers
that
are
like
they're
like
green
and
orange
and
pink,
and
they
say
things
like
if
I'm
wearing
a
an
orange
sticker.
Don't
take
pictures
of
me
I'm
packing
up
yeah
or
there's
I'll,
say
things
like
if
I'm
wearing
a
green
sticker,
it's
okay
to
come
up
and
talk
to
me.
Yep.
C
A
A
D
A
8
o'clock,
because
the
registrations
are
the
kind
of
the
doors
open
at
eight
o'clock,
the
conference
actually
starts
at
nine
o'clock,
so
I
think
we're
all
good
kind
of
logistically
in
that
regard,
we're
bringing
a
bunch
of
chaos
stickers.
We
also
have
some
chaos
poker
chips
that
we're
bringing
as
well
and
then
I
have
some
other
things
for
people
as
well.
So
everybody.
A
There
is
a
chaos
board
meeting
at
open
source
summit,
North
America
ray
you
should
actually
have
that
information.
I
think.
A
B
A
It's
only
an
hour
and
if
there's
we're
just
not
gonna
have
a
ton
of
time.
You
know
it's
mostly
I
think
it's
gonna
be
aids
to
the
board,
but
if
there's
anything
that
you
want
ray
or
and
I'll
say
this
to
everybody
as
well
so
put
on
the
agenda,
just
ping
me
and
I
can
easily
get
it
on
there.
Okay,
yep
anything
else
with
OSS
na
and
chaos
con
knock
what
I
think
we're
pretty
good
all
right.
Kevin
are.
We
are
we
asking
for
the
slide
decks
from
people?
D
E
A
A
E
A
My
guess
is:
it'll
be
easiest
easiest
to
just
rustle
them
up
after
the
fact,
because
at
that
point
I
know
ray
will
be
done.
As
you
know,
so
it's
probably
easier
and
less
annoying
to
just
ask
for
it.
Then.
The
other
thing
I
had
was
Kevin.
I
know
we're
I,
know
you're,
not
gonna,
be
there,
but
we're
recording
all
of
the
talks
as
well.
So
I
had
sent
out
an
email
to
the
movers
asking
if
it's
okay,
if
we
record
I'll,
do
that
again
and
same
with
the
lightning
talks.
A
A
E
A
F
C
F
F
D
A
G
F
A
A
We
can
do
it
too.
If
you
have
it's
no
big
deal
well
just
if
that
was
the
solution,
we'll
just
get
that
in
yeah.
It
wasn't
clear
that
we
knew
that.
That
was
the
agreed
upon
thing.
You
have,
you
have
no
action,
you
have
no
action
item,
we'll
we'll
take
care
of
it.
I
don't
need
to
over
process
the
situation
alright.
So
the
the
one
thing
that
I
kinda
want
to
talk
about
today
was.
A
So
one
of
my
one
of
my
big
things
now
that
we
have
we
have
kind
of
three
things
that
have
happened
over
the
last
year.
We
have
our
first
release
of
metrics
as
you're
all
obviously
familiar
with.
We
have
a
really
nice
set
of
tooling,
whether
it's
grimore
labs
or
for
the
deployment
of
these
metrics
and
we're
starting
to
get
a
huge
volume
of
data
that
these
tools
can
actually
pull
in
and
store.
So
we
can't
have
these
three
things.
One
is
metrics,
one
is
tools,
and
one
is
data.
A
One
of
the
goals
for
me
this
year
is
probably
the
next
six
months
is
to
really
identify
the
deployment
of
all
metrics,
whether
it's
in
tooling
or
in
say
programs,
and
what
I
mean
by
programs
is
that
some
of
the
metrics
aren't
easily
deployed
in
tooling.
So,
for
example,
the
DNI
metrics
are
not
easy
to
necessarily
deploy
in
tooling,
but
the
intention
is,
they
can
still
be
deployed.
A
Whatever
that
way
might
be
I
think
part
of
our
goal
is
to
have
these
metrics
not
only
think
about
what
the
metrics
are,
but
to
have
them
have
a
whole,
but
that
people
can
access
and
actually
use
and
think
through
so
I
last
week,
I,
maybe
a
week
or
two
ago,
I
kind
of
showed
a
way
that
we
can
start
tracking
tracking
this.
But
this.
A
C
F
F
A
A
Some
stories
kind
of
but
there's
pretty
ad-hoc
in
some
of
the
working
group,
so
say
like
the
evolution
working
group,
you
know
work
on
some.
They
were
calling
them
use
cases
for
a
while,
but
they're,
fundamentally
user
stories
about
how
these
metrics
are
making
an
impact
in
the
world
or
how
people
are
deploying
them.
Yeah.
F
D
D
So,
in
my
opinion,
I
think
all
of
the
work
that
we
do
should
be
focused
on
auger
and
gree
more
labs.
You
know,
we've
got
those
two,
it's
sort
of
referenced
platforms,
yeah
I,
don't
think
we
have
enough
resources
to
spread
ourselves
thin,
really
much
much
beyond
that.
So
I'll,
just
I'll
just
put
that
out
there
for
consideration.
Okay,.
A
F
F
A
A
How
they
live
and
how
they're
represented
in
these
table?
That's
okay,
they're,
they're
they're
in
the
tooling,
it's
just
making
an
explicit
connection
between
hey.
This
is
a
Kaos
metric
and
hey.
This
is
its
deployment
in
gorila,
or
this
is
the
Kaos
metric,
and
this
is
this
deployment
in
yeah,
okay,
Andy
I'm,
still
gonna
look
at
the
DNI
stuff,
even
if
it's
not
trace
data.
A
D
What
one
thought
is,
you
know
to
John's
point?
Maybe
we
could
have
a
little
bit
of
a
of
a
better
organization
around
the
around
that
tooling.
You
know:
we've
got
we've
got
sort
of
this
nice,
a
weekly
meeting
structure
to
to
discuss
lots
of
elements,
but
we
don't
have
a
way
to
really
talk
about
software,
specifically
I,
so
I.
A
C
G
A
C
D
A
A
Much
appreciated
okay,
so
the
other
thing
is:
here's,
there's
more
here's
what
here's
more
stuff
to
do
so
with
them.
Looking
at
you
Andy,
so
we
have.
We
have
metrics
tools
and
we
have
a
lot
of
data
and
there's
a
I
think
a
lot
of
you
can
can
suspect
this
or
against
this
or
you've
heard
it.
Is
that
there's
a
lot
of
interest
in
being
able
to
have
predictive
power
in
this
work?
A
A
F
F
B
A
B
A
D
A
lot
of
business
discussions
really
center
around
comparables
people
sit
around
they'll,
say:
oh,
this
project
is,
is
similar
to
this
other
project
that
succeeded
because
of
XY
and
Z.
It's
different,
it's
different
from
another
project.
You
know
for,
for
some
other
reasons,
yeah
to
the
extent
that
we
could
use
our
metrics
to
kind
of
automatically
generate
comparables
to
say,
hey
this
project
is
most
like
some
other
project
gives
I
think
would
would
give
a
way
for
people
to
have
sort
of
meaningful
discussions.
D
C
G
I
think
we
were
talking
like
less
than
a
week
ago
about
how
we
can't
make,
but
we
can
make
determinations
on
the
project
based
on
what
we
know
about
it
like
we're,
not
gonna,
be
the
people
to
say.
Yes,
you
know
on
something
or
a
project
is
doing
well
or
not
so
I
feel
like
that
kind
of
goes.
In
the
same
vein,
it's
kind
of
more
about
making
an
educated
guess
and
like
trying
to
say
how
not
how
I
feel
about
it,
but
how
we
know
from
what
we
know
already.
G
D
F
F
I
mean
we
could
come
up
with
maybe
half
a
dozen
or
a
dozen
scenarios
now
and
tie
those
to
some
of
the
metrics.
We
know
we
can
collect
and
say
we
may.
We
have
a
theory
that
if
we
see
indicators
that
do
XY
and
Z
that
this
may
represent
a
failing
project,
what
is
you
know
in
two
years
in
the
next
two
years?
Will
a
project?
F
That's
implemented
this
fail
and
then
let's
look
at
the
Delta
between
those
two
metrics
and
then
you
have
a
baseline
for
comparison,
I
think
if
we,
if
we
set
up
some
sort
of
I,
guess
baselining
project
for
better
or
worse
now,
with
some
some
scenarios.
We
assume
what
happen
over
the
next
two
years,
then
that
that's
probably
a
useful
thing
for
us
to
do.
I
mean
it
is
a
longitudinal
thing
right.
So.
A
A
A
A
A
You
know
from
a
growth
or
a
decline
perspective,
it
almost
doesn't
matter
and
how
do
we
understand
their
metrics
as
evolving
over
time?
You
don't
I
mean
so
you
would
be
project
a
you
would
say:
project
B
is
quite
comparable
to
mine.
That's
the
one.
I
want
to
take
a
look
at
it's
older,
so
let
me
take
a
look
at
the
existing
set
of
metrics
and
and
understand
how
they've
performed
over
time.
So
it's
an
early
warning
sign
or
an
early
warning
indicator
or
an
early
wait,
not
early
early
warning,
sign
or
early.
A
A
A
C
D
I'd
like
to
talk
about
okay-
and
this
is
specifically
for
value
sure
I-
think
that
I
think
that
the
working
group
would
benefit
a
lot
by
injecting
a
perspective
of
people
from
the
outside.
D
G
D
You
know
a
group
of
academic
and
software
people
yeah,
though
we're
you
know
bringing
our
own
perspectives
into
this
discussion
I.
It
would
be
useful
to
involve
for
value
two
types
of
people.
One
is
people
who
actually
work
in
open-source
program
offices,
okay
and
the
other
is
for
value.
I'd
like
to
you
know,
connect
with
like
an
economist
or
a
strategy
consultant
or
an
investment
banker
to
have
them,
give
a
kind
of
a
business
or
an
economic
point
of
view
about
the
economic
value
of
these
metrics.
How
do
they
think
about
it?
D
Okay,
and
so
my
idea
for
doing
that,
would
be
just
to
grab
a
small
group
of
people
in
each
category
could
be
like
two
or
three
yep
and
have
them
twice
a
year.
Just
you
know,
review
a
report
that
we
produce
or
review
metrics
or
review
something
that
we
give
them
just
to
get
a
little
bit
of
dialogue
going
and
maybe
to
get
a
different
perspective.
D
C
D
A
A
D
B
D
A
So
too,
and
I
think,
because
the
way
you've
the
way
you've
talked
about
it,
with
the
pretty
pretty
low
overhead
commitment
and
I
mean
a
pretty
much
just
off-the-cuff
feedback
sounds
like
is
what
you're
looking
for.
It
may
also
be
a
way
to
identify
people
to
participate
in
the
community
more
regularly.
D
A
D
C
A
D
C
A
E
A
If
not,
I'm
actually
done
I've
made
it
through
my
items,
I
had
my
two
things:
I
wanted
to
bring
forward,
make
sure
the
floor
was
open
for
other
things
that
people
want
to
bring
forward.
I'll
probably
bring
this
issue
up
again
in
terms
of
strategic
directive
at
the
chaos
board
meeting,
as
well
as
in
two
weeks,
we're
not
meeting.
Obviously,
next
week,
I'll
see
most
of
you
in
San
Diego,
so
looking
forward
to
that
Amy
thanks
for
your
time
and
I'll,
see
you
in
about
a
week
well,.