►
From YouTube: 2019 07 03 Memory Team Meeting
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
Right,
like
everybody's
here
so
I
mean
goal
today,
is
to
go
through
the
Puma
rollout
plan.
We
have
a
draft
for
with
memory
team
glad
Andrews
here
so
me
we
can
identify
how
far
off
we
are
on.
The
plan
is
going
to
be
some
dependencies
on
infrastructure
team
and
also
soon
us
folks.
We
have
a
holiday
tomorrow
that
will
be
offline.
A
Has
everybody
taken
the
opportunity
to
review
the
issue
for
the
memory
team,
Puma
planning
I?
Don't
want
to
have
to
read
through
it
all
I'll
do
a
quick
run-through,
so
we
outlined
some
of
the
metrics
that
we're
gonna
gather.
We
have
a.
We
have
an
epoch
for
it
and
even
called
out
the
specific
subset
of
issues
that
Camille
defined
I
think
it
was
late.
A
Last
week
we
have
an
outline
for
testing
and
then
just
to
call
out
to
our
load
testing
steps
and
omnibus
ticket
that
we
have
best
about
the
best
default
values
for
Puma
infrastructure.
So
this
was
originally
the
ticket
that
had
been
created
a
while
back
that
we
promoted
to
an
epoch.
So
we
could
call
out
all
the
steps
that
we
need
to
have
individual
tickets
for
all
steps
that
can
take
place
for
us
to
be
able
to
roll
out
Puma
on
to
get
lab
once
we're
done
the
fellow
development
work.
A
B
Need
to
talk
to
I
mean,
like
literally
since
that
last
meeting
I've
just
been
firefighting,
and
you
know
which
takes
precedence,
but
it's
just
like
ridiculous
way
to
spend
my
time
and
I
need
to
talk
to
Jerry
about
this.
A
lot
of
the
work
is
gonna
be
like
chef
and
that
kind
of
stuff,
and
that's
not
really
my
expertise.
So
I'll
talk
to
Jerry
about
who
the
right
person
is
gonna,
be
to
actually
make
that
make
the
changes
to
the
run
book
so
to
the
shift,
recipes,
etc.
A
That
so,
once
we
get,
those
identifying
looks
like
a
little
probably
carry
over
next
week.
We
had
initially
your
mark,
those
without
talking
to
Andrew
or
the
infrastructure
team,
try
and
work
that
out
this
week,
but
fully
aware
that
the
plan
that
we
wrote
is
optimistic
and
dependent
on
other
teams.
So
some
of
these
things
would
likely
slip
so
I'll
carry
those
down.
A
You've
got
a
lot
of
the
issues
created,
I,
don't
think
we
have
100%
coverage
yet
and
then
four,
that's
pretty
much
it
for
those
things
all
about
planning
and
identification
and
I'll
carry
most
of
these
over
to
the
next
week.
I
think
T
news,
not
here
this
one
will
likely
carry
over.
He
identified
some
things
that
were
not
initially
identified,
an
issue
that
he's
gonna
have
to
work
on,
so
it's
gonna
take
a
little
bit
longer.
A
Is
there
any
way
that
we
can
get
feedback
from
the
community
from
anybody
who
has
actually
turned
on
Puma
using
the
GDK,
because
the
options
there
it's
just
not
on
by
default
I,
doubt
there's
an
automated
way.
We
can
get
any
feedback,
but
if
we
gotten
any
feedback
at
all
about
Kume
usage
with
gitlab.
B
A
A
So
for
next
week
need
to
make
sure
that
we're
on
track
for
the
12:1
milestones
and
then
carry
over
anything.
We
have
for
12,
probably
because
these
things
are
carrying
over
a
bit.
We
will
review
the
plan
again
next
week
and
make
sure
that
we
have
some
confidence.
We
have
stakeholders
from
infrastructure,
make
sure
there's
no
dependencies
that
are
in
the
block,
our
timeline,
and
then
we
can
adjust
accordingly
working
more
on
validation,
testing,
identify
success
criteria
around
what
performance
we
expect
finish.
A
A
lot
of
the
metrics
miles
are
metrics
issues
that
we're
working
on
this
week
and
then
you
can
read
the
rest
of
the
plans
for
the
subsequent
weeks
in
the
last
few
weeks.
Are
there
empty
right
now
until
we
work
with
infrastructure
and
figure
out
timing
on
when
we
can
get
this
stuff
rolled
out
and
what
the
dependencies
are?
We're
pretty
well
planned
out
for
this
week
and
next
that's
about
it
any
questions
or
concerns
or
any
major
gaps
that
we
may
have
missed
on
this
draft.
So
far,.
C
B
C
B
B
A
A
That
is
a
no-no
really.
The
only
thing
else
we
had
on
the
agenda
was
talk
about
Yan
Yan
asked
about
transitioning
back
to
plan
and
sadly
he
wants
to
go
back.
You
know
we
don't
we
don't
want
him
to
go.
He's
been
great
to
have
on
the
team,
but
yeah
starting
on
the
ninth
he'll,
go
back
to
it'll,
be
okay.
Lexi
he'll
go
back
to
plan
team.
I
talked
to
Sean
about
you,
know,
I'm
sure
there'll
be
some
lingering
questions
about
the
work
that
he's
been
working
on
the
Paluxy
in
Jinyu
and
they
said
yeah.