►
From YouTube: Development Metrics Working Group 2019-08-22
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).
B
A
C
A
Really
funny
is
if
I
was
watching,
it
was
probably
about
three
months
ago
and
my
wife
was
in
the
other
room
and
I
didn't
realize
it.
But
if
you
like,
if
you
only
hear
that
movie,
it's
actually
really
just
it's
it's
even
early.
They
even
really
screen
more
strange
because,
like
there's
so
little
dialogue
in
that
movie,
it's
it's
was
pretty
surprising
right.
B
A
Yeah,
so
we
definitely
are
trending
towards
like
about
1800
for
the
month
we
definitely
have
seen
a
shift,
we're
getting
a
little
more
consistency
delivery.
Just
because
we've
gone
to
these
really
drops,
though
there
is
still
a
little
bit
of
a
scattering
where
the
the
week
of
1819
sometimes
can
be
a
little
bit
higher,
but
generally
speaking,
we've
seen
a
pretty
consistent
draft.
A
The
big
thing
is:
is
that
for
August
we
just
appear
to
be
off
of
our
trend
towards
a
2100
on
the
kind
of
including
community
contributions,
part
of
the
graph
and
it
from
what
I
can
tell
so
far.
There
is
definitely
a
little
bit
of
a
vacation,
but
I,
don't
I,
don't
know
if
I
quantify
yet
to
really
give
a
you
thumbs
up
thumbs
down
on
that.
If
that's
really
the
impact
of
it
yep.
B
A
And
usually,
basically,
we've
we've
gone
through
five
M
ARS
per
author.
Obviously
it's
gonna
get
rebase
line
when
we
switch
to
tracking
more
from
the
other
perspective.
This
way
he
described
it,
as
is
ideally
we'd,
be
that
at
the
turn
of
the
month,
which
were
see
here
were
essentially
we're
three
days
beyond
that
are
well
enough.
Two
days
beyond
the
turn
of
the
month,
so
we're
just
a
little
bit
behind
as
well
on
the
data
tree,
which
was
not
surprising.
B
C
A
C
C
Yeah
I
think,
let's
you
know
I
think
of
the
problem
again
and
my
sure
bhakti.
B
Yeah,
okay
charge
you're
cutting
off
silhouettes
I.
Think
I
read
what
you're
trying
to
say.
Let
me
do
this,
then.
Let
me
quit
issue
to
remind
us
to
revisit
this
number
within
a
few
milestones
and
then
I
think
the
iterations
that
we
made
today
I
think
it's
adequate
for
us
to
to
monitor
the
improvements
at
P.
Epsilon
sounds.
It
sounds
good
for
you.
Okay,.
B
That
I
can
do
the
confirmation
of
I
think
that's
in
line
with
what
Josh
was
trying
to
say.
Four
hypotheses
think
we
close
this
out
as
of
last
week.
Awesome
awesome,
awesome
awesome.
So
let
me
just
stop
sharing
my
screen
and
then
we
can
dive
into
the
agenda.
Thank
You
Josh
for
confirming
async
appreciate
it.
I'll
create
an
issue
to
pull
up
like
on
tons
of
result
bugs
later
so
agenda
items
so.
B
To
number
three
I
think
this
was
a
a
follow-up
action
item
from
last
time.
If
you
want
to
include
community
contributions
in
the
periscope
charts
and
I.
Think
mark
has
fixed
it
as
of
last
week,
so
he'd
be
go
to
periscope
right
now
on
the
throughput
numbers,
you'll
see
roughly
the
charts
Mehring
what
we
see
in
a
quality,
what
security
and
can
we
contributions.
B
A
B
Next
one
is
the
biggest
one
I
want
outlined
it
items
that
we
need
and
have
to
be
closed
or
this
band
is
working
group.
So
there's
a
quality
for
interpretation
plan.
The
dashboard
will
still
be
up
and
measure
acoustical
and
if
you
notice
that
we
added
a
banner
a
deprecation
banner
on
top
of
Colley
dashboards
for
just
to
prepare
folks
that
wants
to
come
in
the
coming
quarter.
Again,
it's
not
going
away.
B
The
metrics
would
still
flow
and
it's
kind
of
our
legacy
yardstick
to
measure
the
new,
the
new
residency
of
the
metrics
new
home
of
them
in
the
future
and
the
next
one
is
the
method
of
accounting
of
our
new
way
of
doing
things.
So
I
would
appreciate
if
Dahlia
Christopher,
you
can
take
a
read
and
and
give
us
comments.
I
will
link
the
issue
to
discuss
this
in
a
bit,
but
before
that,
let
me
just
share
my
screen.
There's
this
great
work
from
Remy
doing
the
investigative
40s.
B
So
this
is
all
the
projects
potentially
to
be
include
and
exclude
excluded
the
check
book.
The
checkbox
here
is
what
is
in
gitlab
sorry
in
the
quality
dashboard
right
now,
and
this
is
the
one
time
opportunity
to
do
the
accounting
switch.
This
is
the
column
that
Bernie
added
on
whether
it's
customer
facing
a
feature
feature
for
feature
facing
or
not
so
I
think
this.
This
list
here
is
around
70
now
and
the
curated
lists.
B
Security
products,
so
we
have
a
long,
a
bunch
of
really
small
small
projects
in
Crystal
Bay.
If
this,
if
we
can
include
someone
from
secure
and
defend
p.m.
to
tell
help
tickets
to
look
at
this
I
think
that'll
be
great
as
well
so
security
products
has
a
number
of
them.
I
think
it's.
It
is
I
think
these
are
forward-facing
gymnasium
and
there's
a
bunch
of
test
projects
from
from
security
as
well
so
demos,
for
example,
like
anything,
that's
like
tests,
I
think
these
should
be
excluded.
Now
it's
it's
currently
included
so
yeah
I
applause.
A
B
A
B
B
A
A
Emoji
I
mean
like
somebody's
working
on
that
it
may
be
a
UX
person
like
if
a
york's
person
spends
the
time
to
update
an
emoji
for
whatever
reason
or
add
a
set
of
emojis,
let's
say:
they're
a
graphic
designer
they're
definitely
counted
against
our
count,
so
we
should
include
their
contributions
and
that
measurement-
that's
that's
kind
of
my
take
on
it.
For
that
perspective,
yeah.
I
think
it's
cool
that
we
found
some
that
we
were
missing.
Like
that's,
you
know,
so
this
is
really
a
true
reconciliation.
A
B
C
Know,
I
also
definitely
will
review
the
list
with
the
with
the
team,
but
I
know
we've
done
a
number
of
iterations
when
we're
working
on
the
quality
dashboard.
So
where
we
left
things
off
the
assumption
is
we
have
all
the
projects
for
ops
because
we've
already
iterated
on
them
in
the
quality
dashboard
but
as
as
precaution,
we'll
definitely
review
with
the
managers
and
let
you
know
thanks
Mike
I'm.
C
B
Okay,
moving
on
to
the
next
one,
so
I
have
built
this
collaborative
venue
prior
and
now
everybody
in
engineering
productivity
has
has
periscope
editor
access
by
default
now
going
forward,
and
we
have
been
helping
the
team
to
fix,
bugs
and
accelerate
the
numbers
that
we
need
from
engineering
and
quality.
So
we
have
a
ramp
into
into
working
more
closely
with
them
in
this,
and
I
have
a
dashboard
set
up
by
the
request.
Christopher.
B
B
A
Yeah,
let
me
know,
hit
me
up
with
the
issue
and
then
I
can
make
sure
to
communicate
that
more
broadly
to
the
development
team.
The
other
one
that
I
was
thinking
about
was
is
I
use.
I
personally
in
value
me
have
good
feel
for
this.
I
personally
use
the
dashboard
and
get
laughs
quite
a
bit
to
kind
of
look
at
things
and
different
teams
associate
with
that.
What's
unclear
to
me
is
how
much
of
that
goes
into
periscope
versus
how
much
goes
into
product.
So
that's
that's
the
one
aspect
as
we
deprecate
it.
A
That's
the
one
set
of
criteria
I
have
is,
is
that
we
can
still
easily
get
to
dashboards,
are
related
to
that
and
I'm
not
sure
whether
or
not
the
productivity
team
is
gonna,
be
responsible
for
creating
those
dashboards
and
in
periscope
or
if
that's
gonna
fall
to
development.
So
that's
probably
a
discussion.
We
just
need
to
kind
of
work
out
perspective.
A
B
Yeah
I
happy
to
I
think
it
I
think
we
can't
capture
that
in
this
meeting,
but
in
the
deprecation
plan
that
is
the
single
source
of
truth,
I'm
working
on
right
now,
so
that
that
plan.
It's
it's
a
work
in
progress,
so
we're
listing
everything
in
the
quality
dashboard
right
now
in
that
plan,
and
then
we
deciding
whether
it's
going
to
go
into
insights
or
go
into
periscope
in
that
issue.
Okay,.
A
B
Actually,
I
think
all
the
issues
are
coming
out
of
issue
ones,
one
one
six
I
think
we
should
just
tag
with
that
quality,
so
you
have
visibility
and
where
the
metrics,
it's
basically
a
list
of
issues
with
each
metric
and
where
is
it
going
its
purse
cover?
If
it's,
if
it's
going
into
the
native
version,
that
will
make
it
clear
there
as
well,
you
can
okay,
that
sounds
great
cool.
B
B
A
B
A
So
basically,
the
I
reviewed
the
original
training
and
it's
great
nice
work
by
Dahlia,
so
it
was
about
nine
months
ago
now.
What
basically
we
need
to
do
this
once
we
get
the
deprecation
done,
we
need
to
probably
go
update
that
because
all
the
graphs
and
everything
will
be
different
and
there'll
be
different.
Dashboards
between
the
two,
so
I
opened
up
issue
5
137
just
now
to
basically
address
that.
Ok,
so
you
should
market
is
done
with
a
follow-up
item,
the
137.
Once
we
did
don't
do
the
deprecation
application.
B
B
A
B
And
I
have
the
last
one,
so
the
trash
training
workshop,
so
I
I've
been
very
strict
on
myself.
We
have
two
training
recordings
out
already
and
the
third
one
that
we
showcase
the
charge
package
so
with
all
the
improvements
going
anything
this
is
because
this
can
be
considered
done.
I
can
link
all
the
YouTube
recording
and
just
embedded
in
the
handbook
where
we
list
all
our
charge
packages.
Essentially
this
page
and
I
can
consider
disclosing
these
others
done.
That
is
done
as
well,
so
we
have
just
so.
B
B
A
Well,
Dahlia
is
sent
a
little
silent,
note
so
just
make
sure
to
say
well
verbalize
it
thanks
Mick
for
running
the
meeting
and
the
product
to
you
team
for
the
great
collaboration.
These
efforts
looking
forward
to
continuing
to
work
together
on
these,
so
really
appreciate
all
the
hard
work
everyone
involved.
Thank.
B
You
it's
the
team,
effort,
I,
think
Brandi
and
Mark
are
not
here.
So
all
the
Kyle's
stepping
in
so
thank
you
for
all
the
efforts
and
the
team
is
oh
and
Josh
I
think
you
were
the
the
last
final
piece
of
the
puzzle
to
close
it
out.
So
thank
you
and,
of
course,
Greg.
Our
last
hypothesis
goes
out
cool,
very
low-key,
closeout,
I,
hope
into
recording
and
then
make
the
mrs
and
then
tag
everybody
for
review
and
then
yeah.
We
can
consider
this
working
group
flows.
I
saw
this.