►
From YouTube: CHAOSS Evolution Working Group 5/3/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Welcome
to
the
evolution
meeting
on
may
3rd
2022.
up
for
discussion.
First
is
the
revisiting
of
metrics
and
those
issues
so
I'll
share
my
my
screen
here
make
it
a
little
bit
smaller
for
those
living
a
laptop
life
right
now,
and
so
these
are.
This
is
an
example
of
an
issue
that
was
open
and
bernard.
You
were
saying
that
the
important
thing
is
to
kevin.
You
said
the
important
thing
is
to
make
sure
the
github
location
is
there
that.
C
B
B
I'm
sorry
to
interrupt
you
so
adding
the
google
doc
link
to
it
is
fine.
However,
it
wouldn't
always
have
a
google
doc
link
because
we're
not
always
doing
the
work
in
a
google
doc.
So
a
lot
of
these
a
lot
of
these
revisits
are
going
to
be
done
directly
with
pull
requests
if
they're
minor
when
you're
and
then
when
you're,
when
you're
creating
a
metric.
B
Originally,
when
you
create
this
issue,
you're
doing
that
in
conjunction
with
creating
the
pull
request
for
to
to
create
the
new
markdown
file
right,
so
that
new
markdown
file
becomes
the
the
default
most
important
place
where
work
is
being
done
right.
The
only
reason
to
go
back
to
the
google
doc
is
if,
for
some
reason
we
are
abandoning
this
markdown
page.
C
C
A
C
B
C
A
I'm
just
looking
at
I
have
an
old
version
of
a
fork,
so
old.
In
fact,
I
may
need
to
delete
it
and
start
over
yeah.
I
don't
even
have
the
main
branch,
so
I
just
I
was
just
going
to
demonstrate
how
you
would
go
about
doing
this
so,
for
example,
if
first
I
have
to
delete
my
existing
repository,
because
my
fork
is
so
stale
that
it
doesn't
have
the
right
branches
in
it.
E
A
B
A
E
A
A
F
A
You
were
an
early
creator
of
these,
though
you
were
out
front,
and
so
I
don't,
if
you
want
to
add
the
checklist
to
the
old
issues,
we
can
figure
out
how
to
navigate
to
the
revisiting
metric
tag.
Like
I
don't
think,
that's
a
problem,
I
can
see
updating
the
checklist,
because
that
checklist
is
pretty
helpful.
Yeah.
A
B
C
A
C
A
A
You
know
pro
development
activity
change,
let's
see,
code
changes,
lines,
code,
changes
commits
yeah
and
we
just
updated
this
23
days
ago
and
we
updated
change
request
commits
16
days
ago,
so
we've
we've
included
like
I
guess
this
is
from
the
latest
release.
Probably
these
merges
so
cone
change
commits.
B
C
I'm
also
in
favor
of
reopening
the
world.
This
was
what
I
was
told
when
I
was
doing
is
proposing
it
like
the
suggestion.
Is
there
are
so
many
comments?
We
don't
want
to
go
at
the
very
bottom.
We
just
want
to
have
a
revision
at
the
top
and
checklist
at
the
top.
So
that's
where
we
are
creating
new
one.
C
C
B
A
A
A
A
B
A
A
All
right
that
worked
so
that
one's
up
to
date
now
and
it's
focus
areas
instead
of
metrics
and
then
there's
another
subdirectory
for
issue
resolution.
So
we
have
reorganized,
and
so
some
of
those
those
links
it's
up
to
you.
If
you
want
to
just
create
new
issues,
because
at
that
point
it
almost
becomes
the
same
amount
of
work,
but
we
don't
care.
A
A
A
A
E
A
A
D
A
A
G
B
A
A
B
C
C
A
A
B
And
that
is
across
across
the
working
groups.
There
is
very
little
consensus
on
what
a
metric
is,
what
a
model
is
and
what
a
focus
area
is.
So
it's
all
very
confusing
because
going
going
across
these
working
groups,
sometimes
sometimes
the
focus
area
looks
more
like
a
model.
Sometimes
a
model
or
sometimes
a
metric
looks
more
like
a
model.
A
B
A
B
E
A
B
A
B
A
D
A
A
B
A
A
No,
I
guess
I
can
see
like
as
I
look
at
the
names
of
these
metrics.
I
can
see
how
the
code
development
efficiency
is
a
focus
area
that
it
could
be
distinct
from
the
focus
area
of
code
development
activity.
However,
so
it
also
makes
it
harder
for
so
it
makes
it
harder
for
people
to
navigate
when
we
bucket
them
like
that
too,
because
really
the
data
is
going
to
come
from,
although
the
data
comes
from
a
different
place
than
commits,
so
it
is
different
data.
A
A
I
agree.
I
agree,
you
know
they
really
are
evolution
models,
so
we
have
this
cross
and
one
of
the
principles
that
we
stated
early
on
in
the
metric
model-
work
which
I
don't
know
if
it
stands-
is
that
metrics
models
could
be
developed
by
that
working
group,
but
they
could
also
be
developed
by
other
working
groups,
and
so
I
think,
as
we
go
through
this
review
process,
we
kind
of
need
to
have
a
way
of
how
do
we
think
about
the
decision
to
convert
something
to
a
metric
model.
A
B
Best
plan,
no,
I
think
the.
If,
if
the
recommendation
is
that
the
metric
is
converted
into
a
into
a
model,
I
would
I
would
recommend
that
the
working
group
do
it
yeah,
but
once
again
these
these
this
the
review
process
that
we're
going
through,
I
believe
it's
it
is
actually
a
recommendation,
so
the
working
group
doesn't
have
to
do
it.
B
But
in
regards
to
the
the
hierarchy
of
focus
area
model
metrics
to
me,
they
should
have
different
levels
of
abstraction
with
the
the
metric
is
at
the
bottom,
and
it's
looking
at
a
very
specific
thing
and
the
model
is
a
little
more
abstract
and
then
the
focus
area
is
even
more
abstract
so
and
at
that,
so
that
focus
area.
It's
more
kind
of
an
abstract
context
rather
than
than
a
a
measurable
model.
B
A
The
center
holds
on
our
current
focus
areas
because
pull
request
data
all
comes
from
a
common
set
of
apis
on
any
platform,
github
git
lab
whatever
so
code.
Development
efficiency
is
really
about
change,
request,
incorporation
pace
and
acceptance.
Declination
ratios
how
long
it
takes
and
co-development
process
quality
change.
Request
reviews
argue,
okay,
I
think
those
are
the
same.
A
A
B
A
B
A
B
A
A
C
B
A
B
A
Yeah
I
mean
I
would
I
mean
I'm
hearing,
there's
confusion
about
this
and
I'm
and
as
I
go
through
this
conversation,
I'm
experiencing
some
confusion
myself,
and
so
I
can
imagine
as
a
newcomer
that
this
could
be
pretty
it's
a
lot
of
levels,
a
lot
of
layers
to
the
onion
and
and
do
we
need
all
those
layers
on
the
onion.
Well,.
A
A
B
I'm
just
I'm
just
throwing
that
out
there,
I'm
not
saying
that's
the
ideal
focus
area,
naming
convention
or
but
just
just
like
a
different
way
of
thinking
about
it
rather
than
rather
than
thinking
about
it
as
activity.
Think
about
it
more
as
a
a
context
or
a
space
which
would
be
kind
of
similar
to
the
way
common
doesn't.