►
From YouTube: CHAOSS Evolution Working Group 1-27-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
Welcome
to
the
actual
first
evolution
meeting,
that's
being
recorded
and
note
taken
in
2021
today
january
27th,
I've
posted
the
minutes
in
in
the
chat,
and
I
will
share
my
screen
I'll
make
that
smaller
and
put
it
on
one
side,
one
screen,
and
so
what
I
thought
we
would
do
is
I
went
through
the
the
metrics
that
we
are
working
on
and
I
think
there
are
three
that
are
potentially
releasable
but
require
a
little
bit
of
work.
So
I
thought
maybe
we
could
just
use
this
time
to
work
on
them.
A
If
I
open
that
one,
the
change
request,
acceptance
ratio,
you
can
see,
there's
been
a
lot
of
discussion
and
there's
some
visualization.
So
I
think
this
one
of
the
ones
I
looked
at
appeared
to
be
to
be
the
most
releasable.
A
It
is
in
the
me
it
is
in
the
minutes,
but
I
will
also
post
it
in
the
chat
which
I
have
to
go
to
when
I'm
sharing.
I
have
to
bring
up
a
chat
window
change,
request:
acceptance,
ratio,
okay,
okay,
thank
you,
yeah
right
away,
somebody's
highlighting
reviews,
because
that
is
not
what
this
is
anymore,
so
yeah
go
ahead
and
change
that.
A
So
elizabeth,
what
has
been
our
custom
with
regards
to
recording
during
editing
sessions?
Do
we
stop
the
recording
instead
of
extending
video.
C
Yeah,
I
think
we
used
to
not,
but
we
decided
to
do
that
if
we,
if
we
think
of
it,
just
because
it's
kind
of
boring
for
someone
who's
who's
watching,
but
since
you're
sharing
the
screen
like
it's
totally
up
to
you,
because
someone
can,
you
know,
watch
so
whatever
whatever
you
want.
A
A
The
recording
so
that
there's
a
full
record
of
how
we
proceed
with
these
edits
yeah.
Since
you
know
really,
this
one's
been
left
open
and
I've
pinged
grimoire
lab
a
couple
times
waiting
for
their
input,
but
I
think
at
this
juncture
I'm
gonna
accept.
A
A
A
A
A
A
C
A
C
What
did
you
say
before
that?
You
said
something
about
something
should
be
an
additional
metric.
A
So,
for
example,
one
of
the
ways
that
we've
looked
at
change
request
acceptance
ratios
is
to
look
at
the
length
of
time
that
pull
change,
requests
that
are
open,
I'm
sorry,
the
length
of
time.
A
change
request
is
open
on,
on
average,
for
the
in
a
period
of
time
for
those
poll
requests
that
are
merged
compared
with
those
pull
requests
that
are
not
not
merged.
A
C
Yeah,
we
have
a
change
request,
duration,
so
I
feel
like
that
would
be
a
filter,
then,
on
that
right,
yeah.
A
A
So
that's
a
good
question.
I
think
perhaps
the
whether
the
pull
request
is
initiated
from
a
branch
within
the
project
or
a
fork
of
of
the
project
is
one
way
of
indicating
whether
it's
an
ins
sort
of
you
generally
aren't
able
to
push
to
a
branch
of
a
repository
unless
you
have
some
kind
of
privileges
on
that
repository.
So
the
origins,
whether
it's
a
branch,
whether
it's
a
branch,
review,
a
change
request.
B
A
So
so
I
guess.
C
And
sean
when
you're
done
with
that.
A
I
don't
know
if
this
all
needs
to
be
here.
I
tend
to
explain
or
use
too
many
words.
D
A
A
B
B
A
Actually,
these
visualizations
can
now
be
generated
using
auger
community
reports.
Okay,
so
I'm
gonna
insert
a,
I
think,
there's
a.
B
B
B
A
Let's
see
that
you
would
you
think
I
mean
the
images
come
with
captions,
but.
A
A
A
A
A
E
C
Sorry,
if
you
all
talked
about
this
already,
but
should
we
ping
gremorelove
again
or
what
do
we
want
to
do
with
that.
A
We
we
could
ping
them,
but
I
don't
wanna.
I
also
wanna
hold
up
the
release
of
the
metric
and
I'm
like
through.
I
think
I
guess
my
take
would
be
that
we
definitely
wanted
for
more
lab
metric
in
here
and
when
this
circulates
they'll
create
one,
because
I'm
sure
that
I'm
sure
they
have
I'm
sure
I
mean
I.
But
if
you
have
a
different
opinion
I
mean
we
could
ping
ramona,
I'm
just
trying
to
keep
my
inbox.
A
A
B
Distribute
something
sean
for
the
time
series
analysis.
I
would
suggest
you
make
the
x-axis
you
can
in
incline
it
make
it
like
45
degrees,
so
that
we
really
capture
the
points
you
see
what
I
mean
because
sometimes
55
degree
x-axis.
What
does
that
even
look
like
yeah,
because
if
you
do
it
to
make
it
a
slant
like
let's
say,
30
or
45
degree,
we
will
really
see
the
points
where
they
really
mark
the,
where
the
different
time
series,
of
course,
do
you
have
an
example
of
a
visualization
that
has
a
45
degree.
B
A
You
want
the
labels
to
be
angled,
yeah
that
I
can't
make
that
change
before
the
review
period
begins.
But
I
guess
it's
a
question
of:
does
the
working
group
want
to
hold
up
this
metric
until
that
change
is
made,
or
do
we
want
to
make
that
suggestion
during
the
review
period
and
address
it?
Then
that's
a
basically
a
question
for
you
armstrong,
sorry,
so
it's
the
27th
and
I
think
the
the
metrics
have
to
be
submitted
for
release
by
the
31st,
which
is
sunday.
A
I
suppose-
and
I
I
can't
make
this
change
before
then,
so
our
choice
would
be
to
either
not
release
this
metric
or.
A
I
would
yeah,
I
would
guess
I
would
yeah
let's
and
when
we
release
metrics
for
review.
Is
this
the
process
through
which
kevin
takes
this
and
puts
it
in
the
actual
markdown.
B
A
A
So
that's
why
at
first
I
was
puzzled,
but
now
I
understand,
do
we
want
to.
B
Okay
and
then.
B
Okay,
just
one
thing
in
this
description
for
figo
one,
we
use
the
word.
The
second
line,
pull
requests
open
per
week
in
the
first
case
and
closed
put
per
week.
B
In
the
second
case,
did
we
describe
the
first
and
second
case
some
ways
for
people
to
understand
what
we
are
talking
about,
because
it
seems
it's
just
appearing
out
from
nowhere?
Where
is
the
first
case?
In
second
case
language
configure
one
we
are
beneath
the
figure
you
have.
These
two
visualizations
are
provided.
A
B
And
maybe
the
next
two
visualizations.
A
A
I
don't
know
this
whole.
I
think
that
whole
paragraph
should
could
go
because
I
each
of
the
visualizations
itself
is
captioned
and
you
know
I
don't
want.
A
A
Hi
king,
just
to
let
you
know,
there
are
three
potential
metrics
that
we're
considering
for
to
have
the
potential
metrics
for
release
that
are
far
enough
along
and
we're
working
on
the
first
of
those
three
right
now
and
let
me
just
re-paste
the
minutes.
Let's
see
this
is
the
one
we're
working
on
right
here
and
then
the
minutes
are
right
here.
E
A
Well,
you
could
put
your
name
in
the
attendee
list
if
you
wish
going
back
to
this
metric
without,
I
guess,
if
there's
no
further
discussion,
I
suggest
we
put
this
forward
in
the
spreadsheet
as
ready
for
release.
A
Which
change
request
acceptance
ratio,
so
we
would
say
this
one
should
go
under.
How
does
the
I
you
know?
It's
been
a
while,
since
I've
done
this,
if
I
say
it's
under
community
review,
do
I
need
to
then
do
we
need
to
tell
kevin
about
it
or
do
they
just.
A
C
A
A
A
A
E
D
I
think
the
creator
is
awesome.
I
I
think
it's
very,
very,
very
good.
You
know
a
great
big
gregaters.
A
Yeah,
I
think
I
think
this
metric
is
more
mature
than
the
first
one
we
looked
at
when
we
started
I'm
going
to
accept
any
changes
that
are
not
mine.
E
B
Okay,
yeah
on
the
branch
life
cycle.
I
think
we
should
be
consistent
with
our
what
if
we
are
talking
about
destruction
and
deletion,
we
mean
the
same
thing
but
two
different
work
that
can
create
a
little
bit
of
confusion
here,
which
page
are
you?
I
guess
page
number
from
the
branch
life
cycle,
the
description
yeah.
We
started
by
talking
about
the
actions
that
could
be
performed
on
a
repository
branch.
We
talk
about
like
the
creation,
the
deletion
things
like
that,
then
yeah
death
is
equal.
B
A
A
A
A
A
A
A
A
Because
we
don't
actually
have
this
in
the
straight
up,
auger
dashboard,
it's
something!
That's
in
the
community
reports
that
we
started
to
develop,
but
we
have
the
data
we
could
we
collect
all
of
the
pull
request
data
like
all
of
the
pull
request
data
employed,
including
the
details
of
every
review.
A
C
A
A
A
Is
this?
What
is
it?
Are
we
trying
to
say
that
that
people
are
using
the
same
branch
remotely
and
pushing
their
changes,
because
sometimes
that
does
happen?
If
you
have
multiple.
A
I
think
I
think
that's
true.
I
think
that's
a
valid
criticism
that
that
really,
when
it
comes
to
the
actual
repository
data,
there's
not
much
you
can
get
from
github
about
the
branches
when
they
become
pull
requests
or
merge,
requests,
that's
a
different
matter,
but,
like
every
git
repository,
I
think
to
your
point.
Whoever
space
fish
is
each
I
mean
I
can
get
everything
I
get
all
the
problems.
I
get
all
the
repository
comments
and
everything
out
of
the
git
log.
I
don't
need
github
or
gitlab
for
that.
A
A
A
A
A
Oh
just
if
if
this
should
be
like
using
markdown
header
symbols
or
just
the
bolding
and
my
own
answer
to
my
question,
is
I
have
no
idea
and
we
can
just
leave
it
like
it
isn't.
If
it's
wrong
kevin
will
tell
us.
A
Well,
he's
not
familiar
with
the
github
api.
I'm
really
only
talking
about
the
the
markdown
presentation
of
this
heading
specific
description
of
get,
whether
it's
you
know
whether
it
should
be
bolded,
as
that
markdown
indicates
or
whether
it
should
be
at
a
heading
level,
and
I
actually
have
no
idea
because
it's
not
a
conventional
part
of
the
metric,
but
I
think
it's
essential
here
so
rather
than
us
trying
to
guess.
B
A
B
A
Go
to
the
spreadsheet
that
was
branch
lifecycle.
D
D
A
So
if
it's
green,
it's
already
really
been
released.
If
it's
this
yellow
color,
it's
like
light
yellow,
then
it's
in
some
stage
of
development.
A
So
before
the
meeting
I
went
through
and
identified
the
three
metrics
that
were
farthest
along
in
their
development
and
I
think
we
completed
two
of
them
and
I
think
change
request
comments
is
the
third
which
we
don't
have
time
for
it
is
not
as
far
along
as
the
others,
so
I
would
say,
depending
on
my
level
of
ambition
and
your
level
of
admission
will
versus
hard
or
we
won't
at
the
end
of
the
day.
But
we
have
two
metrics
ready
for
release
here
at
the
end
of
the
evolution
meeting
on
january
27.
A
2021
so
our.
A
Will
be
two
weeks
from
today,
which
I
don't
know
is
gonna,
be
what
I'll
take
I'll
take
I'll
take
an
action
item
here
at
the
end.
To
just
do
the
do
the.
D
D
So
we
we
have
released
the
candidate,
the
metrics
yep.
E
A
A
So
I
think
I
don't
think
too.
I
don't
think
two
metrics
is
bad,
that
that
is
a
bad
showing
for
a
working
group.
That
is,
it
has
a
lot
of
metrics
already.
So
I'm
proud
of
us.
We
did
a
good
job
and
I'm
gonna
stop
the
meeting,
and
I
will
see
you
all
in
two
weeks.