►
From YouTube: 2019 06 20 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).
B
A
I'm
gonna
see
so
with
Camille
and
Andrew
not
being
here.
We
should
probably
do
the
continuation
of
Andrews
doc
from
last
week.
Asynchronously
I
can
push
the
agenda
on
that
make
sure
we
got
some
more
eyes
on
so
basically
just
making
sure
we
have
owners
and
responsibilities
assigned
for
this
doc,
which
we
talked
about
last
week.
So
I
will
follow
up
async
on
that
one.
A
Sorry
writing
out.
Y'all
have
to
wait
while
I
finish
all
right,
pretty
packed
agenda
for
everything
else.
So
there
were
some
questions
about
our
deliverables
and
largely
it's
because
we
have
a
pretty
new
team,
as
Tonya
mentioned
Alexi
join
two
weeks
ago
and
so
ditching
you
so
just
wanted
to
make
sure
everybody
knows
what
we
committed
to
4:12
one.
It's
in
this
kit
lab
kickoff.
It
was
the
scroll
down
to
memory.
A
Like
Alexei
inching,
you
you're
both
working
on
the
same
issue,
but
you
have
subtasks
that
you're
breaking
down
from
there,
so
I
would
recommend
whenever
he
started,
creating
where
we
start
working
on
subtasks,
maybe
break
out
your
own
issue.
That's
specific
to
the
one
thing
that
you're
working
on
the
one
issue
around
the
derailed
benchmarks
is
pretty
big
and
pretty
comprehensive.
So
if
you
and
Qing
you
or
you
and
whoever
else
on
the
team
are
starting
to
kind
of
diverge
or
working
on
specific
portions
of
the
issue,
I
would
just
recommend
creating
a
smaller
one.
B
It's
a
bit
complicated
because
my
issue
like
since
the
old
benchmark
is
involves
a
lot
of
discussions
and
we
talked
with
Camille
and
he
decided
that
we
are
not
ready
to
close
it.
Even
though
we
have
one
request
first
right,
he
decided
that
maybe
we
should
keep
it
in
a
single
issue,
so
I
guess
we
could
discuss
it
on
a
team
call.
This
Camille
exists
not
because
they
shift
yep
yeah.
A
A
What
we're
in
deliver
they're
working
with
product
management
Eric
is
super
overloaded,
so
it's
gonna
largely
be
up
to
me
and
our
team
to
figure
out
what
we're
gonna
commit
to
for
12
I
would
imagine
it's
gonna,
be
a
continuation
of
a
lot
of
the
things
we're
working
on
now
and
then
for
those,
especially
for
the
new
folks.
If
you
haven't
seen
the
development
timeline,
what
all
the
dates
and
milestones
are
I
added
a
link
here.
A
A
Let's
see,
I
got
our
a
sink
retrospectives
setup,
so
the
first
one
would
be
interesting.
Since
most
of
us
were
not
here
for
portions
of
twelve
one,
but
we
can
certainly
give
our
input
and
I
want
to
make
sure
everyone
on
the
team
has
access
to
the
issue.
So
let
me
know
if
you
don't
and
I'll
figure
out
what
I
need
to
do
to
fix
that
and.
B
A
Any
questions
on
that
section
just
basically
covering
our
deliverables
for
the
upcoming
week
or
two
cool
right,
more
specific
to
the
memory
team.
So
we
have
a
couple
time
sensitive
topics.
When
I
first
wrote
this
agenda
item,
we
didn't
have
deadlines
for
fastboot.
Oh
sorry,
that's!
What's
at
the
bottom,
so
open
zoom
channel,
that
was
an
idea
was
thrown
out.
Last
week
we
talked
about
as
a
team
just
setting
scheduled
open,
zoom
channels
for
the
memory
team
to
cover
all
of
our
time
zones.
A
Details
are
in
the
issue,
get
some
feedback
by
the
end
of
the
week
and
then
I
will
schedule
them
based
on
feedback
sounds
like
everybody's,
in
support
of
it.
Just
there's
some
questions
about
timing
when
it's
gonna
work
for
everybody,
Camille
was
gonna
schedule
an
alternating
meeting
time
for
this
meeting
in
Europe
in
Australia,
friendly
time
zones,
I
think
right
now
the
101-102
meetings
are
covering
everything
we
need
there.
So
we'll
look
to
next
week
to
get
those
scheduled
and
then
fastboot.
The
proposal
timeline
was
changed
or
revised
earlier
this
week.
A
So
we
have
to
get
our
proposal
in
by
the
31st
the
issues
link.
There
get
your
ideas
in
whether
part
of
its,
whether
you
think
it's
a
good
idea
or
bad
idea
is
the
timing
work,
especially
since
we're
still
building
out
the
memory
team
right
now,
ideas
on
location,
I
noted
in
our
an
issue
that
Europe's
going
to
be
the
most
likely
destination
somewhere
in
Europe
from
miles
traveled
and
I.
A
A
A
A
Onboarding
template
for
new
folks
as
they
join.
I
will
likely
copy
over
some
of
the
other
general
templates
that
are
in
the
gitlab
org.
So
like
bug,
templates
and
some
other
templates,
so
we
can
start
using
those
make
sure
we're
consistent,
create
a
default
template
from
from
the
gitlab
org.
So
whenever.
D
Thank
you.
So
this
came
up
with
my
my
cameras
and
on
this
came
up
with
my
table
shot
with
Stan,
where
they're
performance
issues
popping
up
everywhere
in
different
teams
and
Stan
was
suggesting
that
maybe
to
make
people
more
aware
of
the
challenges
we
were
facing,
we
should
highlight
and
publish
the
hotspots
that
we
fix
for
each
release
story
for
each
week
and
I'm
experimenting
with
this.
This
team
first
cuz
I,
think
we're
hitting
the
ground
running
with
Emery
and
performance
is
our
our
main
goal
so
yeah
in
the
Week
in
Review.
D
A
We're
just
looking
to
we
can
review-
maybe
we
just
put
in
a
placeholder
in
there,
so
we
don't
forget
to
add
that
in
every
week
I
like
the
idea,
I
mean
I,
don't
think
there's
any
performance
hotspots
we
are
fixing
at
the
moment,
but
we
can
certainly
point
to
areas
that
we're
looking
at
especially
it's
stuff
that
Alexian
teen.
You
are
working
on
so
yep.
You.
C
A
D
D
D
I
think
they're,
using
this
to
debug
and
I,
think
they
contributed
in
building
this
as
well,
so
wanted
to
socialize,
actually
I'm
trying
to
do
it
for
every
groups
as
well,
because
this
enables
everybody
to
debug
if
they
hit
a
performance
snag,
and
this
is
gonna
be
part
of
the
core
tooling,
for
this
team.
This
shows
you
all
the
calls
or
the
sequel
queries.
That's
taking
long,
I
think
this
is
at
four
point
four
milliseconds
and
whatnot
and
gives
go
to
all
other
stack.
D
A
And
right
below
that
I
linked
in
memory,
102
video
from
the
memory
team
I
think,
is
Wednesday
my
day,
Wednesday
Thursday
for
continue
where
he
does
go
over
that
at
about
two
minutes
into
the
video.
He
shows
a
performance
bar
and
they
actually
go
through
a
real
live
performance
issue
and
fix
it
and
submit
a
merge
request
at
the
end.
So
that's
great.
E
A
E
E
So
basically,
this
is
I've
analyzed
last
five
or
six
runs
and
then
I've
taken
DP
95
latency
from
the
for
each
and
every
endpoint
and
I've
added
25
percent
buffer
to
it,
and
then
you
know
going
forward
once
this
Mr
gets
merged
any
endpoint.
That
would
not
need
that
condition.
Would
okay
raise
a
red
flag
and
it
would
be
reported
in
the
queue
be
a
performance
channel.
You
might
want
to
keep
an
eye
on
that
and
if
an
endpoint
fails
consistently,
then
we
would
not
want
to
investigate
and
try
to
fix
the
performance
for
that.
A
F
Know
this
team
I'm
happy
to
do
it
again.
If
it
people
are
going
to
go
her
again,
yeah
I'm,
just
I
just
come
from
a
company
called
fair
in
systems
which
I
was
focused
on
kind
of
delivering
dozens
of
environments
for
teams
in
the
world,
for
automation
and
as
well
as
supporting
tested
virus
for
performance,
testing
and
I
have
recently
started
to
work
remotely,
and
my
last
drove
I
should
work
to
get
luck.
Whitelaw.
F
You
managed
in
local
instance
that
we
had
there
and
I
saw
that
get
LA
was
our
own
company
and
decided
to
give
it
a
go
and
Here
I
am
I,
wasn't
initially
applying
for
memory
testing,
but
so
that's
what
that
kind
of
came
through
the
interview
process
and
I
more
than
that
to
get
into
it,
because
it's
something
that
I've
done
a
bit
of,
but
not
enough
and
I'd
really
like
to
get
into
more
performance
as
well
surgery.
The
two
last
Big
East's
testing,
to
say
the
least.
F
F
A
It
takes
a
while,
so
they
have
been,
they
were
requested
to
provide
available
times
for
interviewing.
That
being
said,
I
think
we
are
at
the
bottom
of
the
priority
list.
Since
we
got
to
I
guess
three
recent
hires
with
joining
the
team,
we
were
officially
moved
to
the
bottom
and
you
can
take
a
look
at
the
priority
list.
It
changes
on
a
regular
basis,
I
think
fulfillments
at
the
top.
Let's
all
look
together,
yep
fulfillment
growth,
then
y'all
can
read
it
so
I'll
keep
looking
in
the
in
the
pooling.
A
So
we
have
our
specific
position
open
and
then
there's
a
back
end
engineering,
pooling
that
all
the
hiring
managers
can
take
a
look
at
and
if
they
see
a
candidate
they
think
that
fits
the
team.
Well,
then,
we
can
request
screening
and
you
know
if
I
request
the
candidate
and
fulfillment
request
in
Canada.
At
the
same
time,
they're
gonna
get
the
priority
over
every
team.
So
that
being
said,
the
pool
is
not
deep.
So
if
you
have
any
friends
that
are
looking.