►
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).
A
A
Okay,
great
thanks
I
just
wanted
to
let
everyone
know
that
I'll
be
out
February,
7th
and
8th,
which
is
always.
You
know
the
trickiest
time,
because
everyone's
trying
to
get
there
weren't
requests
in
last
minute.
I
have
reached
out
to
Chris
here's
the
plan
expert
for
the
UX
team,
but
he's
been
out
of
office
as
well.
So
if
that
fails,
then
please
go
to
Torre,
and
if
that
fails,
then
just
you
know
find
someone
else,
but
yeah
there's
a
little
chain
of
command,
I
guess
but
yeah.
A
A
My
next
point,
I
didn't
really
get
a
chance
to
okay.
I
was
gonna.
Look
at
it
again.
I
just
wanted
everyone
to
know
we're
gonna
move
forward
with
the
tab,
design
for
viewing
epics
or
sub
epics
within
epics
and
I'm
gonna
start
working
on
that
this
week
and
try
and
finalize
that
for
the
next
milestone.
Victor
I
just
read
your
message
on
the
plan
channel
about
the
customer
who's
interested
in
that
I
didn't
know.
A
If
you
wanted
to
talk
about
that
a
little
more
or
if
you
had
an
idea
of
separating
out,
you
know
we
discussed
on
that
issue.
Whether
or
not
we
wanted
to
reorder
epics
within
that
epic
paid
or
I
wanted
to
create
a
whole
new
view,
and
if
you
have
any
insight
from
what
that
customer
was
like,
that
would
be
great
I.
When.
B
We
talked
with
customer,
we
didn't
get
to
that
level
of
detail
in
like
through
design
perspective
and
even
if
they
had
like
a
strong
opinion
I
when
super
super
trust
them
I'm
either
one
customer
out
of
many.
You
know
and
I,
probably
trust
you
as
a
designer
more
and
so
to
confirm
when
you
say
tab
design
served
at
the
mr
merge
request
view
right
where
you
have
the
multiple
tabs
at
the
bottom
right.
A
B
B
A
Know
yeah
I
was
I
was
wondering
if
the
treeview
should
be
like
a
separate
thing
where
you're
moving
things
around,
and
we
should
just
show
the
direct
descendants
right
above
it
where
they
already
are
really
patient,
I'm,
not
sure
yet
I
still
need
to
look
into
it.
I
was
just
letting
everyone
know
that
I
think
this
is
the
best
way
forward
and
then
because
right.
B
Hey
like
I,
don't
have
a
strong
opinion
right
now
because
to
me
it's
like
so
exciting.
The
doctor
there's
so
many
like
to
me
for
a
design
perspective.
There's
so
many
benefits
and
and
negatives
and
I
can't
really
decide
in
my
head.
So
I
think
the
best
thing
is
just
a
ship
in
iteration,
so
I'm
fine
with
it
I'll.
Let
Sean
and
cushaw
comment
here.
C
I
wanted
to
just
ask
for
something
very
quickly,
but
before
you
jump
into
that,
Annabelle
would,
with
this
tab,
design
include
still
the
sidebar
tree
like
for
a
quick
view,
and
then,
if
you
want
to
manipulate
the
tree
or
have
a
deeper
look,
we
go
into
the
tree
tab.
Is
that
the
idea
or
would
the
sidebar
just
not
be
implemented?
At
this
point?.
C
Because
I
feel,
like
that's
a
quick
look
and
then,
if
you
want
a
deeper
look
on
two
tabs
and
I
just
wanted
to
throw
something
else,
which
is
on
the
create
side
there
working
on
design
management
and
it's
gonna
fall
on
issues.
So
it's
not
really
here
on
epics,
but
the
pattern
is
there
to
grow
up
to
the
temps.
Okay,.
A
B
We
already
like
issues
are
already
gonna,
have
tabs
very
likely
soon.
Amar's
have
tabs
and
then
issues
in
epics
or
pro
well
we're
proposing
up
except
tabs
so
yeah.
Maybe
it's
not
the
worst
thing
in
the
world
to
have
tabs
and
then
so
then
I'm
just
gonna
leave
my
thoughts
here
and
then
we
can
move
on
if
he
or
we
can
linger.
If
we
want,
but
like
the
like,
we
have
related
issues.
We
have
have
picks
we
are
like,
and
then
we
have
related
merge
request.
B
I
can
see
a
world
where,
like
a
lot
of
that,
turns
yet
gets
hidden
behind
tabs
or
hidden
is
a
bad
word,
but
like
conveniently
located
behind
tabs,
like
the
obvious
negative,
is
that
you
have
to
click
to
see
it,
but
like
I,
wouldn't
mind
I'm
not
going
to
be
one
of
those
people
that
are
just
going
to
complain
that
I
need
to
click.
One
more
thing:
I
think
it's
a
good
design,
but
I
can
see
a
lot
of
people
complaining
in
going
that
way.
I.
B
D
D
B
We
can
all
we
can
almost
like
avoid
that.
We
can
sidestep
that
problem
right
now,
because
it's
already
limited
right
by
2
5
right
now
like
under
as
a
hard
constraint
anyways.
So
then
the
you
I
will
never
go
beyond
5.
In
the
moment.
We
want
to
relax
that
to
5.
We
can
revisit
this
problem
so
provided,
like
you,
think,
5
levels
is
not
too
terrible
right
now
that
that's
like
the
worst
that
can
happen
in.
B
No
right
now
that
that
is
the
limit
on
the
back
end
for
the
how
long
an
epic
tree
can
be
right.
So
if
you
do
like
ABCDE
and
then
F
like
epochs,
going
down
to
F
F
pick
will
not
work,
it
will
complain
right.
So,
on
the
back
end
perspective,
you
cannot
add
an
extra
epoch,
anyways,
so
I'm
saying
like
if
your
UI
logic
doesn't
have
a
separate
constraint.
It
just
goes
as
far
as
I
can
then
we'll
be
fine
for
now.
D
Although
there
we
had
20
levels
as
the
max
limit,
and
we
encountered
similar
problem,
where,
how
would
we
be
with
the
stepping
think,
like
if
user
has
like
all
the
20
levels
of
nesting
in
place,
then
what
would
happen?
So
one
idea
that
we
tinkered
around
was
to
follow
how
files
managers
do
it.
So
what
we
did
was
when
you
try
to
open
a
certain
item
which
has
for
the
child
items
we
would
like.
D
It
would
appear
same
as
how
you
would,
when
you
open
a
folder
in
a
file
manager
where
you
would
see
a
breadcrumb
with
the
path
like
where
exactly
you
are
in
the
nest
and
in
the
body,
you
would
only
see
child
items
for
the
particular
path.
This
way
we
would
be
fine
with
any
levels
of
nesting
that
we
would
have,
because
at
any
given
point
of
time
you
would
be
seeing
child
level
and
the
breadcrumb
can
be
scholar
with
just
like
a
path
bar
in
the
finder
would
be
so.
D
In
that
way,
we
can
basically
do
away
with
any
levels
of
nesting,
although
Mac
and
has
a
limit
of
5,
but
we
may
never
know
when
this
limit
gets
removed.
So
but
then,
with
that
design,
one
concern
is
what,
if
user
wants
to
see
adjacent
items
like,
for
example,
there
are
two
top
level
parents
and
user
wants
to
expand
the
parent
a
and
see
what
are
the
child
item
within
parent
a
while
also
looking
at
parent
B
I
just
want
to
it
just
to
get
an
idea.
So
that
is
still
an
open
question.
A
Yeah,
that's
definitely
an
interesting
idea,
especially
if
we
decide
to
do
a
separate
view
for
the
entire
tree,
where
we'd
have
all
this
like
what
I
have
basically
in
that
screenshot
would
be
a
separate
view.
So
yeah
I'll
look
I'll,
look
into
that.
Do
you
have
screenshots
and
trying
to
picture
that?
Is
it
it's
just
like
the
file
manager.
D
Might
have
a
screenshots
of
the
work
that
I
did
back
then
I'll
find
out
and
they'll
share
you
on
some.
It
was
very
similar
to
how
managers
would
do
so.
For
instance,
if
you
are
on
a
third
or
fourth
level
of
China
items,
then
in
the
breadcrumb
that
you
see
in
the
top
would
have
all
the
levels
of
nesting
that
you
went
so
far
and
between
two
individual
items
there
will
be
an
arrow
icon,
on
which
you
can
click
and
see
what
are
the
items
right
within
that
particular
parent.
D
A
Awesome
thanks
for
that
idea.
That's
pretty
much
all
I
had
and
think
for
child
epics
I
didn't
get
a
chance
to
look
at
it
yesterday.
So
I
don't
have
much
else
to
add
yeah.
E
I
had
one
question
which
I
put
in
the
dark,
which
is
probably
answered
in
the
issue:
it's
just
a
very
long
issue
in
the
tree
tab.
It's
not
clear
to
me
how
I
would
tell
apart
and
a
child
epic
from
a
child
issue,
and
then
I
was
thinking
like
in
another
lists
like
this.
We
only
show
things
of
one
type
like
you
know
in
Victor's
example,
in
initially
related
requests
and
the
related
issues
and
those
are
in
separate
lake
areas,
whereas
here
we'd
be
mingling.
E
A
A
B
B
Separate
tab
seems
like
pretty
straightforward
of
a
design,
but
maybe
you
purposely
wanted
to
keep
in
the
same
time,
because
you
maybe
want
to
see
everything
together.
I
don't
know
I
mean-
or
maybe,
if
you
you
keep
in
this,
if
you
have
like
separate
tabs
and
one
tab
is
for
child
epics
and
but
if
you
keep
expanding,
you
actually
see
it
sub
issues
of
the
of
your
sub
picks.
Is
that
confusing,
because
in
the
epics
tabs
you
also
see
like
issues
all
the
way
going
down.
B
C
The
screen
show
that
Annabelle
was
in
Miriam
posted
on
the
chat
I,
like
the
concept
of
having
the
same
filter
that
we
use
for
on
merge,
request
and
discussions
of
having
just
the
activity.
Just
the
comments.
Kind
of
is
the
pattern
or
the
places
where
we
just
like
filter
out
what
shows
up
and
then
you
could
choose
to
just
look
at
the
entire
tree,
all
those
just
epics
or
just
issues.
Is
there
the
most
comfortable,
more
pattern
like
approach?
C
F
I
think,
like
a
really
simple
way,
to
make
sure
that
people
can
tell
the
difference
between
what's
an
issue
and
what's
in
epic,
although
I
mean
this
could
be
changing
the
entire,
the
entire
object
right
and
all
that
good
lab
is
right.
Now
we
show
the
title
first
and
then
the
reference
like
the
numeral,
whatever
first
used
him
the
ampersand,
whatever
fer
epics.
So
with
that
first
put
that
before
the
title,
and
then
you
have
a
clear
indicator
of
which
one's
their
epics
and
which
ones
are
issues
in
the
same
line.
Yeah.
B
C
You
might
help
here
so
there's
a
thing
that
probably
about
the
year
are
key.
So
if
you
change
sizes
you
can
make
epics
larger
and
the
issues
smaller
and
that
would
be
like
people
will
learn
that
all
the
time
but
I'll
leave
it
all
of
that.
Just
a
suggestions
for
Annabelle
she
will.
She
will
mail
it
for
sure.
I,
love.
A
All
these
suggestions
actually
I,
like
that
idea,
I
think
that's
that's
good
I
do
wish
that
we
had
a
little
more
visual
distinction.
I
don't
want
to
get
too
different,
so
I
don't
want
it
to
be
I.
Don't
want
to
look
too
different
from
unrelated
issues
and
everything
like
that
so
I
think
maybe
the
font
size
might
be
a
good
choice.
Obviously
we
can't
do
like
a
different
background,
color
or.
D
Yes,
so
next
my
so
we
basically
had
all
the
roadmap
scrolling
related
emerged,
merge
into
master.
There
was
additional
UX
polish
shimmer.
So
what
we
did
in
this,
mr,
was
we
get
get
rid
of
basically
that
loading
spinner,
that
he
would
see
when
the
roadmap
louis
and
instead
you
would
see
skeleton
loader,
so
there
won't
be
any
spinner
at
all.
You
would
see
a
scary
to
know
that
anti-mining
it
will
get
rendered,
and
once
we
have
the
data
we
would
enter
that
data,
so
that
was
submerged
as
well.
D
We
also
did
some
weeks
on
how
we
render
the
timeline
bars
when
we
fetch
for
when
we
fetch
new
data,
so
it
is
more
efficient
compared
to
what
we
had
written
so
yeah.
A
roadmap
scrolling
is
done
from
that.
I've
started
working
on
epic
sidebar
refactor,
so
basically
we
implemented
the
poor
shell
of
the
epics
refactored
app
and
that
was
merged
into
master
and
both
behind
each
of
like.
Finally,
we
are
getting
the
sidebar
done
as
well.
I'll
be
splitting
the
entire
effort
into
multiplied.
D
Mars
I
have
listed
all
the
parts
that
we'll
be
doing
it
in.
We
already
have
one.
Mr
open
and
the
more
will
be
followed
and
although
the
list
looks
longer,
but
I'm
keeping
all
the
mrs
very
tiny
so
that
it
is
fostered,
review
and
much
and
yeah
I'll,
basically
have
all
the
mrs
open
by
Tuesday
next
week
and
we'll
have
those
mods
and
another
quick
update,
is
I'll,
be
off
from
second
cup
to
15.
I
did
a
round
certain
link
all
on
Tuesday
but
yeah
I'm
getting
married
next
month.
So
much
efficiency,
yep
thanks.
B
D
B
B
I'm
doing
that
right
now
and
I
leave
a
comment
forever.
Whoever
reads
it
so
they
know
awesome
yeah
Congrats.
So
if
there's
no
more
things
to
talk
about
just
a
quick
note
from
the
group
conversation
yesterday
that
say
was
asking
about
adoption
and
that
pics
and
stuff
like
that,
so
I
just
wanted
to
share
that
issue
with
you
that
opened,
and
so
we
have
a
process
for
these
things
which
I
link
to
in
the
description
as
well.
B
So
my
general
thoughts
are
that
I
think
we're
pretty
close
to
to
getting
more
adoption
even
with
ultimate
and
that's
that's
how
I
would
prefer
to
be
like
not
not
changed,
but
you
know
these
things
are
certainly
above
my
paygrade
and
like
like
it's
not
something
that
I
lose
sleep
over
anyways.
So
but
my
suggestion
there
and
if
you
guys
care
you
can
you
know,
respond
and
so
forth.
B
My
suggestion
there
is
that
the
epic
object
itself
would
be
in
a
lower
tier,
a
more
advanced
as
we're
building
them
right
now
they
would
remain
in
the
ultimate
ear
and
so
I
said,
for
example,
the
romantic
view
should
remain
not
ultimate
tiered.
The
new
child
epics
functionality
should
remain
in
ultimate,
but
the
basic
epics
and
having
issues
attached
to
them
would
be
in
the
lower
tier
to
invoke
or
insight
some
adoption
good.
F
That
simple
option
is
actually
very
powerful
already
because
it
lets
you
have
all
the
issues
for
their
friend.
That's
right.
Like
my
last
job,
we
actually
won
when
github
started
having
epics,
you
can
only
have
them
from
one
project
that
and
we
thought
that
was
useless.
So
just
having
that
and
be
like
multiple
right.
B
So
folks
here
are
not
looking
at
the
road
map
you,
but
you
are
you
looking
at
epics,
I
hope
and
we
just
shipped
child
epic,
so
you
were
using
things
before
I
could,
but
we
expect
so
I'm
sure
that
feature
as
the
stands
alone
would
wouldn't
have
a
lot
of
usage,
so
bring
it
down.
One
tear
could
be
a
good
strategy,
so
just
wanted
to
share
that
with
you.
Folks,
as
you
folks
are
users
and
should
have
good
ideas
and
insight
into
that
as
well.
So
if
nothing
else,
we
can
continue
conversations.