►
From YouTube: CHAOSS Evolution Working Group Meeting 4-28-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
so
we're
jumping
into
the
evolution
minutes
a
bit
late
because
of
me.
Sorry
about
that.
But
matthew
is
explaining
the
way
that
drupal
recognizes
its
top
contributors.
A
And
how
you
know
that
this
could
possibly
be
something
that
is
developed
into
a
metric,
so
they
get
organizations
get
issue
credits
based
on
how
their
contributions
are
attributed
over
here.
So
a
certain
number
of
how
to
I
guess
the
issue.
Credit
is
some
algorithm
behind
all
of
this
stuff.
B
B
Yeah,
so
I
I
put
another
link
in
the
document
that
shows
like
how
we've
been
using
this,
that
that
link
that
link
to
jury's
boycharts,
like
blog
post,
so
so
dress,
and
I
started
doing
this
back
in
2016,
making
these
blog
posts
about
that
analyzes
these
data.
So
if
you
scroll
down
to
answer
armstrong's
question.
B
It
just
shows
how
much
how
many
contributions,
so
we
can
see
like
how
many
issues
are
fixed
per
day.
You
can
see
that
is
an
astonishing
number.
B
B
This
I
mean
this
blog
post
go.
We
goes
into
great
detail
on
to
how
the
work
is
distributed
into
some
of
the
ideas
that
dries
and
I
came
up
for
measuring.
You
know
how
many
people
are
working
on
contributed
modules.
How
many
are
people
working
on
the
core
of
drupal?
How
many
doing
are
non-product
events,
governance?
B
You
know
every
time
I
run
a
meeting
for
one
of
the
drupal
initiatives.
I
run.
I
create
an
issue
as
well.
Okay,
comment
in
the
issue.
They
can
get
credit
so
yeah,
so
we're
growing
this
and-
and
we
just
we
use
these
data
in
a
lot
of
different
ways-
to
try
and
assess
our
community,
but
also
do
some
incentivize
to
help
with
the
evolution,
and
it
seems,
like
you
know,
we're
by
by
many
metrics
we're
going
growing
by
some
metrics.
We're
not
you
know
so.
There's
there's.
A
A
C
It's
a
nice
project
of
interest,
but
what
I
think
I
we
are
discussing
here
more
it's
more
of
an
active
project
as
opposed
to
a
green
project
because
a
green
project,
we
measure
the
number
of
new
futures
that
are
inter
introduced
over
time.
It
gets
to
a
point
where
it
becomes
mature,
so.
B
C
B
C
A
To
me,
armstrong
like
one
that
could
defy
some
of
those
characteristics
simply
because
the
continuous
generation
of
new
web
tools
for
generating
content
in
new
and
different
ways
means
that
a
web
content
framework
is
always
going
to
have
to
continue
to
evolve
to
meet
those
demands
that
people
who
want
websites
have
yeah.
It
seems
like
a
more
persistent
kind
of
a
problem
than
say
once
we
have
auger
in
a
mature
state.
It
probably
won't
change
a
lot.
C
But
in
that
case
still,
we
just
measure
the
the
influx
of
or
the
volume
of
activities
that
are
coming
in
and
yeah.
So,
if
it
continues,
then
we
see
it's
still
a
green
community.
Oh
it's
it
yeah.
We
just
measure
these
things
and
we
see
the
video.
C
C
C
Okay,
so
it's
interesting
to
know
these
things
and
to
see
if
it
predates
git
github.
It
has
still
been
surviving
up
to
this
very
moment
and
it's
showing
some
future.
You
know
generation
of
use
case
it.
This
is
strong
indicator,
that's
a
project
that
is
worth
investigating,
but
why
are
they
so
successful?
You
know.
A
I
I
mean
my
hypothesis
is:
you
could
tell
me
if
I'm
wrong
matthew
is
that
the
web
content
is
forever
and
forever
evolving
and
if
you're
a
web
content
framework
and
people
use
you
in
their
business,
because
I
imagine
there's
a
lot
of
businesses
that
are
building
websites
for
organizations
and
charge
them
money
for
that
and
use
drupal
as
a
framework.
And
if
some
company
wants
a
feature
on
their
website,
the
the
the
web
development
firm
using
drupal
is
probably
going
to
just
build
it
into
drupal
so
that
they
don't
have
to
maintain
custom
code.
C
A
B
A
Yeah
I
mean
I
certainly
I,
I
think
the
way
that
this
kind
of
system
that
you
have
for
capturing
who
a
person
is
making
a
contribution
on
behalf
of
and
granting
credits
to,
individuals
or
organizations,
is.
A
A
Such
a
system
is
less
of
what
they
need,
but
for
a
lot
of
projects
it
might
be,
even
even
though
it
might
be
if
it
can
be
made
easy,
as
it
looks
using
a
framework
like
github
or
gitlab,
then
it
would
certainly
be
helpful
for
any
project
to
grant
credit,
or
at
least
at
least
the
credit
of
recognition,
if
not
other
forms
of
credit.
B
Yeah,
I
I
could
say
sort
of
quickly.
The
theory
that
dries-
and
I
have
been
discussing
has
just
been
injuries
talks
about
this.
A
lot
is
we
have
we
drupal
started
as
pure
volunteer
and
over
time
it
has
evolved
to
getting
more
organizations
involved,
and
that
was
the
theory
and
we've
continued
to
see
that
play
out
that
we
have
more
and
more
organizations
getting
involved,
more
people
getting
paid
to
do
drupal
and
you
know
again,
sort
of
in
theory.
B
We
think
that
that
makes
the
community
more
healthy,
because
people
don't
have
to
just
do
things
on
their
own
time
that
they're
getting
jobs
doing
it,
and
this
is
giving
us
a
way
to
try
and
measure
that
to
test
that
theory
which
we've
seen
that
it
where
our
the
number
of
volunteers
has
declined,
so
some
people
might
say
that's
but
but
to
be
able
to
measure
that
even
from
the
start
of
a
project
like
a
small
project,
like
you
said,
with
12
people,
if
that
project
started
to
grow,
I
would
be
really
fascinated
just
to
see
how
how
their
like,
maybe
there's
lots
of
projects
that
are
purely
all
volunteers.
B
You
know
survive
just
as
well,
and
if
more
organizations
used
a
system
like
this,
we
might
be
able
to
explore
some
of
those
questions.
For
me,
I'm
just
interested
in
largely
like
as
an
academic
pursuit.
Others
are
really
focused
like
at
the
drupal
association
on
growing
the
community,
growing
the
project
and
all
that
kind
of
thing,
but
there's
a
lot
of
different
ways.
You
can
use
this
information.
A
I
mean,
I
think,
one
place
that
we
might
you
know
what
armstrong
I
don't
know
what
the
rest
of
the
group
thinks,
but
I
think
at
least
enumerating
like.
B
Yes,
yes,
so
there's
there's,
we
have
lots
of
the
same
metrics
that
any
other
git
project
does
and
we
just
combine
those.
We
can
combine
those
in
other
ways.
B
So,
for
example,
sometimes
you
would
assume
that,
because
somebody
has
an
employer
listed
on
their
profile
on
github
hub
or
something
that
they
are
doing,
that
work
for
their
employer,
but
that's
not
always
the
case.
So,
for
example,
right.
E
D
Yeah
right,
it's
paid
a
lot
of
people's
salaries.
It's
pretty
awesome.
I
think
part
of
the
thing
that's
fascinating
to
me
is
that
I
remember
so.
I
was
one
of
the
founders
of
php
women
and
I
remember
back
in
the
day
we
were
trying
to
like
partner
with
projects,
and
I
I
I'm.
D
If
I
recall
now,
it's
been
a
long
time
like
over
10
years,
like
yeah,
probably
15
years
now,
but
I
feel
like
drupal
was
one
of
the
ones
that
we
partnered
with
early
on
and
to
kind
of
foster
that
so
I
I
think
it's
super.
D
It
would
be
interesting
to
see
if
your
or
drupal's
commitment
to
diversity,
inclusion
from
the
early
days
helped
that
project
be
so
stable
and
be
so
successful,
because
I
it
was
clear
at
the
time
that
you
all
cared
about
that,
and
I
just
remember
having
those
conversations,
and
so
I
it
would
be
interesting
to
see
you
know
if
there
I
don't
know
how
you
would
measure
any
of
that.
D
But
I
just
wanted
to
throw
that
out
there
that
I
really
appreciated
that,
and
the
second
thing
is,
I
was
just
curious
on
when
you
were
showing
the
gitlab
stuff.
There
are.
Those
are
those
bits
of
information
through
the
api.
Is
that
where
you
would
grab
that,
whether
or
not
they're
being
an
individual
or
a
volunteer
as
a
you
know,
or
whatever
it
was
with
the
companies
that
does
stuff.
Is
that
through
an
api.
B
So
the
on
drupal.org,
that
is
done,
we
we
store
all
the
data
in
a
drupal
site.
Essentially
so
the
git
lab
issue
is
about
porting
that
system
and
we're
just
beginning
that
process
dries
just
made
this
announcement
a
couple
weeks
ago
at
our
drupalcon
and
we're
we
haven't,
discussed
the
technical
implementation,
but
we
have
been
discussing
it
with
the
folks
from
get
lab
because
they
have.
They
have
actually
made
a
lot
of
changes
specifically
to
inc,
to
allow
for
drupal
to
move
to
get
lab.
We
we
recently
moved
over.
You
know
our
git
repository
there.
B
Then
we
started
moving
over
the
even
the
merge
system.
Drupal
was
using
a
patch
system
up
until
a
few
months
ago,
so
it's
been
a
gradual
process
where
they
have
adopted
things,
but
to
I
mean
to
specifically
answer
your
question.
I
don't
know
the
technical,
specific
implementation
of
how
this
would
all
work,
but
I
feel
like
it
is
it's
a
big.
B
It
has
lots
of
repercussions
for
them
to
add
something
like
this
or
just
or
or
maybe
not
if
they
just
make
it
like
available
as
an
add-on,
and
the
technical
solution
is
not
something.
We've
gotten
to
specifically,
because
you
know
we're
open
to
changing
our
system
to
make
it
to
to
build.
On
the
I
mean
we're
not
the
same
experts
that
a
lot
of
people
in
the
chaos
community
and
you
know,
apache
community
and
all
these
other
people.
I've
heard
on
the
podcast
talking.
B
A
I
I
mean,
I
think
technically,
what's
I
think
the
kind
of
information
you
gather
is
information
that
many
open
source
projects
would
like
to
have.
I
think
how
credits
are
allocated
and
for
what
purpose
is
maybe
a
context
piece.
So
if
you
talk
about
a
chaos
metric,
there
are
some
things
that
we
probe,
that
we
indicate
as
parameters,
for
example,
and
other
things
that
we
indicate
as
we
just
open
one
of
these
up.
A
So
like
issue
response
time
description
and
so
there's
aggregators,
you
know
average
median
and
then
parameters
like
period
of
time.
B
A
It
may
be
a
git
lab
only
mechanism
at
first
and
I
think
from
metrics
perspective
that
the
technical
acquisition
of
data
is
really
just
about
gitlab,
providing
an
api.
That
would
let
you
get
back
at
that
data,
so
they
may
not
need
to
be
responsible
for
the
entire
interface,
but
just
the
storage
of
some
kind
of
metadata
in
some
form
somewhere,
perhaps
as
a
tag,
comment
or
a
label
on
an
issue.
B
Yeah,
I
would
think
it
is
connected
to
the
issue
tracker.
I
mean,
as
I
see
it,
the
issue
tracker
tells
you
like
what
what
is
up
when
there's
changes
you
can
say
well
what
was
the
problem
and
why
is
it
a
problem?
Yeah,
the
git
repository
itself
can
tell
you
who
fixed
the
problem.
How
is
the
problem
fixed?
The
credit
system,
I
feel
like
just
builds
on
that
and
says
like:
why
did
this
person
fix
the
problem?
Were
they
supported
by
their
employer?
A
B
A
The
time
of
a
merge
request
that
this
metadata
gets
allocated.
Yes,
so
yeah,
I
would
certainly
gathering
the
data
and
and
doing
accounting
in
real
time
like
this
is
probably
a
heuristic
that
the
the
maintainer
uses
to
decide
who's
box
to
check
right.
B
A
Yeah,
so
I
think
yeah
I
mean
this.
This
seemed
like
it
would
be
something
that
would
have
to
exist
at
the
time
of
it
was
using
it
to
create
a
commit
message.
But
if,
ultimately,
all
the
information
is
stored
in
the
commit
message
or
or
is
what
is
checked
here,
stored
in
some
backend
database
that
you
use
to
calculate
the
metrics
and
I'm
sorry
I'm
doing
all
techie
on
us
here,
I
should
shut
up.
B
No,
that's
all
right.
The
the
commit
message
itself
contains
the
name
all
of
those
names,
but
it
doesn't
contain
their
their.
The
information,
like
their
employ
the
employer,
they're
working
for
the
client
they're
working
for
or
the
volunteer
right,
commit
message
itself
just
contains
those
names,
and
you
know
the
message
about
what
was
fixed
and
the
issue
number.
B
A
And
so
that
would
I
mean
what
would
be
nice
is
if
github
was
able
to
sort
of
fit
that
into
their
like
is
a
just
a
screen
that
stores
data
in
a
way
that
they
already
store
data
that
could
then
later
be
calculated
by
you
or
others.
B
A
I
think
I
I
haven't
seen
anything
like
this
before
this,
I'm
I'm
fascinated
that
I
mean
I
really
like
this
idea.
I
think
it
has
broad
application.
My
opinion
just
made
matter
not
at
all.
B
That
in
here
yeah
that's
the
the
one.
There
we've
been
trying
to
encourage
people
that
have
have
an
opinion
about
this.
To
add
a
comment,
because
git
lab
itself
does
their
development
out
in
the
open,
yeah.
E
B
We're
having
we're
encouraging
others
like
the
civvi
crm
is
a
project
that
really
yeah
people
historically
and
somebody
from
their
project
came
in
and
said,
we'd
love
to
use
this.
So
the
comments
below
and
whatnot
are
all
are
a
mixture
of
people
from
gitlab,
but
also
outside
people
saying
yeah.
This
would
be
helpful.
Yeah,
wow
and
we've
been
about
we've
been
working
with,
I'm
not
sure
how
to
say
neutral
sanchez
and.
A
B
D
Yeah
she
attends
our
app
ecosystem
working
group
on
mondays.
A
Idea
I
mean
I
I
mean
I,
I
think
I
added
two
metrics
to
our
metrics
tracking
spreadsheet,
under
community
growth
for
individual
contribution
credit
organizational
contribution,
credit
which
is
like
the
first
stage
for
making
a
metric
is
just
to
add
it
to
the
list
of
ones
that
that
we're
considering
and
then
really
who
comes
to
this
meeting
are
kind
of
the
determiners
of
what
we
work
on
because
often
times
these
meetings
doesn't
seem
as
I've.
A
You
know
I've
been
quite
curious
about
this
work
and
the
facilitator,
so
I've
sent
this
off
the
rails
as
usual,
and
you
know
so.
What
we
also
often
do
is
work
on
we'll
spend
some
time
in
a
meeting
working
on
one
of
the
metrics,
and
actually
you
know,
as
the
there's,
a
group
of
people
who
are
participating
in
evolution
evolve
we'll
work
on
different
metrics.
A
During
the
last
meeting
we
had
a
discussion
about
canonical
words
for
elephant
factor,
and
I
don't
know
armstrong.
Do
you
have
anything
to
report
someone
if
you
don't
mind,
so
I
think
I've
captured
these
two
ideas
that
you're
that
drupal
has,
and
I
think
they're
I
like
them
as
metrics.
I
like
the
idea
of
making
them
part
of
frameworks
like
gitlab.
E
A
B
So
the
the
credits
themselves
are,
self-reported,
people
have
to
choose
to
share,
they
don't
have
to,
and
it's
the
same
with
the
diversity
information
that
people
share
in
their
profiles
on
drupal.org.
B
But
by
doing
this
work,
we're
able
to
extrapolate
more
information
about
sponsorship
and
in
in
in
who
who's
contributing
most
to
the
project,
not
just
code
contributions,
so
that
that's
one
way
that
we're
able
to
measure
diversity
based
on
somebody's
drupal.org
profile
and
then
look
at
where
the
diversity
is
coming
from
in
terms
of
code
and
other
events
and
that
kind
of
thing
in
marketing
or
drupal
core.
So
but
the
short
answer
is
just
from
their
profile
information.
Should
they
choose
to
share
on
drupal.org.
A
A
B
Cause
I
I
just
know
like
from
my
own
experience,
how
I
felt
welcome.
We
have
a
whole
mentoring
committee.
We
have
a
whole
group
of
people.
That's
always
you
know
doing
things
to
introduce
new
contributors.
We
have
lots
of
the
diversity,
inclusion,
initiatives
that
we
have
and
so
we're
doing
so
many
things
to
try
and
grow
the
community
and
make
it
more
diverse
that
I
I
don't
even
know
how
accurate
or
useful
these
particular
ones
are,
but
some
of
the
some
of
the
numbers
some
of
the
metrics
seem
like
they
reflect.
B
A
I
mean
you've
got
a
system
for
people
to
proactively
grant
credit
to
different
types
of
contribution
as
part
of
a
pull
request
or
merge
request,
and
I
think
I
mean
I
think
that
is
that's
just
an
idea.
That
just
seems
like
a
really
good
one
and
should
be
reasonably
lightweight.
A
It
yeah
and
they
have
the
they
have
all
the
information
that
you
gather
right
there
on
hand,
especially
as
long
as
you're
using
their
issue
tracker.
It
gets
to
be
much
easier,
and
so
that's
what
your
issue
is
open
for.
A
We
have
five
minutes.
Six
minutes
left
the
other,
so
I
don't
think
we
have
time
to
work
on
a
metric
today,
but
we
will,
in
two
weeks
and
depending
on
who's
here
kind
of
see
what
we
work
on
and
if,
if
you
have
you
looked
at
some
of
our
metrics
templates
and
things
matt
matthew,
is
it
matthew
or
matthew
or
matt?
I
should
ask
you're
muted
now
I
don't
know
why.
A
It's
I
won't
working
with
matt
german
pray
for
like
seven
or
eight
years,
so
I
just
that's
why
I
asked
I've
had
matthew.
I
will
call
you
matthew,
because
that
is
your
name
yeah.
So
thank
you.
I
think
I
think
these
are
metrics
elizabeth,
had
a
comment
in
the
chat
about
these.
These
kinds
of
I
mean
these
particular
metrics.
A
They
might
be
appropriate
for
so
sometimes
it's
not
clear
like
what
working
group
of
metric
goes
in
and
since
the
you
have,
the
deepest
knowledge
kind
of
which
working
groups
you
participate
in
could
help
to
guide
which
working
groups
develop.
This
I
I
certainly
can
see
where
this
would
be
a
value
metric
as
well,
and
it
may
even
contribute
at
the
ei
metric
at
some
point.
A
So
if,
if
you
look
at
the
working
group
meeting
schedule
and
go
to
the
working
group
sort
of
make
your
rounds
and
decide
where
to
go
and
participate,
if
you
decide
you
want
to
participate
regularly
in
value
and
not
an
evolution,
our
feelings
will
be
hurt.
We
can
you
can
move
your
metrics
over
to
value,
I'm.
Usually
there
too
just
not
responsible
for
facilitating,
and
so
so
it's
not
like
the
any
working
there's
not
like
working
group
territory.
It's
you
know
these
are.
A
These
are
ideas
that
you've
shared
with
us
that
I
think,
are
really
great
and
we've
taken
some
time
here
to
talk
through
them
and
I
think
what
I
put
in
the
our
tracking,
our
metric
tracking
spreadsheet,
for
these
two,
the
you
can
see
that
these
two
lines
here
could
easily
be
cut
and
pasted
into
the
value
working
group
over
here.
A
A
B
A
Mean
you
you
try,
I
mean
we
can
we'll
keep
working
on
them
here
unless
you
tell
us
otherwise,
but
I
think
elizabeth
had
a
good,
a
good
point
about
them,
possibly
being
good
evolution
or
value
metrics
as
well,
and
I'm
in
both
of
them.
So
I
don't
care
where
we
build
them.
B
B
So
that's
that's
why
I
showed
up
here
because
they
really
want
to
use
these
to
help,
encourage
contribution
and
as
well
as
recognize
contribution,
quite
honestly,
like
right
recognize
the
people
that
have
made
the
project
so
awesome
over
the
years,
and
that
includes
companies
and
marketers
and
documentation
writers
and
all
that.
So
that's.
Why
that's
why
we
that's
why
I
came
here.
I
guess
yeah.
A
And
there
certainly
are
tools
that
that
we
have
from
evolution.
I
mean
vermour
lab,
has
a
tool
that
you
can
use
to
help
measure
that
across.
If
you
have
more
than
one
repository,
which
I
would
guess
you
do,
you've
got
to
imagine
drupal's,
not
one
big
repository.
A
If
you
want
to
look
across
repositories
like
the
morelab
allows
you
to
do
that,
auger
allows
you
to
do
that,
and
since
groomer
lab
has
a
pretty
tight
partnership
with
vlab,
they
might
be
like
tools
wise,
a
good
partner
for
helping
you
with
the
analytics,
although
certainly
I'm
happy
to
run
auger
against
any
any
repos
you
have
as
well,
but
I
know
my
labs
partnered
with
gitlab,
so
there
might
certainly
I
mean
you
met
new
york,
so
you
know
who
they
are.
A
I
can
get
come
up.
I
can
get
comments
out
of
review
comments
out
of
get
lab
and
I
don't
know
if
you
had
a
chance
to
look
into
the
canonical
or
there
was
a
kind
of
a
word
for
elephant
factory.
We
were
trying
to
think
of
last
time.
A
C
A
C
A
A
A
All
right,
it's
done
and
we're
at
the
end
of
time,
so
next
time
we'll
follow
up
on
this
and
we'll
set
to
work
on
on
finalizing
our
goals
for
the
next
release,
which
is
at
the
end
of
july.
So
I
think
metrics
have
to
go
under
review
at
the
beginning
of
july.
A
Am
I
remembering
that
correctly?
Is
that
our
timeline
elizabeth
or
do
you
not
recall.
A
We'll
figure
it
out,
we
have.
We
have
at
least
two
months,
so
thank
you.
Everybody
matthew
thanks
for
joining
us
josh,
thanks
for
joining
us
hope
to
see
you
next
time
or
another
chaos
working
group
until
until
later,
okay,
bye-bye
bye,
bye.