►
From YouTube: CHAOSS.Common.June.6.2019
Description
CHAOSS.Common.June.6.2019
A
A
B
A
All
right,
okay,
I'm
hopelessly
unprepared
for
this,
because
I've
been
in
meetings
all
day
and
so
I'm
just
so,
he
decided
we're
gonna
talk
about
the
Metra
Solis
and
we
decided
that
this
is
kind
of
a
working
meeting
to
figure
out
what
we
could
release.
So
that's
where
we
were
last
time
and
then
Matt
followed
up
with
a
couple
of
people
on
some
areas
that
we
wanted
to
focus
on,
which
are
basically
our
three
focus
areas.
A
A
A
A
D
D
C
B
C
E
A
A
A
A
A
G
A
A
A
F
F
A
A
D
A
A
A
C
A
B
J
J
B
A
I
D
A
A
C
A
C
D
D
A
C
I
I
C
A
C
It
could
be
I
mean
the
whole
thing
I
mean
you
can
part
of
the
problem
here
is
like
you
could
say,
organizational
diversity
and
organizational
affiliation
are
basically
synonymous
with
each
other.
So
in
that
level
you
do
get
into
the
collection
standpoint.
You
know
the
things
that
Toby
and
I
were
talking
about.
Were
you
know
at
some
point
there
have
to
be.
You
know
when
I
keep
calling
atomic
metrics
I
think
that
we're
just
gonna
have
to
pick
one
and
say
like
organizational
diversity
is
the
atomic
metric
right
and
that
will
be
the
one.
C
F
And
with
with
respect
to
bring
some
more
context
with
other
from
other
people,
we
were
working
with
up
on
a
stack.
They
were
producing
their
own
pile
for
what
they
define
as
mechanization
al
diversity.
You
can
have
a
look
at
please
these
other
dashboards,
so
basically
the
entry
panel.
If
you
go
to
the
down
to
this,
there
are
three
three
four
five
widgets
at
my
might
be
useful.
Here
that
says:
corporate
diversity.
Evolution
proposed
changes,
corporate
diversity,
evolution
in
terms
of
the
issue,
creation
and
in
terms
of
mainly
this
activity.
F
C
F
G
A
When
I'm,
what
I'm
realizing
is
that
this
one
is
complex
enough,
that
I
think
it's
gonna
be
hard
to
brainstorm
as
a
group
I
have
a
hard
time
doing
stuff
like
this
as
a
group,
it's
always
easier
for
me
to
sit
down
and
think
about
things
that
are
complex
and
and
then
formulate
thoughts.
Other
people
might
be
better
at
it.
I'm
just
not
sure
how
we
proceed
with
this
particular
with
this
particular
one
right
now.
I
would.
F
D
B
We've
generally
erred
towards
providing
descriptive,
metrics,
so
not
providing
anything
other
than
percentage.
You
know
like
some
percentages
if
I'm
looking
for
organizational
affiliation
and
organizational
diversity,
probably
the
way
we
would
handle
it
is
to
say
that
we
want
to
understand
how
many
total
organizations
are
contributing
to
a
project
and
a
larger
n
is
better
and
I
think
that
we,
it
would
generally
be
keeping
those
discrete
metric
like
that,
would
be
a
discrete
metric
and
then
another
discrete
metric
might
be
something
along
the
lines
of
look.
B
What
might
include
looking
at
the
number
of
individuals
affiliated
with
each
organization,
so
you
know
how
much
of
the
contribution
comes
from
different
organizations.
You
could
have
10
organizations
but
to
really
doing
90%
of
the
work
and
so
organizational.
The
other
thing
I
would
say
about
organizational
diversity
is
you're
sort
of
getting
into
elephant
factor,
which
is
a
metric
of
organizational
diversity.
Basically,
you
know
how
many
organizations
have
to
give
up
on
the
project
for
it
to
die.
I
think.
B
Right
then,
that's
why
I'm
saying
like
organizational
diversity
is
you
know
the
general
tendency
for
these
kinds
of
quantitative
metrics
is,
has
been
an
evolution
any
way
to
keep
them
kind
of
value
neutral
and
then,
where
appropriate,
providing
parameters.
So
one
filter
or
parameter
that
we
might
consider
describing
on
this
metric
would
be
the
time
period
that
you're
looking
at.
So
you
may
be
most
interested
in
diversity
over
the
past
two
years
or
you
may
be
interested
in
diversity
for
different
purpose
over
the
life
of
a
project,
and
those
are
two
different
things.
C
This
whole
combination
thing:
this
is
what
we
told
me
and
I
ran
into
during
our
discussions.
It's
like
nothing
really
stands
alone.
Okay,
so
you
okay,
so
you
know,
okay,
how
many
organizations
are
in
this
project?
You
know,
but
then
then
you
have
to
figure
out.
Well,
how
are
you
measuring
you're
measuring
the
number
of
contributions,
because
both
of
those
things
are
completely
different?
D
F
A
I
A
I
F
D
C
A
June
is
for
the
what
we're
calling
feature
freeze,
so
we
should
have
links
to
all
of
the
metrics
that
we're
gonna
put
in
the
in
the
release,
because
I
and
I
think
part
of
that
was
because
I
think
some
of
the
governing
board
members
wanted
to
take
a
look
and
have
some
time
to
provide
feedback.
So
we'll
still
be
able
to
change
the
metrics
after
a
feature.
Freeze
we'll
still
be
able
to
make,
you
know,
incorporate
feedback
or
fix
bugs
or
whatever
okay,
but
we
won't
be
able
to
add
new
metrics
after
feature.
Freeze.
A
D
F
F
So
you
cannot
really
think,
and
then
we
what
we
have
there
is
the
average
and
median
time
to
close
on
to
first
response,
and
the
goal
of
thought
of
this
is
all
as
we
in
at
the
beginning.
The
main
goal
here
is
finding
out
whether
we
are
attending
tickets
early
and
solving
them
in
a
reasonable
time,
and
then.
K
K
F
A
G
A
F
A
F
A
F
F
F
A
H
A
G
I
B
B
G
C
A
D
B
B
K
B
B
F
F
Would
you
say,
for
instance,
I
remember
right
now,
conversation
with
people,
certain
communities
and
they
were
really
interested
in
understanding
what's
going
on
with
volunteers,
and
for
this
they
wanted
to
be
really
sure
that
volunteers
were
having
kind
of
a
special
treatment,
so
they
were
for
producing
the
tank.
The
first
response
in
this
case
would
it
be
a
use
case,
yeah.
B
I
think
so,
I
think
somebody
like
so
I've,
like
an
evolution.
I
created
a
community
manager
use
case
and
I.
Think
a
lot
of
these
metrics
in
common
are
gonna
fall
under
that
general
community
manager
use
case.
It's
somebody's
managing
a
community
and
trying
to
understand
something
about
it,
and
so
the
actor
of
a
community
manager
or
open
source
program,
office
manager,
I
think
in
terms
of
metrics
consumption,
I.
Think
of
those
two
categories
of
jobs
as
being
the
main
actors
consuming.
F
F
B
Think
it's
I
think
right
now,
it's
okay
to
just
define
it
with
the
description.
That's
helpful
for
people
to
orient
themselves
to
the
extent
that
we
develop
more
elaborate
or
fully
developed
use
cases
or
there
are.
There
is
a
blog
post
that
actually
describes
the
situation
in
greater
detail.
I
think
that's
going
to
be
helpful.
Okay
for
people
I
think
someone
new
to
Kaos
is
probably
not
going
to
digest
a
paragraph
and
understand
all
of
it.
Well
so
sometimes
we've
included
items
like
blog
posts
in
references.
Sometimes
we've
included
academic
papers
in
references.
K
F
K
A
Cleaning
up
the
documents
for
these
two
metrics
before
the
next
meeting
and
then
just
a
reminder
that
we
are
meeting
again
next
week.
We're
gonna
meet
every
week
until
the
future
freeze,
at
least
to
work,
continue
working
on
the
metrics
so
that
we
can
get
something
out
the
door
from
the
common
metrics
working
group
in
the
release.
A
D
A
E
E
A
The
other
thing
we
should
probably
do
and
I'm
not
gonna
bother
creating
an
action
items.
It's
not
it's
not
super
time-sensitive,
but
we
should
probably
start
creating
the
focus
areas
for
the
other
two.
So
we
created
the
focus
area
in
the
repository
for
organizational
diversity,
but
we
haven't
done
it
yet
for
responsiveness,
metrics
or
geography
and
I
feel
like
we're
almost
getting
to
the
point
where
we
have
enough
of
the
you
know
the
lists
of
metrics
defined
that
we
can
probably
start
taking
a
crack
at
pull
requests
for
those
as
well.