►
From YouTube: 2019 09 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).
A
I'm
sure
they'll
show
up
here
shortly
so
yep
for
those
of
you
have
met
welcome
andreas
to
the
team.
He
officially
starts
with
the
memory
team,
but
they
be
announced
on
that
company
call
as
well
there's
so
under
yes,
is
joining
the
memory
team
he's
still
going
to
continue
being
database.
Maintainer
gonna
help
me
with
the
database
team
proposal
I'm
trying
to
get
that
over
the
line,
get
it
in
one
direction
or
not
for
another,
but
welcome
to
the
team
happy
to
have
you
here
wish.
It
was
sooner.
B
A
A
We
have
to
cover
so
means
less
rotations
for
on-call,
which
is
great
grant,
is
gonna,
be
spending
a
lot
of
time
with,
like
reference
architecture
and
some
big
customers
in
the
near
future,
so
he'll
be
pulled
more
and
more
away
from
the
memory
team
won't
mention
customer
names,
since
this
call
is
recorded,
but
he's
gonna
be
spending
a
lot
of
time
on
some
of
those
bigger
reference
architectures.
So
just
an
announcement.
Let's
see,
everybody's,
probably
seeing
all
the
emails
for
single
source
code
migration.
Some
of
the
important
dates
are
listed
in
the
emails
em.
A
Ours
will
be
closed
on
the
22nd.
Nothing
can't
do
anything
with
them
after
that,
so
basically
just
have
to.
If
you
have
one
open
and
them
in
talking
with
Larissa
rpm
she'd
mentioned
that
the
distribution
team,
when
they
have
something
that
should
be
announced
or
is
interesting
enough
to
announce
to
customers
that
they
label
the
items
with
release
post
items
so
that
they
are
included
in
the
monthly
milestone
wrap
up.
So
if
you're
working
on
something,
you
think
should
be
think,
is
noteworthy
for
the
milestone
notes.
A
A
C
A
C
In
the
worst
case
scenario
on
the
production,
it's
not
gonna
be
enabled
by
default
in
the
worst
case
scenario
under
production.
This
change
going
on
on
in
the
one
week
from
now.
So,
even
though
it
will
not
run
the
device,
I
mean
it's
not
gonna,
be
enabled
to
the
clients
anyway,
videos,
because
at
first
so
in
the
worst
case
scenario,
we
got
on
a
budget
and
a
few
days
later,.
C
C
B
D
E
A
A
B
C
Not
really
I
think
that
what
we
are
right
now
doing,
we've
seen
you
know,
we
gonna
cross
this
issue
before
like
what
we
are
doing
with
Cheney.
We
just
don't
I,
improve
that,
but
more
a
killer
to
be
like
more
flexible
and
this
issue
that
you
need
even
of
source
like
further
improvements.
The
improvement
expert
architecture
in
general
there's
an
iPad
from
the
site,
Kim
amore
killer,
which
in
some
very
special
circumstances
it's
more
aggressive
but
like
we
do
not
have
a
mekinese
to
make
it
too
aggressive.
Well,.
A
C
B
A
A
C
C
It
did
go
whole
like
quite
complex
because
of
the
law
grades.
So
I
think
that
this
is
regular
Samara
this
one.
This
is
like
the
Samara
of
that
of
the
next
steps
for
this
issue.
Okay,
for
this
issue,
and
for
this
actually
work
from
the
community
contributor,
if
you
want
to,
if
anyone
wants
to
eat
that
later.
E
E
A
E
No,
no,
no,
no
I
guess
that's
just
with
our
polish
is
that
we
shouldn't
cause
issue
until
it
is
released
on
production.
So
that's
why
and
about
workers
are
working
on
it
and
we
discuss
it
with
Camille.
We
have
some
strategy
to
try.
It
will
involve
two
nurse
requests,
one
into
Jenna's
into
our
project
and
I
guess
the
first
one
is
close
to
be
nursed
and
the
second
one
is
kinda
semi
ready,
so
I
guess
tomorrow.
I
will
push
it
to
review.
B
A
F
B
A
Coming
back
to
the
milestone
board,
so
I
have
12
4
pretty
well
lined
up
in
the
order
of
priority.
I
need
to
review
it
with
product
manageable
first
and
make
sure
this
makes
sense.
But
it's
basically
a
carryover.
The
work
that
we've
done
before
and
I
will
anything
that
we
carry
over
from
this
milestone.
A
I'll
put,
it
tops
and
say,
are
likely
to
be
in
flight
and
I
priority,
still
continuing
to
work
on
project
import
and
export,
improving
memory
and
CPU
usage
there
and
then
starting
to
pick
up
some
sidekick
tasks
and
then
at
the
bottom.
We
still
have
the
CPU
and
intent
memory
intensive
endpoints
those
will
probably
slip
over
a
favor
or
on
12:4.
C
F
C
C
A
Yeah,
okay.
Does
everybody
get
thought
so,
ideally,
at
this
point
in
time
so
week
three
before
the
seventeenth
we'd
have
a
good
idea.
What
we're
working
on
and
I
think
we
have
it,
maybe
not
down
to
the
individual
issues,
but
we're
so
interrupter
than
that
I'm
not
super
concerned
about
having
the
explicit
list
of
issues
for
the
milestone.
A
So,
like
Camille
said,
maybe
a
week
two,
we
can
start
looking,
and
this
is
what
we're
gonna
work
on
for
the
next
milestone.
Please
review
the
issues
out
there
learning
priority
order
and
about
half
of
them
ideally
should
be
assigned
to
folks,
and
we
can
start
adding
weights
to
them.
But
you
know:
we've
tried
weighting
all
of
the
issues
and
a
milestone
before
and
I
think
there's
some
issues
out
there
that
we've
waited.
You
know
couple
milestones
ago
that
we
still
haven't
even
touched.
A
So
I
get
the
idea
of
talking
through
all
the
issues
and
trying
to
add
a
way
to
them,
but
it
didn't
work
out
super
well
last
time
so
I'm
still
in
favor
of
adding
the
weights.
When
you
pick
up
and
having
folks
talk
about
them,
as
we
pick
them
up,
does
anybody
have
any
thoughts?
Besides
me
or
Camille,.