►
From YouTube: Magento PWA Backlog Grooming, 9 November 2018
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
We
talked
a
lot
about
ratings
and
others,
but
now's
a
great
time
for
folks
to
get
started,
especially
they
have
the
cycle
to
help
get
ahead
on
this
on
these
key
experiences
that
that
won't
be
for
they're
there
for
this
month,
but
that
will
certainly
be
there
shortly
afterwards
as
we
continue
to
release
out
to
the
public.
So
a
real,
quick
and
everybody
see
my
screen
yeah
excellent,
excellent.
A
All
right
well
welcome
to
grooming,
so
today
we're
going
to
cover
again
wishlist
we're
going
to
cover
ratings
and
then
we're
also
going
to
maybe
delve
into
either
carousel
or
tutorials
time
time
remaining
and
so
on
this
one
so
again
with
wishlist.
Let's
walk
through
this
pretty
quickly,
I
think
for
those
who've
been
following
quite
a
bit,
the
add
to
wishlist
functionality
has
been
there
from
the
get-go.
A
It's
been
a
static,
static
action
from
the
product
details
page
but
again,
based
on
their
based
on
where
we
want
to
hit
for
this
month
or
something
that
we
consciously
deferred
that
we
knew
we
could
fast
follow
with,
but
I
think
in
the
interest
of
making
this
a
very
short,
a
very
straightforward
story.
One
of
the
things
in
pre
grooming,
I,
thought
would
be
a
really
great
way
to
start
would
be
to
essentially
perform
the
action,
but
then
just
validated
on
the
back
end
right.
A
You
can
actually
start
to
see
the
wish
list
being
created,
open
source
first
I
think
if
we
start
to
look
at
commerce
and
EE,
it
gets
a
little
bit
more
complex.
But
let's
keep
this
small
and
start
to
see
what
can
happen
on
the
front
end
and
as
it
relates
to
the
back
end
and
of
course,
that's
going
to
pressure
test
the
api's
in
terms
of
what
can
be
done
when
see,
if
that's
possible,
with
some
of
the
new
community
graph
QL
work,
but
ultimately
create
experience.
A
That
would
then
bring
back
the
the
wishlist
here,
hopefully
in
a
couple
weeks,
I
look
at
some
level
of
validation,
which
is
something
to
think
about
letting
you
know
that
that
action
has
been
performed
and
then
again
just
for
the
sake
of
this
being
the
first
of
several
iterations
being
able
to
verify
those
verify
those
behind
the
scenes.
In
this
case,
our
friend,
Veronica
Steph
Costello
be
able
to
see
that
and
Steve
and
then
be
able
to
understand.
Yes,
that
is
this
had
made
that
change.
A
Future
stories,
of
course,
will
include
be
able
to
go
directly
into
my
account.
They
let
see
the
wish,
let's
be
able
to
manage
the
whistle
s
and
also
share
the
wish
list,
but
in
the
spirit
of
Natalie,
just
I
think
making
some
forward
progress,
but
also
carving.
This
up
to
do
a
couple
smaller
stories,
kind
of
one
at
a
time
share
being
its
own
account
will
probably
come
later,
because
we
will
want
to
take
a
look
at
some
more
complicated
product
details.
A
Scenarios
after
MVP,
like
bundled
and
in
virtual
as
well,
will
be
able
to
add
those
kind
of
all
in
kind
of
one
swoop.
But
look
at
this
in
very
small
pieces,
which
recently
have
gotten
some
good
uptake
on
the
community.
If
they're
one
or
two
pointers
in
some
cases
will
come
back,
you
know
will
come
back
in
the
morning
from
Austin
they're
done
and
checked
in,
and
that's
that's
great,
and
so
that's
the
spirit
of
this
one
again.
Super
super
straightforward.
There's
really
no
additionally
on
this,
but
this
is
the
kind
of
the
scenario
and.
B
A
Would
love
that
I
think
for
this
one
I
think
I.
If
we
can
get
this
done
before
that,
I
would
be
great
I
think
we
would
fast
follow
with
the
right
experience.
The
way
this
works
currently
in
then
yeah
you,
you
have
to
be
authenticated
right
and
so,
and
so
you
will
assume
that
you're
already
authenticated
in
this
and
the
stuff.
You
know
this
then
gets
you
into
a
fairly
different
experience
altogether,
which
I'm
quite
honestly,
I.
A
Think
if
you
given
you
the
time,
maybe
in
the
future
sprint
I,
would
love
to
reevaluate
that,
because
it's
a
bit
unnerving
to
kind
of
go
from
this
into
an
account
experience
altogether
versus
something
that
maybe
again
just
thinking
of
other
commerce
experiences
a
modal
or
something
that
a
little
bit
more
self
self-contained
versus
going
to
something
that
is
maybe
a
bit
overwhelming
for
that,
and
so
we
should
spend
a
lot
more
time.
I.
Think
thinking
through
that
more
detail,
but
I'm.
A
A
B
C
B
A
Please
yeah
I
did
a
placeholder
one,
just
to
kind
of
get
the
ball
rolling.
This
one's
really
gonna
be
more
of
a
test
of.
Can
this
be
done
and
what
needs
to
be
happened?
It
needs
to
happen
and
again,
you
know
part
of
the
task
could
very
well
be
to
identify.
You
know,
identify
coverage
and
graph
QL
or
others
as
part
of
the
process,
which
is
absolutely
fine.
That's
why
I've
kind
of
labeled
this
as
discovery
right,
let's
get
started
on
this.
A
So
with
that
in
mind,
any
are
there
any
questions,
any
any
comments
on
this
one
before
we
we
come
together
on
an
estimate.
A
Fully
well
understood
that
this
is
so
so
maybe
I've
made
this
so
small.
It's
just
you
know
incredibly,
incredibly
well
understood,
so
all
right,
well,
very
good!
Well,
let's,
let's
go
ahead
and
take
a
look
at
them
and
the
the
estimate
so
we'd
like
to
what
to
get
us
started
on
this
one
I.
F
I
was
muted.
This
is
a
for.
You
I
know
that
the
people
on
the
call
perhaps
cannot
answer
these
stories
definitely
are
for
future
release,
which
means
that
that
they
will
potentially
well
that
they'll
definitely
be
using
graph
QL
functionality,
that's
not
in
the
current
beliefs.
So
when
you
do
the
discovery,
you've
got
to
do
it
on
two
point:
three
develop
and
we
don't
really
have
this
concept
like
fully
articulated
in
our
documentation
and
I.
F
Think
we
should
I
think
there
should
a
be
a
label
for
two
points
we
develop
or,
for
you
know
two
point
three
point,
one
candidate
or
whatever
and
and
I
think
that
we
need
to
provision
cloud
that
is
specifically
for
like
canary
and
that's
something
we'll
talk
to
them
about,
but
for
you
guys,
like
it
bar
green,
you
know
that
there's
like
the
one
instance
that
you
definitely
work
on.
That
is
two
point.
Three
point,
oh
release.
F
F
That's
the
thing
is
that
you
know
we
all
kind
of
did
away
with
it,
because
we
were
like.
We
got
a
schema
for
this.
Now
we
we
now
have
to
have
a
distinct
notion
of
everyone
should
be
able
to
switch
between
I'm
working
on
stuff
for
the
current
branch
or
a
hotfix
for
the
current
branch
and
or
I'm
working
on
stuff
for
the
the
edge
version
because
like
if
you
look
two
point
three
develop
has
way
more
graph
QL
in
it.
F
It's
super
cool,
actually
I
mean
I,
don't
know
how
much
of
it
works,
but
the
schema
is
much
larger.
So
so,
when
you
do
discovery
on
this
like
that,
will
lend
itself
very
much
to
estimation.
So
I
want
to
say,
let's,
because
this
is
a
relatively
new
workflow
for
all
of
us.
I
want
to
add
a
couple
points
to
this
story,
just
on
that
basis
alone,
so
so
I'm
just
throwing
that
out
there.
My
estimation
is
close
to
Jimi's
I
would
call
it
a
five
or
an
eight
depending
yeah.
E
A
A
We're
going
to
mark
this
one
to
you
cool,
let's
take
a
look
at.
Why
kind
of
are
on
the
mindset
of
pushing
the
graph
you
all
coverage,
I'm
gonna
call
a
little
bit
of
an
audible
here
in
let's
talk
about
rating.
This
may
be
something
that
still
blocked
to
date.
I
want
to
you
know:
I
want
to
stress
this
on
as
well
what
they,
the
fact
that
UX
is
still
probably
gonna,
be
in
development.
On
this
one.
A
We've
had
some
initial
thinking
on
the
showing
ratings
in
the
past,
which
I
think
is
a
good
starting
point,
but
I
think
we're
we
were
we
hit
a
roadblock
in
the
past
was
the
availability
of
the
API
coverage
initially,
which
I
believe
and
maybe
there's
someone
in
the
car
can
help,
as
I
believe
is
opened
up
with
crafty
well
recently,
so
I'm
not
entirely
sure.
If
that's
the
case,
this
opens
up
to
new
possibilities
after
MVP.
Right
again,
this
is
a
discovery.
A
Work
to
see
what's
possible,
I
think
we
take
a
look
at
something
that
is
in
flight.
That
is
that
again,
it
could
be
roughed
out
to
be
fairly
close
to
what
we
see
here
on
the
on
the
category
page,
but
then
would
be
representative
of
live
data,
and
so
this
would
just
be
the
presentation
of
that
information
and
the
the
usage
of
hopefully
brought
you
all
that's
available
and
then,
then,
with
that
I
will
set
up
some.
A
You
know
following
stories
on,
of
course,
you
know
contributing
to
a
rating
and
managing
a
rating,
all
that
which
at
which
I
think
will
kind
of
nice
nice
to
have
once
this
has
been
established,
but
that,
but
that's
that's
the
spirit
of
this
one
again,
taking
something
that
we
we
hit
a
bit
of
a
block
on
the
on
the
API
over
for
there's
been
a
lot
of
progress
and
graph
QL
and
again
as
a
shopper,
you
want
to
be
able
to
view
product
ratings.
We
think
this
is
gonna,
be
a
really
important.
A
One
fast
fall
in
the
MVP
release.
This
is
exposed
in
so
many
places
categories.
This
one
example,
you
know
we
do
have
it
of
course,
and
want
to
have
it
on
product
details
and
others
and
again,
prior
to
our
discussion,
that
you
know,
we've
got
some
assumptions
here
on
part
of
those
discoveries
to
determine
that
coverage,
see
which
way
it's
gonna
go.
F
Enables
perhaps
the
integration
of
a
service
and
a
lighter
way,
I
mean
it
when
you
sort
by
rating
I?
Think
probably
Magento
needs
to
have
that
information,
so
we
probably
don't
probably
shouldn't
mess
with
it,
but
just
the
fact
remains
that
any
ratings
third-party
that
handles
review
stuff
if
they
have
a
graph
QL
API,
we
can
sort
of
stitch
those
schemas
and
navigate
them
as
a
single
as
a
single
thing.
F
A
F
A
C
A
F
A
E
E
A
Thank
you.
Everybody
we'll
move
that
over
to
ready
to
start
again.
This
is
a
little
bit
more
ambiguous
than
others,
but
in
the
spirit
of
the
folks,
can
take
a
look
at
this
in
parallel.
So
while
we
yeah
bring
bring
bring
this
home,
I
think
this
would
be
really
good,
really
good.
Work
for
us
so
register
its
update
and
sorted,
but.
A
You
go
hey,
maybe
even
I
can
do
this.
No,
not
so
much
so!
Let's,
let's
talk.
Let's
talk
through.
Let's
see
our
dealer's
choice
that
tutorials
or
the
image
indicator
bridge,
let's
go
through
tutorial,
so
this
is
I
was
reluctant
to
go
on
this
one,
but
what
I?
What
I
like
about
this
is
the
spirit
of
what
we're
trying
to
do
around
MCP
and
so
talking
to
mr.
Calculon
on
this
one.
A
You
know:
we've
got
a
lot
of
documentation
ahead
of
us
as
we
look
to
enable
and
get
ready
for
the
MVP,
and
so
this
would
be
a
bit
of
a
non-traditional
grooming,
but
I
want
to
get
the
what
I
get
the
input
from
from
this
group
here
on
what
would
be
a
useful
set
of
tutorials
going
into
some
of
the
how-to
around
the
studio
and
so
by.
You
know,
by
all
stretches
of
the
data
that
we're
seeing
on
PW
studio
io
setting
up
the
venue.
A
Storefront
is
the
number
one
it's
if
you
look
at
in
the
heat
map,
it
looks
like
everybody's
just
looking
right
at
that
and
then
they're
going
to
the
rest
as
they
as
they
learn.
But
if
you
compare
this
to
other
contents,
that
we
do,
you
know
that
we
do
and
make
available
for
free
and,
let's
say
like
an
Magento,
you
we're
kind
of
going
through.
Step-By-Step
instructions.
A
A
This
alone
is
likely
an
epic
and
it's
your
own
right,
but
I,
but
I
wanted
to
use
this,
especially
with
this
audience
here,
as
it
means
to
talk
to
and
maybe
even
prioritize
a
discussion
on
what
what
might
be
important
here
and
I.
Think,
as
we
look
at
this,
you
know
you
know.
We
would
then
turn
this
in
together
individual
stories
or
or
make
this
a
reasonable
story
that
that
James
can
take
a
look
at
with,
with
the
team's
input
to
start
looking
at
what
some
of
that
basic
concept
might
be.
A
So
again,
it's
very
topical
in
terms
of
our
kind
of
our
last
strides
here
towards
MVP.
You
know
we
are,
of
course
partnering.
That's
agenda,
you
and
others
on
this,
but
we
do
I
think
it
would
be
irresponsible
for
us
not
to
have
at
least
an
example
or
two
on
how
to
make
some
some
basic
changes
here,
based
on
all
the
great
overview
that
we've
got.
Some
of
the
architectural
work
we've
got
and
then,
of
course,
set
up
a
configuration.
A
So
that's
that
so
this
one
is
again
beginning
to
the
discussion.
Let
me
just
kind
of
read
you
through
some
initial
thoughts
here,
based
on
existing
materials
and
so
I
think
we
can
link
to
the
overview
of
PDA
which
exists.
I
do
want
to
link
out
to
relevant
developer
tools
where
it
makes
sense
on
things
like
lighthouse
and
others.
We
do
a
good
job
of
that
kind
of
showing
what
the
browser
is
capable
of
in
the
front-end
training
web
pack
I
think
we
can
curate
what
might
be
relevant
for
people
to
learn
about
web
packs.
A
Same
could
probably
be
said
about
react.
A
basic
exercise,
so
Zeppelin
has
done
a
has
done.
You
know
some
small
color
changes,
some
image
changes
in
the
past
in
demos.
That's
a
nice
way
to
at
least
start
to
feel
comfortable
where
somebody
can
make
a
change
and
makeup
make
and
still
update
the
build
and
see
how
that
goes,
build
on
to
play
updates.
That
might
be
a
result
of
that
and
then,
of
course
again
just
linking
to
related
concept.
We're
not
reinventing
a
lot
here,
we're
packaging
and
curating
that,
and
so
I
think
this.
A
You
know
if
you
look
at
this
as
one
place
where
we
can
link
to
other
places
that
still
allow
you
to
create
your
first
or
make
your
first
change
to
venya.
This
would
be
a
great
piece,
and
so
your
assumptions,
of
course,
that
hopefully
you
know
what
pedo
a
is
what
and
when
and
and
how
that
works.
Some
basic
knowledge
of
front-end
technologists,
we're
not
going
to
teach
you
react
here.
A
We
might
give
you
a
good
good
link
or
two
to
get
started
in
this,
and,
of
course,
so
it's
a
working
knowledge
of
magenta
too
and
I
say
that,
based
on
the
the
dependencies
and
the
understandings
that
we
you'll
you'll
want
to
have
around
how
the
api's
work,
at
the
very
least
maybe
linking
to
some
of
the
new
rest,
api
and
graphic.
You
welcome
documentation.
That's
out
there
as
people,
people
start
to
work
with
it
and
just
one
task
testing
a
documentation.
So
so
that's
that.
A
F
A
F
Help
but
think
about
the
deltas
in
project
set
up
that
I
want
to
close,
but
so
I'm
just
going
to
say
them
and
then
try
to
put
them
aside
one.
One
certainly
is
that
we
need
proper
scaffolding
rather
than
hey
clone.
The
whole
thing.
Yeah
and
I
know
that
you
know
we
have
to
have
a
discovery
story
for
that.
That's
not
2.3,
but
but
it's
hard
for
me
to
conceive
of
a
reasonable
guide
that
starts
with
clone
this
giant
git
repository,
so
we
need
to
have
scaffolding,
and
secondly,
this
is
more
of
a
quality
thing.
F
Out-Of-The-Box
there's
a
lot
that
works.
Great
we've
done
some
weird
stuff,
and
so
we
need
maybe
to
write
the
code
that
that
makes
hot
module
replacement
sort
of
maximally
good
like
we
need
discovery
on
adding
react,
hot
loader
on
making
sure
that
the
graph
QL
does
HMR
etc.
So
those
are
just
two
stories
but
separately
from
that.
I
would
say
that
the
very
first
like
developer,
tutorial
thing
that
we
would
want
would
be
to
introduce
the
Magento
developer,
who,
let's
face
it.
F
The
big
difference
is
that
when
we
introduced
composer,
we
used
only
like
the
package
installation
aspect
of
composer
like
nothing
else
in
cloud
we're
starting
to
use
other
things,
but
we
use
nothing
else,
NPM
we're
using
scripts
and
were
sort
of
running
our
package
life
cycles
through
that
and
we're
using
awareness,
so
I
would
say.
The
first
thing
to
do
is
to
introduce
here's
what
to
do
with
an
NPM
project.
Here's
what
happens
when
you
install
ours,
here's
the
sort
of
the
life
cycle
of
it,
and
when
you
are
in
working
mode,
you
know.
E
C
E
A
E
E
E
You
know
because
having
a
mixture
of
input
here
from
you
know,
folks
who
are
more
like
zetlen
myself,
you
know
who
have
a
lot
of
experience
with
all
these
technologies,
but
just
want
to
talk
about
the
idiosyncrasies
of
this
project
versus
you
know.
I
see
we
have
a
Karl
Haas
on
the
on
the
project,
who's
diving
into
not
only
all
this,
but
also
react,
you
know,
and
so
you
know
people
like
that
will
have
a
completely
different
perspective
on
stuff.
That
would
definitely
need
to
be
in
this
kind
of
guide,
yep.
A
Perfect,
alright,
well
about
what
hey?
Thank
you
so
much.
Everybody
I
appreciate
it
again.
Apologies
again
that
was
a
bit
shorter
than
usual,
but,
as
always
always
appreciate
your
time.
Your
perspective,
your
estimates,
of
course,
and
all
of
your
energy
for
this
project,
we're
on
the
home
stretch
for
the
MVP
and
we
we
could
not
be.
We
cannot
be
where
we
are
without
you,
and
so,
as
always,
we
have
any
questions.
Comments
concerns,
let
us
know
otherwise.
I
have
a
great
rest
of
your
day
and
have
a
great
weekend.
Okay,
thanks.