►
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
good
stuff
over
the
last
week
just
have
some
notes
in
the
doc
I
reordered
it.
So
the
most
recent
is
at
the
top,
not
at
the
bottom
easier
to
find
so
kyle.
I
think
I
think
it's
great
all
the
the
work
done
on
the
idol.
A
Mr
triage
reports
triage
issues,
the
good
stuff.
I
took
a
look,
I
don't
know,
do
you
want
to
maybe
bring
one
up
and
share
the
screen
and
we
can
kind
of
review
it
together.
Yeah.
B
All
right
so
this
was
like,
I
would
say,
an
early
prototype.
I've
asked
originally,
the
ass
was
just
to
really
have
what
I'd
say
is
in
this
section,
the
four
weeks
stale.
B
I
did
capture
all
the
numbers
for
two
weeks
still
as
well,
for
all
the
groups
that
we
did
dry
runs
for
it's
very
simple,
triage
package.
The
idea
here
is
that
it's
assigned
to
the
same
people
that
the
team
triage
package
is.
This
looks
at
all,
mrs
that
have
not
been
updated
within
four
weeks.
This
just
just
kind
of
displays
them
as
very
simple
guidance
of
review.
These
mrs
identifies
any
steps
to
shorten
the
time
to
merge
and
some
suggestion
here.
B
Usually
when
we
do
a
team
triage
package
like
this,
we
try
to
communicate
broadly
in
advance
and
make
sure
there's
a
clear
action
for
the
triage
package
owners,
because
otherwise
there's
a
lot
of
confusion
and
then
it
won't
get
off
to
a
good
start.
So
I
provided
some
feedback
to
jin
shin
who
was
the
who
worked
on
the
triage
package
just
to
make
some
adjustments
like
show.
Only
the
four
weeks
section
and
then
once
and
he
shared
that
he
that
those
should
be
done
next
week.
He
is
off
on
monday
as
well.
B
So
I
think
it
won't
be
till
the
middle
of
the
week
and
we
can
start
to
communicate
out
to
the
triage
package
owners
and
create
an
issue
for
feedback.
After
doing
a
you
know,
one
or
two
runs,
which
should
be
every
two
weeks.
One
of
these
will
be
generated,
so
it's
not
going
to
increase
load
significantly.
A
Yeah,
I
think
it
looks
great.
It
sounds
a
great
great
plan.
One
thing
is
a
little
a
little
separate
topic
or
tangent
topic.
If
this
is
successful,
which
I
think
it
will
be
as
we
tune
it,
we're
actually
initially
going
to
see
an
increase
in
mr's
merge
greater
than
30
days,
because
people
are
going
to
be
more
aware
of
them.
That
doesn't
mean
it's
not
that
doesn't
mean
it's.
B
Yeah-
and
that
would
be
the
metric
that
I
think
we
look
at
is
find
how
many
mrs
are
past:
two,
like
our
open
past
two
weeks,
past
four
weeks
and
see
how
that
trends
over
time
because
yeah,
I
think
the
right
tail
is
going
to
skew
as
some
of
these
that
have
been
open
for
quite
some
time
get
addressed.
A
B
Yeah,
I
think
next
week
we'll
do
we'll
get
it
to
a
final
state.
Look
for
final
feedback
from
this
group,
get
the
communication
ready
and
then
the
following
week
is
when
we
would
run
it
for
the
first
time.
D
B
B
D
B
So
since
this
is
for
mrs
and
that's
I
would
say,
issues
issue
focused
it's
it's
like
an
additional.
It's
an
additional
triage
package.
Just
the
way
I
look
at
I
don't
they
don't
really
intersect,
I'm
unless
I'm
missing
something.
D
Right
but
the
the
load
on
the
the
getting
pings
on
issues
for
the
rest
of
the
team.
That's
that's
that's
where
I'm
coming
from,
because
I
we've
seen
that
some
bugs
and
figures
charge
package
did
not
even
get
any
movement
when
it
comes
to
bugs.
Like
nobody
cared
about
it,
they
only
look
at
features,
and
I
wonder
how
that's
going
to
affect
the
overall.
B
It
could
be
ignored.
I
think
that's
something
that
maybe
we'd
look
at
after
a
few
weeks
is
how
many
what's
the
change,
I
would
say
so
like
if
one
group
has
six
issues
in
the
first
trash
package,
the
two
weeks
later
and
the
next
one
is,
are
those
same
six
there.
B
A
Maybe
we
we
use
these
to
select
for
issues
to
add
to
discuss
when
the
iteration
office
hours
of
you
know
if
it's
idle
for
a
long
time.
That's
indicative
of
you
know
one
day
it
might
you
know
I
only
say
that
tony
it
might
be
actually
some
of
the
ones
we
choose
to
encourage
folks
to
discuss
in
that
meeting.
A
That's
that's
good
observation
it.
It
is
so
when
they
get
back
to
them
their
lower
priority
when
they
get
back
to
them,
they
might
be
harder
to
merge
because
the
you
know
the
base
files
they're
based
on
have
likely
changed.
They're,
not
likely
they've,
possibly
changed.
So
I
think
we
have
that
in
the
advice,
if
in
the
advice
text
is,
you
know,
is
to
keep
do
we
have
that
actually
in
the
text
of
the
of
the
triage
issue,
triage
report?
C
Want
to
get
people
to
take
on
opportunities,
so
I
don't
want
them
to
feel
like
it,
but
if
they
before
it
gets
deep
prioritized,
then
you
know
we
may
see
that.
So
that's!
If
that
becomes
back
the
justification,
we
may
decide
that
there's
no
action
here.
If
that's
the
majority
of
them,
but
I
don't
think
we've,
I
don't
think
we've
seen
that
actually
yet
right
like
we
haven't
proven
that
yet
that's
a
hypothesis.
A
You
know
things
like
just
I
don't
know
all
right
in
front
of
me,
but
things
like
number
of
matter
the
size
of
the
mr,
which
can
be
measured
in
various
ways
if
that's
outside,
if
it's,
if
it's
looking
like
it's
more
like
the
ones
that
take
more
than
30
days,
even
when
it's
less
than
30
days
and
some
of
the
other
metrics-
and
I
did
take
a
look
thanks
lily
for
pulling
the
data
on
threads,
I
did
pull
the
data
on
thread,
so
that
might
be
one
we
want
to
do
as
well
in
the
future.
A
So
just
less
so
all
merge
requests.
The
average
number
of
threads
is
four
median
was
one
90th.
Percentile
was
12
threads
for
merge
requests
merged
in
greater
than
30
days.
Average
number
of
threads
is
four
fold
more
16.,
9
and
90th
percentile
is
44
threads.
So
if
we
decide
to
go
there,
we
would
probably
take
something
closer
to
a
round
number,
but
you
know
once
it
get
with
the
average
at
four
and
the
median
at
one.
A
Perhaps
if
threads
goes
greater
than
10
we'd
want
to
add
that
you
know
and
say
hey,
you
know,
there's
a
lot
of
discussion
on
this.
Can
it
be
broken
up?
Further,
you
know
is:
is
there
some
rootish
root
challenge
on
it,
etc
and
state
you
know
most,
mrs,
are
you
know
our
most
merge
requests?
Have
you
know
less
than
five
threads?
This
one
has
ten.
A
So
it's
not
a
problem,
but
it's
something
potentially
to
look
at
because
it
might
be
something
that
can
be
something
to
take
action
on
and
we've
got
the
other
metrics
as
well.
But
let's
just
go
with
this
first
one.
First
on
idle.
C
A
Yep
agreed
to
mex
point
on
all
of
these.
If
the,
if
these
get
ignored,
then
we'll
want
to
figure
what
we
want
to
do
differently
either
to
make
them
not
not
ignored
these
triage
issues
or
to
you
know,
use
other
methods,
but
let
let's
wait
and
see
you
know
we'll
publicize
it,
and
is
that
I
like
what
we're
doing
but
yeah
it
might
yeah.
D
Yeah,
so
I'm
coming
from
from
so
looking
at
it
closer,
so
I
didn't
get
to
review
it
when
we
discussed
it
last
week.
D
I
I'm
not
sure
if
adding
the
product
manager
here
will
help,
because
we
want
to
speed
up
the
review
and
it
may
be
there,
the
reviewers
instead
that
they
need
to
take
a
look
at
this
just
trying
to
be
sensitive
on
what
we
may
be
hearing
from
product,
and
since
I
erased
this,
another
small
iteration
we
can
do
is
instead
of
instead
of
21
issues
every
two
weeks,
maybe
just
one
issue
and
then
that's
all
the
stalemate,
requests
that
that
may
be
another
alternative
to
to
lessen
the
noise
and
just
have
people
work
up
on
one
one
main
list:
that's
a.
B
Is
built
that
it
would
generate
one
report
for
every
group:
okay,
all
right,
yeah,
we
could
do
exactly
like
mec.
What
you're
saying
we
could
do
that
with
the
current
logic,
where
it's
just
one
report,
we
would
want
to
tweak
the
format
of
it.
I'd
want
to
give
that
some
thought.
A
I
would
lean
towards
all
because
if
they
don't
like
it,
they'll
ignore
it
and
and
then
get
feedback,
ask
for
feedback
from
everybody,
and
then
we
improve
on
iteratively.
But
you
know,
there's
definitely
benefits
with
some
some
a
smaller
subset
first
to
get
initial
feedback,
but
I'm
fine
either
way
whatever
whatever
the
group
prefers.
C
I'm
okay
with
well
I'm
okay,
with
going
big.
The
only
thing!
Actually
I
request.
Is
you
either
go
next
week
or
go
the
week
of
the
18th?
I
would
not
go
the
week
of
the.
B
C
Yeah
we
get
18
sounds
like
the
right
thing,
because,
like
anything
too,
is
if
it
you
know
like,
like
we've
already
gotten
feedback
about
pressuring
on
on.
Mrs,
you
know
pressuring
pressuring
on
mrs
what
I
don't
want
to
be
confused
with.
Is
that
we're
causing
that
as
much
as
we're
just
trying
to
look
and
see
how
we
can
get
better
convergence?
D
C
I'm
not
going
to
do
it
today,
but
tuesday
I'll
wait
if
you
remember
to
put
it
in
the
agenda
or
I'll,
try
to
remember
a
tuesday
development
meeting.
We
can
review
on
friday
and
we
can
do
that
two
weeks
in
a
row
from
that
perspective,
that
that
would
be
my
mode
plus
my
channel
for
senior
director
of
development,
channel
development
and
engineering.
We
could
advertise
in
all
three
of
those.
D
D
Yeah,
I'm
just
I'm
just
worried
if
we
launch
something,
then
let's,
let's
make
sure
people
are
aware,
but
if,
if
this
is
what
the
group
decides
in
there,
let's,
let's
go
ahead.
Yeah.
C
C
B
Yeah
my
plan
was
before
the
meeting
next
week
to
have
an
issue
in
triage
ops
for
feedback
and
the
handbook
update
done
so
that
we
could
start
communicating
ahead
of
that
and
then
get
a
sense
going
into
our
discussion
next
week.
If
we
have
mostly
supportive
or
I'm
sure
some
people
will
be
concerned
about
adding
another
thing
to
the
stack,
I
would
say,
like
engineering
managers,
we've
gotten
that
feedback
before
when
we
changed
the
team
triage
package.
So
we'll
see.
B
Yeah,
it's
really
not
long,
there's
a
breakdown
that
I
linked
to.
I
think
in
the
merge
request
in
the
merge
request
of
here's
all
of
the
groups
with
a
dry
run,
how
many
would
be
so.
I
think
the
most
was
eight,
mrs.
C
So
this
is
a
good
example.
If,
if
the
everybody,
even
just
picks
up
one,
you
know,
that's,
that's,
that's
still
pretty
significant.
I
believe
internet,
I
think
that's.
The
key
aspect
is,
is
you
know
if
folks
feel
like
they
have
to
do
them
all
in
the
first?
Go
then
that
that
may
be
challenging,
but
you
know
at
least
be
thinking
about
it.
B
B
C
If
em
say,
if
em
say
to
me,
don't
have
time
to
do
this
I'll,
be
like
okay!
Well,
what
are
these
mrs
consist
of
oh
well.
This
is
a
feature
we're
trying
to
ship.
Well,
don't
you
have
time
to
commit.
B
A
B
The
the
things
I
would
be
looking
for
in
the
second
row
like
going
into
the
second
round
of
this,
is
how
many
remained
in
the
report
from
the
previous
generation.
How
many
were
merged?
How
many
were
closed?
I
think
you
might.
The
other
thing
we'll
see
is
maybe
just
a
lot
of
people
going
in
and
say
this
isn't
important,
I'm
just
going
to
close
it
for
now,
which
that's.
C
Good
right,
like
if
yeah
like,
if
you,
if
you
didn't
code,
merge
30
days
ago
and
you're
expecting
that
code
to
still
be
the
same
state,
it's
either
going
to
be
really
a
part
of
the
code
base.
We're
really
not
using
you
know
like
you're
gonna.
You
might
have
to
do
just
as
much
work
to
to
get
it
to
update.
D
And
this
this
trash
report,
is
it
gonna
be
into
the
main
project
kyle?
Is
it
on
a
separate
project,
so
the
reports
are
separate,
but
what's
the
current
iteration.
B
D
A
Have
a
great
friends
and
family
day
tomorrow,
everybody.