►
From YouTube: 2019 10 14 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
B
Yes,
so
guys,
my
name
is
Nicola
and
I'm
coming
from
Serbia
I
live
in
Serbia
and
I
was
senior
software
engineer
in
global
testing.
This
is
the
UK
crowdsource
QA
testing
company
and,
like
decision
to
join
the
club,
I
would
like
the
startup
culture
and
when
the
company
has
great
projects
great
product,
that
works
on
the
great
scale
and
somehow
get
loved
was
logical
step
for
me.
B
A
Thanks
Nicola
and
welcome
to
the
team,
so
this
is
our
usual
Monday
meeting.
We
go
through
what
we
what's
in
flight
for
the
week
raised
any
questions
and
walk
through
some
of
the
boards
that
we
have
so
first
thing
we
have
a
couple
boards,
Nicola
you'll,
get
links
to
them.
I'm
gonna
share
a
memory
team,
onboarding
tasks
with
you
here
shortly
and
you'll
get
all
these
links
to
and
actually
in
the
memory
team
channel
at
the
top,
you
can
you'll
be
able
to
see
that
the
links
are
on
top
as
well.
A
We
have
planning
and
workflow
and
milestones
the
ones
where
we
spend
the
most
time
or
the
milestone
board,
but
the
workflow
board
is
important
as
well
and
we
could
probably
make
better
use
of
it
as
the
memory
team
and
once
we
actually
get
a
product
manager
involved,
which
I
have
a
meeting
later
on
today,
we'll
start
making
use,
there's
a
column.
That's
missing
here
that
I
will
add
it's
ready
for
no,
actually
it's
right
there
in
trying
to
be
ready
for
development,
so
we'll
use
that
to
prioritize.
A
Where
can
people
start
picking
it
up,
but
where
it's
important
for
outside
this
team
is
just
to
see
what
issues
are
in
development
and
I
usually
review
these
during
the
week
to
make
sure
that
they
have
the
right
labels
on
them.
So
folks
know
that
what
we're
working
on
what's
in
review,
what's
been?
What's
blocked
and
what's
been
closed
and
that's
just
kind
of
a
long
list,
but
take
a
look
at
the
boards
make
sure
your
issues
are
properly
properly
labeled
as
you're
going
through
development
with
them.
So.
A
So
there's
get
a
different
tab
open
here,
so
there's
the
milestone
board
and
what
this
says
so
we're
in
12
for
right
now
and
everybody
should
have
work
assigned
to
them
and
if
there's
something
that's
not
assigned,
you
can
pick
it
up
from
top
down
order.
So
I
think
this
is
what
you're
referring
to,
which
is
I.
Think.
C
A
Yeah
I'm
not
sure
to
be
honest,
I'm,
not
sure
if
you
reorder
them
in
one
board,
if
it's
reflected
here
I
would
think
so.
But
in
any
case,
if
you
have
any
question,
just
ask
the
memory
team
channel
as
well.
I,
typically
look
I,
will
plan
off
of
this
board
and
make
sure
that
things
are
in
top-down
order
for
the
milestone
and
then
I'll
take
a
look
at
these.
A
This
board
the
workflow
board
to
make
sure
that
everything's,
labeled
or
I'll
ask
you
know
where
is
this
in
the
workflow
pipeline
and
I
use
the
planning
board
less
but
gives
you
an
idea
of
the
priorities
from
outside?
If
you
don't
know
what
the
p1
p2
you
can
just
hover
over
them,
see
what
they
mean.
A
A
Probably
not
gonna
be
answered
by
anybody
here,
but
I
got
feedback
from
someone
that
they
weren't
getting
any
attention
on
an
mr,
like
it
took
over
a
week
before
now
took
a
week.
They
didn't
get
any
feedback.
They
pinged
folks
that
were
part
of
the
reviewer
roulette
and
still
didn't
get
any
feedback.
So
I
just
asked
them
to
start
reaching
out
to
other
folks
directly,
especially
within
the
team,
if
they're
not
getting
any
feedback.
But
let
me
know
if
it's,
if
you
encounter
this
as
well,
the
turnaround
time
is
supposed
to
be
two
business
days.
A
Right
on
to
what
folks
are
working
on
so
Camille's,
mostly
working
on
Puma
related
tasks
and
some
health
check
endpoints
and
need
to
be
added,
so
what
we
ran
into
while
we
were
trying
to
get
Puma
out
on
the
canary
was
we
had
a?
We
couldn't
do
zero,
downtime
and
there's
a
bunch
of
work
that
was
identified
needs
to
be
related.
We
had
up
to
my
timeline.
A
D
I
am
just
trying
to
finish
this
magic
words
that
you
see
on
these
issues
because,
like
I'm,
actually
waiting
to
finish
the
one
that
I
listed
here,
1
7,
9,
6
tool,
I
I,
have
functioning
that,
but
I
still
have
to
finish
test.
Maybe
I
don't
know
tomorrow
or
day
after
it's
customary,
then
it
unlocks
omnibus
changes
and
I
could
then
finish.
D
These
were
at
readiness,
probes,
I,
lined
us
to
drive
to
what
we
discussed
on
the
meeting.
This
is
super
easy
chance,
but
I
need
to
close
this
issue.
First,
halves
of
this
magic
was
first
once
we
have
that
like
because
vector
technically
I
have
to
merge
like
these
I
have
too
much
too
much.
It
was
out
of
the
story.
One
is
created.
Second,
it's
not
yet
created
body's
gonna
be
super
small,
because
it's
basically
gonna
be
both
all
other
tracks
from
the
arrive
of
checks
doesn't
make
any
other
difference.
D
D
D
D
Guess
it's
a
blocker
because
until
like
we
March
omnibus
trances,
which
I
kind
of
like
Mike
it's
blocking
on
waiting
1796
to,
they
cannot
wait
like
deployed
and
tested
it.
Okay,
I'm
trying
to
think
he
that
it
cannot
be
easier
for
me
to
much
this
much
requests,
don't
create
another
one
and
have
something
being
done
in
the
parallel.
It's
much
easier
to
read
the
desk,
so
big,
so
I
should
have
to
read
it
tomorrow
and
maybe
like
tomorrow
or
day
after
it
should
be
managed.
Okay,.
A
C
C
C
More
general
questions,
I
did
a
couple
in
the
issue
itself.
I.
Let
junior
follow
up
on
that
as
well
to
get
on
his
view
again,
because
I
mean
you
start
about
it
way
more
than
I
did,
but
yeah
this
definitely
needs
breaking
down.
It's
probably
not
something
that
I
could
be
like
super
hands-on,
useful
for
right
now,
so
I'm
so
open
to
work
on
like
something
else.
Smaller,
that's
yeah,
more
actionable
one
tangible
right
now:
okay,
hey.
D
A
A
D
D
D
C
D
D
D
D
D
So
we
could
close
that
because,
technically
speaking
like
we
have,
this
is
by
fixed.
So
we
should
rather
have
like
the
serpent
match,
just
fix
the
bug,
fixing
sort
of
bonding
that
something
thicker
from
the
process
perspective,
and
this
follow-up
seems
that
I
hope
that
I'm
gonna
cross
that
as
well
I'm
a
struggle
on
getting
the
commentation
be
done.
He's
my
son.
So.
D
A
D
About
this
execution
limit
for
filing
I
would
propose
doing
some
sync
meeting
like
me
and
senior
and
Matias
to
try
to
evaluate
that.
How
important
is
that
and
what
we
could
do
the
simplest,
because
I
am
seeing
some
discussions
right
now
on
that
you
my
tears.
Have
that,
like
probably
confuses
me
exactly
what
we
have
to
do
decent
with
this
issue,
so
maybe
doing
something
called
on
this
particular
one,
since
this
is
at
the
top
of
the
list,
would
be
quite
helpful.
C
C
D
A
A
D
Because
because,
for
example,
I
am
looking
like
dynamically
sub
DB
pull
if
boom
I
see
news,
it's
quite
easy
and
I'm
sure
that
we
should
fix
that
as
soon
as
possible,
because
it's
also
quite
easy
investigate
memory.
Consumption
for
detail
up
slightly
process
I
have
no
idea
what
we
should
be
doing
terribly
well.
I
think
I'm
are
used
to
sidekick
tasks.
D
I
kind
of
connected
with
the
previous
one
at
an
IP
I
endpoint
for
the
profiling
seems
like
the
simmilar
are
swaps
and
produced
from
each
is
metrics,
unlike
maybe
we
don't
needs
to
do
wheels
at
all
then,
like
we
have
this
intensive
endpoints
and
we
have
also
correct
import
best
values
for
Puma
zero
downtime
deployments,
update
documentation
for
Puma
switch
over
our
github
control,
reloads,
so
kind
of
like
random
items.
At
least
of
these
moments.
A
D
A
And
maybe
I
need
to
sync
up
with
Andrew,
because
the
reason
their
sidekick
work
was
prioritized
was
because
of
that
outage
that
we
had
a
couple
months
ago
and
it
was
identified.
The
sidekick
was
causing
a
lot
of
problems,
but
I
think
with
the
fleet
in
queueing
updates.
He's
done.
Maybe
it's
less
of
a
problem,
but
I
would.