►
From YouTube: 2020 03 16 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
I
know
the
time
changed
a
little
bit
and
probably
messed
up
some
people's
schedules.
So
all
right,
so
you
just
run
through
the
agenda
so
in
our
total
for
the
month.
So
far,
sixteenth
and
I
think
with
all
the
docs
work
that
everybody's
jumping
in
on
probably
see
a
nice
spike
over
next
week.
So
and
thank
you
for
everybody
jumping
in
on
that
quickly
and
cranking
out,
a
bunch
of
them
are
us
to
review,
looks
like
progress.
Is
going
really
well
there.
B
So
thank
you,
I'm
just
gonna
jump
over
to
the
board,
so
we
can
run
through
twelve.
Nine,
since
that
is
in
the
tomorrow,
is
effectively
the
last
day.
So
looks
like
Camille
just
joined
us,
so
Camille
were
just
running
through
the
board
and
you
are
the
first
one
on
there
so
upstream
patches
for
Akuma,
yeah.
C
C
A
B
A
B
D
So
we
broke
out
a
sucky
shoot
from
this,
because
it's
not
really
directly
related
to
this
story,
but
generally
there's
something
wrong
with
exporting
projects
on
staging,
occasionally
breaks
on
certain
types
of
projects
or
sizes
of
projects,
but
not
totally
sure.
Yet
it
breaks
with
an
error
message
about
like
object,
storage
being
enabled
so
I
hold
in
infrastructure.
D
D
Completely
it
is
working,
so
it
works.
Did
you
pick
a
smaller
project,
but
those
are
very
useful
to
measure
so
I.
Think
at
this
point.
I
should
just
start
working
on
something
else
and
like
ones,
export
in
general
fix
and
staging.
We
can
just
like
retest
this
with
this
project
that
was
broken
before
and
if
it
works,
and
we
can
just
kind
of
done
then.
B
D
A
D
I,
don't
I,
wouldn't
the
only
thing
I
would
do
so
so,
assuming
the
fix.
So
soon
we
fix
exports
or
what
I'm
a
problem
that
is,
we
don't
know
yeah.
The
only
thing
I
would
do
is
I
would
change
an
environment
variable
which
is
just
a
project
confident
even
have
to
write
code,
it's
just
to
point
it
to
a
different
project
and
that
that
should
be
like
far
any
unforeseen
other
problems.
So
if
we
want
to
call
it
done,
we
can
call
it
them.
Oh.
D
B
C
D
So
I
tested
again
this
morning,
I
posted
the
results
in
there.
It
is
like
I
think
it's
done,
I
mean
that
we
broke
out.
Everything
that
we
know
is
an
issue
has
follow-up
items.
It
looks
like
an
improvement
on
the
air.
I
think
that
Dania
is
because
not
all
the
fixes
have
made
it
to
production
yeah
at
least
not
as
of
this
morning,
but
only
to
staging
I
was
only
able
to
test
it
on
staging
so
far,
so
in
production
it
will
still
be
off
the
future
town
hall
and.
D
D
D
B
E
We're
course
acceleration
yeah
this.
This
one
is
done
and
I
just
need
to
verify
it
on
prod,
maybe
I,
don't
know.
I
just
wanted
to
wait
a
bit
until
I
I
am
sure
that
there
are
no
issues
in
channels
and
so
forth.
I
already
made
an
applaud
and
it
works,
so
we
could
basically
close
it
and
I
wander
if
I
will
be
able
to
nourish
the
second
part
as
well,
which
is
currently
scheduled
for
tell
but
I'm
finishing
the
last
night
request
as
well.
So
maybe
it
will
be
nursed
very
soon
shot.
Okay,.
B
B
C
C
Yes,
I
actually
brought
it
back
again
from
the
12.10
because
it
seems
that,
like
most
of
these,
changes
are
pretty
much
in
flying
I'm,
not
sure,
because,
like
I
opened
them
mr4
like
Puma
Walker
configuration
mean
only
path
to
change
the
defaults,
but
there
is
seems
to
be
another
match.
Ship
is
being
opened
by
BAM,
so
it's
likely
that,
like
this
em
are
gonna,
be
matched
anyway.
C
C
It's
it's
strange
because
this
one
is
pretty
similar
to
right
to
the
previous
one.
Yeah
III
would
rather
even
say
like
that
top
T
case,
so
my
mean,
and
it
has
to
be
some
cleanup
that
we
should
do
like.
Maybe
we
should
merge
these
two
issues
and
basically
close
this
I
like
the
ban,
how
dare
to
get
smashed.
C
B
C
E
Any
any
specific
instruction
we
are
going
to
put
into
this
documentation
or
we're
just
going
to
say
that
you
need
to
do
it
manually
and
figure
out
anything
for
according
to
our
best
radians
and
to
cross
link.
Everything
here,
I
think
it's
more
of
the
latter,
so
just
to
make
sure
top
database
and
great
yep.
C
A
B
A
B
B
B
All
right,
so
we're
gonna
run
to
1210.
Look
at
the
goals,
we'll
do
the
high
level
instead
of
going
through
issue
by
issue,
so
Colton
I
put
them
in
themes.
Cuz,
there's
a
lot
going
on
in
1210,
just
try
and
keep
it
somewhat
organized
so
CI
minutes.
Obviously
that
got
prioritized
for
us.
This
milestone.
It
doesn't
seem
like
it's
a
ton
of
work,
I
think
it's
something
that
Camille
on
Aleksey
will
probably
pair
on
as
Alexi
gets
freed
up
from
the
work.
B
Colors
work
that
he's
doing
right
now,
there's
still
some
organization
on
the
issues
like
I
still
need
to
create
that
epic.
But
these
are
the
issues
that
were
created
by
Camille.
Take
a
look
boom.
Oh,
we
went
through
some
of
the
twelve
nine
issues
that
got
pulled
back
in,
but
there
are
a
few
things
that
we
need
to
finish
up.
The.
A
B
And
then
there's
a
blog
post
and
then
there's
a
couple
of
their
small
issues
that
we
need
to
clean
up
and
then
for
development
practices
that
we
keep
talking
about.
Actually
working
on.
These
are
the
ones
that
we
pulled
in
for
12:10,
probably
maybe
Matias
and
Jinyu
pair
up
on
those
or
whoever's
available
and
then
import.
There
were
a
few
things
that
we
want
to
finish
up
and
then
for
stretch
goals.
There
were
some
usage
pings.