►
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
Matt
just
asked
the
big
question:
is
we
just
recapping
or
what's
purpose
today
so
purposes,
just
go
over
the
items
that
we
didn't
get
a
chance
to
go
over?
We
didn't
get
a
chance
to
go
over
the
last
time
we
ran
out
of
time
and
then
any
anything
new
and
any
new
updates.
So
if
you
look
at
the
document,
I
believe
we
left
off
at.
B
B
A
A
A
Thankfully,
in
Kyle
I
haven't
looked
to
go
bout,
I
sampled,
non
late
ones,
rather
than
having
all
the
data
analyzed,
but
20
seemed
like
a
nice
round
number
and
was
statistically
significant
to
say
most
non
late
ones
have
less
than
20
threads
and
mostly
and
a
large
percentage
of
late
ones
have
more
than
20
threads.
So
that
might
be
a
good
thing
to
in
the
future.
Have
a
bot,
detect
and
comment
on
what
a
folks
think.
B
This
is
gonna,
be
tactical.
How
do
you
know
if
the
trial,
your
server
list-
and
this
is
an
opportunity
for
us
to
doll
food,
so
it
will
s
to
do,
can
cannot
be
time-based
and
meaning
like?
Is
there
a
way
to
like
detect
if
this,
mr
has
been
above
30
days
immediately,
there's
like
a
ping
on
a
discussion
for
people
there
I.
D
B
And
another
thing
I
think
we
could
do
is
set
a
due
date
and
if
we
set
due
dates,
we
actually
dog
food
get
lab
email.
Another
vacation
as
well
and
I
think
that
also
flows
nicely
in
line
with
the
recent
handbook
update.
It's
like
we
set
due
dates
in
our
you
know,
Mars,
but
that
may
be
a
bit
controversial.
It's
that's
really
across
the
board.
B
D
Think
it
might
be
a
little
new
so
point
where
it's
controversial,
that
might
be
a
behavior
that
we
would
need
to
get
some
broader
feedback
on.
I
can
say
that
it's
possible
through
quick
actions
to
do
exactly
what
you
just
said
so
triage,
whether
it's
trade,
jobs
or
triage
that
should
be
able
to
you
can
set
dude
in
X
or
like
n
days.
So
the
feasibility
is
there
right.
B
D
That
that
might
be
something
for
like
a
second
iteration
of
like
a
nudge
in
combat
all
right
so
like
if
we
start
with
a
Mars
after,
like
better
still
after
a
certain
threshold,
not
being
actionable.
Maybe
that's
where
we
can
try
to
drive
it
action
from
a
different
angle
by
you
by
using
due
dates
because
it
at
minimum
it
might
force
someone
to
go
in
and
at
least
change
the
due
date
you
know
or
like
look
at
when
are
we
targeting
this
to
be
completed?
Yep.
B
E
I'm,
trying
to
high
level
what
I'm
trying
to
wrestle
with
is
there's
two
dates.
Where,
like
people
assign
you
something,
and
they
say
this
is
when
it's
due
by
vs.
way.
We
have
in
the
handbook,
which
is
you,
are
signing
up
for
this
right.
So
if
we
put
it
in
a
bot,
you're
essentially
assigning
a
due
date
for
something
and
I
guarantee
that
a
lot
of
people
will
interpret.
That
immediately
is
oh.
E
This
is
one
the
time
I
need
to
do
if
I
is
supposed
to
be
more
efficient
and
potentially
doing
it
even
sooner
than
that
and
right
from
that
perspective,
which
is,
if
you
self
sign
up,
then
maybe
you
say
you
can
get
something
done
more
quickly,
so
we
probably
need
some
clarification
around
that
just
to
make
sure
we're
approaching
from
the
right
way.
There
is
the
concept
of
SLO
or
SLA,
though,
which
says
you
know.
E
This
is
our
expectations
for
the
team
and
overall,
that
would
be
a
reason
to
use
the
due
date
column
if
you
could
somehow
indicate.
Oh,
this
is
the
SLO
associated
with
it
that
we're
really
trying
to
achieve
so
then
people
have
a
much
better
idea.
If
you
know
hey,
if
I'm
outside,
if
I
know,
I'm
not
gonna,
be
able
to
hit
this
SLO
I
should
be
immediately
punching.
This
out,
I
think
basically
give
this
to
another
reviewer
maintainer
associate
what
this
is
kind
of
the
thought
process.
Okay,.
E
B
E
Kind
of
have
a
similar
kind
of
low
form
solution,
which
is
we
have
the
zoom
feature
now
so
like
if
I
get
above
another
certain
number
of
threads,
recommending
that
they
do
a
zoom
zoom
session.
I,
don't
know
if
you
notice
that-
and
it's
mainly
used
for
incident
management,
but
it
could
be
used
here
as
well,
where,
basically,
you
can
add
a
zoom
link
to
a
channel.
There's
a
little
bit
of
now
that
we've
changed
our
policy
with
passwords.
There's
a
little
bit
of
issue
there
that
we're
going
to
work
through.
But
it's
an
idea.
A
E
A
Like
often
documentation
has
or
or
issues
or
tag
guys
backstage
or
they
get
multiple
label
and
I
think
we
prefer
max
if
it
has
backstage
and
documentation,
we
call
it
backstage
perhaps,
but
that
being
said-
and
it
was
a
smaller
number,
you
know,
perhaps
the
documentation
teams
should
take
the
iteration
training
and
then
also
0.7
is
about
40%
of
a
time.
Ours
come
from
40
authors
and
in
94
for
that
month
that
had
you
know
one
or
more
M
ours.
So
that's
a
maybe
perhaps
focus
on
those
40
authors.
A
Sometimes
I,
don't
feel
that
it's
kind
of
them
that
they
get
something
wrong.
It's
something
it's
something
wrong,
it's
that
you
know,
and
it
may
be,
that
ther
Amar's
you're
late
for
all
sorts
of
reasons
that
iteration
training
would
not
have
covered
at
all.
But
you
know
maybe
a
light
recommendation
saying:
hey
you
might
be
interested
in
this
would
be
great.
What
does
the
team
think
of
these
two
ideas.
D
B
So
if
in
the
handbook
documentation
is
under
a
backstage,
we
should
move
it
out
because
that's
in
line
with
improving
documentation
if
there's
documentation
tomorrow,
let's
let's
make
sure
it
is
credit
to
as
such
and
long
term
I
think
we
discussed
earlier.
I
think
we
need
to
make
things
both
is
a
big
I
may
be
back,
say,
should
go
away
and
if
its
technical,
let
me
call
a
technical
debt
if
it's
refactoring,
they
call
it
factoring,
but
it's
a
long-running
thing
because
before
you
have
them,
you
have
the
next
point
being.
If
you
wanna
write.
F
B
E
F
E
Take
down
this
technical
debt,
it's
gonna
Amelie
gets
into
a
discussion
around
what
is
engineering
spending
its
time
on,
so
it's
it's
gotta
be
I'm,
not
sure
what
the
type
should
be,
but
it's
either
be
a
feature
or
or
like
like
like
we
got
to
get.
We
got
to
dig
in
on
what
those
things
are.
What
people
classify
typically
as
technical
debt
is
immediately
then
associated.
Well.
E
C
E
Think
I
think
in
other
organizations
people
like
to
talk
in
terms
of
debt,
which
is
customer
value,
add
that's
not
necessarily
detectable
right.
From
that
perspective,
my
view
would
be
is,
is
that
you
know
internal
improvements
that
help
the
product
our
value
add
so
I'd
rather
have
other
terms
use
than
dead,
because
most
organizations
the
way
they're
set
up
is
they
have
some
kind
of
8020
rule
or
something
like
that.
We
don't
have
that
right,
we're
supposed
to
evaluate
everything
on
its
merits.
E
F
E
A
Not
the
idea
on
focusing
on
the
author's
nudging,
the
authors
that
have
you
know
two
or
more
EMR
that
took
more
than
30
days
on
taking
the
iteration
training.
I
could
see
that
really
being
seen
as
negatively
like
oh
I,
get
something
wrong,
or
just
you
know,
sometimes
presented
as
some
iterative
improvement
and
just
suggestion.
I
think
it'd
be
great.
A
E
A
E
The
one
thing
that
I'm
we've
been
trying
to
not
avoid
both
we've
designed
as
her
round
team
metrics
as
opposed
to
having
individual
metrics
like
this
so
like
this
is
getting
in
that
category.
Where
we're
starting
to
argue
individual,
though
we
want
people
to
obviously
be
in
iteration.
So
in
that
regard,
if
we're
gonna
ask
I
cease
to
take
the
training.
I.
Would
one
you
you
don't
want
to
put
somebody
on
penalty
box?
Take
a
training
you
want
to
take
the
training
before
they
get
put
in
the
penalty
box.
A
So,
lastly,
dealing
with
email
bankruptcy.
So
you
know,
we've
talked
a
lot
about
thoughts,
adding
comments
based
on
various
criteria
and
I.
Think
that's
great,
but
I
think
as
well.
You
know
many
have
declared
email
bankruptcy,
they
miss
those
and/or,
they
see
them.
You
know
they
may
see.
You
know
bought
comments,
as
you
know,
as
spammy.
A
So
one
idea
which
could
just
transfer
the
problem
elsewhere
is
to
use
a
combination
of
comments
and
issues,
and
you
know
Christopher's.
You
mentioned
a
comment
that
mentions
hey.
Maybe
you
should
get
on
zoom',
here's
a
zoom
which
we're
using
a
send
in
sense
or
or
and/or
slack
messages,
but
that
Mecca
easily
turn
into
an
annoyance
to
the
the
people
working
on
the
issues
and
then
also
turn
into
you
know
make
slack
get
ignored
at
this.
You
know
at
a
similar
right
that
email
make
it
ignored
for
some.
So
it's
a
con.
A
F
Totally
agree
with
your
assessment
that
email
comments,
all
those
things
of
those
automatic
spam
bots
are
just
a
nuisance
and
they
don't
drive
institutional
change
as
much
as
we'd
like
to
we
got
to
retrain
people.
That's
that
doesn't
happen
by
sending
a
message.
How
much
request
is
overdue?
To
get
that?
How
do
you
help
them?
I
had
a
50-minute
scheduled
iteration
office
hours
this
morning,
and
only
two
people
showed
up
and
only
one
person
made
could
an
example
in
there.
F
So
no
one,
no
one
wants
to
kind
of
no
one's
seeking
training,
and
it's
very
disappointing.
I've
tried
to
keep
the
tone
of
those
things
really
liked
and
I
thank
people
for
seeking
feedback
and
it's.
But
if,
if
that's,
if
that's
how
it's
going,
it's
not
going
well,
so
maybe
we
should
take
the
ten
things
that
take
the
longest
and
discuss
those
as
a
company,
and
it's
it
shouldn't
be
about.
The
person
should
be
about
the
example,
but
in
the
end
this
has
to
be
a
conversation.
F
A
F
E
B
E
A
B
Think
this
may
have
been
Lindsay
because
I'm,
a
scroll
down
below
I
think
she
added
a
it's.
The
same
language,
we're
encouraged
you
look
you'd
like
to
do
is
to
easily
track
that
there
you
go
one
a
I,
think
it's
the
same
line,
it's
emails
or
to
deuce
I.
Think
it's
it's
the
same
thing
at
different
different
mechanisms.
I
think
need
to
go
back
to
what
we
discussed
earlier
is
have
find
a
right
trigger
for
people
to
break
things
down.
B
E
People
do
look
at
their
mrq,
though,
generally
speaking,
right,
I
would
think
that
at
least
you
know,
that's
a
slightly
different,
the
things
that
are
assigned
to
them.
I
wonder
if
we
should
separate
things
that
you're
working
on
versus
things
that
you're
in
assigned
to
basically
review
in
some
fashion.
C
With
the
with
the
Mrs
that
have
timed
out
that
they've
fallen
through
the
cracks,
do
we
have
analysis
that
says
in
whose
Court
they
waited
today?
Was
it
that
the
ping-pong
ball
was
moving
slowly
between
both
participants,
or
did
it
tend
to
timeout
more
with
the
reviewer?
Or
with
these
it's
a
common
person
who
posted
the
code?
Do
we
have
any
stats
on
that
yeah?
It's.
A
A
combination
there
are
some
stats
earlier
on
in
the
in
the
docking
and
the
lint
spreadsheet,
but
the
ones
it
takes
a
really
long
time
like
more
than
60
days.
They
tend
to
go
idle
for
more
than
a
month,
sometimes
more
than
one
time
more
than
you
know,
one
or
more
times
for
ones
that
are
less
than
that
one
of
the
most
you
know
you
know
in
the
30
days,
or
so
you
know
a
little
over
30
days,
it's
a
it's,
often
in
reviewer
and
maintainer,
author
or
think
long.
A
You
know
back
and
forth
and
sometimes
not
quick
responses.
So
those
are
just
two
of
the
top
patterns
that
I
note
some
looking
through
the
data,
it's
great
question
so
in
the
clinic,
so
how
to
measure
success.
So
all
these
these
things
were
playing
we're
thinking
about
doing
with
bots
we
are
doing
with
BOTS
runs
the
risk
of
being
ignored
and
it
works
knowingly
developers.
So
you
know
we
should
for
each
type
of
bot
this
discovered
situation
and
comment
analyze,
success
rate.
A
So
is
that
comment
working
for
those
so
look
at
them
and
seeing
if
it's
working
and
if
it's
not
optimizing
it
or
stop
doing
it,
we
should
gather
feedback
from
the
development
from
the
developers
under
any
new
bot.
Behavior
is
making
a
public
issue
when
we
start
doing
it
and
encourage
them
to
give
feedback
on
how
to
improve
them
or
if
they're,
helping
or
not,
and
also
you
know,
continue
to
measure
both
average
days
to
merge
and
percentage
emergence,
request
rate
or
30
days
and
seeing
if
things
aren't
perfect,
that
thoughts
on
these.
B
I
think
three,
having
it
broadly
shown,
the
metric
wise
will
help
I
think
leading
to
the
success
of
a
mr8
credit
to
to
Christopher
and
it's
organization.
It
agreed
either
put
the
metric
front
and
center
I
think
that
seems
to
be
helping
with
a
sense
of
urgency
and
that
everybody
needs
to
corral
together
to
get
them
at
the
metric
up.
I
think
we
will
be
weary
with
the
bots,
because
I'm
there
already
email,
fatigue
and
I
will
selectively
add
additional
notifications
as
we
see
fit
as
that's
my
take
on
it
I'm
happy
to
hear
others.
A
Sue
we
discussed
a
couple
of
the
action
items
last
time
that
people
proposed
and
someone
didn't
get
to
so
I'll
just
copy
them
over
to
today's
so
say,
I
think
we
got
your
point
that
you're
more
than
you're
willing
to
do
more,
iteration
training,
etc.
Does
your
comment
from
the
derivative
to
the
last
meeting
and
then
we
covered
it
here
as
well.
A
D
A
F
E
E
F
Yeah,
okay,
the
next
the
next
project
I
work
on,
is
trying
to
set
a
deadline
and
working
groups
and
get
rid
of
them
at
some
point.
The
whole
idea
is
not
to
have
working
groups
not
to
have
more
of
them
so
yeah.
Let's
get
some
content
in
the
handbook
instead
of
the
doc
I.
Think
that's
the
important
thing.
A
So
I
will
so
fewer
working
groups.
Let's
get
things
into
the
handbook
and
Lily
was
able
to
pull
additional
data,
which
is
great,
so
we
can
look
at
additional
trends
and
validate
with
more
accuracy
some
of
the
existing
ones,
so
I'm
gonna
haven't
been
able
to
look
at
that
yet,
but
thanks
Lily
and
I
will
and
I'll
keep
our
meeting
I'll
make
this
meeting
weekly
put
it.
Should
it
go
on
one
of
the
group.
Calendars
I
didn't
see
an
obvious
one.