►
From YouTube: Building metrics models based on the state of the art best practices | Xiaoya Xia & King Gao
Description
Building Metrics Models Based on the State of the Art Best Practices
The purpose of defining metrics is to continuously improve the workflow, empower open source projects with the capabilities of governance, operation, and development. We looked into some best practices of the benchmarking communities in the industry on how they measure and govern the project, and constantly explored which metrics and factors will affect the results of measurements. This talk will further seek connections among the current metrics and build a set of models, not only to address existing problems in communities, but also to predict the direction of future community development.
A
Hi
everyone,
I'm
so
thrilled
to
have
this
opportunity
to
give
this
talk
on
chaos
con
2021st.
So,
together
with
king,
we
will
present
the
topic
building
metric
models
based
on
the
state-of-the-art
best
practices.
A
So
what
are
the
characteristics
of
an
excellent
community?
The
first
element
is
paypal.
A
A
The
code
of
conduct
should
be
clarified
and
be
complied,
and
there
are
some
other
social
norms
that
are
predefined,
because
each
community
is
like
an
independent
village
with
with
its
own
social
culture
that
requires
contributors
to
do
their
homework
first,
to
learn
the
basic
questions
in
advance
like
the
basic
for
wwh
questions
instead
of
just
stumbling.
A
This
also
requires
maintainers
to
take
enough
patience
and
responsibility.
The
best
practice
here
is
the
apache
way.
I
I
list
some
of
the
points
about
making
the
community
based
built
on
trust,
trust
and
consensus
by
actually.
By
summary,
the
people
in
a
good
community
is
respect
and
responsibility.
A
A
While
most
of
the
contributors
in
cncf
comes
from,
companies,
company
could
lead
the
direction
of
the
community,
while
it's
still
openly
governed
by
the
foundation
and
the
openness
can
be
influenced
by
the
strategy
of
the
company
like
android,
mongodb,
etc.
They
allow
users
to
participate
in.
They
allow
users
to
participate
in,
but
the
project
is
controlled
by
maintainers
who
from
the
company
and
the
structure
also
evolves
as
the
community
grows.
I
like
the
picture
on
the
right
side
with
a
single
project.
A
It
becomes
a
foundation
governed
model
and
aside
from
tlc
now
we
also
need
user
committee,
marketing
committee,
etc,
and
now
the
foundation
now
is
from
the
always
from
aboard
a
board
of
director
team
to
lead
the
strategy
level
of
decisions.
A
The
development
workflow
in
open
source
is
actually
the
agile
model,
release
early
and
fast
adoration,
so
an
efficient
collaboration,
workflow
and
even
automate
automation,
trolls,
are
important,
frequently
occurred.
Concepts
here
are
devops
aka
development
and
operation
and
and
to
assure
the
quality
in
the
same
time
and
ci
cd
develop
continuous
integration,
continuously
delivery
and
continuous
deployment.
A
Let's
now
look
at
a
project
named
reproducible
boots.
It's
a
set
of
software
development
practices
that
create
an
independent,
verifiable
path
from
source
to
binary
code.
The
keywords
here
are:
reproducible
and
verifiable.
A
It's
a
part
of
the
chain
of
trust
by
promising
identical
results
are
always
generated
from
a
giving
source.
That
is,
you
can
always
produce
exactly
the
same
binary
code.
It
allows
verification
that
no
vulnerabilities
are
introduced
into
the
components
so
open
source
component
security
is
a
critical
topic
during
development.
A
A
We
can
see
three
examples:
apache
apache,
look
at
it
from
community
development
and
community
governance,
community
development
will
code
license
and
copyright
a
release,
version
and
quality
are
the
elements
that
are
highlighted
and
community
governance,
where
it
looks
at
the
community
consensus
and
independence
and
cncf
divide
divide
the
majority
of
projects
to
three
levels:
graduated
incubating
and
sandbox,
and
this
is
voted
by
cncf
tlc.
A
And
one
of
the
oh
sorry,
one
of
the
basic
requirement
is
to
achieve
and
maintain
a
cia
best
practice
badge.
So
how
does
the
ci
badge
evaluate
a
project?
A
It
focus
on
the
it
focus
on
the
security
perspective,
look
at
look
looks
at
the
some
basic
elements
like
websites
license
and
documentation
and
change
control,
the
vulnerability
and
bugs
quality
and
tests,
and
and
so
on,
so
to
have
an
to
have
a
conclusion
we
can
see.
Despite
of
different
focus
and
dimensions,
the
element
and
practice
are
highly
overlapped
actually
and
that's
why
we
need
to
integrate
them
and
read
them
up
as
metrics.
A
This
is
how
I
look
at
kiosk,
an
open
source
community
itself.
I
mean
for
how
to
make
a
better
community.
So
now
king
will
talk
about
more
about
a
framework
and
metric
models.
B
Thanks
to
shaya
for
shane
and
came
from
china,
I
will
continue
to
share
our
insight-based
environmental
framework
for
open
source
community
and
how
metrics
are
connected
to
a
form,
a
model
and
the
supporters
from
work.
This
is
the
first
is
our
measurement
framework,
which
is
divided
into
four
layers.
I
will
analyze
it
from
the
bottom
up.
First
at
the
bottom
is
the
awareness
and
culture
of
the
community
perspective
accidentally
participate,
makes
accident
communities
and
accident
projects
such
as
respecting
others.
Toxic
cheap
show
me
the
code
exactly.
B
A
B
B
We
also
mentioned
that
the
measurement
is
now
to
the
goal.
It's
aimed
to
continuously
improve
and
build
more
compliance,
security,
diversity
and
inclusive
community
and
involve
more
developers.
B
The
current
indicators
are
quite
complete
and
we
are
constantly
improving
too
many
indicators
will
bring
problem.
How
should
I
look
at
them
which
indicators
so
we
need
a
model
that
make
it
easier
for
people
to
understand
the
health
of
the
project
before
starting
the
model.
We
need
to
think
about
how
the
magic
I
relate
to
the
modem.
B
B
Renault,
cleaner
logic,
inclusion,
logic,
impact
and
no
connection.
The
criminal
logic
is
easy
to
understand.
It's
similar
to
the
upstream
and
downstream
process
of
the
pipeline.
In
the
following
example,
open
issue
should
be
followed
by
the
issue
command.
B
B
The
logic
relationship
is
not
a
direct
airplane
relationship
is
that
a
magic
change
may
bring
another
magic
change.
For
example,
the
large
number
of
the
issue
common,
the
more
different
people
may
join
them
community
and
comment,
but
only
one
person
may
comment,
so
it's
possible
consequence,
but
they
may
be
strong
or
weak
links
at
the
last
ones,
two
magics
that
have
no
relationship
at
least
for
now.
We
don't
see
any
factors
that
affect
each
other,
such
as
the
license
companies
and
the
vulnerability
attending
the
simplest
relationship
in
this
is
carino
logic,
chronologic
and
inclusion.
B
Based
on
this,
I
tried
it.
First,
I
just
participated
in
the
chaos
project
and
found
the
simple
kit
workflow
simple
list
it
followed
to
do
it.
I
think
link
linked
the
metrics
that
have
been
discussed
in
the
issue
and
requests
can
see
the
relationship
between
the
outer
and
inclusive,
and
this
is
output
was
also
contributed
to
the
health.
B
Let's
thought
about
the
relationship
between
the
issue
and
request,
which
is
that
I
did
this
year.
Therefore,
so
the
following
model
is
created.
I
link
the
issue
and
appear
through
the
indicators
of
the
branch
like
branch
left
circle,
because
the
prequest
starts
from
the
issue.
No
matter
the
issue
is
requirement,
function,
feature
or
box.
B
B
Now,
we're
glad
that
we
have
established
the
matrix
model
group.
We
can
explore
more
model
together.
There
must
be
logic
relationship
in
the
matrix
model,
work
group.
They
are
also
very
interesting.
We
welcome
you
to
join
the
magic
motor
world
group
for
discussing
and
welcome
more
people
to
join
the
chaos
community.