►
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
So
thanks
sorry
for
coming
who's
interested
who
are
interested
in
this
subject
of
you
know,
analysis
of
mrs
merged
in
greater
than
30
days,
so
I've
seen
a
lot
of
good
comments
already
in
the
document.
Let
me
let
me
share
my
screen
here.
A
A
You
know
there
is
definitely
a
behind
a
significant
number
at
a
really
high
amount,
like
you
know,
90th
percentile
120
days
about
a
quarter
or
idle
for
greater
than
or
equal
to
a
month,
sometimes
multiple
times
about
a
quarter
head
scope.
It
was
possibly
too
large
for
one,
mr,
which
was
a
judgment.
Call
just
eyeballing
them.
A
A
About
40%
of
the
mrs
took
greater
than
30
days
to
merge
were
from
forty
authors
out
of
the
92
total
that
had
one
or
more
that
were
more
than
30
days,
so
there's
kind
of
a
little
bit
of
cluster
there,
but
not
a
huge
cluster
and
median
days
to
merge
by
label.
Documentation
was
actually
much
higher
than
others,
but
there
were
very
few
ones,
tagged
with
documentation,
so
that
might
have
been
it.
C
C
A
It
was
that
I
did
notice
where
it
got
they
honest
they
get.
They
were
assigned
to
somebody
who
left
the
company.
Occasionally
that
was
the
case
or
sometimes
they
unassigned
themselves
and
nobody.
They
commented
a
you
know
so-and-so.
Could
you
pick
it
up
and
they
didn't
or
they
just
assign
unassign
themselves
and
it
left
it
stayed
on
a
sign
for
a
while,
so
that
I
didn't
notice
that
those
things
very
often
usually
it
stayed
with
the
same
person.
Okay,.
D
A
A
great
question:
I
don't
know:
I
do
have
the
data
linked
which
doesn't
have
people's
names
in
it.
So
it's
got
officer
IDs,
so
I.
Look
here.
We
you
can
take
a
look
I
think
we
can
spend
some
time
on
that,
but
here's
just
by
days
this
is
actual
days
to
merge
and
the
number
of
them
so
like
here
we
take
the
ones,
let's
say
greater
than
or
equal
to
90.
A
D
A
D
It's
a
good
point
just
spending
ten
seconds
here.
This
is
like
a
something
that
we've
been
looking
at
for
a
while.
It's
the
type
of
backstage
work
like
the
whether
it's
a
document
or
something
else
I've
been
having
backstage
right
now
at
the
level
of
the
operating.
Doesn't
it's
not
as
helpful
so
just
went
to
it
that
we
have
an
issue
going
back
to
what
we
talked
before.
I
think
row
number
seven,
that's
also
refactor
Docs,
that's
also
backstage,
and
just
what
point
is
like
there's
a
number
of
new
documentation
here.
D
A
E
Think
there's
a
priority
order,
so
what
a
lot
is
I
think
in
that
calculation
is
a
priority
order
and
documentation
towards
the
end
and
documentation
is
frequently
collided
with
other
type
labels,
so
maybe
reordering
that,
for
this
analysis
or
in
general,
might
be
a
good
idea
to
have
documentation
with
depth
or
to
the
top
I.
Remember
right:
the
order
was
like
community
contribution,
feature,
bug
backstage
and
then
documentation,
I'm
Lily,
you
may
know,
based
on
this
analysis,
I.
D
Think
for
the
purpose
of
analysis,
we'd
have
to
jump
when
I
get,
but,
yes,
I
think
all
we
should
have
discussed
as
a
team.
How
we
want
to
have
that
accounting,
but
for.
C
Either
way
mech
I
agree
with
you,
we
should
try
to
get
backstage
down.
It
feels
like
it's
just
too
heavily
used
ain't.
Somebody
at
one
point
told
me
today.
A
lot
of
this
is
feature
work
I've
been
using
fifty
fifty
fifty
feature
of
fifty
technical
debt,
but
the
problem
that
I've
heard
is
is
like.
If
we
use
the
feature
label,
then
that
leads
to
other
things
like
they're,
expecting
documentation
actually
included
as
part
of
it,
which
you
know.
D
A
C
E
Iii
like
down
at
the
bottom,
to
a
snippet
that
derives
a
lot
of
those
feel
so
down.
In
the
discussion
section
I
went
to
a
snippet
that
has
like
Easter
beauties
like
a
number
of
different
items.
That
could
be
helpful
if
there's
probably
more
fields
that
we
can
look
to
use
and
that
snippet
should
encompass
a
Mars
that
you're
doing
so
when
you
and
I
or
Lily,
like
the
three
of
us
there's.
Some
combination
of
us
can
figure
out
how
to
take
the
data
that
put
together
in
that
snippet
and
add
it
to
your
awesome.
F
E
A
F
A
A
A
C
Make
sure
to
find
thread,
everybody
remember
this
is
fun
to
bully
threads
are
and
she's
a
data
analyst,
not
a
software
developer.
Threads
are
the
method
at
commentary
and
potentially
get
changes
associated
with
an
mr.
So
like
it's
an
opportunity
for
people
to
give
feedback,
and
typically
what
happens
is
somebody
will
give
some
feedback
and
I
forget
if
you
have
to
determine
whether
you
actually
open
a
threat
or
not,
but
then
there's
response
back
and
forth
and
then
once
the
issue
is
resolved
and
they
resolve
the
thread.
A
Items
I'm,
sorry,
the
other
items
worth
what
we
think
is
worth
that.
Looking
into
studying
his
pipelines,
his
number
of
times
changes
were
made
and
basically
the
CI
CD
pipeline
was
kicked
off
to
check
it
and
then
commits
his
number
of
changes
done
as
part
of
this
change,
not
number
of
files
updated,
but
number
of
changes
done
to
any
number
of
files.
A
All
right
so
notice,
the
number
of
folks
you
know
know
there
are
a
couple
of
recommendations.
Added
these
are
draft
would
be
really
clear.
These
are
draft
so
idle,
mrs
mrs
calm,
idle
idle,
and
they
then
are
often
forgotten
for
a
while
for
various
reasons.
So
my
initial
thoughts
were
if
a
merge
request
is
idle
for
greater
than
two
weeks
have
a
body
out
of
comment,
saying
hey:
this
has
been
I
over
two
weeks.
A
You
know
maybe
consider
splitting
it
down
to
smaller
ater
change,
reassigning
moving
non-critical
review
feedback,
separate
issues,
and
if
it's
greater
in
four
weeks,
look
up
the
group
manager
and
tag
those
same
recommendation,
and
maybe
this
is
too
much
that
just
the
first
one
is
okay,
because
the
managers
are
often
watching
the
issues.
But
that
was
an
idea
on
idle,
mrs
and
adding
that,
just
before
I
paws
is
mrs,
it
may
have
fallen
to
the
cracks.
It
might
be
that
they're
idle.
It
might
be
that
they're,
not
idle
and
they're.
A
Just
they're,
just
being
worked
on
over
a
longer
period
of
time,
is
maybe
bought.
Adding
a
comment
around
that
and
then
also
different
kind
of
thing,
adding
a
reporting
periscope,
so
many
ORS
we're
open
greater
than
four
weeks
and
have
it
part
of
the
directors
responsibilities
to
review
that
periodically.
What
does
everyone
think
of
these.
B
D
Is
a
kind
of
the
same
head
of
an
in
line
with
how
we're
doing
the
sorry
for
the
noise
community
contributions
report?
We
have
a
weekly
report
that
sends
out
to
a
peg
on
what
are
the
scale
community
contributions
in
mars
and
he
helps
review
now.
That
is
a
smaller
population.
I
think
we
can
take
some
of
the
loadings
there
and
applied
here.
I.
Think
having
a
reminder
works
great,
maybe
even
help
have
the
body
help
set
up
you
take
that
might
be
controversial,
but
we
can
explore
multiple
options
here.
E
E
C
E
E
Yeah,
so
there
may
be
something
I'm
missing
so
like
similar
disclaimer,
normal
disclaimers,
but
I,
don't
think
it
would
be
too
hard
at
using
last
updated
they
we
could
create
an
issue,
but
one
I'd
want
to
look
at
the
priorities
across
the
team.
Make
sure
that
this
is
the
right
thing
to
jump
in
on
right
now.
It.
D
C
What
I'm
wondering
is,
if
we
just
start
with
a
single
one
for
the
entire
group
and
it's
gonna
be
super
long,
but
then
I
get
the
directors
to
look
at
and
then
we
get
feedback
on
it.
Based
on
that
to
figure
out
whether
or
not
there's
a
better
way
to
tune
it
is
what
I
don't
want
to
do
is
create
tuning
before
a
pre,
premature
optimization.
So
that's
I'm
wondering
that.
What
do
you
think
about
that
tactic,
or
do
you
think
it's
better
to
try
to
go
to
EMS
or
I.
A
A
We
run
the
benefit
benefit
of
helping
there's
a
risk
of
annoying
people
with
lots
of
you
know,
issue,
comment,
spam
and
issue
spam,
etcetera
or
maybe
perceived
as
such,
so
I
definitely
want
to
do
everything
on
this
list,
even
if
we
like
them
all
initially
so
I
actually
kind
of,
like
the
periscope
report,
a
little
more,
but
that's
partially,
because
I
haven't
seen
a
triage
package
issue
before
so.
A
Does
this
you
know
we
can
make
it
part
of
you
know
something
we
review
Christopher
and
you're
kind
of
like
we
do
for
availability
triage
or
we
make
it
an
agenda
item
and
your
weekly
meeting,
maybe
once
a
month
I,
don't
know
this
is
what
I
prefer,
but
it's
probably
because
I
know
what
one
I'm
more
familiar
with
this
kind
of
thing,
but
I'm
good
with
either
so
wondering
this.
Is
we
mark?
This
is
Kyle
for
you
to
research,
this
one
and
yeah
Mick
for
you
to
research,
one
two
and
three
that.
C
You
know
outside
in
or
small
inside
out,
so
like.
If
there's
a
particular
group,
that's
more
problematic
than
we
could
start
with
that
director
in
that
that
manager
or
set
of
managers
will
need
to
classify
based
on
that
I.
Like
the
suggestion
that
way,
maybe
maybe
that's
the
discussion,
we
have
it
the
next
one
next
development
meeting
or
we
start
trying
that
push
that
for
that
perspective,
because
right
now
we're
looking
at
closed.
So
we
need
the
open
list.
C
C
E
C
C
Like
the
trash
package,
the
reason
Wayne
that
I
like
the
triage
package,
is
it's
it's
a
less
at
the
senior
leadership
level
and
more.
If
you
will
be
the
accountable
x',
but
then
it
gives
eum's
the
ability
to
actually
execute
on
it
right
from
that
perspective.
So
that's
the
reason.
This
reason
why
we
use
triage
they
use
it
a
lot
for
our
lower
level
stuff.
Maybe
when
we're
not
using
it
defend
quite
yet,
but
that's
that's.
Definitely
it's
been
pretty
effective,
pretty
the
dev
organization
and
solving
problems.
That's
right!
Yeah.
E
D
C
To
be
honest,
if
you
had,
if
you
really
want
to
get,
this
is
way
too
much
work,
but
if
you
really
want
to
get
good
at
this,
you'd
go
back
and
refactor
that
and
make
it
into
an
epic
and
then
have
the
issues
below
that
broken
out
based
on
type.
Because
then
you
could
have
team
different
team
members,
detecting
difference,
that's
so
the
parts
the
problem
associated
with
it
right
because,
like
this
is
an
element
I'm
thinking
back
to
the
triage
package.
C
E
D
C
A
B
A
Do
a
sampling
of
em
ours
that
are
done
merged
in
less
than
30
days
versus
more
so
the
number
was
about
20
I
seemed
to
be
a
good
break.
I,
go
to
the
statistics,
unthreads
per
Mr,
so
greater
than
30
M,
ours
merged
in
less
than
30
days
and
18
threads
on
average
compared
with
8
days.
It's
our
eighth
writes
for
less
than
30
days
and
the
median
11
for
ones
greater
than
30
days.
I'm
gonna
call
those
late.
D
Think
it's
at
small
color,
to
the
reason
why
something
is
taking
the
long
blonde
pole
I
asked
below
of
the
the
delay
or
the
long
haul
is
actually
review,
since
that
seems
to
correlate
to
some
of
that
aspect.
A
Yeah,
you
know,
I
didn't
actually
look
into
it
that
level
of
detail,
but
that
would
be
there,
be
there
be
great.
So
if
we
could
get
not
only
time
to
merge,
but
you
know
where
it
is
in
the
various
stages,
so
in
development,
in
with
the
reviewers
and
with
the
maintainer
I,
don't
know
if
that's
something
that
we
can
add,
but
that
would
be
creatively
I
didn't
look
to
if
that
exists,
that
don't
think
it
exists,
at
least
in
the
table.
We're
looking
at
now.
Did
that
be
great.
Add
the.
C
Other
question
would
be
is
if
there
was
a
threshold
like
those
20
threats
all
got
created
at
once
or
if,
if
those
were
like
done
over
a
period
of
time,
if
it
turned
out
that
it's
like
you
know,
if
you
had
five
threads
start
off
immediately,
this
is
already
like
an
early
warning
that
this
is
gonna,
be
a
long.
Mr
from
that
perspective,
right
cuz
like
it.
If
it's
J,
if
it's
added
over
time,
it
may
just
be
too
much
back
and
forth,
but
it
could
be
also.
C
E
D
E
A
With
five
ish
minutes,
left,
I
think
I
think
I
think
it's
been
great
discussion
yeah.
What
I'd
recommend
we
do
is
I'll
update
the
things
where
we've
already
discussed.
You
know
we
didn't,
we
didn't
mister
go
in
order,
which
is,
of
course
fine,
so
I'll
catch
up
on
those
like
you
know
your
your
items
on
you
know
some
of
this
as
well.
At
war
time
is
spent.
Maybe
that's
something
Lily
you
can
look
into
as
well
by
stage
where
we
know
it,
and
then
is
this.
A
D
C
A
C
Here's
maybe
the
right
way
to
approach
it,
so
I
think
Mac
and
I
are
basically
saying
we
don't
have
the
bandwidth
necessarily
drive
this,
but
we
want
to
definitely
see
the
results
with
it.
So
if
Wayne
you
wanted
to
be
the
exec
sponsor,
three
things
are
going
to
find
somebody
to
represent
from
quality,
maybe
Kyle,
maybe
somebody
else
as
a
team
member
somebody
to
facilitate,
which
could
be
one
of
your
engineering
managers
who
is
interested
in
this
or
it
could
be
another
engineering.
C
And
then
the
third
thing
is
is
just
you
know,
DMR
to
actually
merge
it.
So
if
you
think
it's
worth
I
think
it
I
think
I'm
kind
of
on
the
fence
on
this
one
because,
like
I,
feel
like
it
could
be
a
short-term
thing
or
could
actually
be
a
long-term
thing
and
I
can't
I
can't
put
my
finger
on
which
one's
good
this.
C
E
C
C
The
one
thing,
though,
is,
is
that
we're
gonna
figure
out
I
could
slay
this
tail
and
then
we're
gonna
get
asked
to
move
to
the
next
tail.
So
that's
the
that's.
The
one
thing
I
could
see.
So
that's
something
Nikki
and
I
probably
need
to
think
about
or
there's
gonna
be
some
other.
As
we
last
the
spring,
we
had
a
basically
an
analytics
working
group
and
may
be
worthwhile
for
us
to
do
that
again
with
a
different
cover
to
folks
metrics
yeah,
the
dead
metrics.