►
From YouTube: 2020 03 23 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
A
So
so
far
this
we
have
our
highest
total
of
Mars
for
a
month
and
we
still
have
a
week
to
go
so
47
at
Mars
today
and
we
have
a
week
to
go
nice
work
and
you
can
see
the
dashboards
there,
links
to
them
for
work
items,
jinyu,
updated
his
work
items,
so
the
you
can
read
his
updates
and
then
there
were
a
couple
of
issues
we
were
looking
to
close
early
in
this
milestone.
Camille
commented
on
the
issue
that
Nicola
was
working
on.
Did
you
have
any
questions
on
that?
My
god.
B
B
C
Take
a
look
at
that.
It's
like
the
second
one
is
like
not
yet
fully
finish.
This
first
one
is
finished.
I
only
have
to
do
like
quickly
base
again
a
new
review
cycle
on
it's
like
I,
I,
would
say,
80
or
90%
finished
I
only
have
to
move
around
like
two
or
three
tears
and
I
get
it
green,
basically
right
for
the
second
one
and
I
think
it's
gonna
kind
of
close
these
two.
This
issue.
B
A
A
C
Because,
like
we
enabled
it
on
death
and
I,
asked
him
20
Fabio
for
him
to
also
look
under
weather
like
we
see
any
difference
or
not.
If
we
would
not
see
any
difference
will
basically
and
I'm
good
at
on
staging
and
and
try
to
optimize
them,
but
maybe
like
if
I
free,
Nikola
from
bronze,
maybe
Nicola
would
help
me
like.
We
did
it's
testing
these
of
the
atomic
processing,
because
there
gonna
be
some
aspect
of
the
optimizing
that
implementation.
C
D
E
D
E
Yeah
the
first
story
just
called
in
today,
it's
pretty
small,
because
it's
just
enabling
a
cup
that
already
exists
so
I
did
that
and
it
found
a
couple
offences
only
three
of
them
that
I
was
able
to
fix,
because
this
one's
pretty
straightforward,
so
I
just
sent
out
an
mr2
review
its
great
way,
I
guess
well.
The
second
one
is
like
debatable.
A
E
Took
more
time
to
build
as
well
I'm
like
not
because,
like
it's
like
this
case,
where,
when
it
happens,
it's
pretty
bad
but
there's
just
way
too
many
false
positives.
Where,
like
it,
is
fine
to
do
it
because,
like
the
files
that
you
read
are
fairly
small,
so
we
will
probably
have
it.
So
if
we
enable
the
cup
like
that
yeah,
it
would
probably
get
more
in
the
way
than
it
would
help.
I
guess
so.
A
E
Yeah
I
guess
we
just
like
I'd
like
yeah.
Sorry.
Most
of
the
discussion
is
in
the
MRI
right
now,
so
we
were
just
like
yeah
like
thinking
about
what
could
be
alternative
ways.
You
know
maybe
just
documentation
right,
because
we
have
the
performance
guidelines.
I,
don't
know
how
much
people
look
at
this,
but
could
be
another
paragraph
where
we
just
it's.
E
Choice
right
now
is
to
just
like
write
up
a
paragraph
about
hey,
be
careful
with
I
all
read
and
file
and
read
and
read
lines
and
in
here
and
then
even
give
a
little
snippet.
You
know
like
here's
how
he
could
rewrite
that
just
a
heads
up
and
then
make
sure
making
sure
that
yeah
in,
like
mr
reviews,
we
actually
look
for
these
things,
yeah,
which
I
don't
know
like
I
guess,
maybe
we
maybe
in
the
engineering
weekly
we
can
post
the
heads
up
so.
C
E
But
yeah
like
what
I
just
said
like
we
probably
don't
want
to
have
it
like,
and
this
is
you
know,
yeah
I.
Guess
like
my
it's,
not
this
specific
issue
necessarily,
but
because
we
had
a
few
of
those
and
the
other
story
is
maybe
a
little
less
controversial,
but
I'm
wondering
in
general,
like
how
is
that
a
good
strategy?
You
know
to
have
cops
for
performance
related
problems
because,
more
often
than
not,
they
are
probably
not
problems.
It's
more
like
a
heads
up.
E
You
know
like
this
could
be
slow,
so
we
always
run
the
risk
of
just
getting
in
you
know
in
people's
ways
of
productivity.
The
main
thing
I'm
concerned
on
so
yeah
that
Camille
is
also
why
I
said.
I
think
this
is
something
we
should
decide
as
a
team.
First,
that's
why
I
didn't
want
to
put
it
out
to
review
and
have
people
like
with
you
like
Ruby
code.
A
Yeah
I
mean
one
of
our
goals
is
to
be
more
proactive
and
call
out
these
things.
But
if
the
signal
to
noise
ratio
is
wrong,
then
probably
should
start
with
just
the
paragraph.
Like
you
indicated,
and
then,
if
we
we
can
always
come
back
to
this
implementing
the
cop.
If
it
makes
sense,
if
we
see
enough
these
patterns
going
forward,
yeah
yeah
I
think
it
makes
sense
to
revert
to
a
paragraph
instead
should.
D
B
B
B
B
A
C
C
So
I
guess
like
I,
mean
because,
like
I
think,
we
need
to
figure
out
a
way
to
do
it
like
next
time.
Maybe
maybe,
like
our
cone
like
right,
Peter,
the
one
that
would
write
it
would
happen
right
before,
like
the
race.
We
could,
maybe,
after
like
the
action
item
to
our
call,
to
look
out
all
our
issues
and
Amar's,
which
would
be
good
ones
to
indicate
in
the
release
post,
as
kind
of
like
recording
thing
for
us
like
to
talk
about
that.
A
Yeah
we
talked
about
adding
a
release
post
item
labeled
to
issues
or
mrs
that's
something.
I
went
back
and
logged
in
and
see
any
in
there,
so
definitely
something
we
can
get
better.
I
like
the
idea
of
reviewing
or
just
having
a
note
in
there.
I
will
figure
out
a
way
to
add
that
to
the
agenda,
template
yeah.
F
I
think
I
think
the
release
post
labeled
is
great,
and
then
that
will
we
can
we
can
you
know
we
should
pick
it
up
and
you
can
look
at
it.
You
also
course
scan
through
the
Amara
list.
Just
make
sure
we
don't
miss
anything
or
also
you
may
be
seen
the
five
ones
that
are
more
important.
That
would
be
great,
also
sorry
for
missing.
So.
C
Guess
like,
for
example
in
these
carries
trenches
that
we
to
the
failure
ization,
they
were
part
of
the
nd
Jason,
and
this
big
is
not
yet
closed
but
like
we
introduced
anyway,
I'd
be
performance,
optimization,
which
was
like
part
of
them
on
a
mark.
So
now
that
person
is
like.
Would
this
really
supposed
to
be
right
for
the
mr,
or
should
we
kind
of
create
additionally
issue
to
indicate
this
optimization
that
received
yeah.
F
It's
like
that,
I
would
just
leave
it
on
the
mr
good
thing
you
could
do
is
just
create.
I
mean,
if
you
I,
think
just
the
name.
Where
is
fine?
The
other
thing
you
can
do
is
actually
create
a
release
post
item,
mr
against
the
like
unreleased
release,
post
branch-
and
that
will
that's
probably
the
best
way
to
do
it-
make
sure
really
doesn't
get
missed,
but
that's
that's
a
little
more
work.
I
can
try
to
do
that.
None
can
I've
released
first.
E
So
these
release
post
items-
that's
basically
like
it's
kind
of
like
a
change
lock,
but
a
bit
more
condensed,
but
it
is
it
like
bullet
points
or
like.
How
would
we
support
what
would
be
included?
I
guess
we
had
talked
about.
Can
you
chase
not?
This
is
just
like
a
paragraph.
Is
this
something
we
bright
or
is
that
done
by
the
release
team,
yeah.
F
E
F
F
But
there
are
two
types
of
sections
so
there's
this
section,
which
is
basically
I,
would
say:
there's
three
options
really
4.4
like
performance
improvements,
the
first
one
is,
you
can
just
label
it
with
performance
and
and
there's
a
link
at
the
bottom
of
this
block
right
here.
That
will
take
you
to
the
list
of
performance
improvements.
F
So
yeah,
so
so
that's
the
list
of
mrs
that
were
merged
and
added,
and
then
the
principal.
So
so
that's
one
way
to
get
in,
but
that's
probably
not
ideal
right
so
that
I
would
say
that
can
be
used
for
things
that
you
know
didn't
really
have
that
much
of
an
impact
for
the
streaming
exporter.
If
you
go
back
to
the
release
post
they're
like
I'll,
let
you
drive
a
little
faster.
F
Alright,
so
if
you
go
back
so
that
that's
this
one
and
then
the
next
step
would
be
to
just
add
it
to
this
list
here,
which
is
sort
of
relatively
significant
improvements,
but
but
not
massive
ones,
and
then
the
next
option
from
there
would
be
to
actually
add
it
to
the
list
here,
which
is
its
own
feature
block,
and
so,
if
it's
a
particularly
important
one,
you
know,
for
example,
the
the
streaming
import,
for
example,
should
get
its
own
item
here.
We
can
do
that
and
here's
some
examples.
F
F
F
Alright
anyways
I've
done
other
words
in
here.
We
did
do
one
that
actually
had
a
little
little
jiff
that
showed
the
database
end
points
previously
and
then,
after
the
change
and
like
missus,
went
from
mostly
read
as
far
as
missing
that
performance
targets,
all
green,
and
so
for
things
like
that,
we
can
definitely
use
a
full
on
performance
block
like
this
and
the
way
you
do
it
is.
F
F
So
there's
three
types
of
items
that
are
typically
here
we
have
the
top
items.
Top
item
is
the
most
important,
which
gets
like
the
biggest
space,
which
is
this.
We
then
have
primary
items,
which
then
get
side
by
side
views,
and
then
done
here
is
down
here
are
now
secondary
items
which
get
sort
of
like
just
you
know,
take
the
content
above
the
image
so.
E
F
It's
basically
product
management.
Well,
probably
interval
usually
get
a
sense.
Oh
I
think
this
is
a
primary
I
think
this
is
a
secondary,
I,
think
it's
at
the
top
and
then
once
you
get
closer
to
the
end
of
the
lease
post
process,
product
marketing
will
then
chime
in
and
then
say,
like
you
know,
I
think
these
are
the
top
three
features
of
this
rules
like
impact
wise
and
there's
a
discussion
around
that
but
yeah
but
anyways.
F
Then
this
is
really
what
has
to
happen
just
to
contribute
a
little
llamo
file,
and
you
just
say
what
the
name
it
is
what's
available
in
a
link
and
then
a
little
blurb,
and
if
you
want
you
can
have
an
image
attached
as
well.
Images
are
not
required
for
secondary
items,
and
you
can
see
all
the
fields
here
what
they
do
up
in
this
comic.
F
So
one
would
look
like
yeah,
of
course,
so
one
would
here's
an
example.
One
right
here
this
one
that
looks
like
didn't
make
told
that
nine,
and
so
it's
been
pushed
controlled
about
ten.
So
and
if
you
and
there's
a
merge
request,
template
I
can't
take
it
up
without
actually
a
branch,
but
I
can
show
you
what
it
looks
like.
F
F
A
F
F
A
Then
the
minimum
we're
gonna
have
the
performance
label
to
the
issues
that
went
through
our
merger
for
us
that
went
through
too
and
they'll
get
picked
up
in
this
list,
so
between
Josh
and
I
won't
get
it
squared
away
today
to
at
least
add
those
items
to
the
performance.
Improvements
list
will
get
the
really
expose
updated
thanks
for
pointing
that
out.
Camille
and
I'll
get
I'm
gonna
added
to
the
template
so
the
week
before,
or
we
start
talking
about
it
and
again
the
release
posts
item
labels
are
available
for
us.