►
From YouTube: 2020 02 24 Memory Team Weekly 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
Progress
all
right
so
today,
quick
updates,
if
you
haven't
signed
up
if
you're,
going
to
contribute-
and
you
haven't
signed
up
for
your
Curtin
excursions,
I-
would
recommend
you
do
so
throughput
for
the
month
we're
about
half
where
we
were
yet
January
at
the
end
of
January.
So
for
all
projects
we're
at
13
for
the
limited
set,
that's
that's
being
counted
by
most
or
at
eleven.
So
just
a
heads
up
on
that.
B
So
for
current
work
for
twelve
nine
I'm
trying
to
focus
on
indie
JSON.
So
we
can
hand
import
back
to
the
import
team.
Have
that
dock
out
there
so
that
there
was
some
comments
added
this
morning
before
the
meeting
I
haven't
read
through
them,
thanks
Mateus
for
adding
your
suggestions
on
requests,
but
please
take
a
look
and
see
how
we
can
break
this
down
and
ship
it
by
ship
as
much
as
we
can
of
indie
JSON
and
make
sure
it's
working.
B
C
Yeah
so
so
I
think
that,
like
this
I
I,
don't
know,
I
think
that,
like
we
need
to
maybe
spend
some
time
on
understanding
exactly
what
else
is
left,
because
we
are
running
on
the
tight
deadlines.
If
you
want
to
make
Puma
and
I
would
by
default,
because
there
is
some
discussion
right
now
why
it
was
typed
to
enabled
it
by
default.
C
Because,
like
at
least
my
perspective
is
that
we
can
enable
Puma,
by
default
only
on
major
release
because
of
the
amount
of
the
changes
that
potential
user
can
make,
have
to
do
and
I'm
wondering
if
we
miss
these
13.0,
it's
unlikely
that
we
gonna
able
directing
definitely
point
one
or
very
big
thirteen
point
two,
because
this
is
becoming
a
minor
release
done
so
I
am
kind
of
like
asking
like
we
need
to
kind
of
assess
exactly
what
else
is
that
and
what
it
make
us?
What
we
would
have
to
finish?
D
I,
my
Gracie
I
think
ok,
I
discussed
this
four
years
ago.
I
need
to
get
into
Miss
you
apologize
for
not
doing
that.
Yes,
the
tentative
plan
we
had
was
told
that
mine,
opt-in,
ideally
remove
the
experimental
status
and
add
a
stronger
and
add
a
stronger
nudge
and
the
release
post
to
get
people
to
get
more
people
to
try
this
thing
and
set
a
time
frame
for
opt-out
and
then
13
that
Oh
being
an
optimistic
opt-out.
Okay,
I
think
it's
gonna
challenge
in
the
hip.
We
have
a
lot
of
work
to
the
documentation.
I'm.
D
Not
we
haven't
really
widely
deployed
this
yet,
and
so
you
know
it
making
it
making.
A
change
like
that
is
is
interesting,
plus
we'll
have
a
lot
going
on
there
to
know
that
we'll
be
doing
PG
eleven
as
the
minimum
requirement
plus
cream
law.
So
we
have
a
lot
of
a
lot
of
big
big
changes,
but
I
think
making
an
opt-out
includes
me.
That
was
is
probably
okay
and
then
well
its
aggressive,
but
potentially
achievable,
and
then
the
removal
of
unicorn
1400s
I
think
that's
the
most
destructive
change,
which
is
hey.
C
D
C
D
I
I
think
the
probably
challenges
is
that
when
do
we
make
this
opt
in
and
how
much
comfort
do
we
get
around?
You
know
it's
my
concern
is
we
need
to
make
this
opt-in
it's
already
opt-in
right,
but
we're
not
really
telling
people
to
go,
try
and
use
yet
because
we
don't
make
documentation
on
how
to
deal
with
this
thing.
C
D
Yeah
block
would
be
great
and
then
also
making
sure
we
had
guidance
then
make
sure
we
had
the
annulus
defaults
until
that
line
right.
So
we
get
the
right
defaults
going
in
the
omnibus
and
then
making
sure
we
have
documentation
available
for
people
on
H
a
and
they
just
may
be
a
nice
to
have,
but
pretty
nice
to
have,
but
certainly
on,
like
the
worker
in
front
counts
for
larger
sized
instances.
Because
not
everyone
has.
You
know
two,
two
or
four
core
boxes.
E
For
the
a
piece
we're
done
with
FEMA
from
the
beginning,
that
was
done
with
the
expectation
that
pyramids
gonna
be
made
more
official
sooner
rather
than
later.
So
there
were
reasons
get
and
13
0.
If
we
don't
put
in
first
0,
officially
they're
not
rolling
to
re
look
at
our
performance
testing
is
gonna,
be
the
recommendation
longer.
C
F
C
D
D
It
just
told
you
to
turn
it
on
and
that's
it
I,
don't
think.
That's
I,
don't
think!
That's
good
enough,
like
you,
don't
like
anything
about
I
mean
limitations
about
you
know,
utilize
need
a
health
check
and
so,
like
you,
do
able
to
use
this
thing
like
an
earnest
and
you
know,
I
think,
need
to
give
them
more
guidance
and
I.
D
C
Don't
know
like
from
my
perspective
it's
enough
for
like
to
reach
to
people
and
say
you
can
start
using
Puma.
These
are
not
efficiencies
and
issues
in
it.
What
else
we
work?
As
for
the
documentation
there
going
to
be
enough,
people
like
trying
that
out
and
testing-
and
we
can
just
be
fine
documentation
and
updated
blog
post,
but
the
longer
we
wait
is
just
the
harder
it
gets
for
us
to
get
in
the
time
yeah.
So.
D
I
think
questions
can't
be
obtained
documentation
until
at
9
I
think
it's
a
ton
of
work,
but
you
know
we're
already
advertising
Kumaon
or
at
least
post.
So
it's
there
we're
saying
it's
instrumental,
but
I
think
if
we
want
to
actually
tell
people
that
hey
try
this,
because
if
you
don't
try
it
now
we're
gonna
turn
on
for
you
in
30,
not
oh,
like
that's
a
different
message
and
I'm
earning
it.
A
lot
more
people
try
and
use
it
and
I
think
I
would
I
think
it's
achievable.
D
I
would
just
hope
to
be
a
better
documentation
for
our
customers
so
that
we're
telling
them
to
go,
try
it
out,
but
how
they'll
be
more
likely
to
have
a
good
experience,
but
anyways
I
don't
need
a
ton
of
work.
The
question
is:
is:
do
we
have
the
capacity
here
given
the
other
import
work?
We've
got
going
on.
It's
probably
a
couple
days
of
work,
maybe
for
the
documentation
maybe
a
week.
Not
a
lot
of
time
can.
D
C
It's
kind
of
it
feels
to
me
that
if
we
start
writing
H
a
documentation,
we
never
when
I
finish
that,
because
we,
like
the
knowledge,
you
know
we
have
the
knowledge
about
how
to
start
and
configure
uma
and
in
what
setting
and
how
to
use
health
check
and,
like
everything
else,
he's
fake.
We
don't
know
that
I'm.
E
For
for
a
minimum
or
MVP,
I
would
only
expect
there
to
be
the
occupation,
that's
equivalent
to
the
unicorn's
occupation,
as
there
already
I.
Don't
know
to
my
knowledge.
If
there's
like
a
specific
page
on
our
details
about
running
unicorn,
88's
I
decided
the
scaling
a
high
availability
page,
which
is
where
our
reference
environments,
our
work,
is
for
Puma
and
stuff.
We
we
do
kind
of
advise
a
little
bit
on
because,
like
I
did
so
on,
it's
paid,
dependent
or
depending
on
your
CPU
okay,
we
do.
E
We
did
severe
it
to
say
for
trads
when
I
think
I'm,
when
I
learned
that
that
was
going
to
be
the
new
kind
of
default
resided.
Therefore,
hey
J
I,
don't
think
is
anything
specific
to
Puma.
That
needs
to
be
documented
per
se.
Just
more
that's
more
of
a
higher-level
kind
of
documentation.
Piece
of
you
have
septum--ah,
but
then
you
just
need
to
replicate
that
and
no
bounce
it
and
that's
the
only
I'd
see
it
with
the
Davina
here.
C
You
know
the
last
time
I
look
at
the
H,
a
proxy
document,
a
sha
documentation.
There
was
basically
nothing
very
conclusive
exactly
how
to
run
it
up
in
a
way.
So
I
would
rather
say
that
there
is
no
way
check
the
documentation
that
will
discuss
that
fully
exactly
cut
around
it.
It
means
that
to
some
extent,
it
custome
needed
the
documentation.
C
D
So
I'm
actually
needed
everything.
Sorry
I
think
in
my
two
cents
is
this
further
need
to
hats.
Go
is
it's
the
Omnibus
defaults,
it's
some
documentation
on
configuring,
the
health
check
right
and
I.
Don't
think
I,
don't
think
we
need
to
make
this
exhaustive
or
even
part
of
the
H,
a
documentation
right
now.
I
didn't
you
see
on
the
Puma
page,
something
which
says
you
know
make
sure
you
have
this
and
your
little
balance
your
configuration.
F
D
F
D
E
2D
and
it's
a
very
like
I
said
earlier-
it's
a
very
generic
kind
of
page
is
talking
about
good
lab
reals
generically
it's
not
top
of
a
specific
stuff
because
to
be
in
in
the
actual
details.
Really
all
this
required
exciting
Pumas
friends
and
workers.
Really
everything
else
is
just
general
kit
lab
rails,
config
health
checks,
wise.
You
have
this
exchange
behavior,
that's
fair
enough!
That
should
be
called
out.
I,
don't
know
there
is
a
page
to
do
with
both
health
checks.
E
E
E
Was
actually
a
current
asked
for
energy
clean
up
the
main
Haiti
page
abscess
reason
issue,
but
that
that's
going
to
be
coming
in
soon?
It's
just.
It's
actually
is
gonna,
be
making
it
cleaner.
There's
a
lot
there's
a
lot
of
old
stuff
on
it,
but
I
won't
be
adding
anything
so
yeah.
If
you're,
bringing
in
a
tech
writer
that'd,
be
really
good.
E
B
It
could
be
wrong,
but
let's
finish
up
on
that
and
make
sure
that
we
have
12:9
lined
up
and
we
can
put
all
the
puma
work
at
the
top
of
the
board
so
that
those
come
in
as
priority
and
yeah.
This
was
important
to
talk
about
I'm
glad
we
did
talk
about
it.
I
wasn't
sure
how
much
needed
to
be
done
for
12
9.
That's
why
I
asked
so
I
was
taking
out
a
lot
of
stuff
over
the
weekend
and
Josh
noticed
because
we
really
want
to
get
import
transferred
over
to
the
import
team.
B
B
A
D
A
A
A
A
Need
to
kind
of
second
this
a
little
bit,
because
this
was
like
my
breakdown
that
I
just
threw
in
there,
because
I
thought
that
what
everyone
was
doing
and
then
we
could
kind
of
see
what
we
kind
of
decide
how
we
gonna
tackle
those,
because
we
had
like
a
slightly
different
breakdown
initially
in
DMR,
yeah
I,
don't
think
make
sense
if,
like
we
all
started
running
off
and
do
our
own
thing
funny,
Jason
yeah.
So.
C
Think
it
would
help,
even
if,
if
this
is
part
of
the
bigger
epic,
if
you
would
create
an
issue
associated
with
that
tomorrow,
it
would
help
exactly
like
to
try
that
that
way.
H
D
Yeah
I'll,
be
there
I
mean
Denis
meetings,
but
in
an
hour
so
I'll
time
to
focus
on
this
today.
Okay
and
basically
I
think,
but
the
sahaba
plan
makes
sense,
opt
in
well.
We
will
advertise
more
heavily
until
that
nine
release,
post
animal
and
nice
to
have
blog
post
I
think
that
need
to
have
is
that
is
the
released
post
entry
with
the
big
entry
on
Puma
telling
people,
basically
that,
like
give
it
a
try,
we're
seing!
These
awesome
benefits
we're
running
out
on
get
live.com
and
we
will.
D
We
will
opt
you
in
in
13
that,
oh,
so
please
try
it
now.
I
basically
will
be
the
message
coming
out
of
all
that
nine,
with
the
plan
to
then
make
it
opt
out
in
13
that
oh
and
then
probably
removal.
Unfortunate,
though,
is
their
concern
and
like
like
that
plan
in
particular
I
guess,
like
till
an
INTJ,
our
pods
as
fast
as
we
possibly
can,
but
fortunate
always
should
we
try
and
pull
it
in
sooner
or
is
that
okay.
C
G
C
D
Mean
potentially
I
think
we
need
a
friend
before
the
party
others,
but
we
can
explore
it.
The
breaking
changes
led
me
to
be
in
be.
We
can
say
that
breaking
that
change
is
1301.
We're
shifting
and
we'll
give
you
like
a
grace
period
to
sort
of
complete
the
migration,
so
yeah
I
think
we
can
probably
lose
my
sense.
C
Because,
like
I
assumed
that
it
should
be
enough
for
us
to
give
striking
ground
a
window
that
we
have
for
our
security
partisan,
how
many
ways
as
we
support,
because
we
assumed
that
our
customers
to
some
extent
dark
after,
like
I,
think
three
or
four
really
says
behind
our
regular
my
stones.
So
if
we
have
that
window,
they
could
really
start
testing
Puma
once
they
jump
into
13.0
and
then
kind
of
gradually
switch
to
Puma,
but
make
us
not
wait
to
14.0,
because
I've
been
wondering.
Okay,
I
mean.