►
From YouTube: 2019 08 12 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
C
C
B
B
All
right,
any
other
blockers
that
they
didn't
put
here,
assume
that
to
know
the
deliverable
label
not
well
documented
or
communicated,
but
once
we
make
our
plans
for
a
milestone,
we're
supposed
to
mark
all
the
issues
that
we
have
in
that
plan
as
deliverable,
and
it's
basically
saying
we're
committing
to
do
this
work
for
this
milestone,
so
I
know
I
sent
a
note.
I
think
it
was
in
slack
letting
everybody
know
if
you
saw
the
the
labels
flying
through.
B
That's
why
I
and
I
went
back
in
marked
was
a
12-1
with
all
the
things
that
we
committed
to,
so
that
the
graphs
were
cleaned
up
a
bit.
It's
on
the
quality,
metrics
dashboard
somewhere,
I'm,
not
gonna,
fumble
through
and
try
and
show
everybody
I'll
link
it
up
here
later
on,
so
y'all
can
see
where
it
is,
but
we're
measuring
where
we
get
our
deliverables
and
what
we're
delivering
above
and
beyond
that,
and
there's
still
some
discussion
about
like
discovered
items
during
the
milestone
because
they're
not
necessarily
deliverables
right.
B
So
carry
over
just
priorities
for
the
week,
so
Puma
continue
to
move
forward
still
waiting
for
the
item
that
I
just
listed
above
reconfiguring
Deb.
So
we
have
a
better
plan
for
staging
and
then
Canarian
and
production
by
the
end
of
twelve
three,
the
big
emergency
that
happened
last
week,
we
had
a
bunch
of
issues
come
through
that
caused
our
website
to
not
function
as
well
as
it
should.
So.
We
are
I've
been
labeled
as
the
DRI
directly
responsible
individual
for.
B
Re-Implementing
our
queueing
processes,
so
it's
all
listed
out
here,
there's
a
doc.
We
have
a
daily
stand-up
right
now
until
we
have
at
least
some
short-term
solutions
in
place.
One
of
the
things
that
most
immediately
affects
us
is
the
issue
that
Jinyu
is
working
on.
I
know:
he's
talked
to
Alexia
about
making
it
possible
to
kill,
running
sidekick
job.
There's
no
easy
way
to
do
it
right
now
we
can,
but
it's
fairly
tedious
work
around.
B
B
The
sidekick
jobs
adding
more
log,
just
better
understanding,
better
awareness
what's
going
on
in
your
environment,
so
those
are
the
high
priority
items
going
on
right
now
and
it
will
affect
12:3
and
then
we
have
a
lot
in
the
queue
right
now
plan
for
I'm.
Sorry,
we're
no
good
12:3
I
got
all
right.
So
next
milestone
it
will
affect
some
of
the
work
that
we're
doing
in
there
I'm
sure
they'll
push
some
out
adds
a
new
work
there.
B
So
any
questions
on
that
work,
cool,
alright
and
then
general
announcement
get
labs.
Creating
a
search
team
still
need
rails
and
Ruby
experience,
but
the
main
focus
here
is
going
to
be
working
with
elastic,
searching,
go
to
better
enable
our
search
experience
on
get
lab.
It's
not
great
right
now,
there's
lots
of
things
we
need
to
add
and
we
need
to
dedicate
a
team
to
do
it.
B
We
have
folks
that
are
working
on
the
go
working
on
go
to
create
the
elastic
search,
indexing
work
and
that
that's
already
in
the
get
lab
repo,
but
we
just
don't
have
enough
folks
focusing
on
the
search
experience,
let's
get
lab
in
general.
So
spinning
up
team
issues
link
there
I,
don't
think
the
jobs
have
been
posted
yet,
but
once
they
are,
you
know
anybody.
That's
got
a
either
of
those
experiences.
Then
let
them
know
that
we're
iron.