►
From YouTube: Measuring Community Health - CHAOSS Initiative
Description
Measuring Community Health - CHAOSS
Georg Link (Bitergia)
Dr. Matt Germonprez (University of Nebraska at Omaha)
OpenShift Commons Gathering on Community Development
June 15, 2020
A
A
minute
ago,
so
the
automat
welcome
to
Topher.
Today
what
we
have
is
introduction
to
the
KH
community.
This
is
the
acronym
for
community
health,
analytics
protein
source
software
and
so
I
had
a
great
pleasure
to
meet
Matt
and
anger
from
2016-2017
when
all
these
projects
started.
So
this
was
announced
in
September
2017,
laying
one
of
the
open
source
emits
vital
information.
B
What
we
mean
by
that
is
that
we
want
to
look
and
understand
at
the
potential
that
our
open
source
projects
and
communities
can
continue
developing
quality
software
and
in
when
we
look
at
the
literature,
there
are
different
ways
that
we
can
look
at
communities
to
understand.
If
they
have
everything
they
need.
We
can
look
at
the
code
make
sure
that
it
is
of
high
quality.
We
can
look
at
the
community
to
understand.
Who
are
the
people
involved?
Are
they
being
active?
B
Is
there
good
diversity
and
we
can
look
at
resources,
make
sure
that
our
communities
and
projects
have
the
finances
to
pay
for
the
servers
or
if
they
need
special
infrastructure,
that
everything
we
need
for?
Our
communities
is
in
place
or,
as
we
heard
in
the
last
session,
the
Commons
that
the
Commons
is
healthy,
and
this
is
a
matter
issue
for
a
lot
of
different
stakeholders.
B
B
Organizations
care
to
minimize
their
risks,
but
also
to
leverage
their
influence
and
impact
and
have
an
assessment
of
how
they're
doing
in
the
communities
the
communities
themselves
care
because
they
want
to
be
inviting
places
for
their
community
members
and
they
want
to
just
as
contributors,
enjoy
the
work
that
they're
doing
foundations
who
are
doers
of
open-source
projects
and
communities.
They
care
about
the
health
of
their
projects,
because
it
can
give
them
an
indication
whether
they
need
to
have
interventions
or
it
can
also
help
them
identify
where
the
best
practices
are.
B
B
It's
really
hard
now,
with
open
source
growing,
we've
seen
an
influx
of
organizations
and
companies
coming
into
open
source,
and
there
are
lots
of
people
who
are
just
learning.
What
open
source
is,
how
the
communities
work
and
so
on.
So
we
need
to
take
that
knowledge
of
community
health
and
come
up
with
a
different
way
that
it's
more
accessible
to
everyone,
and
this
is
what
this
talk
is
about.
How
together,
we
can
be
better
stronger,
faster
for
understanding
community
health.
B
This
better
stronger,
faster,
comes
from
a
TV
show
the
Six
Million
Dollar
Man,
where
the
person
was
assembled
and
improved
through
bionics,
and
we
can
do
this
together.
We
can
figure
out
how
what
is
community
health?
How
can
we
understand
it
so
that
we
all
can
be
better,
stronger,
faster
and
so,
let's
walk
through
start
with
together
the
chaos
community
is
this
place
where
we
can
work
on
this
together?
B
We
started
this
project
in
2017
at
the
Linux
Foundation,
to
create
analytics
and
metrics
to
help
understand
community
health
to
have
procedures
and
practices
that
we
can
share
and
understand
to,
and
so
it's
a
group
of
industry
professionals
and
academics
and
open-source
practitioners
from
a
variety
of
different
projects
and
companies
that
come
together
and
chaos
is
the
platform
to
talk
through
the
thorny
issues
of
what
is
community
health
and
how
to
be
assessing
it.
And
in
this
work
we
are
building
practices
to
become
better.
B
We're
also
building
a
stronger
foundation
through
metrics
and
in
the
chaos
project.
Just
to
give
a
little
background
when
we
started
the
project
we
had
that
we
started
collecting
a
list
of
metrics
that
everyone
was
interested
in.
It
was
a
really
long
list
and
in
defining
them
we
decided
to
split
up
into
working
groups
that
had
specific
focus.
Si
focuses
poky.
B
The
diversity
and
inclusion
working
group
looks
at
metrics
to
understand
how
welcoming
and
inclusive
our
community
is
and
having
metrics
around
that
the
risk
working
group
looks
at
communities
and
projects
and
unders
to
understand
what
is
the
business
risk?
I
don't
want
to
be
stuck
with
the
project
that
I've
used
as
an
organization
in
my
innovation
stream
and
then
suddenly
I'm
left
with
maintaining
it
myself.
So
we
want
to
understand
that
or
license
risk.
B
You
want
to
make
sure
that
there's
compatibility
in
the
licenses
and
it's
compatible
with
not
only
inside
the
project
but
also
when
we
use
it
ourselves.
We
want
to
understand
the
evolution.
This
is
the
third
working
group
is
a
project
growing.
Is
it
already
mature
or
is
it
in
decline,
understanding
the
activity
levels
and
how
that
fits
in
with
the
history
and
the
story
of
the
community
is
super
important.
B
The
value
working
group
asks
questions
around.
What's
the
value?
What's
the
business
value
monetary
value
for
organizations?
What
about
for
individual
contributors?
Is
there
value
in
contributing
to
a
specific
project
or
community?
Maybe
there
is
because
their
job
postings
out
there
for
skills
that
I
can
build
in
this
community
or
what's
the
social
or
the
broader
value
for
society?
Is
this
community
project
making
an
impact
in
the
world,
and
then
we
have
common
metrics?
B
This
is
a
working
group
where
we
sometimes
call
it
the
work
group
for
the
misfit
metrics
that
don't
fit
anywhere
else
or
that
have
broader
implications,
understanding
what
organizations
our
contributors
work
for
understanding
this
organization
affiliation
then
helps
us
to
identify
other
areas
like
the
risk
for
diversity,
inclusion,
and
so
that's
where
the
common
working
groups
come
in
now.
Building
out.
B
We
identify
the
data
sources
and
solve
the
problem
of
collecting
the
data,
we're
solving
the
issue
of
how
do
we
present
the
data
and
the
metrics,
the
Anila
dicks
to
users,
so
that
you
can
start
doing
that
more
quickly.
We
can
also
trial
new
metrics
and
ideas
and
practice,
because
sometimes
someone
comes
to
the
cares
project
says:
hey
I'm,
really
interested
in
understanding
this
part
of
our
community.
What
is
the
data?
B
Remote
lab,
for
example,
has
Patricia
as
a
company
that
provides
services
around
this
project
and
I
know.
The
open
community
has
a
dashboard
that
is
powered
by
groom
or
lab.
Agar
is
also
being
used
by
companies
like
Twitter
or
VMware,
and
then
Craig.
It
is
a
pool
that
allows
to
see
like
dip
blame
who
has
changed
something
in
the
source
code,
but
not
at
the
line
level.
It
goes
down
to
the
token
level
or
who
introduced
this
variable
or
edited
last,
and
that
is
heavily
used
by
the
Linux
kernel
community.
B
So
we
have
software,
it's
out
there
available
for
you,
everyone
to
use
and
through
our
work
on
becoming
better
stronger,
faster
gather.
We
have
learned
several
things
that
I
want
to
share
with
you
if
you're
thinking
about
starting
your
metrics
journey
or
if
you're,
already
looking
at
metrics
and
analytics
for
community
health,
we
recommend
or
we've
seen
that
it's
really
important
to
listen.
B
B
Question
metric
approach,
TQM
start
with
what
you
want
to
accomplish
as
a
community
as
a
foundation
as
a
company
and
ask
yourself
what
do
I
need
to
know
whether
or
not
I'm
reaching
that
goal,
or
that
can
help
me
find
the
way
for
reaching
that
goal,
and
that
is
where
the
metrics
then
come
in
and
using
the
gold
question.
Metric
approach
gives
a
direct
rationale
for.
Why
am
I
looking
at
this
data
point
but
data
out
by
itself
for
metrics
by
themselves
or
nice?
Pretty
graphs
are
not
enough.
B
You
need
to
tell
a
story
with
the
data
community.
Health
is
very
context
driven
and
let's
say
we
are
looking
at
a
graph
that
shows
the
number
of
new
issues
in
the
project
have
gone
up.
That
can
be
a
good
thing
or
a
bad
thing.
Maybe
there
are
more
and
more
users
who
are
asking
questions
which
can
be
good,
but
maybe
it
means
the
last
release
had
a
lot
of
bugs
and
they're
being
reported,
or
maybe
it's
not
even
related
to
the
project.
B
B
A
word
of
advice
or
caution
here
is
to
avoid
gaming
of
metrics.
If
you
have
incentives
around
metrics,
let's
say
once
you
hit
100
commits
on
the
code
base,
you're
being
recognized
as
a
frequent
contributor,
people
will
start
to
change
their
behavior
to
hit
those
metrics
and
commits.
If
you
have
contributed
to
repository,
you
know
you
can
make
small
and
big
commits.
B
You
can
have
thoughtful
commits
that
touch
a
lot
of
different
files
or
you
can
separate
them
out
into
multiple
commits,
and
once
you
have
that
metric,
the
incentive
is
to
contribute
to
a
lot
of
permits,
whatever
it
takes,
and
that
might
distract
from
actually
accomplishing
the
goal
of
developing
quality
software
or
the
documentation
or
whatever
the
community
needs
that
leads
into
the
next
point.
You
want
to
value
all
contributions,
because
it's
easy
to
look
at
the
commit
history
and
focus
on
that.
B
But
a
healthy,
open
source
project
and
community
has
a
lot
of
different
types
of
contributions.
We
need
marketers
who
advertise
our
project.
We
need
people
who
help
in
forums
answer
questions
about
triaging
is
very
important
so
that
the
people
who
can
answer
know
which
issues
to
focus
on
versus
the
ones
who
can
actually
dive
into
the
code
and
need
to
do
debugging,
so
open
source
projects
and
communities
have
a
lot
of
different
work.
That
needs
to
be
done
and
we
want
to
find
data
that
represents
all
of
this
different
work.
C
Thanks
Georg
a
great
website
just
to
kind
of
reiterate
a
few
things,
so
thanks,
Kari
that
this
was
great,
so
I'm
the
cast
community
is,
is
not
just
a
single
super
expert
but
we're
a
collection
of
people
with
an
interest
and
a
passion
to
think
about
open-source
community
health.
So
we
encourage
you
to
come
and
be
part
of
part
of
that
team.
Right,
be
part
of
that
part
of
that
group.
That's
investigating
this
and
together
we
can
start
understanding
this
complex
issue
in
more
detail.
C
So
that's
really
important
and,
as
Garrett
pointed
out,
one
of
the
real
key
things
in
the
Chaos
project
is
we.
We
don't
just
develop
metrics
for
metrics
sake
right,
and
so
one
of
the
things
that
we've
learned
is
that
there's
kind
of
a
push
to
develop
metrics
just
right
out
of
the
gate,
but
they're
not
provided
kind
of
that
goal.
Question
metric:
we
don't
know
what
the
goal
of
the
metric
is.
C
We
don't
understand
the
context,
so
we
take
a
considerably
more
systematic
approach
towards
developing
metrics,
which
is
kind
of
first
thinking
about
why
we
might
even
what
we
need
to
understand
in
the
first
place
and
from
there
we
have
the
development
of
metrics
that
can
inform
that
the
KSR
project
also
works
really
hard,
as
gay
as
Georg
mentioned
on
practices.
So
we
work
to
draw
out
hard
to
see.
C
Metrics
though
some
metrics
are
observable
in
trace,
data
like
git
repositories,
right
and
others
are
considerably
more
difficult
to
see,
and
so,
for
example,
around
our
work
in
diversity
and
inclusion.
So
not
only
does
the
chaos
project
develop
software
to
help
bring
those
trace
data
metrics
forward,
but
also
practices
or
processes
to
bring
those
I'll
say
non
trace
data
metrics
forward
as
well.
So
we
don't
want
the
metrics
just
to
live
in
isolation.
C
We
don't
just
develop
those
metrics
and
say
you
know
done,
and
so
we
work
on
these
things
as
well,
and
then
this
is
also
a
scary
pointed
out
context.
Does
matter
right,
so
it's
it's
challenging
in
the
chaos
project
for
for
us
to
ever
say,
and
we
won't
that
this
is
a
healthy
project
and
this
is
an
unhealthy
project.
That's
not
the
goal
of
the
chaos
project,
so
our
goal
is
to
give
you
the
tools
by
which
you
can
then
make
that
assessment
locally
as
an
important
decision
for
yourself
right.
C
So
what
context
does
matter
so
right
before
just
thinking
about
red
hat,
brett
hat
has
probably
a
few
open
source
projects
they
care
about
right,
but
I
would
suspect
that
they
are
not
all
understood
in
the
same
way
right.
So
a
metric
in
community,
a
might
be,
might
have
a
very
different
impact
than
that
same
metric
in
community
B.
So
it's
really
up
to
to
the
individuals
in
their
local
context,
understand
and
think
about
what
those
metrics
mean.
C
So
I
just
wanted
to
reiterate
some
of
those
points,
and
we
can
talk
about
those
as
more
as
well.
So
there
are
a
lot
of
ways
that
you
can
connect
with
with
the
Kaos
project.
So
I'll
give
a
nod
here
to
K
org
and
many
other
people
that
they've
been
really
making
some
great
advancements
on
the
Kaos
cast.
C
So
this
is
a
weekly
podcast
in
from
the
Kaos
project
that
brings
different
people
from
outside
of
the
Kaos
project,
sometimes
internals
of
the
Kaos
project
to
think
about
what
open-source
community
health
can
mean
to
them
right,
and
so
it's
it's
great.
It
gives
you
a
look
under
the
hood
at
the
project
itself,
but
it
also
gives
you
a
look
as
to
how
the
work
is
having
an
impact
beyond
just
the
project
itself.
One.
A
B
C
That
we
think
about
metrics
is
is,
is
building
blocks,
so
at
the
moment
we
have
40
some-odd
metrics
that
are
released
as
part
of
the
current
release
and
the
expectation
isn't
that
you
would
use
every
single
metric
to
analyze
community
health
for
your
particular
interests,
but
that
you
can
assemble
those
blocks
accordingly.
In
your
own
context,
I
do
think
one
of
the
things
that
we're
going
to
think
about
in
the
KSR
project
is,
as
our
number
of
metrics
continues
to
grow.
C
C
We're
starting
to
take
on
right
now
software
can
be
the
software
that
Georg
mentioned
can
be
really
an
important
way
for
you
to
start
seeing
this
trace
data
in
in
kind
of
a
time
history,
so
you
can
start
looking
at
it
over
time.
You
can
look
at
the
evolution
of
things
and
in
fact
you
can
start
even
comparing
projects
between
each
other.
C
So
if
there
is
an
aspirational
project
that
you
might
have,
an
interest
in
tooling
can
help
kind
of
reveal
how
an
aspirational
project
is
performing
and
how
you
might
want
to
think
about
your
own
activity
within
your
projects
and
then
the
chaos
community
right,
I
kind
of
mentioned
this.
We're
not
we're
not
just
a
single
super
expert
or
a
collection
of
people
trying
to
trying
to
understand.
C
C
Take
a
look
at
the
metrics
that
we
have.
So
if
you
just
go
to
Kass
that
community
slashed
metrics
you'll
see
the
current
release,
we're
going
to
be
doing
a
new
release
in
about
six
weeks
from
now
contribute
to
the
software,
as
georg
pointed
out,
all
pretty
accessible
and
pretty
easy
to
contribute
to.
And
then
we
have
weekly
working
group
meetings.
So
each
of
the
working
groups
that
georg
had
listed
earlier
has
weekly
or
bi-weekly
meetings.
B
C
The
software
groups
have
their
own
calls
and
we
have
an
asia-pacific
call
as
well
that
meets
every
other
week
on
join
our
mail
list,
nice
activity
on
there-
and
you
know,
don't
let
us
know
what
you're
thinking
about
community
health,
so
wood
together
replaced
with
the
chaos
community.
That's
us
right
to
help
us
build
this
better,
stronger,
faster
help
us
build
a
better
way
of
understanding
community
health.
C
We're
listening,
we're
not
just
pushing
our
ideas
right,
we're
trying
to
capture
the
ideas
that
people
have,
because
a
lot
of
people
have
thought
about
this
for
a
long
time,
next
slide
and
so
I
think
we're
gonna
be
moving
into
a
live
chat.
Is
that
right
right
now?
I'm,
not
sure
how
you
want
to
proceed
with
this
right.
A
Yeah,
so
thank
you
for
for
the
great
presentation.
There
are
a
couple
of
comments
now
in
to
each
I
can
see
sir
then
I
will
I
will
start
with
you
there
the
question
today
and
we
can
start
with
the
open
discussion
and
they
asked
me
anything
to
anyone
here
in
the
chat
to
each
or
any
other
platform.
Please
feel
free
to
ask
anything.
So
it's
politically
the
what
the
question
we
have
is
and
I'm
literally
reading
here
the
way
I
do
analysis.
Visualization
doesn't
follow
this
approach.
A
This
focus
on
having
all
the
data
in
one
place,
and
this
is
what
do
I
need
to
serve.
The
question
he
has
is
what
do
I
need
to
measure
and
can
a
mystery,
but
that's
my
first
question.
So
it
says
criminal
data
first
before
I
have
a
question,
sets
up
an
expensive
game
board
or
gaming,
though
I
don't
have
an
opinion
or
comment.
I.
A
A
B
The
question
of
what
to
measure
is
really
a
question
of
what
is
your
goal?
What
do
you
need
the
metrics
and
data
for
and
without
knowing
that
first
we
can.
We
can
make
a
recommendation
of
40-plus
metrics
that
we
have
in
the
case
project
right
now,
but
without
actually
knowing
why
you're
looking
at
metrics
in
the
first
place,
it's
hard
to
narrow
that
down
and
not
drown
in
data,
because
once
you
start
opening
the
data
firehose,
you
know
there's
so
much
to
take
in.
D
A
D
One
thing
that
people
I
think
protect
when
they're
considering
data
is
that
they
already
have
the
data.
It's
simply
not
assembled
the
vast
majority
of
data
that
you
are
going
to
be
using
for
this
metric,
these
metrics
it's
generated
right.
You
can
gather
it
from
various
sources
on
the
fly
and
yes,
it
will
take
time
to
do
so,
but
you
are
creating
it
through
the
acts
of
your
community,
and
so
you
don't
necessarily
have
to
flip
the
switch
and
start
assembling
it
right
then.
D
So,
if
it's,
you
are
worried
about
having
data
overload
right
and
getting
just
buried
and
too
many
data
just
wait
and
take
that
time
to
figure
out
what
you
actually
do
want.
What
are
your
goals
and
that's
the
primary
problem
I've
seen
almost
every
single
project
hell
every
single
company
I've
worked
with.
Is
they
don't
answer
the
question?
What
are
we
trying
to
accomplish
here
and
if
you
don't
have
that
answer,
then
you
can't
see
whether
you're
even
on
track
for
it
right.
If
you
can't
answer
what
success
looks
like,
then
you
can't
identify
failure.
D
C
B
C
All
of
these
metrics
great
so
sometimes
it's,
it's
really
just
small
steps,
I
would
say
which
would
help
with
this
reducing
the
sea
of
data.
That's
out
in
front
of
you
just
ask
questions
about
issues,
ash
questions,
about
pull
requests
or
very
simple
questions
and
see
if
I
help
you
make
more
informed
decisions
over
time.
Well,.
D
One
of
the
things
I
found
very
helpful
and
it
sounds
like
a
pitch,
but
it's
not
because
I've
legitimately
found
it
really
helpful.
Is
a
Victoria
launched
cauldron
earlier
this
year,
cauldron,
IO
and
the
public
dashboard
for
cauldron.
Io
does
not
have
every
metric
Under
the
Sun
for
a
free
and
open-source
software
project.
So
for
people
who
don't
know
cauldron,
Daioh
is
a
service
which
you
can
use
for
any
free
and
open
source.
D
We're
project
together,
that's
and
data
and
metrics,
and
display
them
to
people
and
just
sort
of
track
various
metrics
over
time,
and
it
is
just
absolutely
brilliant.
It's
super
useful,
but
it
does
start
from
just
those
sorts
of
things
that
nearly
everyone
is
going
to
care
about
right.
What's
your
number
of
contributions
over
time
for
the
companies
or
where
are
people
coming
from
to
contribute
to
your
project
right?
Even
those
bare
bones,
basic
things
are
incredibly
useful
and,
as
matt
said,
you
know,
and
and
georg
get
off
zero.
D
The
way
I
phrase
it
is
baby,
steps
are
still
steps
right,
so
even
taking
one
tiny,
small
movement
to
gather
something
or
to
get
something
going
can
help
to
set.
The
mindset
of
the
entire
community
around
paying
attention
to
the
these
numbers
in
some
way
and
and
cauldron
has
really
helped
a
great
deal
with
that.
As
I
show
it
to
me-
and
these
are
like
oh
wow-
we
can
actually
see
this
stuff
of
it.
I.
C
D
B
A
Yeah
having
having
questions
great
so
yes,
I
just
wanted
to
serve
with
you,
so
I
think
it
was
in
some
Oscar
years
ago.
We
were
one
of
this
I,
don't
remember
where
exactly
but
don't
throw
a
question
like.
What's
what's
the
metric
that
mattered
to
you,
and
we
were
now
the
answer,
30
or
40
people
and
we
helped
like
20-something
different
metrics.
So
there
are
two
lessons
learned
here.
A
So
that's
something
the
first
thing
on
those
high
level
stuff
and
then
forget
about
measuring
things
for
the
pressure
of
measuring
things,
because
that's
that's
the
other,
less
of
them,
because
oh
I
am
basing
my
decision
making
because
I'm
able
to
allow
Komets
but
not,
for
instance,
the
request
or
diversity
and
inclusion
in
my
community
and
because
I'm
not
able
to
analyze
that
and
I'm.
Basing
my
my
strategy
and
this
data,
but
doesn't
make
sense
because
then
you
are
facing
in
some
kind
of
bias,
data
which
is
kind
of
the
previous
discussion
we
have
like.
C
Can
start
so
one
of
the
things
that
we're
looking
at
in
the
value
working
group
and
Kari
had
alluded
to.
It
was
the
ability
say,
for
example,
of
a
project
to
have
social
impact
or
a
positive
social
impact
in
the
world,
which
could
be
particularly
important
in
today's
state
of
the
world?
How
do
we
go
about
doing?
That
is
a
that's,
a
very
difficult
question,
and
so
what
would
what's
the
goal?
What
are
the
questions
and
one
of
the
metrics
so
the
data?
C
It
doesn't
just
jump
out
at
me
as
to
what
that
might
be
so
I
I
think
that
in
the
chaos
project,
though,
through
talking
and
listening,
we
can
help
figure
out
what
might
be
that
meaningful
data.
So
I
do
think.
There's
some
data,
that's
perhaps
more
evident
as
evident
through
Sade
github
repository
and
some
which
is
harder
to
track
down.
It's
it's
not
impossible,
but
we
have
to
think
through
carefully
what
that
data
could
be.
So
yes,
certainly
I'll,
say
one
other
thing
too,
is
as
we
look
in.
C
If
we
look
in
in
the
se
corporatized
open
source
space,
the
data
that's
available,
there
might
be
very
different
than
the
data
that's
available,
say
in
a
scientific
software
space,
and
so
what
that
data
is
and
what
it
means
can
be
can
be
very
different
things
so
the
provenance
of
that
data
and
then
what
that
data
can
mean
for
for
an
ecosystem
it
it
it.
It
can
be
very
different
in
different
spaces
and.
D
I
think
it's
worth
kind
of
reinforcing
something
that
Daniel
mentioned,
which
is
I've
seen
frequently
people
who
kind
of
let
the
cart
lead
the
horse
so
to
speak.
You
know
we
have
this
data,
and
so
therefore
this
is
what
we're
going
to
use
to
make
all
of
our
decisions,
rather
than
figuring
out
what
decisions
we
need
to
make
and
then
what
data
do
we
need
in
order
to
do
that?
And
it's
I
understand
the
desire
you
know
went
but
just
because
all
you
have
is
a
hammer,
does
not
make
everything
a
nail.
D
So
there
are
these
things
called
hardware
stores
where
you
can
go
and
you
can
get
other
tools
that
will
allow
you
to
get
your
job
done
appropriately
same
thing
for
your
metrics
and
your
data.
I
am,
and
it
does
make
sense,
rather
than
just
using
your
one
hammer
allowing
that
to
guide
what
sort
of
house
you
build
go
out
and
buy
yourself
a
decent.
You
know
table
saw-
and
you
know
maybe,
when
those
really
cool
pneumatic
nail
guns
and
things
like
that
right,
there
are
different
things
you
can
use
there
and
that's
something
that
I.
D
Don't
think
people
pay
a
lot
of
attention
to.
It's,
not
the
exactly
exactly
the
question
that
you
gave
to
us
Daniel,
but
I
thought
it
was
worth
reinforcing
because
it
is
a
problem.
I
see
a
lot
of
companies
and
a
lot
of
projects
make
if
they
care
about
data
at
all
or
if
they
pay
attention
to
date
at
all,
which
is
really
the
first
hurdle
getting
them
to.
You
recognize
that
this
is
something
they
should
even
pay
attention,
and
so
that's
a
question.
B
B
Understanding
the
context
and
the
communities
are
important
and
then
there's
other
data
that
may
require
a
survey
or
manual
data
collection
or
completely
new
data
collection
methods,
and
then
what
how
do
we
get
started
with
metrics?
How
to
get
people
to
care
is
something
that
we
are
we're
thinking
through
in
the
chaos
project
and
one
of
the
things
that
we've
started
doing
is
having
user
groups
where
we
have
so.
B
We
started
one
for
the
app
ecosystem
after
scale,
and
so
these
are
books
from
the
genome
foundation
from
the
KDE
foundation
and
chaos
and
we
get
together
and
we're
like
okay,
so
we
want
metrics,
we
know
we
need
them
and
what?
What
is
it
that
we
should
recommend
to
the
people
who
are
in
different
roles
within
our
foundations
and
the
app
ecosystem?
C
Yes,
I
do
think
one
of
the
things
in
me.
Hopefully
this
is
working
in
the
chaos
project,
just
even
with
the
different
working
groups
so
having
one
working
group
focusing
on
Sadie
and
I,
one
working
group
focusing
on
risk
one
on
evolution
right
off
the
bat
that
helps
kind
of
segment
areas
of
metrics
that
you
may
or
may
not
have
an
interest
in
within
each
of
the
working
groups
themselves.
C
So,
for
example,
with
Indy
and
I,
we
have
focus
areas,
and
so
one
focus
area
in
DNI
would
be
stay
event,
DNI
or
event
base
DNI
so
and
then
the
metrics
that
would
help
reveal
DNI
with
respect
to
events.
So
again
that
helps
localize
a
series
of
metrics
that
can
provide
insight
into
a
very
particular
area.
So
we've
taken
time
to
kind
of
structure
the
chaos
project,
but
it's
not
just
a
grab-bag
of
metrics,
but
but
structuring
them
to
be
meaningful
as
a
collection.
A
Yeah
and
I
would
like
to
do
to
answer
here
as
well,
so
first
I
think
it's.
It's
been
really
useful
to
have
everyone
in
the
discussion
at
the
same
time
in
the
same
place
or
built
on
place,
because
that
helps
to
have
a
feeling
of
ownership.
When
you
are
defining
metrics
and
instead
of
working
at
the
level
of
individuals,
try
to
work
at
the
block
teams,
then
you
are
in
a
team
or
in
a
community,
and
then
you
are
trying
to
improve
by
I'm,
looking
certain
and
desire
situations
or
looking
to
improve
bottlenecks,
etc,
etc.
A
A
There's
a
way
to
to
improve
these
orders,
we
need
to
tune
the
metrics
in
somehow.
We
all
have
a
voice
again,
so
we
can
keep
iterating
those
metrics
course
metrics
from
time
to
time.
We
need
to
improve
them,
or
you
know
elaborate
them
a
bit
more
or
simply
dismissed
and
because
they
are
not
useful
anymore.
But
those
are
those
are
a
couple
of
interesting
things.
A
The
other
thing
is
context
and
still-
and
with
this
I
would
like
to
bring
back
Diane
Diane
hoped
you
were
around,
because
we
are
kind
of
ran
out
of
time,
but
I
would
like
to
bring
here
because
one
of
the
things
or
the
the
lessons
learned
that
we
have
we
have
together.
Thank
you,
hello.
Diane.
Is
this
difference
between
context
knowledge
that,
in
this
case,
is
Diane
and
uncertain
data
knowledge.
That
is
my
part.
So
we've
been
working
together.
A
E
It's
like,
if
you
know,
diversity,
information
around
the
data,
how
to
identify
that
how
to
do
that
securely
and
privately
within
you
know,
when
people
aren't
sharing
that
information,
that's
a
big!
You
know
it
it's
an
issue
for
us
to
better,
create
diverse
and
inclusive
and
communities,
but
it's
also
a
privacy
issue
as
well.
So
like
we
have
d
anonymized
the
organization's
for
a
lot
of
the
people
that
are
part
participating
in
our
openshift
commons
work.
That
hasn't
happened
in
all
of
the
other
ecosystems
as
well.
E
Some
work
that
we've
been
doing
in
kovat
up
here
in
canada.
They
don't
have
any
diversity,
background
information
on
the
patients,
so
they're
not
getting
the
breakdown
by
race
or
ethnicity,
or
you
know
all
kinds
of
other
things,
because
they
don't
actually
have
that
information
and
that's
that's
I,
think
one
of
the
bigger
issues
I
think
with
a
lot
of
our
kind
of
dependency
on
people's
self.
E
Identifying
and-
and
that's
a
good
thing
people
should
have-
we
should
respect
their
privacy
z--,
but
it
also
makes
it
harder
to
understand
all
the
dynamics
of
the
data
and
to
not
let
the
data
influence
or
drive
our
decisions.
If
we,
if
we
know
we
don't
have
that
information,
I,
think
that's
one
of
the
key
learnings
from
from
the
work
that
Daniel
and
I
have
done
and
I
think
the
work
that
all
of
us
have
done
and
what
J
band
de
mie
J
reiterated
earlier.
Today,
though,
I
think
that's
that's
key
and
I.
E
E
Well,
thank
you
because
really,
the
whole
impetus
for
doing
today
was
the
cancellation
of
chaos
Khan
and
Daniel
and
I
having
a
conversation
about
how
important
your
work
was
and
that
you
know
we
really
wanted
to
continue
that
conversation.
So
we'll
we'll
do
this
again
and
often,
though,
thank
you
very
much
guys
for
all
of
this.