►
From YouTube: 2019 07 25 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
All
right
jump
right
into
it,
so
today
is
the
week
enablement
week
in
review.
So
if
you
have
anything
interesting,
don't
worry
to
add
to
the
dot.
Please
feel
free
to
do
so.
Go
incident,
like
happens
every
week
on
Thursday.
So
probably
remind
folks
of
your
week,
like
the
note
thinker
and
just
put
in
about
three
Puma
running
nightly,
would
be
pretty
awesome
share
with
the
others.
The
three
diss
doc
I
see
under
the
next.
A
So
there
was
some
questions
comments
about
how
our
new
continuous
delivery,
what
are
the
dates
on
continuous
delivery
and
folks
that
rolled
it
out
admitted
the
communication?
Wasn't
great,
so
I
just
put
it
here.
So
everybody
knows
what
the
major
dates
are
in
the
new
continuous
delivery
timeline.
So
you
can
take
a
look.
Basically,
twenty
third
milestone
starts
and
then
every
week
we
have
a
deployment
and
then
twenty
second
has
a
release.
Date.
A
During
that
time,
we'll
have
to
figure
out
what
work
to
offload
from
Lexi
had
a
bunch
of
sidekick
work
scheduled
for
12:00
tear
and
that's
the
likely
candidate
to
move
over
to
chin
yoo-hoo.
If
he's
watching,
this
recording
will
be
surprised,
the
Dec
7th
to
him,
but
yet
so
we
didn't
talk
specifics.
We
talked
about
Alexi,
shadowing
Camille,.
A
B
It's
more
like
a
life
sentence:
I,
don't
think
that
we
have
to
discuss
turds,
it's
more
like
peace
with
that
will
cut
the
graphs.
If
you
find
anything
interesting,
I'm
gonna
be
creating
a
bunch
of
the
issues
about
like
then
github,
dark,
validation
and
I
think
that
we
go
nah,
I
kind
of
follow
up
on
that
pretty
much
nothing
else.
So
far
like
from
my
perspective,
it
seems
that
everything
works
as
it
should
be
no
surprises
there
wish
we
didn't
have
to
reverse
the
configuration
change.
B
A
So
we
are
as
an
engineering
or
we
are
measured
on
throughput
I,
don't
know
how
many
folks
have
seen
like
the
individual
dashboard
that
we
have
for
the
memory
team-
some
data
not
there,
because
we
haven't
been
the
team
for
super
a
long
time
so
weekly
throughputs,
looking
great
the
color
is
based
on
the
labels
that
we
apply
to
the
MRA's
that
go
through
and
I
checked
this
weekly
to
look
for
any
undefined
labels.
If
they
are
undefined
and
I'll
go
I
figure
out.
A
Typically,
our
team
is
going
to
be
working
on
bugs
and
backstage,
but
it
could
also
be
feature
and
performance
are
some
of
the
labels,
so
I'll
go
through
and
look
at
them
on
a
weekly
basis
and
then
they
graph
and
as
an
engineering
org,
we
have
a
goal
to
get
to
I
think
it's
10
and
Mars
per
author
per
month
and
we're
not
quite
there.
Yet
we
are
I
think
we're
in
eight
to
nine
rings
as
a
team,
doing
pretty
well
obvious
growth
since
we're
coming
together
as
a
team.
A
C
Cool
yeah
mine's,
just
a
quick
announcement
that
we
had
a
test
automation,
engineer,
accept
an
offer.
She'll
start
August
19th,
then
she's
in
Russia,
but
she
currently
is
working
us
hours.
Even
though
she's
in
Russia,
she
took
our
interview
at
2:00
a.m.
her
time,
I'm,
not
sure.
If
that's
how
she'll
continue
to
work,
I
told
her.
It
wasn't
expected
so
I
guess
to
be
determined
what
time
zone
she
works
in
not
really
based
on
where
she
lives.
So.
C
D
Yep
so
I'm
just
a
few
quick
updates
for
memory.
I
made
the
test.
Epic
and
I
wanted
to
give
it
a
bit
more
before
it's
just
a
bit
more
bigger
wants
to
give
it
actual
real
deliverables,
so
I'm
updated.
Now,
please
have
a
look,
and
let
me
know
if
you
think
I'm
missing
anything
or
if
you
think
you
will
be
good
enough.
The
idea
is
to
also
make
it
so
that
this
would
be
completely
to
him
to
complete
this.
D
D
We
particularly
were
looking
at
project
import
from
pouring
data
to
make
it
as
easy
as
possible,
previously
we're
imported
from
get
help
which
two
colors
can
be
a
photo
repair
to
the
importer,
just
very
it's
hardball
that
also
took
actually
longer
and
then,
if
Camille's,
healthy,
actually
but
elfin
fix
these
color
from
like
floors
to
like
twelve
minutes
less
the
chat.
So
it's
a
massive
game.
So
with
that
Mary
means
that
people
can
just,
hopefully
only
have
to
run
a
few
simple
commands
and
they
can
start
a
little
testing
there.
D
D
26,
oh
yeah,
build
into
them
something
to
eat
next
up
day
was
just
one
of
the
deliverables
for
the
test
powers.
Definitely
getting
the
Forrester
report
against
tree
in
primo,
so
that's
running
their
nightly.
If
you
go
to
the
forest
channel
from
tomorrow,
you
should
start
to
see
the
results
go
through
there,
as
I
say
in
the
on
the
document
that
they
are
currently
we're
testing
of
twenty
responsible.
Second,
this
will
be
no
optimal
for
those
environments
who
seem
to
come
back
with
quite
slow
response
time,
so
I'm
trimming
and
pushing
it
too
much.
D
So
the
next
steps
just
me
going
off
and
trying
to
figure
wise
this
environment
actually
able
to
handle
and
tune
the
test
accordingly,
but
for
now
there
is
at
least
something
happening
with
them,
and
the
last
bit
is
just
trying
to
make
sure
that
the
monitoring
is
up
to
scratch,
I'm
still
at
the
Scott
roof
infrastructure
best
to
do
and
pull,
and
not
only
like
the
Megan
virus
inhabit
like
the
tank'
environment
and
stuff
into
one
place
that
we
can
start
point
to
people
towards
to
say
look.
This
is
where
you
go.
D
There's
kind
of
deciding
how
best
to
look
quality
doing
they
don't
want
non
production
data
on
a
production,
that's
where
it's
site,
so
they're
still
trying
to
figure
out
talking
with
them.
But
at
the
moment
there
is
a,
but
on
there
at
least
should
feel
free.
Camille
says:
there's
actually
Creek
them
as
well,
and
there
I
thought
wasn't
so
and
speech
them
after
see
this,
so
I
can
ask
quickly.
That's
it's
me.
A
Listen:
okay,
well,
Sean
is
working
on
an
on-call
rotation.
One
of
the
suggestions
that
somebody
made
was
look
into
volunteers
for
aankhon
engineer
in
the
on-call
rotation,
so
this
is
still
very
much
work
in
progress.
Everybody
take
a
look
at
the
link
that
I
put
there
and
add
your
name
if
it
makes
sense
or
if
you
want
to
volunteer
for
on
call
the
problem.
We're
trying
to
solve
is
there's
very
few
people
that
get
pained
for
on-call
support
right
now,
because
we
don't
have
a
like
a
formal
or
official
on-call
rotation.
A
So
typically,
if
all
the
people
like
stand
and
cameo
and
a
very
small
set
of
folks
when
something
goes
wrong
to
go
and
support
the
product,
so
we're
trying
to
bring
in
an
on-call
rotation
to
spread
the
wealth
and
actually
it'll
help
spread
the
knowledge.
So
take
a
look
and
your
name
if
you
want
to
volunteer
this
is
just
a
survey
at
this
point
in
time.
We're
it's
not
sure.
A
A
All
right
fast,
food,
I'm,
gonna,
try
and
finalize
proposal
today,
I
think
we
have
mostly
information
what
I'm
seeing
from
the
budget
is
either
if
we
go
to
Aberdeen
or
if
we
go
to
Warsaw,
the
budget
is
within
I,
think
five
or
six
hundred
dollars.
So
I'll
just
go
with
a
general
proposal
and
not
pick
a
location.
Yet
take
a
look
at
the
issue
itself.
There's
a
grid
for
availability,
so
we
can
kind
of
zero
in
on
the
time
I
have
put
in
slots
the
budget
for
the
new
test
person.
A
A
New
person
and
for
the
memory
team,
I
budgeted
for
the
two
new
hires
and
actually
another
announcement.
We
were
just
given
a
third
higher,
so
we
have
three
vacancies
for
the
memory
team.
One
of
the
front
end
teams
decided
they
didn't
need
a
candidate.
They
could
share
with
another
team
so
that
the
headcount
was
allocated
to
us
and
we're
still
talking
to
a
couple
of
internal
candidates.
We
have
I
guess
moving
on
the
hiring
update
and
we
have
a
pretty
decent
pipeline
of
folks
at
applied.