►
From YouTube: CHAOSS Evolution Working Group 10-5-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
A
We
have
made
probably
over
600,
commits
in
this
release,
so
it
is
substantially
improved
in
a
myriad
of
ways
that
said
on
the
emoji
metric.
I
have
not
reached
out
to
remy
on
that,
but
I
do
talk
to
him
every
few
weeks
and
I
think
I
believe
I'm
talking
to
him
next
week,
so
I
will
make
sure.
A
Okay,
so
I've
now
actually
reached
out
to
remy,
and
so
I
took
care
of
that
action
item
and
then,
from
last
week,
new
metric
to
work
on
change,
request
commits.
C
A
C
C
I
think
either
that
or
html
has
had
html5
has
had
some
sort
of
update
that
has
removed
the
possibility
for
so
change.
A
The
most
interesting
thing
is
that
the
change
request
commits,
unlike
the
regular
commit
log,
is
it
will
not.
Essentially
there
is
a
common
practice
of
squashing
commits,
so
the
commits
that
are
associated
with
a
change
request.
A
Don't
give
you
the
level
of
detail
of
the
commits
that
you
process
by
navigating
the
commit
log,
give
you
it's
not
good
or
bad.
It's.
C
So
I
should
note
that
code
changes
commits
is
a
name
change
that
has
not
been
released
yet
so.
E
C
No,
no,
I
don't
think
this
is
in
the
review
process.
I
think
that
we
are
holding
that
for
the
next
review
and
let
me
just
take
a
peek
at.
C
A
C
So
yeah
and
I
think
we
were
doing
the
water
and
it's
possible-
we
even
have
a
pull
request
in
for
it
that
we
just
haven't
yet
we
haven't
accepted
it
yet
and
the
reason
we
if
we
look
at
that
pull
request
we're
going
to
see
yep
there's
a
message
that
said
that
says
this
change
needs
to
wait
for
the
next
release
cycle
so,
and
I
can
share
that
with
you.
If
you
want.
A
C
Yeah,
so
the
english
vers,
so
I'm
actually
in
the
community
meeting.
I
was
going
to
talk
about
that,
but
I
think
the
I
think
we
give
the
working
groups
two
weeks
to
do
their
final
reviews
and
ready
the
metrics.
C
So
if
that's
the
case,
then
the
plan
on
releasing
the
metrics
on
the
15th
or
18th
and
then
give
the
translation
team
a
week
to
do
the
translations
so
plan
on
releasing
the
translated
metric
on
the
22nd
or
the
25th.
So
I'd
like
to.
I
still
want
to
get
this
release
out
in
october,
but
I
think
a
two-week
a
two-week
window
for
the
working
groups
to
make
sure
that
their
metrics
are
where
they
need
to
be
is
fair.
C
Yes,
however,
if
we're
so,
if
we're,
if
we
are
introducing
another
metric,
that
is
this
close
to.
A
C
Oh,
no,
I
mean
yeah,
I'm
not
really
talking
about
the
like,
releasing
I'm
talking
about.
Maybe
if
we're,
if
we're,
if
we've
got
two
metrics
that
are
kind
of
similar
to
each
other,
we
should
maybe
take
a
look
at
both
of
the
metrics
to
make
sure
that
there's
not
any
confusion
about
them
that
they're
differentiated
they're.
C
C
A
I
mean
I
do
I
do
I
am
so.
I
was
involved
in
the
development
of
the
original
code.
Changes
commits
metric
and
I
am
very
certain,
but
let's
just
take
a
look
here.
A
So
including
merge
commits
are
really
the
merge
commits.
Are
the
the
novel
commit
if
you
will,
that
is
introduced
on
any
platform
hosted
repository,
so
that
would
be
most
of
the
repos
and
open
source
that
we're
talking
about
every
time
you
may
or
may
not
have
noticed
that
you
merge
a
pull
request
that
actually
creates
a
commit
in
the
repository
related
to
that
that
merge
requests
merging.
A
It's
also
worth
noting
that
merger.
So
if
I
think
of
change,
requests
versus
commits
one
aspect
of
a
change
request,
is
that
not
all
change
requests
are
involve
the
default
branch
for
a
repository?
A
So
you
can.
You
can
have
a
record
of
commit
activity
that
doesn't
ever
reach
the
main
or
the
default
branch
of
a
repository.
So
there
is
there's
information
about
process
in
the
change
requests
and
the
change
request
commits
that
is
not
revealed
by
the
commits
you
will
see
dead
ends
and
things
like
that.
A
So,
for
example,
if
I
have
a
development
branch
that
I
merge
into
another
development
branch,
but
that
development
branch
never
sees
the
light
of
day
and
never
gets
merged
into
the
default
repository
branch,
then
all
that
will
be
recorded
in
change.
Request
data.
All
that
will
be
recorded
in
change,
request,
commit
data,
and
none
of
that
will
be
represented
ever
in
the
commit
log
for
the
default
branch
of
the
repository,
which
is
what
we
are
implicitly
always
talking
about.
A
A
A
However,
I
think
the
possibility
is
super
small,
because
nobody
really
looks
at
commits
that
aren't
part
of
the
default
branch
they're
looking
for
things
that
are
released
into
the
wild,
but
it's
not
stated
explicitly
here
and
there
are
certainly
commits
and
repositories
that
never
make
it
to
the
default
branch.
A
C
C
A
Way,
I
would
change
if
I
would,
if
I
was
to
make
it
if
I
was
to
try
to
make
it
sort
of
even
more
clear
than
it
is
and-
and
I
see
I
think,
where
theory
are
going.
I
would
maybe
change
the
question
to
how
many
changes
were
made
to
a
source
code
repository
during
a
source
code.
Repository's
default
branch
during
a
specified
period
and.
A
And
I
could
even
just
change
if
even
just
adding
the
word
repository
and
not
including
default
branch,
would
would
make
it
and
get
repository,
because,
ultimately,
we're
really
only
talking
about
git
repositories
in
this
community
and
the
git
repository
is
an
object
that
people
understand
and
if
we
make
it
clear
in
change.
Request
commits
that
these
are
patterns
of
commits
within
a
change
request
on
a
get
platform.
A
D
C
D
C
A
To
and
when
we
link
to
the
metric
kevin,
do
we
provide
the
link
to
the
git
repository
or
the
link
to
the
website.
E
C
A
C
It
would
be
commit
patterns
within
change
requests
if
we
were
to
change
the
title
and
I'm
not,
I'm
not
sure
we
need
to
I
after
after
talking
through
this.
This
is
making
sense.
To
me,
it's
just
change.
Request
commits
is
a
is
a
more
focused
view
of
commits
right
of
chain
of
code
change,
commits
we're
just
we're
looking
at
it
in
a
in
a
specific
context,
and
that
specific
context
is
the
patterns
of
commit
activity
within
change,
requests.
A
That's
that
are
reflected
by
the
platform
and
associated
with
change
requests.
Yeah,
that's
right,
and
if,
if
I
was
to
suggest
wanting
to
understand
the
complexity
of
commits,
I
would
say
that
the
change
request
commits
combined
with
change
request
files,
give
you
a
full
picture
of
the
scope
of
a
change
request.
C
E
So
yeah,
I
was
because
I
was
just
reading
the
name
and
I
was
lost
like
without
going
into
further
detail.
Okay,
what
is
the
difference
between
change,
request
and
change?
Request
comments.
Just
simple
that
question
was
confusing
to
me.
C
So
you
can
have,
you
can
have
multiple
commits
within
a
change
request
right
right.
So
when
you're,
if,
let's
just
say,
if
we
were
counting
commits
within
a
change
request
right,
you
have
one
change
request
and
within
that
change
request
you
could
have.
You
know
five
commits
right.
However,
you
have
one
change
request
right,
so
the
the
change
request
is.
The
change
request
is
in
in
git
repositories
that
the
change
request
is
that
it's
that
place
where
all
of
this
other
stuff
can
happen
right,
so
reviews
can
happen
within
change.
C
C
A
So
if
I
was
to
get
at
the
nuance
of
of
these
are
I've
actually
saw.
I've
actually
obviously
been
looking
a
lot
into
this
recently,
and
so
these
are
the
detailed
nuances
that
have
to
be
taken
into
account
when
one's
looking
at
change,
request
commits.
A
Yeah,
there's
it's
it's
it's
not
trivial
and
that
that's
one
of
the
reasons
I
think
we
should
possibly
you
know
point
out
that
one
one
of
the
ways
that
people
use
change
request
commits
is
to
try
to
understand
the
sort
of
level
of
complexity
involved
in
a
pull
request,
and
this
I
think
this
metric,
combined
with
the
files
metric,
provides
an
understanding
of
the
impact
of
any
particular
change
request
there.
A
While
there
may
be
a
number
of
squashed
commits
they'll
still
likely
be
more
commits
and
a
very
large
pull
request
and
there's
certainly
going
to
be
an
you
know.
It
will
be
unambiguous
when
we
look
at
change
request
files
that
if
there
are
500
or
10
files
involved
in
a
particular
change
request,
so
yeah
my.
A
E
E
It's
nuanced:
it's
yeah,
it's
insane!
So
for
me,
for
example,
when
I
read
the
word
catalyzed,
we
are
trained
over
a
period
of
time
right
like
for
the
open
source
developers
or
a
community
or
whatever
the
process
is
so.
Are
we
looking
at
that
trained
over
a
period
of
time
how
they
are
doing
it
or
am
I
really
reading
it
incorrectly
pattern?
Has
some.
A
Change
requests,
if
I
was
gonna
change.
Requests
are
an
excellent
candidate
for
a
metrics
model
to
be
candid,
because
if
you
want
to
look
at
patterns
you
need,
I
think
the
things
that
you
need
to
examine
are
the
pull
re,
the
change
request
itself
and
how
long
it's
open
prior
to
either
merging
or
closing
the
extent
to
which
it
is
sent
back
to
for
review.
A
The
presence
or
absence
of
formal
reviews
and
reviewers
gives
you
a
insight
into
the
process
that
a
particular
project
follows
with
regards
to
change
requests.
I
think
the
use
or
non-use
of
labels
provides
another
dimension.
So
if
I
wanted
to
have
a
broad
understanding
of
how
change
requests
are
employed
across
projects,
I
would
include
all
of
these
elements
because
they
all
disclose
something
about
how
a
project
works.
C
So
I
I
agree
with
that.
I
think
change
requests
is
an
excellent
metric
model
to
look
at
yeah
and
then
to
to
venard's
point
earlier.
The
the
question
should
be
explicitly:
what
are
we
measuring?
Not?
What
are
we?
What
are
we
inferring
right,
so
complexity,
com?
If
complexity
is
something
that
we
would
we
could
infer
from
measuring
this?
C
So
if
that's
the
case,
we
could
we
could
mention
complexity
in
the
objective
right.
You
might
measure
this
to
explore
the
complexity
of
a
project,
but
complexity
should
not
be
part
of
the
question
and
I
don't
think
it
should
be
part
of
the
description.
So
the
question
the
description
should
be.
This
is
kind
of
this
is
explicitly
what
we're
measuring,
and
this
is
explicitly
the
description
of
what
we're
measuring
so
we're
not
measuring
complexity.
E
I
agree,
but
my
only
I'm
not
saying
that
I
want
to
stick
with
the
complexity.
My
only
concern
was
when
I
read
the
word
pattern.
I
see
a
trained
over
a
period
of
time.
That's
what
I'm
trying
to
understand.
Are
we
majoring
in
trained
over
a
period
of
time
like
from
time
1
to
time
2?
What
is
the
pattern
of
comments?
Is
it
that,
like
to
me,
the
word
pattern
tells
have
trained
over
a
particular
period
interval,
okay,.
F
E
A
G
A
A
Count
basically
how
many
code
change
commits
are
in
a
code
and
a
change
request,
and
and
for
the
reasons
I
outline
in
the
description
that
number
can
vary
depending
on
the
platform,
as
well
as
the
practices
of
the
project
right.
C
So
we
do
this
metric
enumerates
each.
What
is
that,
and
what
is
the
total
so
in
the.
C
C
It
is
more,
it
is
more
than
that.
It
has
more
depth
to
it
than
just
a
count,
and
I
think
that's.
Why
that's
why
the
the
pattern-
language
originally
yeah?
C
It
was
a
better
fit
than
count,
and
I
still-
and
I
still
think
maybe
pattern
is
a
better
fit
than
count
if
we
just
if
we're
just
counting
the
commit
and
we're
not
describing
the
commit
based
on
the
number
of
lines
of
code
and
files
changed
in
the
commit,
then
then
the
accounting
makes
sense,
but
the
the
fact
that
we
have
this
I
mean
and
describes
the
commit
based
on
the
number
of
lines
of
code
and
files
changed.
C
I
think
that
that's
something
that's
something
more
than
a
count,
so
this
is
another.
G
A
A
Myself
now
and
say
that
the
the
number
of
the
files
files
code
commit
change
request
files
is
a
different
metric
than
change
request,
commands.
C
C
Oh
yeah
yeah.
In
september
1st
we
had
proposed
that
one
looks
like.
C
Okay,
so
it's
it's
a
count
of
commit,
but
it's
also,
it
also
tells
you
who's
making
the
commits.
A
C
Yeah
that'd
be
the
it's
a
new
new
common
metric
managedtainer.
Somebody
managed.
A
A
I'm
sorry
I
ignored
you
for
the
principal
part
of
the
meeting.
We
always
like
to
welcome
newcomers
and
I
guess
my
head
so
far
in
the
game.
I
failed
to
do
that.
So
please
introduce
yourself
no.
F
It's
terrifying,
it
seems,
like
everyone
was
very
involved
in
the
work,
so
I
didn't
want
to
disturb
I'm
pcma
perry.
I
am
a
designer
and
I'm
part
of
the
open
source
community
africa.
F
In
the
past
couple
of
weeks,
I've
joined
the
the
app
ecosystem,
metrics
group
I've
been
working
with
george
and
the
rest
of
the
folks
and
I'd
say
to
contribute
more
into
the
chaos
community
and
I'm
trying
to
find
a
group
join
various
groups
to
see
what
is
going
on
in
each
group
and
see
how
I
can
help
with
the
my
skill
and
this
knowledge.
I
have
and
then
just
basically
be
part
of
folks
that
create
metrics
around
the
success
of
opportus
at
large.
A
F
A
So
the
the
app
ecosystem
working
group
is
a
great
working
group.
What
we
do
here
in
the
evolution
working
group
is,
as
you
could
have,
as
you've
probably
heard
if
you
were
just
you
know.
Listening
to
our
discussion
is
try
to
sort
of
make
sense
and
disambiguate
some
things
that
are
unclear
if
you
just
look
at
the
platform.
A
Central
daylight
time
tomorrow
morning,
just
as
an
aside,
we've
started
talking
about
metrics
models,
so
each
of
the
metrics
really
for
the
most
part,
with
the
limited
exception,
represent
a
very
like
counting
one.
Little
piece
of
the
activity
on
a
project
and
a
metrics
model
is
something
more
along
the
lines
of,
as
so.
A
For
example,
if
we
want
to
look
at
change
requests
as
a
model,
there
are
probably
eight
to
ten
different
dimensions
of
a
change
request
that
we
can
track
and
count
and
bringing
them
together
as
a
model
represents
a
pattern
of
how
a
project
is
behaving
over
time
with
their
merge
request
or
pull
request
activity.
So
the
pull
request
itself
or
the
merge
request
itself
is
the
main
thing,
but
then
it
also
has
commits
associated
with
it
and
files
associated
with
it.
Those
are
two
other
things.
A
There
are
comments
that
can
be
made
on
a
change
request.
That's
like
another
thing.
There
are
reviews
that
can
be
provided
that
either
approve
or
deny
merging
into
the
change
into
the
primary
branch
of
the
repository
each
re,
each
pull
request,
change
request
can
be
labeled
and
those
are
those
are
like
the
myths
like
all
that
stuff
together.
A
C
Mostly
metrics
the
models
work,
there's
actually
a.
There
is
actually
a
models,
working
group
that
does
that
that
does
the
models
work.
So
the
a
lot
of
the
working
groups
are
there's
overlap
between
what
happens,
and
a
lot
of
metrics
that
are
worked
on
within
working
groups
can
can
could
fit
in
other
in
other
working
groups.
C
C
That
would
help
them
understand
the
health
of
their
community
and
by
the
way,
I'm
I'm
sorry
sean.
There
is
one
agenda
item
that
we
do
need
to
get
to
before
this.
This
ends.
Okay,
let
me
say
one
more
thing
about.
A
A
We
don't
yet
have
a
standard
template
that
we
use
to
describe
metrics
models,
so
the
metrics
models
working
group
is
working
on
defining
a
metrics
model
and
in
the
process
of
doing
that,
building
a
template
for
extra
explaining
a
metrics
model
so
that
other
working
groups
can
then
develop
metrics
models
that
are
related
to
their
particular
area
of
interest,
so,
like
change
requests,
would
be
a
metrics
model
in
addition
to
a
metric.
A
A
C
Yes,
so
we
have,
we
have
released
one.
We
have
released
one
metric
or
we're
in
the
process
of
releasing
one
metric
in
this
group.
That
is
the
contribution
attribution
metric
all
right,
so
we
need
to
make
sure
that
this
metric
is
ready
for
release
and
we
need
to
make
the
so
so
I
would
say
there
are
two
things
we
need
to
do.
I
think
we
need
to
review
the
metric
again
to
make
sure
it
is
what
we
want
it
to
be.
Yeah.
I'm
sorry.
C
Yeah
and
through
that
review,
we
should
make
any
edits
that
that
need
to
be
made.
A
A
B
A
A
I
think
I
agree
with
him
that
that
the
text
is
a
little
hard
to
understand,
because
in
fact
we
are
talking
about
which
people
and
organizations
should
get
at.
Our
question
is
long
and
complicated.
His
question
is
short
and
decontextualized,
and
perhaps
we
could
meet
somewhere
in
the
middle.
C
Can
you
tag
tag
matthew,
tifton
this
as
well,
because
he
took
the
he
took
the
lead
on
this
metric.