►
From YouTube: CHAOSS Evolution Working Group 6-23-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
C
A
B
So
that
has
been
progressing.
I'm
not
sure
what
happens
with
that
next,
but
so.
E
Yep
I
took
a
look
at
it
last
week.
I
think
I
made
some
minor
edits.
I
was
actually
I
was
gonna,
wait
for
sean
to
take
a
peek
at
it
before
merging
it,
but
he
went
on
vacation,
so
I
could
I'm
comfortable
merging
it
now.
So
maybe
I
will
just
do
that.
A
Maybe
we
can
wait
for
sean,
I
don't
know
whatever,
because
in
the
last
meeting
we
agreed
it's
final
and
let's
just
need
to
go
in
for
the
review.
E
A
E
E
You
know
we
generally
don't
have
a
process
in
place.
That
says
you
have
to
announce
when
you've
put
something
into
the
review
process.
Okay,
so
we
create
an
issue.
I
usually
mention
it
during
the
during
the
community
meeting
on
tuesdays.
E
Yeah,
but
I
don't
think
we
need
to,
I
don't
think
we
need
to
do
like
an
email
like
okay,
although
we
have
in
the
past.
B
A
Okay,
then
we
have
the
potentially
related
metric.
I
don't
know
chaos
elephant.
A
E
Yes,
can
you
share
the
you
sure
actually
share
the
the
notes
document
with
me?
I
don't
have
that.
E
E
Are
we
looking
at
pull
requests?
I'm
sorry!
I
was
late
to
the
meeting,
so
I'm
still
kind
of
caught
up.
A
E
In
in
general,
I
know
that
there
are
a
couple
metrics
that
were,
we
were
talking
about
adding
a
data
ethics
kind
of
disclaimer
to
that
is,
and
that
is
something
we've
done
in
the
past,
specifically
when,
when
a
metric
could
be
abused,.
F
We
want
to
bring
this
up
in
the
community
call
because
there's
also
another
suggestion
regarding
the
templates
and
updating
the
templates
around
thinking
about
dei
how
a
metric
can
affect
dei
in
in
practice.
So
so
we
have
a
couple
of
revisions.
So,
let's,
let's
bring
that
up
at
the
community
meeting.
What
do
you
all
think.
E
E
Break
it
the
best
the
best
way
to
move
that
forward
might
actually
be
to
just
do
a
pull
request
to
the
template
to
add
a
data
ethics
section
that
my
guess
is.
That
would
be
a
third
level
heading
called
data
ethics
and
we
probably
add
the
optional
tag
to
it.
E
A
E
A
A
A
Yes,
these
notes
are
from
the
last
meeting
because
I
was
not
sure
so
I
just
copied
last
meeting
notes
and
I'm
just
reviewing
them.
Did
I
miss
last.
E
Week
remember
the
last
meeting
I
may
have
missed
it,
I'm
not.
I
don't
see
my
name
on
there.
Yeah,
I'm
not
yeah,
I'm
not
sure
what
this.
What
this
one
is,
the
reaction
filter
was.
Does
anyone
else.
A
B
A
B
B
E
Characterizing,
what
different
emojis
mean
across
projects?
There's
gonna
be
a
lot
of
context.
That's
required
and
also
kind
of
the
way
some
projects
use
them
may
be
different,
so
it
may
be
a
cultural
issue
as
well
project
culture
issue.
A
E
Looks
like
yes,
we're
just
the
only
one
we're
talking
about
in
that
pull
request.
That's
mentioned
is
thumbs
ups,
so
we're
not
even
we're
not
even
talking
about
plus
ones.
E
Which
I
guess
the
the
thumbs
up,
emoji
technically,
is
the
plus
one,
but
that's
yeah.
This
is
only
the
thumbs
up
that
is
being
discussed
in
this
poll
request.
A
E
I
think
this
this,
in
my
opinion,
this
is
something
I
would
defer.
I
think
this.
I
think
this
issue
is
kind
of
complex.
I
would,
I
would
defer
it
to
a
later
date.
E
If
I,
if
we
were
to
try
to
create
a
metric
out
of
this,
I
think
I
don't
know
how
useful
it
would
be
and
I
feel
like
we
would
just
be
pushing
it
through
just
to
push
it
through.
It
makes
sense
to
have
it
as
a
as
a
a
filter
in
some
of
the
metrics,
the
plus
one
just
to
mention
it.
A
E
E
And
this
this
would
be
super
complex,
figuring
out
the
different
emojis,
what
each
emoji
means
and
then
applying
the
context
across
different
project
cultures.
E
And
then
what
is
and
then
what
what
would
our
metric
describe?
Would
it
describe
the
process
of
counting
it,
or
are
we
attributing
some
sort
of
meaning
to
these
emojis
as
well.
E
A
E
So
this
is,
this
is
looking
at
activity
within
pull
requests
right.
So
in
our
in
the
our
previous
work
we
were
we
we'd.
We
had
made
the
name
change
to
change
request,
and
then
we
were
looking
specifically
at
change.
Request
comments.
E
A
E
Any
other
things
to
move.
We
are
just
looking
at
the
commits
we're
being.
This
is
we're
being
very
specific
about
about
what
we
were
doing
here.
E
E
Okay
yeah:
it's
part
of
the
code
development
activity,
yeah
yeah,
so
this
is
about
yeah.
This
is
specifically
about
breaking
down
the
parts
of
a
pull
request
into
into
miserable
components
right,
so
we
can.
We
can
measure,
we
can
look
at
the
number
of
files
in
a
pull
request.
We
can
look
at
the
number
of
commits.
We
can
look
at
the
number
of
comments.
We
can
look
at
the
number
of
lines
of
code.
E
C
Just
a
single
one:
it's
a
small
update
regarding
mars
project,
so
I
guess
just
update
you
so
for
the
automated
matrix
release
process,
we
require
some
of
some
of
the
things
that
we
want
to
extract
from
the
markdown
files
of
the
metrics
like
the
metric
name,
the
metrics
question
the
focus
area
goal
so
the
extraction
of
these
files.
C
C
C
E
A
A
A
I
think
this
is
sean's
mapping
of
release
that
metrics
to
be
included
in
the
auger.
I
guess
this
is
what
my
hand
is,
I'm
not
sure.
E
No,
the
I
think
this
is
the
these.
Are
the
metrics
that
we'd
like
to
that
we'd
like
to
release
in.
A
A
E
And
then,
when
we,
when
we
started
so
this,
this
was
about
this
was
about
breaking
down
like
the
work
and
activity
that
exists.
C
E
C
E
A
A
E
E
A
Yeah,
so
these
are
like
wish
wishlist
for
the
release
and
what
work
to
be
done.
E
Yeah
yeah,
this
is
yeah
the
the
wish
list
or
the
the
things
that
we
should
that
we
should
be
working
on,
and
I
think
the
I
think
the
idea
here
is
to
just
is
to
focus
on
change,
requests
and
kind
of
do
a
deep
dive
on
change
requests.