►
From YouTube: CHAOSSconEU 2023 - Panel Discussion about Using Open Source Health Metrics in Your Context
Description
Join panelists Ildikó Váncsa, Dawn Foster, and Sean Goggins as they discuss implementing and using open source community health metrics in your context.
A
A
All
right,
so
the
topic
today
is
how
to
use
metrics
in
your
context
and
and
the
first
question
for
our
panelists
is:
could
you
talk
about
the
context
with
in
which
you
engage
with
open
source,
Community,
Health,
metrics
and
mega
on
the
first
time
that
you
answer
also
introduced?
Who
you
are
where
you're
from
so
we
understand
your
context.
B
A
B
C
B
Does
is
we
are
supporting
open
source
software
development
communities
and,
as
part
of
my
job
role,
I'm,
both
looking
into
Community
Management
at
large,
as
well
as
I'm,
a
community
manager
for
one
of
our
projects.
It's
called
starting
X
I
thought
now
going
into
the
details
of
that
project
right
now.
It
really
is
the.
B
We
would
like
to
understand
the
Dynamics
of
our
communities
and
the
ecosystem
around
them,
because
it's
not
just
about
the
community
itself,
but
also
all
the
other
individuals
organizations
companies
who
are
doing
anything
with
the
the
work
and
artifacts
that
our
communities
are
working
on,
and
we
also
would
like
to
understand
how
the
communities
are
operating,
whether
they
are
struggling
with
anything
whether
people
are
happy,
they
are
efficient
and
whether
or
not
they
are
able
to
work
towards
the
goals
that
they
have.
So
we
obviously
started
to
look
into
Trends.
A
B
I'm,
usually
the
person
who
always
tells
people
that
never
ever
look
into
a
metric
or
Trend
without
knowing
and
learning
about
the
context,
because
without
the
context,
that's
really
just
a
number
and
A
number
being
higher
or
lower.
How
do
you
know
which
one
it
should
be
and
I
think
I
will
let
others
ramble.
D
But
my
my
context
is
Loosely
open
source
program
offices
and
helping
companies
engage
in
open
source
projects
the
right
way
and
help
make
sure
that
the
projects
that
we're
engaged
in
are
healthy.
So
that's
really
my
focus
when
I'm
looking
at
metrics
is
around
project
health.
So
looking
at
not
just
the
projects
that
you
know,
VMware
kind
of
drives
making.
D
C
D
D
Scalable
project
Health
metrics
that
we
look
at
across
all
of
the
repositories
that
VMware
is
kind
of
driving,
so
the
projects
that
we
own-
the
ones
in
our
GitHub
organizations,
and
so
we
run
the
we
run
metrics
every
month
on
about
125
repositories.
So
those
are
the
repositories
that
have
enough
activity
interesting.
So
we
we
take
a
look
at
those
every
month
and
look
at
which
ones
seem
to
be
doing
well
and
which
ones
aren't,
and
sometimes
we
talk
to
projects.
D
D
C
D
Then
we
also
do
my
team
does
some
health
assessments,
so
we
look
in
in
a
lot
of
detail
about
some
of
the
both
the
projects
in
our
GitHub
works,
but
also
third-party
projects,
and
we
look
at
things
like.
So
it's
not
just
metrics
driven,
but
we
just
also
look
at
things
like
like
governance.
Does
it
have
a
good
governance
model?
You
know?
Are
we
engaged
in
the
project?
Are
we
in
leadership
positions?
C
E
I'm
Sean
Goggins
I'm,
one
of
the
co-founders
of
the
community
and
currently
co-director
with
Nicole
husman
I'm,
also
a
maintainer
for
the
auger
project
and
the
computer
science,
professor,
at
the
University
of
Missouri.
My
interest
in
context
is
really
just
taking
the
chaos
metrics
in
auger
and
making
them
visible.
So
getting
all
of
the
data
that's
required
to
create
metrics
and
then
once
you're
completely
overwhelmed
by
the
volume
of
data,
and
you
can't
it's
just
blowing
you
away
and
there's
so
many
metrics.
What
we're
working
on
right
now
is
tuning
more
I.
E
Guess:
I
characterize
it
as
a
data,
scientific
approach
to
making
things
visible
and
making
the
data
accessible
to
people
who
think
in
data,
as
opposed
to
most
of
us
who
think
in
code.
It's
a
different
different
mindset
and
we
pay
particular
attention
to
things
like
that
are
associated
with
risks
of
dependencies
Licensing
and
trying
to
put
some
context
around
so
to
get
to
context
building
them.
The
points
ability
going
on
me
trying
to
get
some
context
around
where
the
projects
that
you
invest
in
or
rely
on,
perhaps
have
the
most
risk
of
being
de-supported.
E
So
if
you
can
identify
across
the
Thousand
projects,
for
example
within
your
organization,
which
ones
use
which
Imports
the
most
frequently
so,
which
things
are
you
most
dependent
on
but
they're,
perhaps
hidden,
and
then
you
can
make
a
decision
about
where
to
invest
that
way,
so
part
of
your
context
is
just
assessing
that
risk
perspective.
In
my
experience,
that's.
A
It
yeah,
thank
you,
thank
you.
So
we
have
on
the
panel.
We
have
ildico
from
Foundation
Don
from
a
corporation
and
Sean
from
the
academic
setting
so
and
one
thing
that
I
kept
hearing
from
all
three
of
you
is
that
metrics
need
to
be
looked
at
in
context
and
there
is
not
one
right
metric,
but
we
need
to
understand
what
we're
using
it
for
so
I'm
gonna.
Give
you
all
the
opportunity.
If
you
have
a
question
on
this
something
on
your
mind,
we
can
share
otherwise
I
move
on
with
another
question
here.
B
C
B
B
C
B
Who
are
the
people
who
really
are
carrying
the
project
on
their
back?
Who
are
the
people
who
are
casual
contributors?
Who
are
the
people
who
could
be
turned
into
maintainers
of
the
project?
And
long-term
contributors
could
be
turned
into
project
leaders
to
to
make
sure
that
the
project
and
the
community
itself
is
balanced
and
sustainable
and
they're
really
a
good
environment
to
work
in
and
I
mentioned
the
project
that
I'm
the.
A
B
For
it's
called
starting
Max
and
we
have
150
people
contributing
to
it
roughly
currently.
So
it's
it's
a
very
different
Dynamic.
Sometimes
we
feel
like
you're.
Almost
personally,
you
know
everybody
in
the
room
who
shows
up
for
meetings
or
replies
on
the
main
gaming
list,
so
there
you're
trying
to
look
into
metrics
like
who
are
the
newcomers
who
are
the
new
people
showing
up
on
the
meetings
or
the
mailing
list
or
or
trying
to
contribute
something?
B
How
is
the
rewarding
process
for
them?
Is
it
easy
enough
to
join
the
community?
Is
there
any
roadblock
that
many
people
are
facing?
That
would
prevent
them
from
from
being
able
to
so
for
us
and
for
me
personally,
it
really
is
more
about
the
evolution
of
metrics
and
and
how
we
are
both
collecting
data
and
interpreting
data.
At
the
same
time,
like
the
visualization,
obviously
is
really
really
helpful
because,
as
Sean
mentioned,
data
is
just
endless
and
it
really
easily
becomes
overwhelming,
and
we
just
feel
like
that.
B
You're
drowning
in
data,
if
you
want
to
you,
could
spend
all
day
every
day,
24
7
looking
at
numbers,
and
you
may
not
get
anywhere
with
them,
because
it's
just
too
much
so
really
you
kind
of
need
to
also
go
with
a
little
bit
of
instincts
as
well
figuring
out.
What
really
are
those
Peaks
up
or
down
that
you
should
be,
should
be
focusing
on,
and
there
are
bottlenecks
in
the
community
that
shows
up
that.
B
You
can
then
use
the
metrics
to
to
understand
what
the
underlying
issue
might
be,
and
the
other
thing
that
we're
also
trying
to
do
is
not
just
look
at
numbers,
but
every
now,
and
then
also
do
surveys
and
really
just
go
and
talk
to
people,
because
sometimes
no
matter
how
many
numbers
and
how
much
data
you
have.
You
just
have
to
talk
to
the
human
being
in
terms
of
what
makes
them
happy
what
makes
them
sad
what
they
are
struggling
with.
Sometimes
the
data
will
just
not
give
you
that
information.
D
Yeah
and
just
to
you
know
to
build
on
that
a
little
bit
one
of
the
things
that
so
I
mentioned
that
I
use
auger
and
we
have
kind
of
four
metrics
that
we
track
for
all
of
those
125
projects
and
the
the
goal
behind.
That
is
to
give
people
just
kind
of
a
quick
look
at
a
few
things
that
I
think
are
important
but
and
we're
turning
that
into
a
metrics
model
for
chaos.
So
I've
I
should
have
a
PR
for
that
in
the
next
next
week,
or
so
I
think.
D
But
this
it'll
describe
more
detail
those
those
four
kind
of
starter
metrics,
but
the
whole
goal
behind
that
is
to
get
the
projects
thinking
about
what
else
they
need
right,
like
those
are
just
to
get
them
started.
It's
a
quick
look,
but
what
I
really
want
people
to
do
is
then
to
dig
in
in
more
more
detail.
So
we
have
another
team
within
the
within
VMware
and
one
of
our
business
units.
D
A
E
Building
on
what
Don
and
ildico
said,
I
think
some
of
the
things
that
are
happening
within
chaos,
especially
the
development
of
metric
models
that
are
collections
of
metrics
that
are
commonly
used
together.
We
we're
seeing
a
way
of
sort
of
bringing
all
that
data
and
context
to
bear
in
a
very
targeted
way,
so
don
recently
authored
a
metric
model.
E
It
was
called
starter
metric
model,
starter
project,
Health,
metrics
model,
which
is
you
know
just
these
four
I
think
is
the
the
same
four
metrics
you
were
talking
about
just
now,
so
it's
it's
a
way
of
saying.
Okay,
you
have
all
this
data,
and
this
starter,
Health
metrics
model
can
get.
You
know,
yeah
yeah.
E
We
need
an
acronym
yeah
I'm,
not
going
to
parse
that
out
up
here,
but
so
that
kind
of
lets
you
get
started.
Lets
you
see
the
initial
contacts
and
it
gives
you
some
really
Baseline
metrics
that
you
can
use
to
sort
of
understand
the
activity,
levels
and
engagement
that
exist
on
a
larger
portfolio
and
then
decide
where
you
drill
in.
A
So
what
I'm,
what
I'm
hearing
from
you
to
synthesize
and
probably
will
not
do
justice
is
once
you
have
the
metrics.
There
will
be
more
questions
and
you
can
dig
in
and
understand
more
and
it's
not
about
just
having
metrics
and
having
a
in
Germany.
What
called
Shema
F,
where
you
just
make
decisions
good,
bad,
whatever
it's
really
to
start
understanding
and
digging
in
to
the
data
and
the
communities,
and
it
helps
to
maybe
validate
hunches
that
you
have
about
the
community
but
also
provide
evidence
for
what
you're
seeing.
B
B
Within
chaos
is
that
we
are
looking
into
collaborating
with
the
to-do
group
and
in
ospo's
and
well.
Don
is
a
good
example
of
singing
and
sitting
in
an
Osborne
and
having
that
broader,
View
and
sort
of
a
bird's
eye
view
in
terms
of
what
what
a
company
needs
in
order
to
figure
out
how
to
contribute
to
open
source,
how
to
be
a
good
open
source
citizen.
How
to
integrate
that
into
their
processes
and
I.
B
B
I
started
to
contribute
a
lot
10
years
ago,
something
like
a
really
long
time
ago
and
I
feel
all
down
and
back
in
the
day
when
I
started,
I
started
with
openstack
and
we
did
have
a
dashboard,
it
was
called
stackalytics
and
companies
were
looking
at.
You
know
who
has
the
the
most
comments
in
a
Rio
who
contributed
the
most
lines
of
code,
and
what
does
that
mean
at
the
end
of
the
day,
practically
nothing?
It.
B
People
are
in
the
communities,
like
individuals
are
focusing
on
these
kind
of
competitions
that
will
not
help
anybody
to
move
forward
and,
at
the
same
time,
with
supporting
communities.
I
also
see
the
struggle
sometimes
where,
where
people
or
companies
just
don't
really
understand
still
what
open
source
is
about,
and
so
they
have
a
struggle
on
the
process
side
in
terms
of
how
to
build
that
into
their
own
processes
and
at
the
same
time,
they
don't
know
what
metrics
and
and
data
and
Trends
to
look
at
in
the
open
source
Community.
B
Neither
do
they
necessarily
know
what
kind
of
data
to
look
into
internally
like
to
figure
out
if
they
are
successful
in
what
they
are
trying
to
do.
Are
they
efficient?
Could
they
do
this
better,
even
just
in
the
internal
processes,
so
I
think
that
chaos
working
together
in
the
hospitals
could
really
move
the
needle
on
solving
the
challenge
of
really
not
just
focusing
on
the
open
source
Community
itself,
but
the
ecosystem
around
it
and
those
companies
who
and
individuals
who
are
just
looking
from
the
sidelines,
and
you
know
oh,
this
is
healthy
enough.
B
D
B
D
You
know
building
on
that
discussion
around.
You
know
working
more
closely
with
with
the
open
source
program
offices.
You
know
one
of
the
things
that
we've
seen
historically
I.
Think
a
lot
of
us
have
taken
sort
of
naive
approaches
to
metrics
right
we're
looking
at
lens
of
code,
we're
looking
at
commits
we're
looking
at
and
things
that
are
indicators
of
maybe
other
things,
but
in
a
relatively
simplistic
way
and
I
think
I
think
really.
The
the
future
is
to
move
more
into
looking
at
things
from
kind
of
a
data
science
perspective.
D
The
you
know,
and
not
just
the
data
scientists
looking
at
it
too,
like
the
tools
are
starting
to
build
this
stuff
in
so
like
from
our
lab
started,
is
starting
to
or
has
for
a
while
had
a
lot
of
networking
and
nationality.
That's
a
part
of
it
that
I
think.
Maybe
maybe
we
don't
use
enough
enough
of
that.
You
know
an
auger
has
some
machine
learning
stuff
built
in
as
well
that
a
lot
of
people
don't
really
know
how
to
use
so
I
think
I.
D
E
And
the
only
thing
I
have
to
I,
plus
one
to
everything.
That's
on
elderco
said
for
sure.
The
only
thing
I
have
to
add
when
I
think
about
the
future
is
if
I
look
outside
of
the
chaos
project,
the
one
place
where
I've
had
the
most
pressure.
I
think
a
lot
of
us
had
had
the
most
Crusher
in
the
last
year
is
understanding
the
risk
associated
with
our
projects
and
being
able
to
understand
their
software,
build
materials
and
their
currency,
genes
and
I
think
those
are.
E
A
Yeah,
thank
you.
We
still
have
a
few
minutes.
I'm
opening
up
to
the
to
you
all.
If
you
have
anything
that
came
to
mind
listening
something
where
you
you
think
something
we
need
to
work
on
or
work
towards
in
chaos
or
if
you
have
some
metrics
that
you
think
are
interesting
and
you
would
like
to
share.
F
Have
you
seen
in
our
business
in
your
business
in
similar
I'm
talking
about
your
position
or
your
company,
but
in
similar
companies
with
similar
positions
as
yours?
Have
you
seen
or
have
you
feel
the
pressure
from
the
Mass
from
the
management
leadership
from
from
the
management
management
board
to
have
metrics
at
the
point
that
they
are
trying
to
replace
experts
like
you
with
metrics?
D
I,
don't
I,
don't
know
that
I've
I've
personally
seen
at
least
in
the
kind
of
the
software
context
that
I
work
in
I
haven't
really
seen
them.
Trying
to
replace,
replace
us
with
metrics
I
mean
I,
think
you
do
see
it
in
in
other
areas.
Right,
like
you
know,
there's
an
article
around
BuzzFeed
is
replacing
some.