►
From YouTube: CHAOSS.Value.March.29.2019
Description
CHAOSS.Value.March.29.2019
B
D
F
A
F
C
G
F
E
Looks
good
to
me,
I
mean
I
saw
it
earlier,
there's
another
paragraph
that
you're
gonna
have
to
include
I,
think,
which
is
why
this
issue
is
important:
okay,
I'm,
guessing
okay,
should
we
do
this
before
we
send
it
in
yeah,
I?
Think
so?
Basically,
it's
really
I
think
it's
pretty
straightforward.
Uh-Huh.
C
E
F
E
G
G
F
As
I've
been
talking
about
this
when,
when
talking
about
you,
know
kind
of
the
the
core
sort
of
social
good
that
this
can
deliver,
I
usually
express
it
in
terms
of
you
know,
trying
to
set
up
the
environment
with
metrics.
That
would
allow
people
that
would
allow
companies
to
expand
the
open
source
workforce
so
that
people
can
can
make
a
living
wage
through
open
source.
F
E
G
At
this
point,
since
so
much
pivots
off
of
kubernetes
in
the
linux
foundation,
I
would
say
that's
a
that
market
valuation
is
probably
more
important
even
than
the
significant
labor
investment,
and
so
sometimes
projects
can
you
know
like
a
tech
company
takeoff
and
recognizing
or
trying
to
estimate
those
values.
I
think
has
utility.
F
So
there
might
be
two
ways
of
expressing
this
ecosystem
value.
You
know
one
might
be
hey
if
you
could,
if
you
could
own
and
control
this
whole
ecosystem
as
a
company,
and
then
you
were
to
you
know,
put
this
company
up
for
sale.
You
know
in
an
M&A
deal
like
what
would
the
value
B
and
for
kubernetes
it
would
be
very,
very
high,
yeah
and
maybe
another
way
to
express
the
ecosystem
value.
Is
you
know
if
you
are
a
company
like
Facebook
that
has
got
this
react
ecosystem
and
you
you
wanted
to
control.
F
E
G
F
You
know
I
think
it'll
be
useful
to
to
be
able
to
express
to
ourselves
and
and
to
you
know,
people
who
are
interested
in
this
project.
Why
should
companies
and
why
should
contributors
be
interested
in
these
value,
metrics
and
so
okay,
so
I
gave
I
gave
one
hypothesis
why
they
should
be
interested
is.
F
Is
that
for
the
for
the
labor
force
you
know,
potentially
these
metrics
will
will
help
to
shape
the
ecosystem
in
such
a
way
that
it
expands
out
opportunities
for
people
to
make
a
living
wage
in
open
source,
and
maybe
there
are
maybe
we
can
think
of
reasons
why
companies
would
be
interested
in
these
value.
Metrics
and
I.
F
G
A
F
F
You
know
we
attempted
to
do
a
little
bit
of
market
segmentation
and
we
identified
four
roles.
One
is
sponsor.
One
is
an
in
sponsoring
like
a
CIO
in
a
company,
you
know
somebody
who
would
allocate
budget
and
somebody
who
would
let's
say
endorse
the
decision
to
create
and
an
open-source
program
office
within
a
company
that
would
be
a
sponsor
role.
F
Another
role
would
be
a
maintainer
which
could
either
be
a
project
maintainer
or
the
person
who
is
the
leader
of
an
open-source
program
office
that
so
that'd
be
another
role
in
this
segmentation
and
then
the
other
one
would
be
the
contributor
which
we
know
that
role
super
well
and
the
final
role
would
be
the
role
of
the
user
of
the
software.
You
know
they're
gonna,
they're
gonna
have
a
say
in
in
all
of
this,
and
so
when
we
think
about
when
we
think
about
motivations-
and
we
think
about
the,
why
do
I
care
question
I?
G
F
It's
just
rude:
that's
right:
yeah
yeah,
you
could
probably
think
about
strategies
for
for--why
contributors
would
attach
themselves
to
projects,
and
you
know
one
strategy
is
you
know:
I
need
to
put
food
in
the
fridge
and
what
can
and
I
need
to
pay
my
rent,
you
know
what's
the
fastest
path
to
that
and
another
strategy
might
be
hey,
I'm
I'm
interested
in
just
learning
mm-hmm,
and
you
know
so
within
the
contributor
world
there
can
be
different.
You
know
segments
of
people
who
have
different
motivations,
yeah.
E
G
Yeah
and
and
I
think
maybe
that's
where
some
of
the
contributor
working
on
open
source
projects
that
they're
not
paid
for
a
while
they're
working
on
projects
that
they
are
paid
for.
So
it
might
maintaining
something
that
isn't
very
sexy
or
current.
But
it's
essential
because
my
company
wants
me
to
I
may
go
off
and
become
a
contributor
to
something
like
kubernetes
or
a
project
that
is
emerging
because.
C
F
A
E
E
From
from
my
perspective,
just
trying
to
articulate
what
these
focus
areas
is
a
great
first
step
and
then
I
think
there's
gonna
be
things
obviously
under
the
hood
of
these
focus
areas,
which
are
what
what's
the
goal
associated.
This
is
the
goal
question
metric.
So
if
I
just
picked
expanding
opportunities
for
people
to
make
a
living
wage
mm-hmm,
you
know
what's
the
what's
the
goal
of
this
focus
area
and
then
underneath
there,
what
questions
do
we
need
to
answer
to
kind
of
satisfy
right
right.
E
In
themselves,
what
questions
do
we
need
to
to
to
perhaps
satisfy
our
understanding
of
that
goal?
So
if
the
goal
is
to
expand
opportunities
for
people
to
make
a
living
wage,
a
question
wouldn't
be.
You
know,
what's
the
current
cost
of
milk,
that
wouldn't
that,
wouldn't
matter,
that's
not
a
question
that
needs
to
be
answered.
So
what
are
the
questions
that
we
need
to
answer
to
address
that
goal?
E
Typically,
those
questions,
I,
don't
know,
there's
maybe
half
a
dozen
ten
questions
in
it
and,
like
I,
think
I've
told
you
before
Andy
we're
always
trying
to
just
kind
of
move
this
forward.
So
this
doesn't
have
to
be.
You
know
the
single
canonical
list
right
out
of
the
gate.
Oh
Oh
for
sure.
Is
that
a
pretty
good
canonical
list,
though
I
want
to
do
well?
E
E
A
Opportunities
for
people
to
make
a
living
wage
and
open
source
as
a
goal.
One
of
the
questions
could
be:
how
much
can
people
earn
who
work
on
this
project
and
then
a
metric
could
be
number
of
commercial
offerings
around
this
project
where
people
can
earn
or
average
pay
for
jobs
that
required
this
project,
and
this.
E
E
G
E
A
E
G
E
F
So
sometimes
you
know,
as
a
newcomer,
I've
I've
seen
in
some
situations,
people
say:
hey
we're
just
going
to
publish
a
list
of
metrics
and
Rea
agnostic
as
to
how
they
actually
get
implemented
and,
in
other
ways,
sort
of
actually
scenes.
You
know
some
really
nice
tools
that
people
have
built
so
I'm
just
curious.
F
G
You
see
it
shaking
out
so,
first
of
all,
I
think
I
think
we
can
define
the
metrics
agnostically
in
the
similar
way
to
the
way
that
we've
done
it
in
the
other
working
groups.
I
think
I
think
the
exercise
of
writing
it
down
it's
like
in
software.
You
do
it
well,
if
you've
taken
a
minute
to
decide
what
your
design
is
going
to
be,
and
then
those
different
Asians
can
drive
designs,
but
I
also
think
it
can
work
in
the
other
direction.
G
So
it
looks
at
lines
of
code
involved
and
then
there's
an
implementation
of
Kokomo
that
actually
is
derived
from
David
wheelers
decade
ago,
implementation
of
Kokomo.
So
you
look
at
code
complexity
and
it
actually
outputs
it
outputs
about.
You
know:
evaluation
numbers
like
what
would
be
the
effort
level
to
put
this
into
place.
I
think
when
it's
so
that
I'll
breathe
now
so.
F
G
Yeah
and
I
mean
you
probably
look
at
Kokomo,
or
at
least
heard
about
it.
I
have
not
so
it
comes
out
of
actually
very
bames
software
engineering
work
in
the
90s
at
USC,
and
you
know
it's
not.
It
hasn't
I've
been
looking
around,
get
out
there
and
there's
not
a
substantial
project
that
I
can
find
that
implements
it
other
than
this
SDC
one
which
is
extremely
active
and
has
a
lot
of
it,
seems
mindshare
around
it.
G
So
I
think
it's
I
think
it's
a
way
to
go,
and
certainly
is
something
that
we're
gonna
we're
experimenting
with
actively
right
now
to
see
what
an
integration
would
look
like
and
kind
of
the
way.
I,
always
the
way
that
I've
wit
were
thinking
about
doing
these
things,
a
repository
in
my
repository
bases.
So,
unlike
some
things
like
when
you're
looking
at
commits,
you
can
look
at
commits
as
they
emerge
over
time.
I
think,
code,
complexity,
I
think,
there's
a
need
to
look
at
the
evolution
of
code
complexity,
it
you're
waiving
practical,
okay,
wait!
G
It's
good
to
see.
I
just
I
have
another
meeting.
I'm
Kotaro
no
worries,
I,
didn't
know
what
the
wave
was.
It's
okay,
yeah,
so
there's
ways
to
look
at
code
complexity,
I
think
we
just
want
to
look
at
point
in
time:
estimations
I
in
most
projects
unless
they're
evolving,
rapidly
they're
not
going
to
change,
but
we
could
I
could
conceive
of
storing
snapshots
so
I
mean
some
metrics
are
have
a
temporal
dimension,
organically
and
I.
Think
that's
in
Perl
dimension
for
code
complexity
might
be
if
it
had.
F
So
so,
if
I
could
sort
of
restate
what
I
heard,
there's
kind
of
it's
like
what
we're
trying
to
produce
as
an
outcome
is
like
in
two
levels:
okay,
at
the
simplest
level,
it's
a
list
of
metrics
and
I
would
almost
interpret.
What
you
told
me
is
you
know,
a
list
of
metrics
could
almost
could
almost
take
the
form
of
a
requirements.
Spec
mm-hmm.
C
F
F
G
F
That
way,
all
right
and
then
and
then
the
second
level
thing
is
suffer
implemented
which
may
serve
to
actually
be
like
real
useable
things
that
people
can
use
or
or
maybe
the
software
implementation
is
done
as
a
learning
exercise,
because
you
learn
so
much
you
know
actually
by
getting
hands-on
and
cranking
out
the
code.
You
know
you
gain
new
incidents
that
that
you
wouldn't
have
without
doing
that
right.
D
F
G
A
F
Let's
say
so,
I
think
you
know
it's
it's
kind
of
an
interesting
time
for
me
right
now,
because
I'm,
a
newbie
and
you
know
I,
haven't
been
exposed
to
chaos
before
and
so
will
believe
been
immunized
well,
so
that
that
was
something
that
was
a
little
bit
unclear
as
to
you
know.
What
actually
does
chaos
produce
mm-hm.
H
F
A
G
G
Can
you
know
start
with
that
code
in
their
own
tooling
I,
don't
have
to
install
something
as
complex
as
auger
or
glue
or
lab
to
start
playing
with
it,
obviously,
with
auger
we're
working
toward
being
a
more
of
a
prototyping
tool
and
that's
what
we
are
but
I
think
that
our
we
haven't.
We
haven't
generated
a
ton
of
prototyping
community,
yet,
but
I
think
part
of
that
is
there's
reason.
There's
those
reasons
for
that.
We've
prototyped
a
lot
of
metrics,
though
all
right
in
a
public
way.
F
Sort
of
reaction
they
have
so
I
got
I
got
auger
installed,
I
looked
at
green,
more
labs,
actually
I
installed
Percival,
yeah
and
personnel's
great
tool
with
gathering
stuff.
You
know
my
imprint,
my
initial
impression,
looking
all
at
all
this
stuff
as
man.
This
is
like
a
real,
disparate
hodgepodge
of
stuff.
You
know:
there's
there's
like
virtual
machines,
there's
Python
scripts!
There's
just
you
know
it's
like
it's
like
a
shotgun
blast.
You
know
without
sort
of
a
unifying
theme,
but
when
I
looked
at
Percival,
I
thought.
Oh,
my
god.
This
is
actually.
F
This
actually
has
like
real,
like
solid
potential
to
be
actually
useful
and
but
but
then,
when
I
dug
into
it
a
little
bit
more.
There
are
things
that
I
didn't
quite
understand
and
I
thought
man.
It
would
really
be
great
if
there
was
like
some
some
learning
materials
or
documentation
or
if
there
was
if
there
could
be,
if
I
could
like
get
connected
with
a
mentor.
F
G
F
A
F
G
F
G
A
G
Git
repo
and
that
one
of
the
reasons
that
we're
using
it
is
because,
with
Perceval
that
data,
the
camera,
it's
personal
or
sorting
sorting
it
does
the
user
name
recognition
or
mapping,
but
but
they
put
everything
in
an
elastic
search
database
which
makes
it
actually
harder
they
consume
from
a
producing
metric
perspective.
So
the
the
labor
is
sort
of
not
on
the
front
end.
The
labor
is
on
the
back
end,
where
you're
building
something
you
want
to
consume
that
data.
F
H
A
F
G
G
G
F
B
F
G
F
G
And
it
is
it's:
it's
been
mentioned
as
a
data
source
by
others
before
it's,
not
it's
not
as
complete
as
the
github
API
stuff,
and
it's
not
as
so.
If
and
it's
if
you
wanted
to
do
like
accounting
of
everything
in
a
repository
and
a
reconciliation
of
the
names
so
far,
I've
not
found
it.
There's
too
many
API
calls
so
I
found
it
far
easier
to
clone
the
github
repo
and
then
just
go
through
it
locally
with
git
commands,
I.
Think
I'm,
not
saying
that
is
canonically
the
way
that
it
has
to
happen.
F
So
maybe
there
are
some,
maybe
there's
something
else
that
we
could.
We
could
chat
about,
and
I've
already
talked
with,
with
Georg
and
and
Matt
about
this,
but
but
not
you,
Sean
and-
and
that
is
one
of
the
things
I'd
like
to
do
I
plan
to
do
is-
is
to
put
together
a
kind
of
an
interview
program,
okay,
so
in
in
my
view
of
about
value,
metrics
I
think
there's
two
kinds
of
value:
metrics
that
would
be
useful
one
or
what
I
call
public
metrics?
F
F
F
Exercises
you
know
where
we've
gone
out
and
interviewed.
You
know
potential
customers
tell
them,
give
them
a
proposition,
see
if
it
resonates
or
not
see
what,
with
key
performance
metrics
very
using
to
drive
their
own
business.
That
that
you
know
would
would
be
relevant
yeah.
So
that's
that's
one
context
where
I've
done
that
kind
of
thing
and
then
the
other
context
is
that
at
you
know,
in
strategy
consulting
engagements,
you
know
we've
done
exercises
where
we've
gone
out
and
done
benchmarking
for
like
an
industry,
sector
mm-hmm,
and
so
you
know
we
would
go
to.
F
We're
going
to
be
talking
with
you
know
a
certain
number
of
your
peers
and
we
would
like
to
collect
confidential
data
from
you
and
in
return,
what
you'll
get
is
is
access
to
anonymized
results
and
you'll
you'll
be
able
to
know
where
you
fall.
You
know
where
your
metrics
fall.
You
know
within
your
peers
in
such
a
way
that
everything
is
anonymous.
So
you
can't
point
to
you
know
any
one
company
and
you
know
really
drill
down
and
what
they're
up
to
yeah.
G
I
think
I
think
that
would
be
about
they'll
be
valued
as
a
WZ
gonna
be
very
valued
I.
Think.
Do
you
imagine
a
way
that
that's
something
that
could
be
shared
broadly
in
a
community
or
would
that
be
something
that
would
be
built
on
top
of
some
of
the
metrics
that
we
define
is
a
business
service
offering
almost
because
I'm
just
I'm
trying
that
bridge
of
trust
like
people
don't
want
to
think
the
definitions
will
be
well-received,
universally
yeah.
The
data
that
you
describe
I
think
that
would
be
a
value.
G
F
I
think
I
think
there's
sort
of
two
things
that
can
emerge
from
that
type
of
an
exercise.
One
is
what
questions
do
people
really
care
about?
Yeah,
that's
at
some
point
and,
and
that
is
that
is
something
that
I
think
ought
to
be.
Shareable
publicly.
You
know
I,
think
yeah,
I
think
so
you
know
we've
gone
out
and
we've
talked
with
a
dozen
open-source
program
offices.
F
F
You
know
it
kind
of
depends
on
what
we
learned.
I
mean.
There's,
there's
going
to
be
a
big
discovery
process
in
terms
of
how
sensitive
are
people
about
this
information,
and
you
know
like
how
secure
are
they
in
their
jobs?
You
know,
do
they
feel
like
they've
got
really
solid
backing
and
they
can
be
open
or
is
it
a
little
bit?
Not
that
way
is
a
little
bit,
not
that
way
and
they're
more
sensitive
to
it.
So
I'm
not
sure
what
we
would
find.
F
A
A
F
Know
not
gonna
happen,
not
gonna
happen
or
they
might
say.
Yeah
I
can
talk
to
you
about
it,
hey
we're
experimental,
you
know
we're
getting
stuff
up
and
running.
You
know
we
really
want
to
come
at
this
with
an
open
mind
and-
and
you
know,
we're
really
open
to
it.
So
we
could
find
either
attitude.
I,
I,
don't
know
what
we
would
find,
but
I
think
either
in
either
case.
It'd
be
an
interesting
thing
to
know
for
sure.
F
F
G
I
think
you're
right
people,
knowing
those
questions
that
are
important
and
and
I
think
you'd
have
some
cute
open-source
project
managers,
office
directors,
whatever
that
would
be
very
clear
about
what
questions
they
wanted
to
give
others
who
would
be
kind
of
more
trying
to
figure
it
out
and
the
intersection
of
those
different
sets
of
considerations.
I
think
gonna
give
you
a
pretty
full
view
and
if
those
those
questions
are
then
operationalized
around
the
goals,
question
metrics
framework
inside
of
chaos
as
value
working
group,
then
now
you
have
something
that
is
really
valuable.
G
F
H
F
Nice
yeah
that's
great
and
there's
a
there's.
Another
colleague
that
Georg
and
I
have
her
name
is
Melvin
Corral,
oh
yeah
I!
Don't
meld!
Okay!
Okay!
Now
let
go
once
in
a
conference
call
in
here
who's
starting
the
blood
plug
mark,
okay,
right
yeah,
so
I've
been
talking
with
her
and
so
she's
interested
in
being
part
of
this
interview
process
and
she
may
not
appear
on
these
Friday
calls,
but
but
she'll
be
another
person
who
will
be
part
of
that.
B
F
G
D
G
Think
I
think
you
know
recruiting
people
into
the
working
group,
even
if
they
participate
in
the
list
and
not
on
the
calls
I
think
is
incredibly
valuable.
Yeah
I
think
that's
doing
some
work
with
the
Piast
websites
and
make
it
a
little
bit
more
clear.
Well,
okay,
I
want
to
contribute
the
metric
or
an
idea
for
a
metric.
How
do
I
do
that?
Yeah.
F
G
I,
you
know
I've
had
several
conversations
with
auger
contributors
who
have
got
this
idea.
I
want
you
this
metric
and
it
takes
a
good
deal
of
chat
back
and
forth
to
help
them
understand
how
how
do
they
do
that
right?
You
know,
and
it's
once
you
see
it,
it's
pretty
easy
before
core
Evo,
you
add
stuff,
you
do
a
pull
request
and
I.
Think
it's
the
navigation
to
what
is
the
stuff
I
add
and
what
is
the
format
and
where
is
that
that
we're
gonna
make
a
little
bit
more
transparent
through
that's
that's
efforts.
F
G
50
here
it's
good
to
hear
and
if
you
have
specific
suggestions
for
ways
that
would
make
fogger
or
good
more
lab
first
of
all
easier
than
having
it
I
encourage
you
to
create
issues
and
those
repos
as
well
just
say:
hey
I
was
a
newcomer
and
I
stumbled
on
this,
or
why
can't
it
do
this
I
think
I,
don't
think
any
of
us
know
ego
wrapped
up
in
it.
We
would
like
to
hear
what's
not
working
for
someone
who's
actually
loaded
the
stuff
and
tried
it
out
and
found
it
lacking.
F
So
so
I
will
do
that
and
I'll
just
say
my
number
one.
You
know
if
you
can
find
somebody
who
just
makes
it
their
job
to
figure
out
how
to
make
all
of
these
tools.
Consumable
that'd
be
a
great
role
for
somebody.
Yeah
and
you
know
doing
it
through
like
that,
might
be
a
really
nice,
like
google
Summer
of
Code.
If
you,
if
you've
got
some
people
who
are
coming
in
for
that,
I've
got
one
person
interested
in
auger,
so.
F
G
F
F
A
Know
I
was
just
working
on
my
action
item
so
moving
forward.
It
was
always
good
to
remind
people
that
our
weekly
call
is
coming
up,
and
so
what
some
working
groups
have
started
doing
is
assigning
a
facilitator
for
the
next
meeting,
who
is
responsible
for
setting
up
reminder
at
least
one
day
in
advance.