►
From YouTube: CHAOSS Evolution Working Group 9-7-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
welcome
to
the
evolution
meeting
for
september,
7th,
2021
or
march
590th
2020,
depending
how
you
look
at
it.
So
what
we're
doing
is
just
going
to
check
and
see
if
we
have
any
comments
on
our
metric,
that
is
a
candidate
for
release.
B
B
C
B
Can
you
open
this
yeah
just
scroll
it
down?
Can
you
open
the
next
link.
B
A
E
You
scroll
up
to
participants.
C
E
B
E
E
B
E
E
D
B
E
Just
so
there's
another
person
to
to
bother,
although
I'm
just
going
to
tell
everyone
to
contact
you
so.
A
And
for
the
previous
metrics,
so
metrics
release
notes.
Do
we
need
to
create
an
issue
for
metric
release,
notes
or.
E
Oh
change
it
to
change
that
to
ten
edit
it
and
change
it
to
ten
yeah.
Yes,
for
this
one,
we
just
need
to
add
what
is
it
contribution
attribution
yep
to
the
list
here,
all
right,
otherwise,
it's
accurate.
A
Think
I
think
once
vanad
does
the
does
the
the
readme
update
we're
definitely
reorganize
the
repository.
I
mean.
A
A
B
A
E
Yeah
everything
so
we
went
through
this
one
before
everything
looked
good,
but
there
was
one
place
where
he
was
changing
some
language.
That
was
a
little
problematic
yeah,
but
other
than
that
I
thought
everything
was
okay
and
it
was
the.
A
A
E
Metric
that
metric
probably
needs
to
be
needs
to
exist
before
we
can
add.
E
Do
we
wanna
so
some
of
the
working
groups
like
to
track
new
metrics
that
by
creating
issues
do
we
wanna
do
that.
A
We
can
we
don't
need
to
do
that
in
a
meeting,
but
I
mean,
I
think,
that's
not
a
bad
idea.
I
think
that's,
I
think
that's
a
good
idea
that
we
have.
I
know
we're
based
on
the
minutes
a
lot
to
do.
A
This
emoji
in
there
I
just
want
to
change
that.
To
that
yeah
then
give
me
numbers.
A
A
Let
the
machine
do
that
so
yeah
we
have
11
metrics
on
our
plate
for
the
next
release,
so
I
think
we'll
be
busy
building
metrics
in
future
meetings.
Hopefully.
C
E
You
know
earlier
where
I
said,
I
would
wouldn't
tell
you
if,
if
I
did
something
wrong.
E
I
didn't,
I
didn't
add
the
the
chaos
quality
checklist.
Oh
metric,
that
we've
released
yeah,
so
I
we
should
probably
add
it,
maybe
just
peek
through
the
checklist,
real,
quick.
E
Sorry.
I
remember.
E
A
A
Sh,
I
guess
sure
it'd
be,
I
think,
easier
for
all
forever
for
people
to
follow,
along
with
the
home
game.
Okay,.
E
So
create
the
review
issue.
We
did
that.
A
A
D
E
We
added
the
metric
to
the
release.
Notes,
yes,
updated
the
metric
spreadsheet.
A
We
did
that
last
week,
so
I'm
confident
that's
done,
which
one
is
when
where's
that
one
at
is.
It
should
be
under
community
review.
A
A
Yep,
it's
way
down
at
the
bottom,
under
community
growth,
oh
community
line,
82.
A
What's
the
difference
between
ready
and
under
community
review,
I
think
that,
basically
issuing
the
pull
requests
and
doing
all
the
things
to
make
it
available
on
the
website.
So
there
are
a
few
few
technical
steps
in
between
the
working
group
is
done
with
it.
We
want
to
show
it
and
get
it
approved
by
the
community,
but
we
have.
There
are
some
steps
that
we
have
to
follow
to
get
put
on
the
website
and
officially
under
review.
We
have
to
create
the
issue
and
all
that
stuff,
I
think,
is
the
difference
kevin.
C
A
A
So
this
metrics,
so
this
is
okay.
We
had
this
long
discussion
about
this
about
cone
changes
commits.
A
A
A
We
talked
about
changing
it,
but
we
never
actually
did
the
pull
request
to
change
it.
All
we
want
to
do
is
add
code
changes.
We
don't
want,
we
wanted
to
add
the
word
commits
to
it,
but
we
never
created
that
pull
request.
E
A
E
A
I
created
the
pull
request
and
we
can
merge
it
after
the
freeze.
Okay,.
A
E
A
Oh
it's
so
this
is
in
common,
and
so
I
believe
if
we
go,
if
I
go
to
the
common
tab.
E
A
That's
released,
this
is
interesting:
yeah,
okay,
so
yeah
it's
organization.
So
this
is,
I
think
we
have
a
new
category
now,
which
is
moved,
but
maybe
that
text
is
not
yet
cut.
Yeah,
there's
a
moved.
A
E
I
just
created
an
issue
for
the
name:
change
for
code
changes
commits
okay.
E
Okay,
anyway,
back
to
okay
issue
created
in
translations,
repo,
that's
a
good
question.
A
E
E
And
the
metric
is
contribution,
contribution,
attribution.
C
E
B
Metric,
so
I
would
propose
having
a
focus
area
for
them
so
that
they
can
directly
go
rather
than
just
look
into
each
focus
area
and
find
out
the
matter.
That
should
be
a
suggestion,
so
that
will
be
easier
for
the
translation
folks
to
exactly
find
where
to
go.
Rather
than
look.
B
B
B
A
Yeah
there's
a
part
of
this
process.
I
find
it's
like
inevitably
circular,
because
we
have
to
create
the
issue
in
order
to
have
an
issue
number
and
then
go
back
and
add
the
specific
link
to
the
issue.
Number
you're,
not
wrong,
I
mean,
but
there's
no,
I
mean
it's
like
I've
thought.
Is
there
another
way
to
do
this?.
B
And
there's
not
so
yes,
yes,
so
what
is
now
thing
that
I
have
observed
in
different
groups
is
like
when
you
start
working
on
the
issue
or
like
when
you're
working
on
a
template.
You
create
an
issue
at
that
time.
B
B
E
D
B
A
B
E
Generally
speaking,
if
the,
if
the
image
so
that
yeah
there
so
there
is
a
convention,
there's
a
there's,
a
format
that
we
would
like
you
to
use
when
we
create
images
and
prime
the
primary
reason
for
that
is
just
to.
E
Because
in
the
in
converting
the
mark
down
into
html
some
of
the
it's
pretty,
it's
pretty
easy
to
what
some
things
that
work
on
on
github
will
not
work
off
on
github
right,
okay,
so
but
in
general,
if
the
visualizations
are
working
on
the
website
yeah
they
will.
Then
they
will
work
on
the
the
release.
E
Okay,
okay.
So
if
you-
and
if
you
look
at
the
metrics
template
the
the
second
page
of
the
metrics
template-
is
actually
some
some
guidance
on
naming
conventions
and
for
yeah
for
for
for
the
for
the
name
of
the
metric
itself,
for
the
how
to
do
images
and
general
formatting
instructions
for
the
metric.
So
it
is
there
in
the
template
when
we
pull
that
template
into
working
group
to
work
on,
we
usually
delete
that
bit
out.
A
A
I
don't
know
you
know,
if
probably
those
people
who
move
stuff
around
during
the
website
migration,
you
miss
something
that's
to
talk
with
them.
I
can't
think
of
what
it
would
be,
though.
No.
E
E
It
should
it
should
take
you
to
the
that's
in
page
scrolling.
It
should
take
you
there,
yeah
yeah,
it's
been
driving
me
crazy
for
ever
since
the
migration-
and
I
I
don't
know
if
it
happened
prior
to
the
migration
and
we
just
didn't
notice
it
or.
B
E
Was
the
cause
of
the
issue
or
if
it
was
if
it
was
an
issue
that
was
that
was
there
before
the
migration
and
it
might
have
been
an
issue
that
was
there
before
the
migration,
maybe
yeah
well,
either
way
I've
been
trying
to
figure
it
out.
I've
messed
around
I've
yeah,
no
clue
all
right.
So
I'm
hoping
I'm!
E
Oh,
you
know
what
I
haven't.
Are
you
using
firefox?
I
am.
I
wonder
I
haven't
actually
checked
other
browsers.
A
Yeah,
it
could
be
a
firefox
thing
for
sure.
That's
certainly
not
out
of
the
question.
E
So
anyway,
so
we
have
the
content
and
the
quality
and
the
technical
requirements
that
we
would
go
through,
and
I
would
say
so
those
those
bits
I
think
are
best
looked
at
when
we
do
when
we
actually
review
the
metric
itself.
Okay,
it
doesn't
work
in.
A
C
E
E
E
E
Yeah
naming
convention
yep,
that's
there.
Okay,
if
a
new
focus
area
is
created,
the
ensure
the
focus
area
is
added
to
the
working
group
within
the
focus
area.
Add
the
metric.
If
we
just
did
that.
E
B
A
E
Not
yeah
not
evolution
business.
I
do
have
a
question
for
elizabeth
that
I
would
like
to
ask,
but.
A
We
have
to
not
record
oh
okay,
I'm
going
to
stop
recording.
Thank
you
very
much
for
starting
the
evolution.
Meeting
have
an
awesome
day,
see
y'all.