►
From YouTube: Magento PWA Backlog Grooming, 19 October 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
So
again,
not
the
you
know
not
the
biggest
moment
today,
but
I
really
want
to
put
a
couple
small
ones
in
here,
as
our
contribution
has
actually
increased
quite
a
bit
I'm
looking
at
the
reports-
and
we
had
five
PRS
outside
of
Magento
this
week
and
and
and
roughly
I
would
say
roughly
twice
as
many
contributors
in
the
past
30
days
that
we
did
before
so
all
signs
point
to
that
and
we
keep
getting
more
requests
so
kind
of
walking
through
the
story
itself
fairly.
Straightforward
to
the
shopper
I
want
to
know.
A
If
my
shopping
cart
is
getting
done
yet
so
they
can
continue
shopping
assumptions.
Assumptions
are
that
you'll
be
using
the
the
checkout
that
we've
already
created.
You
can
get
that
today
at
github,
then
that
you
have
awareness
of
the
the
empty
checkout
scenario.
So
it's
you
know
it
has
to
be
situation
already.
Haven't
added
something
tasks
here:
very
straightforward:
implement
there
are
no
items.
There
are
no
item
screen
in
the
checkout,
so
that's
insomnia,
there's
a
link
to
the
prototype
at
the
top
and,
of
course,
testing
and
documentation
as
well.
A
So
we
put
a
link
into
the
the
boilerplate
links
to
the
boilerplate,
a
link
from
out
from
James
on
this
one
on
what
that's
worth
looks
like.
So
hopefully
this
is
very
straightforward,
but
it's
a
good
one
for
those
who
are
just
joining
the
project
and
but
but
want
to
get
everybody
to
take
on
this
and,
first
of
all,
we'll
start
off
with
any
questions.
Any
any
questions
on
this
one.
Any
any
comment.
C
C
D
A
Would
I
would
think
so
if
this
is
one
of
kind
of
our
ethics
or
master
stories,
but
for
that
for
device
and
browser
requirement
that
I
would
defer
to
kind
of
our
master
requirements
for
that
one.
So
I
I
think
we
would
assume
that
the
need
for
this
would
be
no
different
than
what
we've
typically
done
for
that.
A
A
Perfect,
all
right,
so
let's
go
ahead
and
get
to
I
get
two
estimates
on
this
one
again.
This
one
should
be
pretty
straightforward
and
so
Allah,
just
because
of
the
simplicity
of
one
I'd
like
to
think
this
is
probably
a
one
can.
Can
anybody
make
a
case
for
this
being
any
more
than
a
one
from
an
estimate
standpoint.
A
All
right,
I'm
gonna,
keep
this
as
a
1
again.
This
is
really
just
a
means
for
us
to
kind
of
get
started.
I
think
this
one's
pretty
straightforward.
Does
this
value
would
be
that
you
have
more
context
and
you
have
an
SD
card
and
I
think
what
I'd
like
to
do
is
also
offer
this
one
up
for
for
help
needed
so
and
Help
Wanted.
So
for
someone
who
is
new
to
the
project,
okay,
we've
had
quite
a
few
contributions
this
week.
A
So
for
those
who
familiar
with
that
with
a
category
page,
so
one
of
the
one
of
the
key
features
on
this
one
is
sorts,
will
cover
filtering
second,
and
so
the
ID
here
is
two
so
again
as
a
hold
on
just
a
second.
So
the
shopper
I
want
to
be
able
to
filter
and
sort
products
within
the
category,
so
that
I
can
make
a
and
inform
purchase
on
again.
So
this
is
the
design
from
Samuel.
A
That
was
more
of
a
concept
because
we
don't
have
the
other
ratings
API
available
for
this,
and
then
both
ascending
and
descending
sort
order
for
that
one.
So
so
again,
the
creation
of
this
creation
of
this
slider
this
panel,
that
comes
up
people
to
make
a
choice
and
then
from
there,
of
course,
as
with
any
sort,
you
would
be
able
to
see
the
the
related
items
as
a
result.
So
the
assumptions
themselves,
of
course,
must
have
a
working
category
page.
A
That
should
be
straight
org
and
again,
I
did
mention
the
other
ratings,
not
quite
over
than
GP.
If
you
happen
to
have
to
happen
to
be
interest
in
that,
and
people
upgrade,
but
we're
not
expecting
ratings
idolo
on
this
one.
That's
that's
not
part
of
that
VP
and
then
the
tactics
themselves
is
really
again
for
especially
new
people.
New
to
the
project,
there's
gonna
be
some
discovery.
Work
on
the
graph,
you
oughta
rest
API
coverage
for
products
and
category
there's
the
implementation
of
the
panel
with
basic
options.
A
I
would
say
if,
if
it's
easier
to
do
one
or
two
of
these
first
and
then
iterate
and
do
the
other,
the
other
remaining
five
to
six,
then
I
think
that's
fine
and,
of
course,
testing
and
documentation.
That
will
be
something
that
that'll
be
something
that
we
would.
Of
course,
link
out
to
and
want
to
make
sure
that
that's
covered
with
mr.
Callen
no,
but
that
sort
so
any
any
any
questions
or
comments
on
this
one.
E
E
A
Yeah-
and
that
would
be
part
of
the
discovery
again
without
having
James
here
necessarily
I,
can't
say
the
extent
of
where
that
coverage
would
be,
but
I
think
was
just
like
anything
else.
We
have
with
graph
QL
and
rest
API
coverage
there'll
be
some
level
of
discovery
on
what's
covered
and
what's
not
from
the
sensor,
this
I
think
we've
got
pretty
decent
coverage
clearly
with
ratings.
We
don't
but
I
think
as
part
of
that
I
think.
A
F
A
F
Blue
jeans,
clients,
updated
itself,
I,
don't
know,
I
always
have
some
problem
anyway.
I
was
I
was
trying
to
respond
to
your
oh
and
yes,
because
you
were
always
sorting
against
the
entire
collection.
Then
you're
not
gonna
sort
the
window,
products
that
are
in
memory,
so
yeah
Eric
of
course,
is
correct.
This
is
all
whatever
supported
by
the
graphical
idea.
F
A
Your
question
any
other
anything
else
on
that:
one
that
you
wanted
to
I
wanted
to
call
off,
but.
A
A
All
right
we're
efficient
today,
folks
so
estimate.
So
let's
go
ahead
and
talk
about
this
and
again
this
one
I'm
a
little
less
clear
on
this
one.
I,
don't
think
it's
the
one!
Let
me
just
throw
that
one
out
there.
So
what
are
we
thinking
in
terms
of
an
estimate
to
implement
that
we'd
like
to
get
it
started?.
G
And
the
reason
is
that
we
feel
like
we
haven't
done
the
discovery
for
graph
QL,
but
I,
know
graph.
Ql
has
sort
of
stuff
built
in
so
I
feel
like
a
lot
of
the
work
is
just
kind
of
done
by
graph
two
well
and
that's
just
a
matter
of
building
out
these
components,
and
you
know
using
storybook
and
testing
and
stuff.
It
seems
like
most
of
the
work
with
this
yeah.
A
G
A
Yeah
I
think
the
three
makes
sense
I.
You
know
I'm
always
a
little
bit
conservative
them
on
this
one,
especially
if
someone
else
someone
else
fix
this
stuff.
I
know
a
bar
green
three
lately
may
be
different
than
others
for
that
one.
So
if
there's,
if
there's
any
any
kind
of
traps
and
discovery
for
someone
who's
less
familiar,
I
can
be
a
little
bit
more
conservative,
but
again
I
can
also
be
convinced,
convinced
as
well.
I
personally
would
rather
see
this
as
a
three
or
five
three
versus
a
five,
but
what
does
they
all
think?
A
F
I
have
a
general
rule
that
if
there
is
a
new
UX
primitive
that
has
not
yet
been
created,
one
that
would
belong
to
pair,
for
instance,
that's
I
would
add
a
sum
amount
to
the
story
if
you've
already
taken
that
into
consideration
in
folks
at
bargaining,
then
sure.
But
let's
take
another
quick
look
at
the
mom
or
the
sorry.
G
F
Okay,
well,
the
the
you
can
look,
certainly
in
your
own
graphical
explorer
or
you
can
look
at
the
schema
to
see
that
there
is
a
large
number
of
sorting
options
for
product
collections.
I,
don't
know
how!
Well
they
all
work
necessarily
but
they're
everything
that
I
see
there.
We've
got
price
we've
got
name,
but
I
don't
see
that
it's
certainly
not
in
the
venire
data.
F
F
The
concern
that
I
have
that
you
may
run
into
is
that
I
don't
believe
that
these
products
sort
input
options
are
settable
easily
via
variable,
so
you
may
end
up
having
to
have
multiple
queries,
which
is
terrible,
but
but
you
could
probably
implement
in
implement
them
as
query
that
pulls
in
a
fragment.
That
is
the
entirety
of
the
the
category
query
and
then
create
a
bunch
of
queries
for
the
difference
options
that
maybe
what
you
have
to
do
at
this
stage.
If
you
have
any
questions
about
it,
you
can
consult
me.
G
F
A
Feel
like
Larry
had
so
maybe
we
consider
this
the
five
any
objections
to
five
before
it
closes
out
them
all
right
this
one's
grooming.
So
let's
go
and
move
this
over
to
ready
to
start
nothing
to
get
shape
on
that.
Thank
you.
Everybody!
Next
one's
gonna
be
very
familiar
and
very
similar
in
so
we're
gonna
do
we're
gonna
do
filtering,
so
we're
gonna
carry
over
a
couple
of
the
assumptions
we
just
talked
about,
so
this
one's
distance,
hot
off
the
press
and
so
stock.
A
To
saw
me
last
night
and
we've
got
some
additions
here
on
filtering
guys,
so
this
is
again
similar
to
similar
to
sorting
in
that
it's
initiated
from
the
filter
action
on
the
category
page
itself,
but
you're
presented
with
several
different
options.
Of
course
we're
assuming
these
options
themselves
are
going
to
be
sample
data-driven.
So
these
aren't
necessarily
a
stack,
but
these
would
then
present
themselves
into
a
series
of
options.
Sides
going
to
be
a
little
bit
more
straightforward.
Color
is
going
to
ideally
produce
a
swatch
which
I
know.
A
A
I
would
expect
then
the
the
sorting
one,
but
it
could
be
an
important
one
for
us
to
what
to
take
a
look
at,
especially
with
the
larger
catalog
sizes,
where
you
want
to
kind
of
quickly
bring
down
some
of
the
bring
down
some
of
the
choices
you'll
make
as
you're
as
you're
in
the
middle
DEP,
Browse
functionality.
And
so
that's
a
preview
of
things
on
the
link
for
the
prototype
will
be
coming
shortly.
We're
having
some
indigenous
use
on
the
sink
for
that
one,
but
there's
a
likely
be
coming
in
on
Monday.
A
But
then
the
type
of
mechanisms
were
talking
about
which
are
traditional
choices,
but
for
color
we're
looking
for
something
a
little
bit
more
interesting.
Quite
honestly,
I
actually
think
the
the
clearing
is
more
important
than
the
the
swatches,
but
we
can
certainly
talk
about
that,
at
least
as
we
as
we
look
to
iterate
this.
So
the
story
itself
is
again
as
a
shopper
want
to
filter
and
sort
products
within
a
categories
they
can
make
it
purchase
online.
A
It
is,
of
course,
dependent
on
a
category
page
is
done
the
ability
to
retrieve
products
by
category
which
will
be
simple,
some
discovery
there
and
then
readings
which
are
not
part
of
NPP
which
which
wouldn't
be
because
we
don't
have
the
sample
data,
of
course,
for
ratings
in
that
in
that
sense,
and
so
tasks
are
very
similar
to
as
to
what
we've
got
here
on
the
on
the
on
the
sorting.
So
there
will
be
some
discovery
work
in
terms
of
the
graph
QL
rest
API
coverage.
A
Of
course,
there's
the
implementation
of
the
panel
I
could
be
convinced
that
we
would
split
this
and
look
at
this
a
little
bit
more
iteratively
I'm.
Ok
with
that
for
that,
and
then,
of
course,
testing
and
documentation
as
well,
and
so
there's
a
bit
of
a
lag
with
with
enzyme
this
morning.
Any
questions
on
this
one
I
am
going
to
add
some
of
the
assumptions
from
before,
but
but
as
I
as
I
typed.
These
out
any
questions
or
comment
on
this
particular
story
for
filtering.
E
A
F
F
You
know,
I
mean
if,
for
instance,
there's
duplicate
work
being
done
to
create
like
the
again
the
UX
primitives
for
the
selector
or
whatever.
Then
we
should
just
kind
of
call
that
out
in
the
slack,
Channel
and
and
the
those
who
have
taken
on
these
stories
should
be
in
communication.
I
would
trust
them
to
do
that.
It
also
bears
mentioning
that
for
both
filtering
and
sorting
the
same
concern
about
graph
QL
queries
holds
true.
E
A
E
A
F
I
guess
things
like
that:
good
catch
things
like
that
seem
to
require,
like
Rowan's,
suggesting
that
we
make
these
stories
dependent
on
one
another
rather
than
making
them
the
same
story,
which
I
think
would
expand
their
size
in
a
way
that
makes
it
harder
to
continue.
Let's
just
make
one
block
the
other.
A
Again,
I
I'm,
not
not
the
the
same
level
of
detail
on
the
API
front.
Unless
and
it
feels
like,
we
could
probably
do
sorting
first
and
then
come
back
around
the
filtering,
but
then,
when
you
do
filtering
filtering
gets
trickier
with
the
existence
of
sort.
I
could
be,
I
could
be
wrong
there,
but
I.
If
that's.
If
that
is
the
case,
we
can
then
make
make
that
a
dependency
or
formerly
in
github.
How
does
that
sound.
H
A
A
Demanded
somebody
from
you
know
if
somebody
from
community
picked
it
up.
That
would
be
something
that
would
be
great.
This
could
be
done
independently
of
what
we're
doing.
Somebody
picks
it
up
a
community
that
would
be
part
of
next
month's
release.
I
would
argue,
probably
a
higher
for
organization
for
some
of
the
other
things
that
we're
doing
internally.
A
B
A
B
A
A
A
A
B
A
A
A
A
Dimitri
we're
hearing
some
background
noise
from
you
guys.
Can
you
can
you
ask
those
artemiy
please.
H
G
A
G
Please
go
ahead.
Sorry
I
was
just
saying
in
addition,
like
the
new
you
I,
like
the
Clear
button:
oh
no
I'm,
just
adding
in
board
storybook
elements
like
that.
If
we
want
to
make
them
these,
you
know
generic
components
that
can
be
reused.
Everything
that
always
seems
to
take.
You
know
a
substantial
amount
of
extra
time
when
you're,
adding
in
new
UI
components
and
then
the
drop-down
lists
and
stuff.
A
Again,
just
you
know,
as
the
story
gets
picked
up,
if
we
find
a
case
where
we
want
to
split
this
one,
especially
if
we
feel
like
we
can
do
part
of
this,
but
not
the
rest.
I
think
that's
fair
game
for
this
one.
So
we
can
reevaluate
that
one
at
the
sign,
but
I
I,
agree
with
you.
That's
a
new.
You
know
that's
a
new
control
right
there,
that's
that
we've
introduced
and
so
between
the
creation
of
that,
but
then
also
what
we
want
to
do
to
potentially
bring
that
into.
A
A
All
right,
so,
let's,
let's
talk
about
wait.
Let
me
check
time
here,
so
we
win
through
the
ones
that
we
we've
given
it
to
look
at
some
interesting
ones
here
and
so
I
want
to
talk
about
so
something's,
not
Tommy,
I
talked
about.
Is
we
want
to
bridge
the
gap
with
some
of
the
the
period
basics
that
we
know
we've
explored.
We've
actually
done
some
work
in
the
past
on
this
one,
but
starting
to
introduce
the
idea
of
the
manifest
of
things
which
should
be
straightforward
and
in
the
universal.
A
But
I
do
want
to
talk
about
that
as
a
team,
because
for
us
to
hit
MVP
we're
going
to
want
to
have
the
basics
of
this
one,
which
is
much
more
than
a
capability
and
and
really
more
of
a
basic
requirement
if
anyone
wants
to
consume
the
studio
on
this
one.
So
so
this
one
is
so
this
wasn't
again
not
announced,
but
this
one
is
the
the
add
to
home,
with
the
capabilities
of
web
app,
manifest
and
so
by
nature
of
some
of
the
libraries
that
we're
using
the
idea
here
is
again
to
universally
allow.
A
So
I
didn't
work
out
the
details
with.
What's
got
me
on
this
one?
We
do
have
the
iconography,
both
the
192
and
the
5-12
sizes
on
this
one
as
well,
and
then
this
one
would
require
some
some
basic
discovery
on
the
manifest
X
from
Google,
which
I
get
pretty
straightforward.
I
was
able
to
look
at
a
couple
generators
and
create
one
myself,
I
think
it's
just
going
to
need
a
little
bit
of
help
from
James
and
others
I'm
kind
of
understanding.
A
You
know
what
are
the
right
parameters
inside
of
this
and,
of
course,
finding
the
right
way
to
implement
this,
that
the
idea,
we're
starting
off
with
a
single
page
home
page,
is
probably
a
good
good
candidate
for
that
verifying
that
and
lighthouse
would
probably
be
the
test
and
then
looking
at
this
global
across
all
the
basic
pages
home
page
category,
product,
details,
etc,
and
you
get
to
correct
me
if
I'm
wrong,
but
we've
got
all
the
assets
here
again.
These
are
the
you
know.
These
are
the
the
icons
that
we
need
from
here.
A
Straight
org,
one
now
that
we've
got
the
the
basics
of
the
check
out
experience,
but
we're
going
to
want
to
have
this
one
for
MVP
and
I
just
want
to
bring
this
up
for
grooming,
and
this
is
just
the
addition
of
the
manifest,
but
from
a
business
standpoint
the
ability
to
to
add
something
to
a
home
screen
to
be
prompted
by
by
whatever
the
browser
browser
defaults
might
be.
For
that.
So.
F
Yeah,
so
I
can
say
that
we
have
most
of
the
infrastructure
in
place
to
make
this
fairly
quick,
because
we
have
already
incorporated
a
work
box
into
the
serviceworker
plugin
and
work
box
will
provide
most
of
this
functionality
out
of
the
box,
so
to
speak.
Rowen
can
attest
that
we've
footwork
box
behind
us
a
little
abstraction
just
for
our
own
benefit,
so
that
we
can
later
automates
and
things
or
provide
some
sensible
defaults.
F
E
Yeah
the
the
comments
I
would
have
on
this
are
the
the
the
actual
creation
of
the
manifest
is
super
simple
that
that
should
take
like
an
hour
for
someone
to
pull
that
together.
The
harder
bits
in
here
are
one
configuring,
the
serviceworker,
because
the
key
thing
that
you
need
is
to
be
able
to
provide
a
200
response
when
you're
offline,
so
I
potentially,
would
consider
not
actually
that
can
be
part
of
the
same
story
because
doing
the
manifest
is
so
small.
E
The
second
aspect
of
this
is
also
just
capturing
the
ad
homescreen
prompt
on
the
pages
and
just
having
some
decisions
about
where
you
want
that
prompt
to
appear,
though
it
would
be
fine
to
automatically
show
the
ad
home
screen
prompts
on
the
home
page,
but
your
se
not
going
to
want
to
show
ads
green
part
way
through
the
checkout
process.
For
example,
right.
A
Some
discovery
there
and
then
we're
on
yeah
I
think
it's
a
great
point
on
the
offline
experience
again.
Without
you
know,
one
of
my
assumptions
is
that
we
could
could
theoretically
break
out
the
the
200
response
into
a
separate
story.
So
you'll
see
here
in
gray
Laureates
before
I
hit
save
here,
is
that
we
we
could
use
this
blocker
to
create
that
offline
experience
and
kind
of
do
two
stories
in
one
where
you
we
do.
The
discovery
set
this
up
and
then
potentially
demo
these
books
together
for
that,
but
I'm
happy
to
combine
these.
E
E
F
We
have
an
open
request
to
kind
of
settle
that
with
dead
cert
I
thought.
Let
me
take
a
look
but
yeah
it's
supposed
to
trust
and
the
way
that
dev
cert
works,
which
is
what's
underlying
PWA
def
servers.
It's
a
little
utility
that
creates
a
root
certificate
and
asks
your
system
to
trust
it
and,
depending
on
what
operating
system
you're
running,
it
uses
different
techniques
to
do
it.
So
what
OS
are
you?
Are
you
running
to
I'm
sorry,
I
say
one
more?
Oh,
it's
a
butcher.
F
F
F
A
A
A
F
I
can
specify
it
so
I
can
I
have
a
branch,
that's
kind
of
already
done.
I
can
I
can
check
in
a
I
can
open
a
pull
request
and
then
you
can
take
over.
However,
you'd
like
to
implement
it
but
critical
path.
Css
is
something
that
you
need
fully
generated.
F
E
Should
probably
clarify
here,
I
think
patient
have
used.
The
word
critical
is
that
that's
probably
confusing
the
issue
slightly.
What
I
was
meaning
here
is
more
like
more
like
multi-step
user
journeys,
where
the
user
is
in
the
middle
of
some
kind
of
action.
So
the
approach
I
would
probably
take
here
is
by
default.
You
are
just
locking
nad
to
home
screen
all
the
time
and
then
maintain
some
one
kind
of
whitelist
or
which
routes
or
pages
or,
however,
you
want
specify
it.
You
want
them
to
to
show
up,
and
that
way
it
becomes.
A
That's
a
good
call
Rowen,
maybe
I'm
can
I
could
maybe
oversimplify
this
and
be
really
explicit.
Maybe
we
can
whitelist
only
homepage
category
and
product
details
for
MVP
in
that
set
it
with
that
and
then
we're
still
providing
a
useful
example
and
oversimplify
things
a
bit
that
might
be
just
enough.
The
leaves
get
started
on
those
movies.
It
gets
better
yeah.
A
All
right,
let's,
let's
move
estimation
on
this,
so
what
are
we
thinking
on
this.
F
Gosh
I
mean,
with
the
serviceworker
discovery,
that's
necessary
to
do
to
do
this
in
the
work
box.
Discovery
I
think
it'd
be
safe
to
call
it
a
five
again.
A
lot
of
this
gets
automated
and
I
recognize
that
it's
small,
but
we
have
some
testing
to
do
and
especially
device
testing
to
do
so.
I
think
it's
a
it's
a
five
and
it
might
even
be
borderline
there.
E
E
A
I'm,
okay,
with
a
five
you
know,
Paul
I
know
you
guys
this
one's
again
I
kind
of
out
of
sequence,
but
again,
given
some
of
your
robots
I'm
here,
let's
call
it
that.
But
if
you
have
any
questions
again,
you've
got
that
you've
got
the
support
of
Rowan,
James
and
others
take
to
get
this
there
I
would
love.
You
know
the
minute
that
starts
to
get
a
little
bit
bigger
than
what
we've
got.
Let
us
know
and
let's
make
sure,
let's
find
invert,
you
know,
find
the
smallest
way.
A
A
I'm
trying
to
save
you
there
for
the
ones,
though
all
right
well
good.
So
that's
a
good
one.
So
let
me
add,
let
me
go
ahead
and
add
that
one
then
to
ready
to
start
that
one's
in
good
shape,
excellent,
all
right,
let's
what
kind
of
continue
with
the
same
by
the
same
mindset
here
this
again
is
I,
think
isn't
blocked
by
this
one
to
run.
Some
I
was
talking
about
before.
So
this
is
the
basic
offline
experience
this
may.
This
is
definitely-
and
this
is
the
200
response.
A
This
is
definitely
I
think,
depending
on
what
we
just
talked
about
here,
I
guess.
The
larger
question
is:
is
this
something
that
that
should
just
be
combined
or
just
consider
this
kind
of
a
two-for-one,
and
he
thought
that
breaking
this
out
is
any
logic
before
we
talk
about
that
ie,
so
I
pulled
latest.
B
A
Yeah,
so
what
sometime
ention
de
james
today?
Well,
our
we've
got
quite
a
few
things
that
we
still
need
to
take
a
look
at
merging,
but
the
one
one
issue
that
you're
probably
encountering
is
the
the
address
so
for
anyone
installs
her
right
now
that
we're
going
to
take
a
look
at
that
right
now
with
regard
to
I'll,
show
you
which
one
it
is
so
the
thumbnail
pages,
a
thumbnail
images
is
known,
but
this
one.
B
A
Are
if
it's
a
bogging,
it's
well
understood
and
we
have
essentially
steps
to
reproduce.
We
messiaen
it
and
we've
considered
it
the
very
least
ready
to
start
if
there's
questions
investigations,
but
hopefully
we'll
get
those
two
in
progress,
so
that
one
particular,
though
we're
taking
a
look
at
that
right
now,
yep
all
right,
so
you're
taking
a
look
at
the
the
basic
offline
experience
again,
this
one
is
bundled
with
what
we
just
talked
about.
I
think
there's
certainly
a
dependency
there.
It
gets.
The
question,
though,
is
there
any
value
to
having
this
separate,
separate
story?
A
What
do
you?
What
do
you
guys
think
I
was.
E
A
A
Actually,
you
know
I'll
do
the
link,
let's
kind
of
go
through
this
one,
but
I
want
us
that
if
they're
kind
of
got
you
some
questions,
first
of
all,
I
do
the
do
the
link
here
in
so
again,
this
one
at
least
has
initially
intended.
Was
you
want
to
have
basic
feedback
and
storefront
when
your
devices
having
connectivity,
issues
or
offline,
so
that
you
can
have
an
uninterrupted
shopping
experience?
And
this
is
this
is
a
requirement
for
for
lighthouse
and
applies
to
all
of
the
storefronts.
A
So
this
is
more
Universal
than
what
we
just
talked
about
with
that
add
to
at
the
home
screen,
of
course,
is
dependent
on
an
example
storefront,
which
is
good
dependent
on
the
do
200
response,
which
we've
talked
about
and
I
think
for
the
purposes
of
this
one.
We
don't
have
a
UX
for
this
one
yet,
but
I
think
he
placeholder
scenario,
and
so
that
comes
around
is
properly
sufficient.
The
tasks
themselves,
with
the
discovery,
implementation
of
a
single
example.
A
A
A
All
right
so,
while
I
link
this
side,
let's
let's
get
the
yeah
the
estimates
going
that
what's
what
does
everybody
think
on
the
offline
experience.
F
Boy,
I
actually
think
this
might
be
pretty
I
think
this
might
be
pretty
simple.
I
mean
the
way
work
box
operates.
Is
that
you
just
sort
of
whitelist
a
set
of
patterns
to
be
permanently
cached
in
the
serviceworker?
What
you
might
run
into
is
that,
if
you're
on
accustomed
to
working
with
and
debugging
service
workers,
then
you're
gonna
need
to
make
sure
that
you
enable
Service
Worker
debugging,
which
is,
is
documented
in
the
end
of
example
file.
F
And
that's
if
you
need
to
test
again
that
you
need
to
use
the
chrome
developer
tools
to
clear
out
the
serviceworker
and
to
unregister
it.
That's
something
you
just
have
to
learn
once
so
I
would
say
this
is
on
the
small
side
and
I'll
break
protocol
and
say
that
I'll
I'll
start
the
estimation
at
three.
E
And
I
guess
the
things
I
would.
This
is
dependent
on
the
UI
and
Samiha,
because
I
think
you
sort
of
have
new
primitives.
Here
you
want
one
one
which
is
an
actual
like
I'm
offline.
We
can't
display
this
page.
We
need
to
show
like
a
fallback
page
instead
and
another,
which
is
they
come
them
in
page
UI
changes
or
you've
lost
connectivity
and
you've
regained
connectivity.
A
But
how
about
above
this
rule
and
so
I
went
and
so
I
think
it
was
actually
a
great
call-out.
So
what
if
we
cloned
this
one,
because
I
have
seen
some
work
from
Sam
Young
on
the
on
the
engage
experience
from
that
one,
so
I
think
we
may
be.
Is
there
a
way
that
you
could
think
of
like
handling
this
independently
for
this,
but
then
maybe
focus
first
on
the
fallback
page
for
this
one
in
particular,
and
so
we
clone
this
one
and
the
next
one
would
be
kind
of
in
page
experience.
E
A
Yeah
I
think
promoted,
like
everything,
business
value
sample
at
least
even
having
something
placeholder
would
go
a
long
way
here
and
then
yeah.
If
we
cloned
this
one
and
we
get
that
something
grew
next
week,
we
can
add
that
to
the
in
page,
experience
would
just
be
basically
blocked
by
this,
but
that
build
upon
it
because
there's
you
know
the
UI
controls
and
things
like
that,
so
we
can
begin.
Certainly
aa
boom,
all
right.
E
Putting
in
support
of
that
five
I
would
probably
just
add
a
note
against
the
documentation
that
the
documentation
here
should
be
include
some
stuff
around
serviceworker
debugging,
because,
whilst
it's
not
explicitly
kind
of
venya
related
I
think
it's
still
new
enough.
That
people
want
some
some
context.
There.
E
A
All
right,
so
the
physic
we're
we're
pretty
locked
in
out
of
five
here.
So
I
think
that's
good!
You
know
in
terms
of
assignments,
you
know
Paul
again,
don't
want
to
put
you
in
the
spot.
I
know
this
is
pretty
pretty
related
to
add
to
home,
and
so
you
may
be
blocking
yourself.
Is
this
something
that
you
could
potentially
need
to
help
on,
or
is
that
something
that
you
guys
could
take
on
or
then
did
you
want
to
kind
of
take
it
offline,
I
think
about
a
little
bit
I.
H
H
A
Yeah
yeah,
the
only
reason
why
I
suggest
it
cause
it's
so
logically
grouped,
but
but
this
would
definitely
come
even
more
so
than
some
of
the
other
ones
with
with
quite
a
bit
of
support,
because
it's
you
know
it's
based
on
based
out
of
work
box
and
some
some
known
into
you
there.
So
ok,
very
good,
all
right!
Well,
that's
you
know,
that's
really
it
for
this
week
and
then
we
really
covered
quite
a
bit
of
stories.
We've
got
a
couple,
smaller
ones
that
there's
a
less
essential.
A
Some
things
we
look
forward
to
are
the
the
mail
templates
for
Benia.
So
out
of
the
box,
luma,
there's
a
couple
quick
art
swaps
there
for
anybody
who's
familiar
with
them,
too.
We've
got
a
couple
fallbacks
related
to
what
we
just
talked
about
really
to
offline
experience.
There
should
be
pretty
straightforward
once
we
get
that
and
a
couple
redirects
as
well,
and
so
as
you
as
you
kind
of
see
the
the
trajectory
that
we're
going
towards
for
next
month.
A
The
rule
the
goal
here
is
it's
to
get
the
fit
and
finish
done
for
venía
relative
to
the
to
the
2003
release
and
once
everything
has
merged,
and
we
continue
to
get
help
on
on
some
of
the
some
of
those
those
items.
You'll
see
that
all
come
to
life
and
the
kind
of
that
last
layer
is
going
to
be
really
addressing
the
PW
basics.
Right,
that's
a
good
core,
but
we
need
that
layer.
A
You
know
layer
of
the
manifest
and
these
other
experiences
that
complement
everything
we've
done
today.
So
that's
really
going
to
be
the
goal
in
this
thing
really
for
the
next
couple
sprints,
but
as
you
can
see,
we're
pretty
full,
we
got
a
lot
of
things
that
can
still
be
picked
up
at
this
point.
You've
got
eleven
issues:
totaling
totaling
36
points
and
start
taking
a
look
at
that,
and
then
we've
got
quite
a
few
things
that
are
in
flight
as
part
of
certainly
27.
A
Right
now,
but
then,
as
we
move
to
sprint
28
next
week
for
that
one,
so
we've
got
plenty
that
work
fine
and,
of
course
it
gives
have
any
questions,
comments,
etc.
Just
them
just
let
us
know
so
anything
else,
any
other
questions
or
or
any
other
feedback
before
we
have
we
closed
for
for
the
day,
I
wanted.
E
A
A
So
one
of
the
things
that
one
things
we
actually
have
behind
the
scenes
that
is
often
overlooked-
we've
got
a
pretty
active
road
map
here
and
what
we've
done
and
where
we're
going
so
I,
you
know
I,
am
updating
this
relative
to
the
2.3
commits
next
month.
That
a
lot
of
these
are
exactly
we're
talking
about
so
we're
already
talking
about
things
like
upward
I
do
think
this
can
be
simplified
a
little
bit.
A
Then
there's
a
couple
little
things
here
that
we
want
to
clean
up,
but
all
in
all
I
would
say
at
least
this
moments
probably
directionally
correct.
But
one
of
my
tasks
for
this
week
is
to
take
a
look
at
this
and
then
initiate
phase
three.
So
essentially,
this
is
a
a
working
road
map
based
on
at
least
our
perceptions
of
the
current
velocity,
with
the
new
feature
team
on
board,
who
probably
starting
see
some
new
faces
on
the
grooming,
but
also
anticipated
community
support
here
for
the
next
two
to
three
Sprint's.
A
All
right,
well
hey
great
session
folks.
Thank
you
again,
as
always
for
all
of
your
help
book
here.
Both
you
know
book
was
in
the
work.
The
feedback
is,
it
continues
to
be
fantastic.
So,
as
always,
let
us
know
if
we
can
help
have
a
great
rest
of
your
day,
no
matter
where
you
are,
and
yeah
thanks
again
take
care
thanks.
Sir,
thank
you
thank.