►
From YouTube: 2020 09 28 Memory Team Weekly
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
welcome
to
the
monday
memory
team
meeting
jump
right
into
it,
so
we
had
a
follow-up
item
on
our
retro.
From
last
time
where
we
were
gonna,
we
talked
about
improving
the
data
feedback
cycle
and
that's
a
follow-up
item
for
the
company-wide
retro
coming
up.
I
think
in
a
week
or
so,
and
I
had
a
question
we
put
in
there-
that
we
now
have
our
own
gcp
project,
so
it'll
be
much
easier
for
us
to
get
a
fast
feedback
loop.
A
All
right
then,
well,
I
have
everybody,
take
a
look
at
the
issue
and
see
maybe
there's
some
more
context
there
that
I
didn't
cut
into
the
only.
B
A
B
A
I
will
follow
up
all
right,
so
priorities
for
13.5.
We
have
two
and
a
half
weeks.
Just
under
three
weeks
left.
One
of
the
goals
was
to
wrap
up
imagery
sizing,
and
we
had
this
epic
in
here
for
those
that
are
here.
Does
it
still
feel
realistic
that
we
can
wrap
up
all
these
items
in
here.
B
I'm
currently
doing
this
configure
image
scaling
max
proxy
environment
and
yeah.
We
also
need
to
roll
out
and
test
it
in
production
when
we
have
the
workhorse
version
being
released,
but
today
what
I've
seen
we
only
had
security
releases
on
gitlab.com
in
the
morning.
So
probably
it
will
be
tomorrow
or
later
today
and
then
I
think
the
big
thing
is
this
handover
issue,
the
first
one
which
is
needs
attention.
B
So
correlation
idea.
There
is
some
draft
a
mark
from
eagle,
but
I
didn't
look
into
this.
I
don't
know
how
complete
it
is
so
caching
options.
I
didn't
look
into
this.
I
assume
we
will
ignore
it,
because
if
you'll
see
that
in
production
it
wouldn't
it
won't
require
much
time
to
resize,
but
still
maybe
we'll
need
some.
You
know
summary
on
caching
in
it.
Okay,
so
I'm
not
sure
I
alone
could
handle
this
in
two
weeks.
Maybe
I
could
but
not
100
sure.
So
if,
if
you
split
it
a
bit,
then
it's
quite
possible.
B
B
Okay
and
yeah,
I
think
it's
highly
depends
what
we
see
in
production.
I
don't
see
any.
I
don't
expect
any
surprises,
but
still
I
mean
there
could
be
some
new
information
when
we
start
running
it
either.
You
know,
maybe
somebody
will
see
and
will
not
be
happy
with
quality
or
some
something
like
this.
B
C
C
Several
times
with
xingyu
and
I'm
also
working
on
currently,
I
think
that
that
alexa
is
also
assigned
to
this
issue,
but
he's
not
looking
at
it
at
the
moment
for
like
project
create
endpoints
and
it's
the
similar
story.
As
the
thing
you
already
stated,
the
biggest
problem
with
these
samples,
one
cash
pair
is
like
we
have
difficulties
in
reproducing
it
in
a
local
environment
like
for
production,
they're
easily
easily
spottable,
because
they
have
like
we
have
projects
with
a
lot
of
data,
but
on
local
environment.
C
So
I'm
still
struggling
with
project
create,
and
I
think
that
thing
you
also
struggled
with
jobs,
control,
show
action
as
well,
so
we
are
kind
of
trying
to
focus
to
like
solve
at
least
two
of
them
just
so
we
can
document
like
how
we
want
to
test
how
we
can
reproduce
and
how
we
can
debug
the
problematic
parties
like
reproducing
it
on
local
environment,
like
I'm,
able
to
reproduce
100
percent,
that
time
on
staging
and
on
production,
but
on
local
environment.
I'm
still
struggling
to
to
see
those
numbers.
C
Yeah
sure
thank
you.
That
would
be
great,
like
I
guess
it's
something
stupid
but
and
probably
connected
with
both,
maybe
with
local
environment.
Something
is
different.
I
know
I
I'm
listening
as
well,
because
I'm
also
curious
because
it's
strange-
it's
not
just
this
end
point
like
the
three
last
10
points
that
we
were
looking
for,
like
nothing
happened
on
local
and
it's
obvious
that
it's
happening
on
staging
and
production.
C
D
But
like
the
data
structure
that
we
have
on
on
github.com,
it's
like
it's
testing
all
possible
edge
cases
and
like
our
pictures
on
gdk
or
gck,
they
are
kind
of
lacking
and
it's
always
very
hard,
and
it's
pretty
hard
like
to
reproduce
the
same
structure.
Unless
you
know
exactly
what
to
look
at
like
to
look
for
and
like
teams
adding
new
features.
They
very
rarely
add
this
structure.
A
Okay
and
then
the
next
couple
it
looks
like
we'll
look
at
them
later
so
chin
you
going
to
pick
up
the
ramon
kit
lab
and
then
looks
like
we
haven't,
started
anything
on
ruby
27,
which
is
fine,
stan
updated
with
some
interesting
findings
and
recordings
of
all
the
warnings
on
that
epic.
So
I
linked
to
the
note
there,
but
it's
a
problem
for
future
us
and
then
camille
working
on
feature
flags.
D
Yeah
so
basically
like
this,
like
that,
first
and
my
I
have
to
finish
that
series,
because
gitlab
runner
team
is
kind
of
depending
on
fixing
like
very
long
code
standing
back,
and
there
are
also
like
items
related
to
the
feature
flags
that
I'm
looking
over.
D
That's
it
I
guess
like.
Maybe
we
could
look
out
craig
at
the
reach
issue,
maybe
like
on
on
wednesday
and
decide
if
it's
enough
to
close
our
rollout
issue.
I
think
it
should
be
fine
and
there
is
still
like
a
plenty
of
the
feature
flags
that
people
didn't
claim.
D
D
Yes,
so
I
look
at
the
least-
and
I
only
saw
like
two
feature
tracks
that
maybe
are
related
to
us
that
are
not
claimed
and
they
have
nikola
name
behind
them
because
nicola
introduced
them
and
the
question
is
like
how
we
handle
them.
Do
we
like
create
a
rollout
issue
for
the
manage
import
scheme,
or
we
wait
for
the
manage
importing
to
kind
of
do
that.
D
Sorry,
like
it's
not
about
the
rollout
issue
because,
like
these
features,
are
already
rolled
out
right,
so
it's
rather
like
feeling
the
details
and
maybe
like
linking
when
they
should
be
removed.
Because
at
this
point
I
think,
like
it's
more
about
like
removal
of
these
future
flights
than
the
rollout
and
like
acknowledging
the
ownership
of
them.
A
B
Well,
I
would
probably
ask
him
for
tim,
because
I
think
for
them
it
would
be
nice
to
familiarize
family
place
themselves
that
they
have
these
spikes
and
they
need
to
remove
it
excellently
so
so
now
later
they
will
still
need
to.
I
mean
to
know
to
think
about
these
facts.
Why
not?
Now?
No
I'm
feeling
the
information.
E
A
Okay,
we've
actually
hit
all
the
agenda
items.
Is
there
any?
Are
there
any
other
topics?
Anybody
wants
to
cover.
B
B
C
C
This
is
still
like
related
to
design
management,
which
is
totally
a
separate
issue.
B
Yeah,
but
when
they
will
start
to
move
it
that
it
wouldn't
make
sense
to
keep
like
resizing
and
workhorse
and
keep
let's
say
resizing
on
upload
in
separate
component.
In
my
opinion,
I
think
if
they
will
move
it,
if
they
will
decide
to
do
that,
everything
will
go
into
this
component,
both
like
uploading
and
dynamic,
resizing.
D
B
C
B
C
B
C
B
Our
dynamic
resizing
not
completely
like
it's
not
completely
disconnected
from
static
resizing,
because
I
mean
the
ideal,
the
ideal
path
that
was
mentioned
by
team.
I
believe
that
what
we
implement
as
dynamic
resizing
could
be
used
later
for
design
management.
Right,
I
mean
maybe
in
a
static
way,
but
the
same
libraries
is
the
same
approaches.
Yeah.
B
C
F
If
you
could
take
a
light,
look
that'd
be
that'd,
be
amazing.
If
you
have
time,
if
you
don't
have
time,
that's
also
fine,
I
it's
just.
This
is
just
purely
a
bonus
at
this
point.
It'd
be
nice
to
get
in
because
I
know
I'll
make
the
devil
team
very
happy.
But
if
you
can't
figure
out
a
way
to
deal
with
it,
then
oh
well,
we'll
do
it
as
a
next
situation,
but
yeah
after
he
kind
of
did.
F
E
F
Yeah,
I
don't
know
so
that's
something
to
maybe
tackle
there,
but
yeah.
If
you
have
a
quick
look
and
see
if
there's
anything
obvious,
if
there's
like.
Oh
actually,
this
this
actually
is
an
easy
way
to
do
this.
If
not,
then
that's
fine,
I'm
going
to
be
off
next
week,
so
I
need
to.
I
want
to
get
a
stop
up
for
review
soon
around
later
to
get
in
for
13.5.
So
I'm
not
looking
for
anything
heavy
here.
So
if
you
have
a
quick.