►
From YouTube: CHAOSS.Common.May.14.2020
Description
CHAOSS.Common.May.14.2020
A
We
have
a
few
things
on
the
agenda,
so
we'll
review
some
action
items
and
notes
from
the
previous
meeting
look
and
see.
If
we
have
any
PRS
and
issues
which
I
forgot
to
look
before
the
meeting,
we
can
also
review
the
progress
on
the
metrics
spreadsheets.
If
there's
anything,
we
want
to
do
there
progress
on
continuous
release
for
the
time
to
closed
metric,
which
is
the
one
that
we
kind
of
finished
last
time.
A
A
A
I
feel
like
yeah.
This
is
like
the
third
week
in
a
row
third
meeting
in
a
row
that
I
have
not
done
the
thing
that
I
said:
I
would
do
so
yeah
we'll
work
on
that
Shauna
obviously
has
not
done
the
well
I.
Don't
know
if
he's
not
done,
if
he's
not
here,
to
tell
us
he's
done
it.
So,
let's
just
assume
it's
not
done.
A
C
A
A
So
we
have
the
metrics
candidate
time
to
close,
so
we're
still
looking
for
for
feedback
on
that,
so
that
one
looks
like
it's
in
in
good
shape,
so
we'll
see
if
we
get
some
feedback
on
that,
we
can
have
another
look
at
it
again
next
week,
unless
anybody
has
anything
that
they
want
to
want
to
talk
about
on
that
metric.
It
a
lot
more
detail
last
week,
I
might.
C
D
C
A
Good
idea,
common
metrics
release
notes,
so
this
was
for
the.
A
C
A
C
The
initial
message
so
when,
when
the
time
to
close
metric
is
released,
will
actually
will
just
add
the
notes
to
that
very
similar
to
the
types
of
contributors
or
contributions.
Note,
that's
there
now.
So,
just
like
the
name
of
the
metric,
the
link
to
it,
the
comment
period
issue
and,
and
just
when
we
released
it
just
so,
we
have
information
for
the
release,
notes
at
the
end
of
the
year
or
by
yearly.
However,
weird,
but
okay.
A
B
B
A
B
E
This
was
something
I
found
in
a
research
paper
and
the
idea
is
that
activity
is
not
always
the
same,
and
sometimes
you
have
you
know
long
pauses
and
bursts
of
activity
again
and
just
to
have
I,
don't
know
if
it's
a
metric
in
an
outfit.
So
maybe
there
is
I,
don't
remember,
but
it's
a
way
of
looking
at
the
activity,
data
and
making
sense
of
it.
So,
especially
around
releases
scheduled
releases.
You
typically
see
a
lot
of
activity
right
before
and
then
a
slump
over
KT
after.
A
Yeah,
that's
interesting
I,
since
this
comment
honors
that
you
could
apply
it
to
any
any
time
series
metric.
So
is
that
a
is
it
a
metric
or
is
it
a
way
of
measuring
time-series
metrics.
E
D
E
D
B
A
B
A
Yeah,
probably
if
it
was
yeah,
if
it
was
a
kind
of
a
project
that
was
sort
of
strategic
for
us
and
there
was
all
kinds
of
activity
all
of
a
sudden
as
I
would
probably
want
to
know.
Why
and
whether
or
not
it
was
something
that
was
likely
to
continue
because
the
burstiness
could
be
it
could
be
burstiness.
That's
an
indicator
of
a
bunch
of
you
know
like
acceleration
of
the
project
and
future
activity.
So
it
could
be.
A
It
could
look
like
burstiness
and
then
turn
into
something
that
was
sustained
over
time
or
it
could
be
burstiness
where
it's
something
like
you
know.
We
decided
to
refactor
a
big
chunk
of
the
code
and
there
were
a
whole
bunch
of
pull
requests
and
commits
and
lines
added
and
deleted,
and
it
looked
like
a
ton
of
activity
that
was
really
sort
of
a
one-off
and
I
guess.
I'd
probably
want
to
know
which
one
of
those
it
was.
B
A
B
A
Don't
see
burstiness
as
a
metric
in
and
of
itself.
For
me,
it
seems
like
it's
kind
of
something
that
happens
to
another
metric
or
more
of
a
maybe
a
characteristic.
So
maybe
you
would
see
during
a
refactor,
you
might
see
burstiness
and
you
know
commits
and
pull
requests.
If
you
cut
a
release
and
it
turns
out
there
was
something
terribly
wrong.
You
might
see
burstiness
an
issue
filing
filing
of
issues.
For
example,
okay,.
B
E
C
F
F
F
F
F
They
are
the
ones
that
are
telling
you
the
stability
in
the
process,
which
is
pretty
good,
I'm,
not
sure
if
this
applies
I
mean
you
can
have
this
word
first
burstiness
for
comments,
but
we've
seen
everywhere
that
if
we
are
in
in
Christmas
suddenly
everyone
is
at
home,
so
they
are
not
producing
more
comets.
But
what?
If
we
think
about
the
time
too,
so
we
try
to
focus
this
on
process,
but
in
kind
of
distribution.
Our
time
measurement
would
began
in
the
title.
So
then
processes
are
perhaps
more
stable
right.
F
C
F
The
open
source
time
time
of
production
is
part
of
the
time,
but
then
you
have
the
deployment
time
internally
and
the
deployment
to
customer,
and
you
have
some
other
steps
before
this
process.
But
if
you
have
a
proper
process
in
place
that
you
can
really
predict
them
on.
From
that
point
of
view,
that
is
it
really
useful
from
a
company
perspective,
because
you
will
say:
ok,
it's
time
we
withdraw
a
ticket
into
the
community.
F
A
B
If
it's
a
metric
to
me
that
it's
measuring
like
when
burstiness
is
occurring,
so
that
would
be
electric,
so
is
burstiness
occurring
around
releases
as
burstiness
occurring
at
a
certain
time
of
the
year,
is
first
enos
occurring
around
an
event.
So
that's
if
that
would
be
the
metric
to
me
whatever
that,
whatever
that
burstiness
is
whether
it's
a
commit
or
issues
showing
up
or
merged
pr's,
because
then
I'm
measuring
burstiness
I'm
measuring
these
bursts.
F
F
F
A
E
B
So
talking
through
this
I
think
yeah,
because
then,
if
we
had
burstiness
as
a
common
metric
and
it's
appearing
in
these,
these
person
we're
trying
to
understand
burstiness,
then
or
when
these
events
are
occurring,
then
we
could
look
at
its
it's
common
to
me
because
then
it
is
common,
as
it
might
be
useful
to
look
at
the
burstiness
of
issues
mm-hmm
to
look
at
the
burstiness
of
merged
pull
requests.
It
might
be
coming
to
look
at
the
burstiness
of
I,
don't
know
whatever
the
other
metric
is.
Maybe
you're
right
apply
it
to
I.
A
F
E
A
E
A
B
A
A
A
B
You
can
see
that
that
time
zone
could
be
interesting.
I
would
like
to
know
where
people
are
located,
I'd
like
to
have
a
sense
of
where
they
are
geographically.
I
can
certainly
see
that
case.
I
could
also
see
the
case
of
gaining
insight
as
to
when
much
of
the
work
is
occurring,
which
is
the.
When
are
you
men
obviously
entangled
with
each
other?
All
right
I
mean
if
all
the
contributions
are
coming
from
the
West
Coast
I
can
kind
of
make
a
general
guess
as
to
when
those
contributions
are
occurring.
E
Sight
yeah,
so
I
was
just
reading
through
all
the
comments
again
and
to
me
it
feels
like
we
have
what
it
takes
for
this
metric
to
exist
in
the
activities
dates
and
time,
and
then
we
just
filter
it
by
the
different
modules
or
projects
or
whatever
inside
a
community.
So
to
me,
it
feels
like
this
is
a
filter
on
top
off
a
time
zone
metric.
E
Very
good,
so
I
was
reading
through
the
comments
and
cases
and
I
had
an
exchange
here,
looking
at
grimore,
lab
and
auger
in
the
time
zones,
and
we
could
clearly
identify
that
Grimlock
was
more
developed
in
European
time
zone
and
auger
in
the
u.s.
time
zones
and
so
to
me.
It's
like
taking
the
date
and
time
metric
of
when
activities
are
occurring
in
the
project
and
filtering
it
by
different
modules
by
different
types
of
activities
in
the
project.
So
feels
like
the
filter
on
the
date
and
time
metric.
A
E
E
Think
there's
a
different
component
though.
Yes,
this
is
the
time
zone.
That's
one
part
of
this
issue
31
and
the
other
one
is
where
in
the
project
is
that
time
zone
prevalent,
that's
the
project
segment,
so
our
vs.
grimore
lab,
that's
the
filter.
I
was
thinking
of
adding
to
the
date
and
time
my
drink.
Okay,.
E
A
People
agree
with
that
or
or
does
this
really
just
belong
more
in
the
the
when
category.
E
E
E
So
four
to
go
into
the
whoo
metric
I
would
want
it
to
have
an
element
of
people
and
the
level
that
this
metric
is
looking
at
is
like
activity.
We
don't
care
whether
they're
BOTS,
what
they're
people
read
their
employees
rather
than
we
don't
care
about?
Who
is
creating
the
activity?
So
to
me,
it's
not
a
veteran.
A
B
A
G
Yeah
and
I
think
at
least
for
my
aspect:
I
was
I'm
trying
to
remember
I
think
there
was
like
wondered,
maybe
outstanding
questions
I
had
for
folks,
I,
don't
know
if
there's
still
little
tags
in
the
doc
or
not,
but
I
thought
we
were
I
know
we
had
talked
through
this
and
I
thought.
We
were
like
at
least
at
the
90
percent
point,
but
I
could
be
wrong.
Yeah.
A
B
A
G
Think
it's
a
bad
idea.
I
think
it
actually
debated
a
little
bit
of
of
how
we
were
of
how
the
way
to
Divya
down
I'm
kind
of
I'm
racking
my
meat
or
brain
on
this,
but
I
think
I
think
there
was
an
open
question
of
how
specific
he
wanted
to
get
versus
how
broad
you
wanted
to
get
and
I
I.
Don't
know,
I,
think
I
think
there
was
an
effort
and
I
could
be
wrong
here
of
wanting
to
keep
this
ambiguous
on
purpose.
G
G
G
Yeah,
maybe
maybe
I
think,
maybe
that's
just
like
a
data
collection
point
but
I
think
when
were
it
was
I.
Think
now
that
it's
coming
back
to
me
it
was
the
way
that
this
might
be
visualized
or
aggregated.
That
could
be
a
dimension,
but
it
wasn't
define
dimension
and
I.
Think
that's
more
of
like
a
a
date
point,
a
data
point
that
you
might
want
to
collect.
A
Yeah
I
remember
what
you're
talking
about
when
you,
when
you
mentioned
that
we
wanted
to
leave
it
a
little
bit
ambiguous
because
people
might
what
we
talked
about
is
some
people
measure
by
country
by
state
by
city.
So
I
think
that
was
the
level
of
granularity
that
we
didn't
want
to
get
to
and
I
think
we
don't
necessarily
want
to
specify
I.
A
G
A
A
F
B
A
D
A
Yes,
okay,
clarifying
qualitative
measures
Georg.
This
was
your
issue.
Do
you
want
to
talk
about
that?
Oh.
A
A
A
C
F
A
A
F
A
A
look
at
it
and
then
I
think
there
was:
is
there
one
more
management
of
organizational
affiliation
and
email,
aliases
large
scope
for
discussion?
Okay,
we
have
really
five
minutes
left
in
the
meeting.
I'm
gonna
say
that
we
do
we
want
to
tackle
this
one
or
do
we
want
to
table
it
and
make
sure
we
covered
the
rest
of
the
agenda.
A
A
B
A
A
All
right
with
that
I'm
gonna
go
ahead
and
stop
sharing
I.