►
From YouTube: CHAOSS Evolution Working Group 3-31-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
By
the
way,
so
this
is
the
evolution
meeting
for
march
31st
2021.
Is
there
anyone
do
we
who
uploads
the
video,
the
ut
recordings
to
the
youtube
for
those.
A
B
A
B
B
A
So
well,
let's
start
with
issues.
Let's
start
at
the
bottom
cycle,
analytics.
C
D
C
Nice
yeah,
although
what
is
the.
A
What
does
jesus
say?
Jesus
always
argued
for
code
changes,
even
though
his
tools
and
our
tools
all
say
commits.
So
I'm
just
going
to
skip
past
that
at
this
point,
since
it's
over
a
year
old.
C
So
yeah
I
don't
know
so
I
don't,
I
think,
connecting
issues
to
code
changes
is
is
a
bit
much
like
you
can
connect.
You
can
connect
an
issue
to
a
pull
request
and
you
can
connect
and
you
can
say
a
pull
request-
was
successfully
merged
or
closed,
but
I
think
it's
a
bit
much
to
connect
an
issue
with
a
code
change.
C
C
Although
I
will
say
I
did,
I
had
a
paper
a
year
ago,
where
I
looked
at
the
merge
success
of
pull
requests
that
were
linked
to
issues
and
the
emerge.
Success
is
higher.
A
A
I'm
just
saying
basically
yeah,
you
know
you
could
do
it,
but
it
would
require
practices
on
the
project
and
even
with
prs
being
connected
to
issues
that
still
requires
practices
which
are
going
to
differ
significantly
across
repositories.
So
the
likelihood
of
that
association
being
a
metric
of
any
consequences,
extraordinarily
low.
C
Yeah-
and
I
should
say
the
the
case
that
I
looked
at
when
I
did,
that
was
a
case
where
it
was
part.
It
was
part
of
their
design
process
to
actually
link
issues
to
pull
requests.
So
it
just
like
stated
that
that's
what
you're
supposed
to
do
so
line.
C
A
A
C
D
B
Also,
did
he
say
that
they
were
trademarking.
A
An
objective,
consistent
manner
across
thousands,
tens
of
thousands,
some
tens
and
thousands
ten,
I
mean
really
it's
a
hundred
thousand.
A
Well,
I
mean
it's
and
the
answer
is
like.
A
G
A
B
A
E
Is
there
I
created
an
issue
on
the
common
and
it
was
transferred
to
the
risk
for
revolution?
I
guess
you
did
it.
How
I
don't
remember
exactly
my
guess
is
copy
and
paste?
No,
it's
the.
A
F
C
A
Yeah,
we
did,
I
think,
that's
the
one
of
the
few
that
I
left
open
branch
life
cycle.
Did
we
release
that
branch
life
cycle.
C
C
A
C
F
E
Yeah
it's
like
every
morning,
I
open
the
pc.
First
thing
I
do
is
like
look
at
my
email
is
the
result
in
or
not.
E
A
Basically,
the
github
changed
its
default
branch
to
yeah.
You
know
for
reasons
that
are
reasonably
obvious,
so
let's
transfer
that
to
a
tool
which
brings
me
back
to
I
mean
they're
really
kind
of
brutal
about
like.
If
you
transfer
an
issue
you
are
out
of
the
repo,
you
were
doing
issues
in
add
new
metrics.
C
So
this
is,
this
is
the
one
we
we
mentioned
we
mentioned
earlier
when
we
were
talking
about
issues
to
pr
success
where
the
issue
linked
to
a
pr
is
a
value.
I
I
think,
that's
a,
I
think.
That's
a
metric,
however,
taking
it
to
to
merge
success
is,
is
a
bit
too
far,
but
just
linking
an
issue
to
a
pull
request
like
whether
or
not
that
link
exists
or
how
many
different
links
exist.
I
think
that
is
definitely
a
metric.
E
F
A
A
C
Issue
there
there
is
there's,
there's
no
there's
a
tool
to
do
it,
but.
C
B
A
C
What
is
this
one?
This
is
about
renaming
md
documents
shouldn't
yeah,
just
transfer.
I
don't
think
you
need
to
transfer,
because
I
already
have
this
issue
and
I'm
pretty
sure
I
referenced
this.
So
I
just
close
it
and
say
this
is
being
dealt
with
in
in
the
web
in
the
web
content
group.
B
F
C
C
C
A
E
C
B
A
D
B
C
Yeah
yeah,
so
there's
that
there's
the
comment
so
mentioned
this
issue
11
hours
ago,
different
folder
for
completed
and
underdeveloped
under
development
metrics,
and
then
I
know,
we've
talked
about
in
the
past
that
the
the
only
metrics
that
should
be
in
this
repo
are
completed.
Metrics
under
development
metrics
should
only
exist
in
github
or
in
google
documents.
E
C
So
so
there
will
not
be
separate
folders
for
completed
metrics.
We
will
be.
We
will
be
removing
any
metrics
that
haven't
been
released
from
the
repository,
so
the
the
the
evolution.
The
working
group
repository
should
only
contain
metrics
that
have
been
released,
yep
or
are
in
the
process
of
being
released.
Can
someone
paste
a
link
to
the
spreadsheet?
C
A
A
C
C
F
E
A
F
A
Is
this
that
this
is
issue
closed?
So
I
would
say
that
this
would
be
a
tool-specific
implementation
problem,
because
we've
defined
closed
issues
fairly
clearly
right
and
it's
up
to
the
tool
makers
to
ensure
that
that
status
is
reflected.
Can
we
look.
A
B
A
Are
these?
Oh,
is
this
yeah?
It's
just
here's
what
I
found
excuse
me.
So
it's
just
referring
to
a
metro.
Metric
issue
closed!
It's
just
it's
typos!
Let's,
let's
just
go!
Look
at.
F
A
A
A
Yeah,
what
was
the
issue
number.
A
A
C
C
D
C
Only
if
it's
linked
only
if
it's
linked
on
the
on
the
right
side,
where
you
have
linked
pull
requests,
if
you
just
mention
it
in
the
comment,
it
creates
a
link
to
a
lesser
degree
where
it
gets.
C
A
C
E
E
C
If
for
data
collection,
I
think
you
you'd
have
to
you'd
actually
actually
grab
that
explicit
link,
but
then
you
probably
also
have
to
scrape
the
comments
yeah
to
pull
out
the
hashtag
number,
and
that
would
be
the
that's,
probably
the
two-way
for
github.
That's
how
you
would
that's
how
you
would
figure
out
if
it's
linked.
A
Yeah
and
yeah.
A
So
I'm
going
to
say
the
chaos
community
decided
that
we're
going
to
remove
metrics
and
development
and
from
the
metrics
folder
and
make
them
part
of
the
spreadsheet.
C
Yeah
metrics
under
development
yeah,
they
should
only
exist
in
the
spreadsheet
and
in
google
docs.
Only
yeah
only
released
metrics
or
metrics
that
are
going
through
the
review
process
for
release
should
exist
in
the
repository.
B
Sorry
to
interject,
but
I
just
did
a
quick
google
search
if
you
type
in
fixes,
then
hashtag
the
issue
that
will
automatically
close
it.
D
C
A
A
A
Case
of
this
bag
of
words,
it's
it's
like
a
bag
of
words
like
in
auger,
like
kate
stewart,
and
I
collected
a
set
of
tags
for
50
projects.
There
were
there
were
common
tags
across
projects.
C
A
Feature
bug
yeah,
so
it's
it's
really
a
question
of
like
we
could
probably
get
some
amazon
turkers
to
identify,
synonyms
and
classify
the
tags
as
as
being
in
the
same
category.
So
auger
does
this
already
and
you
know
creating
a
metric
around
it
is
I
mean
it's.
I
think
it's
a
worthwhile.
C
A
Classification,
I
think
so
some
you're
right
some
tags
are
thematic
in
nature,
but,
like
bug,
fixes
features,
front,
end
features,
back-end
features,
api
features.
E
Yes,
I
have
written
an
intro
on
that.
I
was
thinking
of
proposing
it
sean
like
because
I,
when
I
was
joining
the
risk
working
group,
I
saw
you
and
kept
doing
this
and
I
was
like
this
is
a
you
are
collecting
entire
data
you're
doing
everything
is
just
we
can
like
make
a
paper
out
of
it,
so
I've
added,
I
have
already
written
an
intro.
I
might
send
it
to
you
guys
once
a
look
at
it.
A
F
A
E
C
A
A
A
Sorry,
it
was
like
everything
was
gonna
break,
and
so
I
think
another
so
that
you
said,
if
you
say,
quality
or
efficiency
at
the
end,
kevin.
A
A
A
And
this
is
not
in
progress.
I
would
call
this.
A
C
Do
you
do
you
want
to
put
the
the
and
in
there
explicitly
what
did
I
do,
change
request
and
issue
tagging
change,
requests.
A
B
A
Gayward
all
right:
we've,
okay,.
F
A
A
A
A
Yeah,
I
think
I
don't
think
we're
going
to
get
we've
made
some
we
cleared
out
our
issue
queue
and
yeah.
G
A
So
when
we
put
in
the
focus
areas
folder
are
we
putting
them?
I
guess
they'll
be
just
move
the
metrics
folder
here
and
then
unreleased
metrics
will
be
removed
either
moved
to
the
spreadsheet
or
killed.
I
think
most
of
the
unreleased
metrics
in
the
evolution
working
group
are
early
versions
of
the
metrics
that
were
renamed
and
they
know
they're
they're
very
similar
to
things
that
we've
released
and
they're
that
I
think
I
think
carter
did
a
good
job,
reducing
that
clutter,
but
I
don't
think
the
reduction's
complete.
A
A
A
G
A
C
G
A
It
also
shows
her.
I
think
it
also
shows
respect
for
the
work
that
jesus
did
early
on
to
to
try
to
standardize
it
in
in
the
way
that
that
we
envisioned
initially-
and
I
don't
want
to
just
wipe
that
out-
like
this-
isn't
code
where
wiping
out
old
code
evaporates.
I
think
this
is-
I
mean
for
me,
it's
more
like
an
act
of
respect.
A
A
G
G
The
a
release
tag-
and
I
see
that
back
at
the
in
2020
we
or
you
sean,
actually
created
a
tag
for
hey
before
folders
clean
out.
We
can
just
create
another
tag
to
tag
hey.
A
That's
a
good
point
that
we've
done
okay,
so
we've
done
it
this
way
before,
let's.
A
I
think
I
think
that's
a
that's
a
that's
a
good
idea,
so
yeah
we'll
just
do
a
release
after
cleanup.
A
E
The
issue
we
closed
just
for
I
don't
think
we
have
closed
it.
We
have
left
kept
it
open
right.
C
One
just
for
I
well,
it
vaguely
alluded
to
standardized
working
group
repository
structure.
A
A
A
Yep,
that
sounds
good.
I
will
sit.
We
are
five
minutes
past.
So,
if
that
student
wants
to
look,
we
have
an
issue
for
it
and
thanks
for
a
productive
meeting
cleaning
up
some
some
of
our
old
issue
work
and
I
will
catch
you
all
later.