►
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
B
A
A
B
B
A
B
A
So
so
I
put
together
some
new
based
on
the
new
data
that
really
thank
you
for
collecting
I
was
able
to
identify
some
additional
trends.
So
just
some
of
the
interesting
things
summary
is
number
two:
is
that
late,
mr
see?
No
later
Mars
being
Merson
in
more
than
30
days
days
to
review
on
late
on,
Mars
is
28
days
on
not
late
ones
are
is
two
days
so
14x
difference
and
then
the
different
days
to
review
from
first
note
so
regular
mrs
90th
percentiles
two
days
and
later
mars
is
ten
days
the
average.
A
A
The
assignments
all
mrs
for
later
mars,
8
to
2
x,
difference
number
of
pipelines,
which
I
don't
know
which
of
these
are
useful
or
not,
but
I'm
glad
we
were
able
to
take
a
look
at
them
so
number
of
pipeline
seven
for
all
I
mars
22
for
liquids
they
didn't.
Have
you
know,
3x
more
pipelines
file
has
changed
and
lines
change,
just
a
rough
measure,
probably
lousy
measure,
but
measure
that
we
have
indication
of
this.
A
A
B
Sorry
I
had
a
few
follow-up
questions.
There
I
was
trying
to
get
the
median
before
this
meeting
and
I
wasn't
able
to,
but
I'd
be
curious
on
files
change
in
lines,
change
for
the
median
cuz
I
know.
Some
of
the
like
nudging
that
we
talked
about
was
like
looking
at
how
we
can
iterate
lie
or
improve
our
iteration
and
I'm,
not
yeah
hold.
A
B
A
A
B
C
I'm
some
kind
of
curious
as
to
like,
so
this
is
what
it
looks
like
so
I
guess
is
part
of
product
right.
Do
we
know
how
this
stacks
up
against
other
customers
or
like
these
are
our
stats
for
our
company?
If
we
hit
that
up
dance
like
projects
for
other
companies,
do
we
see
the
same
thing
as
you're,
starting
to
like
dig
deeper
into
the
sort
of
try.
A
To
understand
a
little
bit
more
I
think
it
actually
might
be
a
great
thing
to
study
that
you
know
based
on
data
that
maybe
is
available
elsewhere,
where
we're
kind
of
looking.
You
know,
Nenana
mised
data
across
you
know
like
get
lab,
comm,
hosted
projects
and
might
be
actually
good
once
we're
effective
with
improving
things
without
you
know,
without
creating
bigger
problems
and
we're
solving.
If
you
have
to
be
careful
about,
you
know,
it
sounds
like
it
actually
be.
If
we
can
find
something,
that's
effective,
a
good
enhancement
to
get
lab
overall
yeah.
C
A
C
Go
ahead
and
add
it
because
I
kind
of
started
looking
at
this,
the
commit
to
merge
histogram
has
you're
super
familiar
with
that
so
kind
of
looking
at
breaking
the
commit
to
merge
histogram
by
different
projects.
I
think
I
just
have
a
lack
of
context
and
knowledge
of
how
that
data
sets
in
our
database.
Like
I,
don't
know
if
we
can
track
back
to
a
specific
customer,
but
we
can.
C
A
C
A
Get
web.com
hosted
projects
or
just
yeah
I.
Think
that's
you're,
saying
across
all
get
lab
projects
hosted
projects
yeah,
so
maybe
it's
there's
also
the
there
quite
a
few
get
lab
composted
projects
and
the
the
trends
on
those
would
be
potentially
very
different
than
trends
for
self
hosted
customers,
because
the
some
larger
customers
that
you
know
just
the
same
large
numbers
of
developers,
some
surely
use,
get
lab
comm
many
hosted
some
many
also
run
it
locally
self
hosted.
We
wouldn't
I
think
the
get
lab.
Composter
projects
is
skewed
towards
smaller
numbers
of
engineers
per
project.
B
B
Development
that
happens
on
get
lab
comm.
So,
like
just
other
projects,
it
might
just
be
one
person,
so
the
concept
of
something
being
reviewed.
There
isn't
one
right,
so
the
workflow
that
we
have
here
isn't
necessarily
consistent
with
other
projects,
especially
when
you're
looking
beyond
just
our
groups,
but
there
should
be
some
analogies
that
we
could.
You
know
that
might
be
able
to
be
inferred
there.
Yeah.
C
B
The
analytics
team
might
be
good
someone
good
just
to
have
like
a
copy
chat
with
on
that
too.
So,
like
Jeremy
I,
think
it's
the
p.m.
right.
Now
of
that
and
I'm
not
sure
that
the
e/m
but
yeah
I
know
they
have
a
lot
of
a
lot
of
ideas
and
a
lot
of
things
in
flight
for
how
to
measure
that
review
and
pretty
much
that
that
value
stream
value.
A
So
Lee,
thanks
for
adding
the
additional
data
number
of
threads
I
haven't
I,
haven't
studied
it
based
on
that
base,
I'm
gonna,
post,
similar
data-
you
know
average
median
90th
percentile
for
all
them
ours
and
laid
em
ours
and
then
see
what
see
what
the
differences
are.
So
so
I'll
try
to
do
that
before
next
week.
Yeah.
C
A
Cited
median
in
90th,
percentile
and
but
yeah
it's
a
good
point
is
there's
definitely
significant.
Like
there's
I,
don't
remember
the
numbers,
but
it's
something
like
of
the
ones
that
are
greater
than
30
days
like
50%
of
them
are
30
to
60
and
then
the
ones
that
are
greater
than
60.
The
range
is
really
it.
You
know
it's
really
big.
It's
like
you
know
from
60
to
300,
and
there
are.
There
are
some
you
know
way
on
the
high
side
and
it
was
those
are
different
patterns
than
ones
that
are.
A
So
Kyle,
can
you
give
an
overview
to
the
group
to
us
on
the
scope,
status
and
next
steps
on
that
issue?
453
I
read
through
it,
but
it
talks
about
it.
The
number
of
things
I
wasn't
familiar
with,
although
I'm
more
familiar
with
it
today,
like
what
does
it
look
for
what
actions
does
it
take
based
on
that
etc?
Yeah.
B
So
so,
essentially,
what
what
a
triage
packages
is
going
to
be
a
collection
of
issues
that
it's
going
to
be
an
issue?
That's
created
that
collects
a
number
of
issues
that
fit
a
criteria,
that's
defined
and
then
assigns
that
to
someone
for
an
action.
So,
as
we
kind
of
went
back
and
forth,
I'd
say
over
the
last
few
days
we
came
to
the
inclusion
of
starting
with
a
triage
package
on
those
stale.
B
Mr
so
two
weeks
with
no
activity,
mom
and
I
I
think
what
would
be
best
is
to
have
it
broken
out
at
a
group
level.
So
each
group
that
has
Mr
zip
at
this
criteria
would
get
its
own
triage
package,
assign
that
to
an
engineering
manager,
and
then
we
need
just
I
would
say
some
help
confirming
what
the
language
should
be
or
what
that
engineering
manager
should
do
with
this
report.
So
the
the
other
group
I'll
say
issue
triage
package
is
broken
into
sections
in
each
section.
B
Not
updated
and
the
key
thing
with
not
updated
is
once
it's
in
the
triage
package.
Those
M
ours
are
updated.
That
affects
the
last
updated
date.
Any
activity
on
on
the
Tamar
would
impact
the
last
updated
date.
So
that's
where
those
subsequent
nudges
get
a
little
intricate
and
challenging
and
while
I
think
the
triage
package
would
probably
be
the
the
right
way
to
start
in
just
one
crouched
package,
not
updated
in
the
last
two
weeks
and
try
to
keep
that
simple
sounds.
A
B
A
B
C
A
It
doesn't,
it
doesn't
become
noise
to
the
engineers,
the
negative,
is
it
centralizes
it
to
the
managers,
but
I
think
starting
with
the
tree
audit
report
sounds
good,
because
then
we
can
at
least
experiment
there
and
see
how
effective
it
is
get
feedback
from
the
managers.
What
I
would
and
I'd
be
happy
to
look
at
the
text
is
there
example
text
in
the
issue
come
on
so
right.
B
Now
it's
it's
just
built,
so
it's
one!
So
my
plan
is
in
the
mr
that
I
kind
of
need
to
on
here.
That's
that's
in
progress
and
then
there's
EMR.
That
I
would
just
propose
some
text
with
attention
and
I'll
tag
you
on
that.
You
can
kind
of
tweak
and
we
get
there
and
then
my
intent
is
once
we
settle
on
structure
of
that
triage
package
to
add
it
back
to
the
overall
issue.
A
B
A
A
B
A
That's
the
direction
I'm
going
I'd
say:
what
do
you
both
think
on?
Let's
experiment
with
idle
of
four
weeks?
Okay,
maybe
run
it
every
six.
The
reason
six
sounds
kind
of
weird,
but
the
reason
why
is
then
it
won't
show
up
again
like
I.
Don't
want
the
same
one
to
show
up
every
time
or
flap
I'm
showing
up
in
this
report
and
then
not
showing
up
in
the
next
one
if
it's
not
touched
by
somebody
then
showing
up
in
the
next
one
going
back
and
forth.
B
A
B
A
A
Know
the
alternating
might
be
okay
because
it's
like
well
maybe
you've
missed
it.
Maybe
you
meant
to
you
know
the
manager
meant
to
look
at
it.
Maybe
the
manager
decide
not
to
whatever
and
then
remind
it
again
if
it's
still
there
so
about
I
like
actually
having
at
the
same
time
frame
the
running
at
the
same
time
frame
so
think,
initially,
the
the
the
toggle
back
and
forth
didn't
seem
great,
but
now
the
more
we
talk
through
that.
Do
you
like
it?
So
why
don't
we
just
change
running
it?
A
A
You
know,
look
at
I'll,
look
at
the
text
once
you're
ready
and
then
after
we
do
this,
then
we
start
looking
at
the
other
trends.
Are
there
other
things
we
want
to
detect?
You
know
this
is
idle
time.
Maybe
it's
you
know
the
days
just
you
know
thinking
about
these
here.
You
know,
mr
assignments,
once
it
goes
above
some
value
or
I,
don't
miss
I
know
we
pulled
the
date
on
pipelines
and
files
changed
and
lines
change,
but
I
think
those
are
probably
bad
wants
to
to
base
it
on
unless
it's
really
high
like
like.
A
A
B
Great
there's,
there's
two
other
I
would
say
just
quick
things,
and
maybe
this
is
me
coming
out
from
a
different
direction,
but
I
think
in
that
said,
I
would
be
interested.
This
kind
of
goes
back
to
Mexico
and
last
week,
I'd
be
interested
to
see
how
many
of
those
issues
that
are
in
the
merged
in
greater
than
30
days,
just
have
like
a
documentation
related
label.
Again.
B
This
is
another
thing:
I
was
trying
to
pull
where
the
throughput
label
may
not
indicate
the
type
of
work
that
it
actually
is
because
I
think
like
there's
some
features,
there's
a
there's.
A
significant
number
of
backstage
it
seemed
like
documentation,
is
either
a
portion
of
it
or
the
whole
em
are
to.
C
B
A
B
C
B
I
think
feature
was
another
one
where
that
seemed
a
bit.
So
that's
why
I
was
thinking
almost
like
a
separate
indicator
and
where
I
was
coming
at
this,
as
I
was
looking
at
just
backstage
in
general
across
all
I'll
say
all
em
ours
and
how
we
could
get
rid
of
the
concept
of
backstage
and
migrated
over
and
I
was
finding
a
significant
shift
to
just
documentation
as
you
go
historically
throughout
the
ICANN.
B
It's
more
I
would
say
inferring
it
from
the
presence
of
other
labels.
So
if
I
say
how
many
what
I
was
looking
for
is
what
M
ours
are
exclusively
like
backstage,
so
no
feature,
no
anything
else
yet
then
of
that
population.
How
many
of
those
mrs
have
things
like
I
mean
there
was
a
list,
but
documentation
was
one
of
them
database,
just
all
sorts.
B
A
B
A
Classification
now
I
may
be
misquoting,
some
of
them
so
but
I
remember.
There
was
significant
with
people
who
came
in
the
last
one
or
two
meetings.
They
were
very
interesting.
Things
were
on
those
lines,
so
I
think
that'd
be
great.
If
you
could
put
notes
you
know
now,
while
we're
compromised
from
it,
you
know
on
what
the
plan
is,
what
you're
proposing
for
that
and
the
plan
for
that.
That
would
be
great
yep.
B
Yeah
I
was
kind
of
in
this
analysis
loop.
So
to
get
to
the
point
where
I
had
data
to
inform
a
plan
but
I
think
I'm,
just
gonna
create
an
issue
to
just
start
and
say
like
this
is
the
objective.
This
is
the
work
that
it's
in
progress
to
come
up
with
a
plan,
because
it's
taken
too
long
like
that.
This
is
a
lot
of
data
to
try
and
I'll
say
fiddle
through
and
I'm,
not
as
good
at
it
as
Lilly.
So.
A
A
Thank
you
both
we'll
meet
again
next
week,
I
think
I
made
this
recurring
for
four
weeks.
Maybe
we
don't
need
all
four.
We
just
you
know,
go
to
issue
comments.
You
know
after
that
point,
or
maybe
we
maybe
we
make
it
less
often,
but
you
know
this:
has
it
an
intended
end
time
of
this
recurring
meeting
right
now,
it's
four
weeks
so
but
I
think
we're
making
great
progress
and
doing
some
pretty
cool
things.