►
From YouTube: Plan group 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
B
This
was
basically
to
pull
in
the
epics
for
the
next
time
frame
that
just
got
added.
Now,
if
I
scroll
further
ahead,
you
will
notice
that
we
have
this
one
more
epic
items
shown
up.
This
would
continue
as
long
as
we
continue
to
score
notice
how
the
the
newly
added
epic
shows
up
as
a
fade-in
animation.
So
so
there
you
go
as
you
notice,
like
this
last
item.
B
Got
added
and
scrollbar
is
further
away
from
the
right
edge
and
it
goes
on
so
there
isn't
any
threshold
beat
towards
scoring
towards
the
future
or
pulling
towards
the
past.
As
long
as
user
continue
to
scroll,
we
would
continue
to
pull
in
the
data
and
we
are
adding
the
items
and
basically
we
are
expanding
the
timeline
in
chunks
of
the
same
size
as
the
default
size
of
the
timeline
for
a
given
view,
just
to
make
sure
that
we
do
not
end
up
making
a
lot
of
requests
by
adding
the
single
months
on
every
school.
B
So,
for
instance,
in
the
months
view
we
are
showing
seven
ones
by
default.
So
every
time
user
schools
into
the
right
edge
or
the
left
edge
of
the
timeline
would
add
seven
more
months
from
the
future
or
from
the
past
and
would
pull
in
the
data
for
nighttime
print
and
show
it
into
the
timeline.
So
if
we
go
back
into
the
past
as
well,
so
let
me
scroll
back
and
we
have
the
giant
showing
up
now
if
I
go
back
again.
There
is
one
more
epic
item
added.
B
But
since
we
are
supporting
infinite
scrolling
now,
we
would
also
update
those
existing
epic
items
to
make
sure
like
the
timeline
bars,
are
expanding
to
cover
the
entire
time
frame
that
they
are
supposed
to.
So,
for
instance,
when
we
loaded
this
page,
we
had
these
four
epics
which
had
the
start
date.
So,
for
instance,
this
one
was
starting
at
the
in
June
25th
of
2018
and
similarly
for
rest
of
the
items.
So
if
I
continue
to
scroll
back,
those
bars
are
now
expanding
Israel.
B
So
as
I
scroll
more
into
the
past,
these
items
would
continue
to
expand.
You
would
also
note
this.
Like
the
moment.
Timeline
bar
is
updated
with
the
new
time
frame.
There
is
this
slight
fade
in
animation
as
well
for
those
items.
So
if
we
do
not
like
that
animation
like,
for
instance,
we
have
a
fix
to
be
shown
by
default
when
the
page
loads
and
if
user
continues
to
school
in
either
ways.
If
the
number
of
epochs
do
not
change,
only
the
timeline
Mars
length
is
changing.
B
Then,
if
you
do
not
want
animation
there,
I
would
change
the
code
to
make
sure
like
animation
doesn't
happen,
but
right
now
it
is
sort
of
a
boring,
boring
implementation
where
the
animations
would
happen
every
time,
a
timeline
bar
updates.
So
if
I
scroll,
my
father,
so
as
you
saw
like
the
first
item,
was
starting
in
June
25th,
so
the
bar
is
now
updated
to
reflect
that
approximately,
for
this
particular
same
thing
goes
for
the
second
item
as
well,
which
was
starting
at
the
second
April.
B
So
the
timeline
bar
indicates
the
same
and
as
we
continue
to
school,
behind
the
school
bar
also
updates.
So,
as
you
can
see,
school
bar
is
again
further
away
from
the
left
edge
and
the
items
are
shown
up
accordingly.
So
if
we
change
the
view,
if
we
go
into
the
weeks,
you
then
same
thing
happens
so
right
now,
since
current
week
only
has
a
finite
length
of
start
and
finish.
B
We
are
showing
only
two
items,
so
if
we
kind
of
if
he
starts
pulling
back,
it
would
basically
pull
in
more
weeks
and
the
moment
that
there
are
more
epochs
to
show.
So
like
this
epic
showed
up
right
when
new
time
frame
what
I
did.
It
would
continue
to
add
in
those
items
into
the
timeline
as
good.
So
this
is
again
happening
in
real
time.
It
is
basically
pulling
the
data
or
the
time
frame
or
adding
into
the
store
and
UI
reflects.
The
same
same
thing
goes.
B
If
we
go
into
the
past
as
well-
oh
there
you
go
so
like
lot
of
items
got
added
and
yeah,
so
this
one
was
starting
at
6th
of
September,
so
the
Mar
is
updated
to
reflect
the
theme.
This
one
is
starting
in
April,
so
of
2019.
So
if
we
are
going
back
into
2019,
then
it
would
show
the
time
frame
for
the
same.
So
there
you
go
so
as
the
user
continues
to
school,
there
isn't
any
kind
of
limit
or
thresholds
that
you
put.
B
So
most
of
the
points
were
conquered
by
both
Pedro
and
Anibal,
like
we
were
fine
for
most
of
the
items,
but
two
major
items
that
I
find
sort
of
deal-breaker
push
this
functionality
forward.
First
is
right
now,
as
you
can
see
like
when
the
time
frame
expands
be
into
the
future
or
into
the
past.
We
are
appending
the
items
into
the
list
of
the
a
so
sorting
doesn't
happen
on
the
UI.
B
A
B
B
Then,
for
instance,
if
sort
order
is
such
that
those
two
items
need
to
be
at
the
second
and
third
position
into
the
list,
then
we
would
have
to
insert
it
into
the
store
and
that
would
lead
to
pushing
all
the
following
items
further
down
into
the
list
right.
So
that
would
mean
everything
starting
from
the
second
position
would
have
to
rear-end
her
again
and
that
is
costly
from
the
front
end
of
perspective
as
well.
So
that
was
one
concern.
B
Another
concern
is
that
so,
as
you
can
see,
when
the
page
is
loaded,
we
have
so,
for
instance,
if
we
are
in
this
quarter
view,
then
we
have
first
quarter
showed
up
as
the
initial
column
in
the
timeline.
Then
we
have
second
quarter
and,
if
iSchool
into
the
future
first
and
then,
if
I
scroll
back,
you
would
know
this.
We
just
expanded
the
time
line
into
the
past.
So
the
way
the
scroll
detection
works
is
that
what
I
do
is
when
the
time
line
is
rendered.
B
Animal
would
probably
understand
the
word
I'm
trying
to
explain
here
like
when
the
time
line
is
rendered.
I
take
two
elements
from
the
entire
time
line,
the
very
start
stage
of
the
time
line
and
very
end
edge
of
the
time
line,
and
when
the
school
event
happens,
I
would
detect
whether
this
edge
element
came
into
the
viewport
or
not.
If
it
does,
I
would
expand
the
time
line
depending
on
which
edge
came
into
the
viewport.
B
The
past
would
be
the
future
and
would
the
end
I
would
continue
to
update
these
edge
elements
for
both
start
and
end
as
long
as
user
continues
to
school.
Just
to
make
sure
we
continue
to
expand
the
timeline
as
long
as
user
is
spooling.
So
for
this
to
work
on
initial
load
as
well,
we
need
to
determine
how
many
more
items
we
need
to
show
on
the
page
load.
B
If
we
have
the
space,
if
we
have
the
horizontal
space
available,
you
would
utilize
that
space
and
expand
the
column
size
for
each
of
the
column
in
the
timeline.
But,
for
instance,
if
we
shrink
the
window
size
and
if
there
isn't
space
available,
we
have
the
scroll
bar,
because
we
have
a
certain
minimum
width
that
we
need
to
respect
for
individual
columns
in
the
timeline.
B
So
again,
in
case
of
this
infinite
scrolling
to
work,
we
need
to
make
sure
that
the
horizontal
scrollbar
is
always
available,
because
without
that
scrollbar
available
user
will
never
be
able
to
scroll
and
the
code
bit
triggers
the
scroll
event
and
that
triggers
the
expansion
of
the
timeline
would
never
execute
because
there
isn't
any
score
bar
available.
So
for
that
to
work,
we
need
the
UX
guidelines
like
how
many
months
into
the
past.
We
need
to
further
expand
our
timeline
and
how
many
months
into
the
future
future.
We
need
to
so
to
show
that.
B
Initial
load,
we
just
need
a
number
like
how
many
months
into
the
past
and
how
many
months
into
the
future,
we
need
to
further
increase
again.
He
problem
to
solve,
because
we
don't
know
how
large
screen
size
user
is
on.
So,
for
instance,
if
today
we
determine
like
okay
B,
instead
of
seven
columns
instead
of
seven
months.
Let
me
show
on
the
initial
load,
let's
show
12
months
like
a
full
year
of
range,
where
B
would
be
showing
three
months
into
the
past
and
rest
of
the
months
into
the
future
right.
B
If
user
is
on,
like
55
inch,
4k
screen
for
some
reason
user
is
using
that
screen,
then
all
those
columns
can
fit
in
within
the
screen
without
scrollbar
showing
up
so
that
is
again
a
tricky
problem
to
solve.
What
we
can
do
is
that
we
can
determine
what
is
the
screen
size
and
dynamically
assess
how
many
columns
we
need
to
show
to
ensure
that
the
scrollbar
is
always
available.
So
again,
that
is
still
a
yeah,
but.
A
B
A
B
A
C
A
Yeah
somewhere
and
then
so
my
question
is
say:
you
go
back
to
opposite
extreme
right
now
and
then
you
maximize
your
window.
My
question
is
that
that's
fine
right
now
for
us,
let's
say
let's
say
so.
If
you
refresh
your
screen
right
now,
that's
what
I
saw
and
then
there's
no
scrollbar
right
in
the
case
here
right
so
see.
Imagine
your
your
window
is
even
bigger
like
ridiculous.
A
Thing
because
both
are
related
so
because
yeah
I'm
worried,
like
you,
have
a
really
big
screen
and
then
you
go
really
really
fat
columns
and
then,
when
you're
scrolling
there
it
seems
silly
because
you're
scrolling
really
fat
columns.
We
should
algorithm
that
is
dynamic
right
off
the
bat
and
it
sounds
like
you're
solving
the
same
problem
right
now,
so
you
might
as
well
yeah.
B
B
So
either
we
increase
that
fixed
number
of
how
many
columns
we
need
to
show
on
initial
load,
or
we
make
that
number
dynamic
as
well
like
as
long
as
there's
a
space
available,
maybe
sure,
like
the
column,
size
is
always
set
to
that
fixed.
Do
it,
and
if
there
is
more
space
available,
we
would
just
increase
the
number
of
columns.
B
Although
we
do
need
a
number
in
case
with
like
how
many
months
into
the
past,
we
need
to
show
because
we
need
to
determine
the
location
of
this
indicator
so
right
now
we
only
show
one
quarter,
one
month
or
one
week
into
the
past
and
the
second
column
of
the
timeline
being
and
equally
said,
is
always
the
current
representation.
So
it
would
either
be
current
month.
It
would
be
current
water
or
currently
I.
C
A
Like
so
for
really
small
widths,
we
just
like
a
phone,
that's
in
vertical
landscape.
We
just
pretty
much,
don't
care
about
it,
and
then
you
know
it's
always
a
fixed
width,
and
then
you
always
show
that
red
vertical
line,
so
it's
always
centered
or
like
a
third
away
whatever,
and
then,
if,
if
it's
so,
if
it's
so
small
that
you
can't
show
the
past,
that's
okay,
because
we
can
scroll
there
so
I
think
that
that
algorithm
or
or
that
logic
and
requirement
we
can
relax.
A
B
B
A
Also
putting
like
front
end
sorting
because
we're
retreat
from
the
dock,
yes,
you
have
to
sort,
and
then
you
put
them
in
the
right
place
and
when
you
put
them
in
already
move
things
around
and
both
of
them
are
costly.
And
so
what
does
that
mean?
It
just
means
like
the
computer
will
start
burning
up
and
it
will
be
slow.
Is
that
that.
B
Really
depends
on
how
fast
your
browser
can
run
depending
on
the
underlying
hardware
and
at
the
same
time,
if
we
do
not
want
the
page
to
freeze
up
just
because
it
is
doing
a
log,
but
now
that
I
think
of
that
problem
further.
So
since
we
are
looking
at
little,
Amal
Luna,
for
instance,
as
you
can
see
like
this
list,
is
vertically
scrolling
as
well
because
they
are
affixed
to
show.
B
So
if,
if
we
are
appending
epics
into
the
list
and
if
user
is
scrolling
into
the
future,
then
user
would
never
know
whether
new
epics
got
added
into
the
list
or
not,
and
till
user
schools
further
into
the
bottom
of
the
list
and
then
start
scrolling
the
timeline,
because
we
are
always
adding
new
epics
at
the
end
of
the
list,
not
at
the
beginning
of
the
list.
So
user
would
never
know
where
exactly
in
the
list,
new
items
got
added
or
if
at
all,
new
items
got
added
on
the
timeline
spool.
So
so.
A
Sorry
saying
like
in
the
regular
or
maybe
we
can
just
talk
about
the
regular
like
last
time.
We
chat
about
like
the
the
happy
path
case.
Is
that
things
just
get
added
to
the
bottom
or
to
the
top
and
then
so,
the
rendering
at
least
the
rendering
part
wouldn't
be
costly.
In
that
case,
right
and
yeah
yeah
use
the
due
date
version
and
then
there's
they're
using
these
ridiculously
weird
epics.
Then
it
would
be
possibly
is.
C
B
That
can
be
done,
so
we
already
have
the
information.
What
was
the
sort
order
and
that
information
can
be
exposed
in
the
into
the
roadmap
app
and
based
on
that
we
can
do
a
simple
route
like
if
a
particular
sort
order
is
due
date.
Then
we
would
basically
append
items
and
if
it
is
a
start
date
than
we
would
prepend
items
so.
C
C
A
D
A
E
For
what
it's
worth,
we
should
definitely
develop
that
ordering
function
behind
the
feature
flag.
So
it's
if
it.
If
it
turns
out
to
be
horrible,
then
we
can
turn
it
off
temporarily
until
we
fix
it,
because
there
is
a
potential
for
the
greatly
degrading
performance
there
I
agree
with
Michelle.
So
that's
one
way,
the
other
is.
How
can
we
get
the
information
to
do
the
ordering
in
the
first
place?
Probably
that
challenger.
F
B
So
you
mean
this
list
right,
yeah
that
list
no;
no,
they
don't
both
are
part
of
a
single
app.
So
if,
if
I
show
you
the
AB
structure,
then
there
is
the
row
than
that
and
yeah.
We
have
the
shell,
and
this
is
the
timeline
section,
and
this
is
the
list
section.
So
this
timeline
is
the
upper
half
where
you
would
see
the
actual
column
headers,
and
these
are
the
individual
items
within
those.
And
if
you
see
the
list
action,
then
we
have
individual
epic
list
item
like
these.
So
the
moment
you
expand
it.
F
B
C
B
So
when
the
timeframe
expand
expands
into
the
future,
we
need
to
make
sure
that
the
blue
timeline
bar
representing
that
particular
epoch,
expands
as
well,
who
cover
the
new
time
frame
that
is
available
into
the
area.
So
we
would
still
end
up
updating
that
entire
row.
The
moment
we
expand
the
timeline
so
yeah.
A
So
so
maybe
is
the
next
steps
to
defer
this
decision
of
removing
those
two
sorts
and
then
as
we
develop
it,
and
then
maybe
we
don't
have
to
do
like
her
performance
test.
But
maybe
we
just
do
some
manual
testing
and
see
how
horrible
or
not
horrible
it
is
and
then
like
Andre
said
like
feature
flag
it,
and
then
we
can
see
it
on
stage
with
production
like
data
and
then,
if
it's
really
terrible,
then
we
could
pull
it
back
somewhere
that
so
yeah.
B
And
one
more
thing
that
we
can
do
is
that
so
right
now
we
have
these
individual
list
items
have
a
certain
height,
so
they
they
basically
represent
the
height
based
on
the
items
that
we
show
within
the
list
item.
So,
for
instance,
if
we
go
back
to
the
github.com
show
that
we
have
700
items,
and
this
was
something
that
I
considered
when
we
originally
designed
the
roadmap.
So
I
wanted
to
basically
do
the
buffered
rendering.
So
we
have.
There
is
something
called
you
been
doing
approach.
So
what
happens?
B
So,
even
if
we
are
sorting
700
or
800
items
in
the
front
end
side,
those
700
items
still
live
in
the
JavaScript
object,
not
into
the
Dom,
and
what
we
do
into
the
Dom
is
that
we
would
push
all
the
items
that
are
supposed
to
be
shown
into
the
UI,
and
you
shown
that
the
rendering
performance
can
still
be
solved
because
you
renderers
has
to
worry
only
about
those
20
25
items
yeah,
but
all
the
rest
of
the
items
live
into
the
object,
and
that
is
a
standard,
I
design
back.
So.
B
B
B
E
This
that
I
want
to
bring
up
because
of
UX
is
that
it
kind
of
breaks
find
on
this
page
search
of
the
browser
if
they
want
to
search
on
the
browser
for
something
that
it's
not
on
the
Dom.
If
it's
out
of
view,
they
won't
be
able
to
pick
it
up
on
that
fine
from
the
browser,
but
I
in
this
particular
case
I.
Don't
think.
That's
really
probably.
A
A
E
A
C
C
A
C
G
B
So
what
happens
is
that
when
the
scrolling
happens
and
time
frame
is
expanded
first
thing
that
it
that
happens,
is
we
add
additional
columns
for
the
new
time
frame
that
we
doesn't.
That
was
just
arrived
right
after
that
we
also
refresh
existing
epics
to
expand
those
blue
timeline
bars
to
accommodate.
C
G
B
G
A
You're
sort
of
cheating
we're
not
really
cheating
but
you're
you're,
looking
far
into
the
future
to
grab
the
backend
data
and
then
rendering
it
so
you
you
you
have
some
lead
time
to
help
you
there
yeah,
but
I
think
you're
still
doing
it
like
I,
don't
know
if
transaction
is
the
point,
but
you're
still
doing
one
thing,
which
is
you
look
into
the
future
on
scroll
and
when
you
get
the
data
back,
you
show
it
immediately.
Even
though.
C
A
B
B
A
A
B
So
this
is
the
exact
code
where
the
things
are
happening.
So
what
happens
is
that
when
the
school
happens,
we
expand
the
timeline
by
calling
this
extend
time
frame
and
the
new
time
frame.
It
be
basically
cached
the
new
time
frame
for
our
convenience
and
then
once
the
store
is
updated,
we
re
render
the
existing
epics
and
once
the
rewriting
of
existing
epics
is
done.
We
fetch
new
epics.
So
if
we
just
change
the
order
of
these
two
methods,
things
would
happen
in
Reverse,
where
network
requests
would
happen.
G
C
A
I,
don't
pager
I,
don't
think
loading
state
makes
sense
at
least
how
cushaw
has
designed
the
algorithm.
I
know
it's
sort
of
backwards.
We
should
design
it,
but
from
the
frame
of
reference
of
what
cushaw
has
he's
predicting
stuff,
that's
gonna
be
occurring
because
you're
already
scrolling
forward,
say,
for
example,
and
then
you
look
further
into
the
future
and
then
you're
already
grabbing
stuff
and
then
so.
A
A
bad
experience
but
I
think
that's
okay
for
a
first
iteration,
because
what
I
argued
earlier
is
you
you
load
stuff,
you,
you
pre
cache
stuff
into
the
JavaScript
using
a
front-end
terminology,
but
you
don't
load
it
into
the
Dom
until
you're,
absolutely
sure
it's
gonna,
the
user
is
actually
gonna
get
to
it
on
the
screen.
So
so,
but
if
you
do,
if
we're
thinking
from
that
perspective,
then
loading
state
doesn't
really
make
sense.
A
G
I
think
do
because
if
it
takes
something
to
get
that
information
they
might
scroll
into
the
future,
they
don't
see
anything
and
they
assume
that
there
are
no
epics
there
and
that's
that
and
we
don't
know
how
long
it
would
take.
So
it's
the
same
as
having
an
infinite
scrolling,
and
you
don't
know
when
you've
at
the
bottom.
A
Or
you
you've
seen
all
then
you
get,
then
you
can
take
these
weird.
You
can
do
these
weird
scenarios
and
that's
really
I
I
don't
have
an
answer
to
that
pager,
but
I,
just
I'm
just
challenging
with
another
problem,
which
is
like
the
example.
I
gave
right
you're
looking
far
into
the
future
and
you
stop
scrolling
and
then
so
you
get
a
loading
spinner
and
you
stop
loading.
The
spinner
and
nothing
happens,
and
nothing
happens
right
or
maybe
just
just
the
epic
item
appears
and
the
bar
doesn't
appear
so
I
guess:
I!
Guess
that's!
A
H
G
G
C
G
I'm
just
wondering
if
it's
well
I
think
it's
something
that
we
should
think
about,
because
yes,
we're
welding
something,
and
we
should
give
the
user
expectation
that
something
might
appear
before
they
leave
that
context
right
or
else
they
might
think
okay.
This
is
it
there's
nothing
here
for
me
to
see
so.
I
switch,
tabs
or
I
go
somewhere
else,
and
that's
not
true.
Well,.
C
C
Was
I
say
for
this
iteration
I?
Don't
think
we
need
a
loading
state,
since
this
is
just
the
first
version,
but
I
was
thinking
it
would
be.
It
would
be
kind
of
useful
to
have
something
like
that
kind
of
like
how
Gmail
says,
like
fetching
new
mail,
when
you
click
on
her
face
button
and
it's
just
a
little
toast
at
the
bottom.
We.
A
I
was,
is
we
we
do
this
whatever
like
cleanup
whatever
and
then
the
next
one
I
I
would
push
for,
is
updating
the
design
so
that,
if
you
see
a
list
item
like
on
the
left
side,
but
there's
no
bar
you,
you
do
have
some
design
to
indicate.
Where
is
it
on
the
left
or
is
it
in
the
right?
And
then
once
you
have
that,
then,
if
you
add
the
loading
state,
then
it
all
comes
together
perfectly
because
it
loads
then
it
shows
the
epoch.
A
Then
you
see,
then
you
see
you
see
the
feedback
right
away,
which
is
you
see
the
epoch,
and
then
you
see
the
arrow
telling
you
where
that
time
line
is
and
so
to
you
to
the
user,
then
that's
reassuring
them.
Oh
keep
scrolling
in
that
direction.
You're
gonna
see
something
right,
and
so
it's
that's
what
the
loading
state
will
help
on.
E
That
note
Viktor
one
of
the
things
that
I've
been
thinking
on
top
of
the
loading
just
indicated,
whether
we
have
more
data
or
not,
is
once
we
have
the
new
epochs
coming
in
in
being
ordered,
I
think
the
important
part
is
users
being
aware
of
what
while
was
updated,
and
this
is
for
you
Annabelle.
If
you
want
to
think
about
no
way
to
as
they're
getting
added
to
the
list.
Having
some
sort
of
you
know,
the
yellow
fade
right.
I
learned
that
thanks
cam,
it's
like
boom
didn't
fade
out.
Yeah.
A
E
E
C
For
sure
I
think
somewhere
in
the
issue,
we
were
just
like:
let's,
let's
get
this
working
and
then
I
haven't
designed
any
animation
for
the
demo
I
think
I
had
it
fading
in
as
well,
so
that
was
already
yeah.
That's
definitely
my
radar
I
was
thinking
originally
we
would
have
just
the
height
animate
in,
but
that
was
that
was
when
I
thought
that
they
would
be
going
in
place
all
the
time,
so
that
kind
of
seems
unnecessary.
I,
like
the
idea
of
of
like
a
full
background.
Color
flash,
like
you
kind
of
said
well,.
E
C
B
So
while
we
were
discussing
the
timeline,
I
noticed
one
thing
so,
as
I
explained
in
the
beginning,
like
there
isn't
any
kind
of
threshold
in
the
timeline
with
upper
or
lower,
like
user
would
continue
to
scroll
and
timeline
would
continue
to
scroll
further
or
behind,
but
there
are
situations
where
there
won't
be
any
more
epic
stupid.
So
right
now
the
way
back
and
works
is
that,
as
long
as
there
is
an
epoch
which
falls
into
a
particular
time
frame,
it
would
continue.
It
would
return
those
epochs
into
the
list.
B
But
what
if
the
response
is
empty?
In
that
case,
should
we
want
user
to
not
be
able
to
scroll
further
into
the
future,
because
that
is
doable,
and
that
also
makes
sense
just
to
basically
the
not
too
old
burden
the
server
in
making
unnecessary
request,
because
response
was
always
be
empty
right,
so
I
just
did
that
change.
So
it
was
just
a
small
line:
teeth
I
added
a
flag
whatever,
so
we
are
in
the
quarter
view
and,
as
you
can
see,
first
request
happened
and
we
have
two
items
in
that
request.
B
Now,
if
I
scroll
further
one
more
request
happened
and
now
response
is
empty.
So
at
this
point,
as
you
can
say,
timeline
doesn't
scroll
further
into
the
future
because
there
are
no
epics
to
pull
in
because
the
previous
request
was
empty.
So
do
we
want
this
kind
of
experience
be
part
of
the
design
where,
if
there
are
no
epics
to
show,
then
we
do
not
make
requests
at
all.
D
So
I
think
the
issue
there
is
like
so
for
a
product
like
a
lab
which
is
like
being
developed
all
the
time.
That's
fine,
because
if
you
you
don't
have
a
gap
in
your
roadmap
right,
you
are
always
working
on
stuff.
I
think
it
might
not
work
so
well.
If
you're
looking
at
like
sort
of
products
like
maybe
for
an
agency
or
something
like
that
where
they
might
just
work
on
this,
then
leave
it
for
a
year.
Then
the
client
comes
back
and
says:
like:
can
we
work
on
this
again?
D
D
I
E
E
Earliest
yeah,
my
question
is,
if
it's
possible
to
know
the
earliest
and
latest
epic
that
would
be
listed
and
then
having
that
information.
It's
part
of
the
initial
load
on
the
page
and
then
the
front
end
could
know,
don't
request
anything
outside
of
that
limit
and
that
this
is
a
further
feature.
Iteration,
of
course,
discussed.
I
I
A
C
A
A
Effects
by
the
every
time
we
just
scroll,
it
sits
refresh.
So
so
you
wouldn't
have
that
right.
So
you,
if
you
artificially,
stopped
them
and
from
scrolling
anymore,
then
you
lose
that
capability.
So
so
that's
why
I
think
it
would
be
nice
if
the
backend
told
you
that
and
then
the
front-end
wouldn't
let
you
stop
scrolling,
but
it
would
be
super
nice
to
have,
like
some
type
of
you
like
to
tell
you,
there's
nothing
into
the
future.
Yeah.
H
A
Then
but
then,
but
then
that
would
be
messy,
because
then
you
have
to
ping
the
backend
like
you
would
you
have
to
pull
the
backend
to
say
like
or
something
just
to
refresh
that
message
so
that
they
can
keep
scrolling
or
something
that
so
I
think
I.
Think
there's
there's
like
a
nice-to-have
feature
there.
In
any
case,
I
would
I
would
say
the
nice
to
have
feature
would
be
like
yeah,
like
what
you
mention.
I,
don't
think
it
is
a
is
a
really
common
case
where
you
just
somebody
typically
scoring
outside
in
future
like.
A
Why
would
they
do
that,
but
John's
case?
What
actually
does
make
a
lot
of
sense?
If
there's
just
a
big
gap
in
time,
I
think
there's,
there's
got
to
be
a
good
like
Shawn
mentioned
a
good.
If
there's
a
big
gap
in
time,
then
maybe
the
the
rome
app
just
like
squashes
that
time
somehow
so
that
it
disappears
or
there's
some
other
visual
that
lets
you
yeah.
D
I
A
H
A
Think,
that's
that's
a
great
tool
for
us
I,
don't
like
that.
The
benefit
of
I
actually
thought
about
this
great
question.
Are
you
like
from
Rome
at
view
I
think
we're
still
using
calendar
years
so
for
milestones
at
gitlab?
We're
still
using
calendar
things,
so
I
think
it
should
have
hopefully
had
little
impact
for
us
if
anything
like
for
us
as
users
of
the
roadmap.
A
I
can
see
this
being
like
annoying
for
for
people
like
like
likes
it,
maybe
or
the
other
executive
people
or
people
on
the
sales
side
where
they
look
at
a
roadmap
you
and
then
they
want
to
see
quarters
easily
and
then,
when
they
click
on
the
quarters
thing,
it
doesn't
reflect
their
quarters
right.
So
the
only
feature
I
could
think
of
what
I
think
would
be
like
I
do
not
want
to
build
is
like
you
could
either
customize
what
quarters
mean
or,
like
you
have
like
a
fourth
button
that
says
like
fiscal
quarters.
A
I
D
I
D
J
K
B
Because
what
we
do
is
that,
if,
if
an
epoch
is
missing
either
of
the
dates,
only
one
of
the
date
is
present,
then
the
timeline
bar
shows
up
as
fading
out
towards
the
date
which
isn't
available.
So
in
that
case,
nothing
would
happen
just
that
the
timeline
bar
would
continue
to
fade
out
for
the
others.
All
the
time.
C
A
B
A
B
G
A
Could
actually
be
confusing
if
you
don't
know
so
this
is
actually
a
great
reason
like
a
great
future
iteration
where,
because,
if
you're
just
looking
at
this
and
you
don't
understand,
fading
away
means
infinity,
then
a
person
could
be
like.
When
does
this
end
and
it
keeps
growing
and
you
get
annoyed
so
I
mean
obviously
is
like
really
really
far
nice
iteration.
We.
I
I
C
To
help
with
the
confusion
like,
if
you
see
that
right
now,
just
as
it
is,
it
does
look
weird
you're
wondering
why
it's
doing
that,
but
on
the
on
the
actual
list
view
we
could
have
just
the
start
date
and
then
make
it
like.
Oh
yeah,
it
should
say
maybe
October
5th
and
then
in
red.
You
know,
add
an
end.
C
E
B
So
we
decided
so
in
case
a
sort
order
is
start
date
or
due
date.
If
it
is
due
date,
we
would
append
the
items
and
if
it
is
started
we
would
retain
the
items
so
at
least
for
two
sword
orders.
We
can
determine
whether
we
want
to
add
items
at
the
bottom
or
add
items
at
the
top
of
the
list,
so
not
in
the
middle.
No,
no
so
that
you
leaves
us
with
options
which
do
not
have
any
preference
of
well
items
to
put
in,
and
that
is
an
open
conversation.
B
A
B
B
B
B
B
B
So
what
you're
mentioning
is
so,
for
instance,
if
we
have
one
epoch
we
just
coming
in
in
two
future
tiny
thing
right
and
if
there
is
current
epoch,
which
expands
further
into
the
future
time
thing.
So,
for
instance,
we
have
this
epoch,
which
starts
in
September
of
2018
right
right.
So
if
I
scroll
back
into
the
future,
who
knew
items
what
I
did.
But
this
is
not.
B
So
if
you
see
this
letter
because
that
happens,
we
had
two
items
popping
here
friend
before
that
we
had
these
five
items
40
here
so
out
of
these
five
I
append
only
new
items
into
the
list.
Existing
items
are
discarded
so
in
in
this
cases
we
wouldn't
know
right
which
ones
to
solve,
unless
we
first
filter
out
the
list
and
find
out
the
new
epochs
which
got
added
into
the
list
and
physically
shorten
that
so
those
two
new
items
are
already
in
the
order
which
Mac
and
gave
us
so
those
orders
are
already
preserved.
A
G
Unfortunately,
it
will
be
broken.
I
understand
the
technical
limitations,
but
I'm
much
more
concerned
about
the
starting
due
dates,
sorting
options
because,
to
be
honest,
I'd
I,
don't
see
a
great
reason
to
have
the
created
date
and
last
updated
for
this
view,
and
that's
why
I
created
that
issue
for
us
to
discuss.
G
C
Some
degraded
performance
problems
right,
yep,
so
I
think
I
was
confused
too
I
thought
that
those
two
were
said
and
then
the
other
two
one
option
is
to
remove
them
which
I
like,
but
if
we
want
to
keep
them
for
this
iteration
and
I
thought
that
there
was
a
way
that
we
could
do
some
like
it's
really
poorly
performance
sorting.
Was
that
an
option
or
no.
B
A
B
C
Wondering
if
it
would
be
the
worst
thing
to
if,
if
a
new
one
is
loaded,
just
refresh
the
whole
thing
and
and
reload
all
of
them
in
the
correct
order,
and
then
there
was
new
ones
that
are
loaded,
would
have
some
other
visual
indicator
like
let's
say
a
yellow
background.
It's
not
gonna,
be
Yellin,
probably
but
it'll
be
annoying,
but
at
least
would
be
in
the
right
order.
Every
time
yeah.
B
Because
from
the
back-end
perspective,
what
happens
is
that
sorting
order
is
influenced
by
query?
Baram's
and
Mario
would
know
that
like
when,
when
when
we
basically
change
the
query
parents
or
in
the
new
list,
we
would
make
the
whole
theory
road
again
and
based
on
what
the
backend
returned
with
these
query
parents
in
case,
we
would
show
it
on
the
on
to
the
UI.
B
So
there
isn't
any
way
to
preserve
the
previous
list,
so,
for
instance,
if
he
scold
like
two
or
three
times
into
the
future-
and
we
are
now-
we
had
five
epics
fetched
from
the
expanded
time
line,
then
there
won't
be
any
way
to
cache
those
five
items
locally
and
it
wouldn't
even
make
sense
to
cache
moves,
because
order
of
those
items
would
still
need
to
be
recomputed
again
once
the
page
is
reloaded.
So
it
is
same
as
the
Bible
is
completely
stateless.
Yeah.
C
A
True
but
I
think
I
think
animal.
That
would
be
like
a
separate
I
think
that
that
that
requires
a
lot
of
changes.
I,
don't
doubt
the
design
could
be
a
good
design
right
like
if
you're
changing
the
sort
order
after
you
scrolled
and
then
you
wanted
to
see
things
in
a
different
disordered.
I
can
see
valid
use
cases
for
that,
but
I
think
for
for
this
iteration.
A
B
Yeah
so
yes,
I
assess,
yes,
I
want
to
access
how
soldering
performs
when
there
are
many
into
the
list,
and
would
do
that.
Do
that
for
all
four
swords
and
depending
on
how
it
turns
out
to
be,
you
might
as
well
push
it
at
least
four
11.8
and
see
how
it
performs
in
production.
If
we
realize
like
there
are
performance
problems,
then
we
resort
back
to
a
little
idea
of
like
a
pending
l,
228,
okay,.
A
A
G
Yeah
so
I
just
yeah,
just
you
can
read
it
there
I'm
planning
to
go
on
parental
leave.
Oh
it's
good
news,
but
it's
bad
news
for
the
plan
team,
because
Annabelle
will
be
the
only
go-to
person
for
fines,
UX
which,
which
is
unfortunate.
I
had
already
voiced
my
concerns
about
this
back
in
October.
G
But
again
the
head
counts
was
already
closed
for
last
year,
but
this
year,
until
the
end
of
the
year,
were
planning
to
at
least
hire
one
more
user
experience
designer
for
plan
and
yeah
I
just
wanted
to
share
this
with
the
team
ends.
If
you
I
don't
know,
if
anyone
has
any
concerns,
any
comments
that
they
would
like
to
bring
up
regarding
not
necessarily
my
parental
leave,
but
the
fact
that
we
will
have
less
UX
capacity.
A
We'll
figure
it
out
when
we
get
there
I
would
say
preparation.
We
should.
This
is
a
great
reminder
for
everybody
to
go,
but
Pedro
before
it
leaves
and
so
Pedro
do
you
have
anything
that
you
want
us
to
do
before
you
leave
like
just
to
take
this
opportunity
to
tell
us
to
work
on
certain
things
that
that
you're
no.
G
A
G
That,
if
you
want
to
say
thank
you
for
raising
that
Victor,
that's
a
good
question
today.
This
morning,
I
already
had
a
call
with
Constance
about
one
issue,
and
he
it
was
really
good
because
he
reached
out
to
me
to
go
through
the
design
for
related,
merge
requests
and
what
we're
doing
there
and
talk
a
little
bit
about
it
was
great.
A
G
E
Driving
with
the
mute
button,
sorry
so
yeah,
this
is
just
a
I
wanted
to
ask
around
I
know
that
we're
we
moved
away
from
doing
pre
assignments,
but
I
want
to
ask
Sean
and
Victor
more.
In
particular,
one
of
their
feeling
is
an
impression
so
far,
I
know
that
we're
still
following
up
the
process,
but
I
want
to
hear
your
your
your
thoughts.
Do
you
have
any
so
far,
I
think.
D
A
A
A
Sean
finds
it
I
can
answer
that
I
like
it
and
in
and
also
wanted
to
add
it's
it's
there's
like
there's
like
perspective
and
perception,
and
then
there's
also
like
hard
data
which
we're
not
doing
right
so
that
it
starts
this
hard
to
answer
so
I.
Guess
it's!
It's
very
subjective
and
it's
very
opinions,
but
I
think
it
also
depends
on
perspective
and
and
you're
not
perspective,
but
expectation
right.
A
That
to
me
was
confusing
to
communicate
and
hold
people
accountable
for
because,
on
one
day,
does
you
know
it's
typical
in
any
company
you
can
say
like
today,
like
horizontal
scrolling
is
the
most
important
thing
tomorrow.
It's
like
the
elastic
search
is
gonna,
be
the
most
important
thing
and
then
and
then
you
have
a
limited
number
of
people
working
on
things.
So
it's
really
hard
to
communicate
that.
A
But
with
this
you
can
always
point
to
the
list
of
priorities
and
even
though,
in
the
past
we
could
have
done
that
as
well,
but
by
definition
of
doing
pre
assignments,
you
could
always
say.
Yes,
that's
that's
important,
but
I
haven't
I.
Don't
have
anybody
assigned
to
this
yet
or
this
person
is
like
the
team
is
working
has
already
been
pre
assigned
to
something
else.
A
So
I
think
this
helps
me
as
a
product
manager
communicate
that
and
hold
people
accountable,
and
so
it's
easier
in
terms
of
like
actual
people
providing
status
updates
and
just
code
being
shipped
and
stuff
like
that.
I've
never
really
complained
about
us
going
too
slow
or
obviously
I'm,
not
gonna
complain
people
going
too
fast,
but
I've
never
complained
about
people
going
too
slow.
I've
always
just
complain
about.
We
don't
have
enough
people
to
do
things
so
I,
don't
think
that's
changed,
but.
A
In
my
opinion,
at
least
I
can
see
more
people
being
active
in
communicating
their
status
like
people
are
saying
like.
Oh,
this
isn't
gonna
be
done
at
the
end
of
11.7
victory
and
like
and
then
I
respond.
Saying.
Okay,
that's
great!
That's
that's
weird
at
that
point,
so
I've
enjoyed
that
improvement
in
communication.
Okay,
have.
E
B
A
A
D
You
have
to
take
the
list.
We're
gonna
make
it
clear
what
you
have
to
do
to
work
on
the
thing
at
the
top
of
the
list,
because
if
it's
not
broken
the
problem
with
those
issues
was
that
like
clearly
defined,
so
it
took
a
lot
of
like
ramp
up
time
to
even
figure
out
what
you
were
trying
to
do
with
that
issue
and
I.
Think
that's
the
bigger
takeaway
from
this
is
that
it's
been
from
my
perspective.
It's
been
really
positive,
but
some
and
like
basically,
the
only
way
I
would
change.
This.
A
A
I
So
on
this
retrospective,
this
milestone
I
actually
found
myself.
I
found
it
hard
to
keep
myself
accountable
just
because
we
were
used
to
having
you
know,
pre
assignment
and
say
what
is
easy
to
see.
A
To
me,
a
measure
of
success
is,
isn't
you
know
we
we
say
like.
We
want
to
move
fast
in
all
things
which
is
great,
but
to
me
at
least
in
the
plan
team.
For
me,
the
measure
of
success
is
getting
the
most
important
things
done
as
a
team,
and
and
also
a
secondary
measure
of
success,
which
is
more
obviously
more
engineering
driven.
Is
that
the
merger
quest
are
short
or
get
done
very
quickly,
and
you
know
I
can
I
can
impact
that
by
making
sure
that
scope
is
small
and
and
influencing
that.
C
A
A
The
most
important
thing
in
the
list
is
the
thing
that
is
the
most
important
thing
in
the
list
is
not
the
direction
item
is
not
the
security
item,
even
as
long
as
as
a
Picchu
or
lower,
but
it's
I
think
that's
in
review
and
that's
the
most
right
column
thing.
So
if
you
can
jump
in
as
an
engineer
and
you
have
like
five
minutes
or
you
know
like
half
an
hour,
that
makes
more
sense
and
you
can
finish
off
a
task
that
should
be
like
absent
article
II.
A
E
E
A
Would
you
do
assignments
if
you
have
a
prioritized
for
acing
that,
because
the
way
when
I'm
thinking
of
a
prioritized
board,
it's
a
real
time
prioritized
board?
So,
like
the
moment,
you
finish
something,
then
you
should
be
looking
at
the
next
thing
as
opposed
to
going
down
your
pre-assign
list
right,
yeah.
C
E
Sure
that
the
most
important
ones
don't
get
attributed
by
randomness
or
whenever
someone
gets
free
gets
that,
but
we
we,
as
managers,
can
look
and
see.
This
issue
is
more
tailored
for
this
person
or
that
person,
because
they
have
already
have
knowledge
or
or
they've,
been
working
on
a
very
large
issue.
What
is
mix
it
up
with
small
ones,
so
I
think
there
is
some
value
there
that
were
kind
of
changing.
However,
I
think
it's
too
early
in
the
game
to
make
very
hard
comparisons.
A
A
Assignments,
I
wouldn't
like
to
help
with
what
you
just
said:
I
would
say
instead
of
pre
assignments,
could
we
say
something
like
you
know?
We're
already
doing
this
obviously
like
back
end
in
front
end,
so
we're
already
pre
assigning
issues
in
that
sense,
right
and
then
so.
I
think
what
you're
saying
you
want
something
a
little
bit
more
granular
to
see.
You
know,
like
you
know,
a
senior
engineer
should
pick
up
this
or
this
engineer
has
more.
You
know
this
plastic
search
guru,
so
they're
gonna
do
this
yeah.
A
So
to
me
like,
we
should
still
have
that
and
I
don't
know
a
great
process
for
that.
I,
obviously
don't
want
more
labels
right
so,
but
to
me
it
would
be
like
you
know,
you're
typing,
in
the
comments,
you're
updating
description
to
say
like
oh,
you
know,
this
is
a
elasticsearch
issue,
mario's
expert
here
blah
blah
blah,
and
then
you
just
have
that
ongoing
async.
But
when
you
come
to
the
list,
you're
still
picking
off
the
most
important
thing
and
then,
but
since
you
have
that
context
already,
you
know
like.
Oh
you
know
this
issue.
A
I'm
not
gonna.
Pick
up
this
issue
because
I
know
Yara
is
gonna:
wake
up,
you
know
in
five
hours
and
then
she's
gonna
pick
up
that
anyways,
so
I'm
gonna,
move
on
to
the
elasticsearch
things:
I
I'm,
not
asking
Mario
to
do
ethics
right
for
that
particular
reason,
because
there's
probably
these
pseudo
pre
assignments
and
so
I
don't
know,
what's
the
right
way
to
do
that,
maybe
it
is
pre
assignments
but
like
that,
that's
how
I
think
about
that.
Like
pre
assignments
to
me
is
right
now
this
I.
I
Feel
like
it's
great
that
we
give
like
the
developers,
don't
freedom
to
choose
right,
for
example,
I
both
John
and
Josh
I
picked
up
some
elasticsearch
related
things
and
since
I'm
the
expert
they've
been
they've,
been
asking
me
things
and
that's
perfectly
fine,
and
that
also
shares
knowledge
around
the
team
right,
which
is
something
that
one
so
I
mean.
Maybe
we
should
make
it
clear
that
if
you
don't
feel
like
you
can,
if
you
don't
feel
like
you
can
do
this,
if
you're
a
little
bit
concerned,
then
right
skip
it
grab
them
next.
A
Think
it's
like
communication
to
me
like
I.
You
know
that
particular
case
I
actually
think
Mario
that
you
don't.
You
shouldn't
be
overly
concerned
that
nobody's
picking
up
the
first
one
I
think
that
should
be
a
team
conversation.
It
should
be
something
like
you
know,
everybody's
asleep,
in
your
particular
time
zone.
A
So
that's
not
problem
for
you
I,
think
but
like
if
you
were
like,
if
you're
traveling
to
Mars
or
something
I,
don't
know,
and
then
you
would
say,
like
oh
I
I,
don't
really
want
to
do
this
first
issue
or,
like
I,
think
somebody
else
should
pick
of
it:
I'm
just
pinging
everybody
and
I'm.
Just
gonna
move
on
to
the
next
issue,
because
you
know
I
could
get
it
done
in
30
minutes.
It
makes
sense.
C
A
You
make
the
best
judgment
as
an
engineer,
and
you
have
some.
You
have
some
judgment
and
there's
a
mix
of
things.
It's
gonna
be
like
technical
ability,
it's
gonna
be
familiarity,
it's
gonna,
be
preference,
I,
don't
think,
but
it's
also
gonna
be
you
know
what
the
product
manager
says
should
be
important
right.
So
I
think
we
should
balance
that
and
I
think
I'll
go
ahead
and
say
that
I
think,
like
a
very
high
percent
of
the
order
that
should
be
done
and
should
be
determined
by
the
party
manager
in
this
particular
case.