►
From YouTube: Plan group weekly meeting
Description
Plan group weekly meeting for 2019-06-12
B
Sure,
yes,
as
I
wrote
in
slack
we're
going
to
try
something
a
little
different
as
far
as
issues
that
require
both
front
end
and
back
end
works
in
in
twelve
one.
If
a
front-end
engineer
takes
it
takes
an
issue
first,
then
the
front
end
engineer
should
kind
of
sketch
out
what
they
would
like
to
see
out
of
an
API.
So
it
involves
a
little
bit
more
thought
in
the
early
parts
of
the
issue
or
early
parts
of
development
of
the
issue,
but
and
then
same
same
for
the
back
end.
B
If
a
back-end
engineer
picks
it
up,
first
and
a
front-end
engineer
has
been
assigned
to
it
back,
an
engineer
will
kind
of
sketch
out
what
they
are
going
to
provide
to
the
the
front
end
we're
going
to
try
this
out
for
this
release.
It's
a
good
release
to
start,
because
we
have
a
few
issues
that
are
both
run
in
the
backend
I'm,
so
hopefully
we'll
be
able
to
get
some
some
data
on
on
whether
this
this
is
this
works
or
not.
Question.
Yes,
sorry.
A
Just
one
thing
I
wanted
to
add,
like
we're
not
saying
here
like
don't
like,
have
a
call
or
torch
people
on
slack
or
whatever.
This
is
really
for
the
case
where
one
person
speak
the
issue
up,
but
they
don't
know
who
the
back-end
engineer
or
who
the
front-end
engineer
picking
it
up
is
gonna,
be
once
you
know
who
your
counterpart
is
like
obviously
go
talk
to
them
like
collaborate
as
you
normally
would.
A
So
I
just
going
to
talk
again
briefly:
I
don't
want
to
preempt
things
too
much
because
I've
done
that
before,
but
hopefully
we
will
be
able
to
split
the
back-end
team.
Soon,
I
wrote
a
note
in
the
existing
issue
that
Victor
created
quite
a
while
ago
about
what
I
personally
care
about
here.
So
my
understanding
is
that
when
we
split
the
back-end
team,
we
will
also
split
the
front-end
team
and
everybody
who's
like
shared,
so
eric
Anabelle,
Alexis,
Val
Muir.
You
know
product
marketing
and
stuff
as
well
documentation.
A
A
D
So
while
we
are
splitting
the
team
based
on
team
planning
and
Enterprise
planning,
I
think
it
would
still
be
better
if
we
continue
doing
the
meetings
as
well
as
the
standup
combined,
because
chances
are
that,
if
they're
working
on
a
feature
which
overlaps
between
the
two
at
least
both
the
sub
teams,
would
still
be
aware
of.
What's
going
on
in
the
other
team,
yeah
yeah.
A
I
think
that
makes
sense
and
honestly
just
laziness
make
make
sense
as
well
like
if
we
just
keep.
If
we
just
keep
everything
shared
and
then
once
we
realize
that
sharing
things
doesn't
work
like
the
stand-ups
too
noisy.
The
meeting
like
people
are
saying.
Only
half
of
this
meeting
applies
to
me,
then
yeah,
that's
where
that's
where
we
split
like
I
would
rather
just
keep
doing
what
we're
doing
until
we
start
feeling
some
friction
from
it
and
then
reassess,
but
I'm
glad
that
everybody
seems
to
be
on
the
same
page
about
that.
A
D
Just
a
small
discussion
and
it
is
more
directed
towards
Annabeth's
so
well,
since
we
were
discussing
how
to
basically
do
the
pagination
for
epics
in
case
of
epics
tree,
because
right
now,
graph
queuing
only
allows
to
pull
in
100
items
at
once
when
first
request
is
made.
So
if
an
epic
contains
more
than
hundred
items,
you
would
need
some
way
of
lazy
load.
Additional
results.
I
discussed
this
with
Donald
earlier
today.
D
This
one
like,
if
we
want
to
add
an
additional
scrollbar
on
the
container
of
epics
tree,
that
would
make
rag
and
drop
within
the
pea
difficult,
because
we
won't
be
able
to
move
an
item
from
the
bottom
of
the
list
for
the
top
of
the
list.
If
there's
a
scrollbar
involved
and
if
we
don't
want
to
add
scroll
bar.
C
Think
having
just
the
long
page
no
extra
scroll
bar
is
the
way
to
go,
because
if
you
think
about
merge,
requests
right
now
ones
that
have
huge
amounts
of
comments
and
system
notes.
Those
things
are
already
so
long
and
then
you
go
to
an
another
tab
in
pipelines.
Is
this
small,
so
I
think
that's
fine.
D
E
Was
just
gonna
say
in
in
like
an
NMR
you
if
something
is
really
really
long
in
AD,
if
it
you
actually
have
to
like
click
to
expand
it,
so
we
actually
already
have
that
construct
in
an
NMR
I,
don't
know
if
that
makes
sense
here
so
like.
If
we,
if
we
know
there's
you
know
a
hundred
items
linked
to
an
epic
that
could
be
an
option
as
well.
It's
probably
a
great
option,
but
just
wanted
to
call
that
out.
We
do
that
for
long.
D
So
yeah
we
do
have
it
for
dips,
but
I
don't
see
how
that
would
be
useful
in
case
of
a
pigs
list,
because
what
happens
is
that
individual
items
within
the
epics
child
items
are
not
that
large.
So
what
happens?
Is
that
every
item
that
is
child
of
an
epic
beat
issue
or
an
epic
it's
just
like
15
or
20
pixels
of
height
and
in
case
it
contains
for
the
children.
We
already
show
that
exponent
button,
which
is
manual
so
that
user
would
have
to
first
click
on
that
and
load
additional
children.
D
But
as
far
as
the
direct
children
of
any
epic
is
concerned,
we
would
have
to
show
it
right
away.
So,
while
expanded
lifts
on
the
mr
works
there,
it
may
not
be
possible
to
do
it
here
and
what
we
can
do
in
case
of
lazy
loading
is
that
once
user
Scrolls,
the
page
all
the
way
to
the
bottom,
we
would
load
up
additional
items.
C
C
C
If
you
aren't
mentioned
on
something,
you
get
an
email,
but
there's
no
way
to
view
that
ain't
get
love
because
that's
separate
than
or
to
dues,
and
so
there
are
all
these
issues,
and
it's
already
been
research
done
on
on
these
there's
like
20
issues
and
currently
it's
scheduled
for
January,
2021
I,
think
that
was
kind
of
arbitrary,
maybe
just
sort
of
a
backlog,
kind
of
thing
that
Victor
did
a
while
back,
but
I
think
that
this
is
it's
becoming
a
pain
point
with
multiple
teams
that
I've
heard
so
I
would
like
to
start
doing
sort
of
some
product
discovery
and
in
general
UX
and
work
with
Alexis,
and
there
are
other
you
Xers
and
different
teams
that
want
to
help
out
with
this
too
and
I
wanted
to
know.
E
I,
don't
think
it
has
any
grounding
in
reality,
Anabelle.
So
absolutely
we
can.
We
can
pull
this
in
I
know
that
there's
been
a
lot
of
people
that
have
wanted
to
kind
of
see
like
the
Notification
Center,
see
everything
they're
subscribed
to
and
then
unsubscribe
to
things
and
kind
of
a
mess.
Does
that
does
this
epoch?
Have
that
as
well?
If
not
I
can
take
a
look,
it.
C
Might
I
haven't
had
a
chance
to
look
through
it
like
I
want
to,
but
there
are
two
epochs
so
I'll
I'll
link
to
both
of
them
when
I
attended
this
call
but
yeah
there
there's
just
a
lot
to
go
through
and
I.
Imagine
it's
gonna
be
a
pretty
big
effort
to
get
everything
sort
of
squared
away,
and
so
the
sooner
we
start
on
new
exit,
the
better
yeah.
E
This
is
a
this
is
a
really
nice
feature
that
github
has
is
the
ability
to
see
all
the
things
you're
notified
to
for
a
subscribe
to,
and
obviously
I'm
subscribed
to
them
so
in
general
I'm,
a
favor
of
this
I
personally,
don't
use
to
do's
and
that
bothers
me
a
little
bit
I,
don't
dog
food
it
at
all,
so
yeah
I!
But
let's
bike
into
this
together,
a
development
wind,
yeah.
A
I
think
this
is
a
really
great
idea.
I
just
want
to
call
out
that
I
used
to
do
all
the
time
like
for
everything
so
I
just
want
to
advocate
for
the
like,
whatever
we
do,
not
breaking
that
not
just
cuz
it's
me,
but
because,
like
you
know,
we
don't
want
to
break
existing
workflows
and
I've
got
like
25
that
wasn't
done
to
duce,
so
it
used
them
a
lot.
And
you
know
if
people
are
using
them,
then
we
should.
I
think,
the
the
general
outline
victor
had
in
that
epoch
sounds
good
to
me.
A
The
thing
you
were
talking
about,
Erik
I,
think
was
slightly
I.
Consider
it
slightly
different
and
I
think
it
might
be
part
of
the
other
epic
that
Annabelle's
talking
about
which
is
being
able
to
see
which
issues
you
are
a
participant
in.
So
if
we
want
to
show
you
which
issues
you
subscribe
to,
that's
super
easy,
but
also
not
very
useful,
because
most
people
don't
get
emails
by
subscribing
to
an
issue.
A
They
get
emails
because
they
were
commented
in
an
issue
or
they
were
mentioned
in
an
issue
and
figuring
out
which
issues
you
were
mentioned
in.
We
have
no
efficient
way
of
doing
that
at
the
moment
like
we
can
tell
you,
we
can
tell
reasonably
efficiently
who
was
mentioned
in
one
issue.
We
can't
tell
reasonably
efficiently
which
issues
was
Shawn
mentioned
in
so
that's
the
gap
we
need
to
fill
from
a
back
in
perspective.
That's
a
lot
of
work
to
get
to
that
point.
A
C
C
His
emails
he's
only
using
their
notifications,
which
is
really
the
goal
here,
because
I
used
to
do
this
as
well
and
then
I
get
the
emails
for
the
mentions
for
those
notifications-
and
it's
really
frustrating
I
know
some
people
only
used
to
do
is,
which
means
they
miss
out
on
notifications
free
to
threads,
and
you
know
it's
it's
it's
not
ideal,
but
I
think
but
I
liked
the
other
epic.
So
hopefully
those
will
both
cover
it.
Yeah.
A
A
Well,
the
other
one
like
like
I
said
I
think
is
slightly
different,
because
it's
about
it's
called
bulk
manage
issue
a
merge
request,
an
epic
subscription.
So
it's
more
focused
on
that
that
specific
feature
it
just.
It
needs
to
be
an
epic
because
of
the
amount
of
worked
involved,
I'm
trying
to
link
to
it
right
now,
but
some
my
laptop,
doesn't
work
well
when
I've
got
zoom
running
so
it'll
be
in
the
dark
in
a
second.
F
I
added
some
research
on
that
too.
We
have
a
little
bit
of
research
and
the
research
repo,
mostly
people
kind
of
like
we've,
been
saying
they're,
just
like
it's
too
noisy
it's
out
of
date,
and
they
don't
use
it.
They
just
use
slack
instead,
so
definitely
something
that
can
be
improved
and
sorry
I'm,
a
creepy
floaty
head
in
the
dark
today.
C
E
Yeah
I'm
happy
to
I
would
love
to
get
to
dues
to
a
place
where
they
work
for
me,
I,
don't
Sean,
I
actually
would
love
to.
Maybe
just
have
an
unfiltered
chat
with
you
so
that
you
could
like
walk
through
your
workflow
and
see
how
they
work
and
post
that
on
on
youtube,
because
it's
just
really
hard
for
me
to
tell
like
in
the
list
of
to
dues
right
now
which
each
of
the
issues
and
M
ours
actually
are
like.
E
It
just
says,
like
you
were
mentioned
in
issue
number
three
for
eight
seven,
nine
and
then
the
you
know
the
most
recent
comment
or
whatever
so
I
I,
don't
know.
I
would
love
to
actually
talk
to
you
about
that.
A
little
bit
more
and
it
made
me
animos
like
you
could
just
come
along
and
we
could.
We
could
figure
that
out
together,
so
cool
thanks.
E
E
All
right
looks
like
I
had
the
next
and
last
item,
so
I
had
a
little
listed
this
past
week
and
we
walked
through
the
product
category
page
and
she
kind
of
he
mentioned
a
few
things
that
he'd
like
to
see
changed.
Obviously,
josh
is
kind
of
serving
as
the
the
PM
of
scaling
where
he
sits
and
almost
of
skids
meetings,
and
you
know,
makes
em
ours
for
things
that
Sid
asked
him
to
spike
into
so
just
create
an
NMR
last
night
to
essentially
activate
on
what
said,
Sid
and
I
had
discussed,
which
is
changing.
E
The
plan
two
of
the
three
planning
group
names,
and
so
the
proposed
changes
in
that
M
are
the
summary
of
the
changes
that
team
planning
is
proposed
to
change
to
project
management
and
enterprise
planning
its
proposed
to
change
to
portfolio
management,
which
I
think
aligns
well
with
the
industry
and
kind
of
where
each
of
the
pieces
of
functionality
that
we
have
sit
in
each
other
groups.
You
know
issues
and,
and
boards
kind
of
fall
under
project
management,
ethics
and
roadmapping
falls
into
portfolio
management.
E
A
E
E
And
we're
not
necessarily
watching
on
to
program
management
right
now,
I
would
say
that
it's
not
it's
a
it's
a
role.
I,
don't
know
if
it's
like
a
thematic
category
of
the
work
that
we
do
I
think
project
portfolio
are
much
more
kind
of
bifurcated
in
terms
of
which
functionality
falls
into
each
piece
of
those
fergan
management.
I've
often
seen
as
a
synonym
for
portfolio
management,
it's
multiple
projects,
so
if
there
was
something
that
that
adhered,
you
like
the
program
management
philosophy
would
probably
fall
on
portfolio
management,
ya,.
A
Know
I
think
I
think
this
change
makes
sense,
because
it's
also
how
like
we
talked
about
things
and
I'm
product
marketing
like
john
who's,
not
on
this
cool,
like
you
know,
uses
these
terms
a
lot,
and
I
think
it's
quite
an
easy
way
for
people
to
think
about
things
as
well
like
typically,
if
it's,
if
it's
something
that
exists
at
a
group
level,
it's
probably
gonna
be
like
you
know.
If
it
only
exists
at
root
level,
it's
probably
gonna
be
portfolio
management.
It
exists,
project
level,
project,
management's,
the
name
like
that's
a
clue
yeah.