►
From YouTube: CHAOSS.Value.April.19.2019
Description
CHAOSS.Value.April.19.2019
C
Well,
let's
see
this
is
the
chaos
value
group
today
is
Friday
the
19th
of
April
and
let's
just
go
through
our
agenda
that
we
have
up
here
so
honor
notes.
First,
agenda
item
is
to
review
our
action
items
from
last
week
to
talk
about
software
implementation
of
value.
Metrics
I
would
like
to
add
entries
to
Georg
focus
area
worksheet
for
the
value
group.
C
I
think
we
could
pick
a
crack
at
that
together
on
today,
and
also
personally
last
week,
we
talked
about
putting
together
a
grant
tracking
type
of
a
worksheet
to
track
grant
opportunities
and
I'd
love
to
get
that
started
today.
If
we
have
time,
is
there
anything
else
that
people
would
like
to
talk
about.
B
Yeah
so
I
had
one
item
which
was
with
this
group
because
of
last
week
there
was
an
expressed
interest
of
really
working
on
the
tooling
in
line
with
the
metrics.
You
know,
I
mean
keeping
those
two
really
close
to
one
another
and
I
agree.
I
totally
agree
with
that
and
I
brought
that
up
with
the
common
working
group,
and
they
would
also
like
to
do
the
same
thing
and
I
think
risk
could
do
something
very
similar.
C
B
Approach
or
I'd
be
taking
a
look
at
it
could
be
a
variety
of
things,
but
it
you
know
it
could
be
taking
a
look
at
like
a
data
schema
and
actually
seeing
what
was
available
in
a
schema
and
what
you
can
and
can't
do.
Yes,
it
might
actually
be
kind
of
like
wire
framing
what
the
output
might
look
like.
It
might
be,
I,
don't
know
what
anything
along
the
kind
of
the
development
path.
Yeah.
C
B
B
C
A
C
B
C
C
Probably
that's
going
to
be
Sean,
at
least
with
regards
to
the
vision
and-
and
you
know
maybe,
if
Herschel
gets
accepted
for
the
google
summer
code,
maybe
maybe
Herschel
is
also
you
know,
kind
of
that
lead
person
for
the
for
the
software
implementation.
So
so
in
that
standing
discussion
you
know
probably
that's
going
to
be
led
by
Sean
or
or
Harshal
or
some
combination
of
the
two
or
whoever
else
comes
along
to.
You
know
really
get
involved
in
that.
C
C
C
So
that
sounds
great,
so,
let's
see,
would
it
make
sense
to
just
go
through
the
list
of
agenda
items
then
start
by
talking
about
action
items
from
last
week,
yep,
okay,
they
see
some
action
items
with
my
name
associated
with
it
and
I
have
not
done
either
one
so
I
great
well
moving
forward.
Then
what
happen?
Let's
start
out
with
me
hanging
my
head
in
shame.
C
B
B
C
B
C
C
B
C
C
B
You're
thinking
about
both
grimore
lab
and
auger,
just
thinking
about
the
UI
structure
that
both
of
them
have
mm-hmm
the
the
goal
for
grimore
lab
in
my
mind,
is
to
create
panels
using
their
Dirk
Cabana
interface
in
each
one
of
those
panels
is
representative
of
the
different
working
groups,
so
there
would
be
a
panel
for
risk.
There
would
be
a
panel
for
value.
You
get
the
idea,
yeah
so
and
I
know
that
the
folks
at
grimore
lab
have
been
amenable
to
this
approach.
So.
A
B
Know
perhaps
one
of
our
points
of
investigation
is
the
deployment
of
a
value
panel
yeah
and
what
that
would
look
like
I
think
that
if
that
happened
out
of
this
value
group,
that
would
be
the
first
group
to
actually
do
such
a
thing.
You
know
I
contribute
a
panel
back
to
Chrome
or
lab,
and
that
would
it
would
be
great
because
it
would
kind
of
set
the
workflow
on
how
to
get
that
done.
B
Yeah
for
other
working
groups
and
then,
of
course,
on
the
panels,
are
the
specific
metrics
themselves,
so
that
I
think
that's
kind
of
another
question
of
deploying
metrics
using
the
using
the
grimore
lab.
You
know
the
personal
data
data
aggregator
in
the
back
and
then
as
far
as
auger
goes
auger
takes
a
tab
structure,
so
they
have
tabs
across
the
top.
So
like
an
evolution,
tab
and
our
risk
tab
and
a
value,
tab
and
honest,
you
know
it's
kind
of
the
same
as
the
panels
right.
B
C
Well,
that
sounds
great.
The
the
thing
that
I
think
makes
us
maybe
a
little
bit
interesting.
A
little
different
is
that
you
know.
Last
week
we
came
up
with
this
idea
of
parameterised
dashboards
where,
for
example,
maybe
we
would
we
could
calculate
the
you
know
we
could.
We
could
measure,
let's
say
the
number
of
pull
requests
on
a
project
and
then
the
parameter
might
be.
What's
the
economic
value,
the
average
economic
value
of
each
pull
request
and
that
might
be
different
organization
to
organization.
So.
C
C
B
A
A
B
A
I
think
right
now,
because
we
want
to
start
with
issues,
it
would
be
a
matter
of
tweaking
that
value
paged
at
the
issue,
information
which
already
exists
in
the
growth
maturity
and
decline
tab,
so
the
first
step
might
be
simple
or
someone
to
go
in.
Look
at
the
source
code
figure
out
how
what
did
it?
How
it's
done
in
growth,
maturity
and
decline
and
replicate
the
exact
same
code
on
the
value
page
just
for
commits
sure
that.
C
C
C
C
C
A
C
B
A
A
A
C
C
B
A
C
E
E
There
may
be
a
matrix
like
what
is
the
time.
Duration
for
a
first
response
for
a
pull
request.
That's
the
metric.
We
are
having
in
wgg
MD
working
group,
so
that
can
be
relevant
here
as
well.
If
the
main
trainers
are
active
in
the
project,
so
that
would
be
that
would
the
response
time
would
be
low
for
any
pull
request,
and
it
would
be
better
to
get
involved
in
that
particular
project.
A
E
A
A
So
I
think
they
have
a
good
good
number
of
questions
for
living-wage
this
just
out
of
nowhere,
we
improve
the
focus
around
living.
Wage
was
really
awesome.
I
know
this
was
not
the
main
focus
area
that
we
wanted
to
focus
on,
but
it's
always
good
to
get
the
ideas
down
and
document
them
any
more
thoughts
on
living,
wage
and
return
to
the
labor
investment
metric.