►
From YouTube: Magento PWA Demo, 24 September 2018 (Sprint 25)
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
Oh
well,
then,
the
third
of
starting
on
time
here,
let's
let's
get
started
so
as
mentioned,
we've
got
an
action-packed
lineup
as
usual:
first
print
twenty
five,
and
so
we
we
close
this
print
with
a
lot
of
good
progress
on
UX
and
Docs,
and
so
we're
gonna
have
Tommy
and
James
really
lead.
The
way
speak
specifically
around
account
recovery,
some
of
the
recent
working
orders
and
the
forced
search.
A
This
is
this,
of
course,
for
those
who
are
at
grooming
leads
very
well
into
what
were
what
we're
making
ready
in
terms
of
development
work
as
well
and
so
working
very
much
in
real
time
here
and
then,
of
course,
James.
It's
fast,
following
with
some
of
the
some
of
the
coverage
on
API
and
some
awesome
updates
to
the
homepage,
to
to
reflect
the
contributors
and
some
of
the
work
that
we've
seen
here
very
similar
to
what's
happening
back
to
all
and
others.
Of
course.
A
Last,
but
certainly
not
least,
I
know
I'm
really
excited
to
see
some
of
the
progress
beyond
some
of
the
animations
around
create
accounts,
as
you
know,
Jonathan
Paul
and
the
bargaining
team,
and
done
such
great
work
recently.
On
the
theme,
and
so
in
love,
this
love
to
see
that
and
kind
of
finish
finish
strong.
So
that's
what
we
had
any
and
then
also
want
to
spend
a
couple
minutes
as
well
at
the
end,
to
see
if
there's
any
questions
around
the
updated
release
strategy
and
on
James
and
team
have
been
working
really
hard.
B
B
Any
of
my
account
haven't
included
the
capture
step
in
this
flow,
yet
we're
still
kind
of
trying
to
figure
that
these
out,
but
that's
the
overall
flow
goal
and
then
with
the
purchase
history
with
the
discussion
that
was
had
last
week
with
showing
individual
items
then
going
into
orders
kind
of
like
the
Amazon
model,
you
have
a
list
of
things
that
you've
ordered
and
the
dates
that
you
ordered
them
on.
There
is
an
option
in
the
future
to
filter
by
you
know
certain
days
on
a
product
name.
B
This
piece
is
it's
sort
of
a
find
absque
I.
Have
it
hasn't
been
discussed?
Yet
just
a
suggestion
at
this
point,
if
you
did
click
into
an
individual
item,
would
show
you
that
item
at
the
top,
with
some
individual
product
related
actions
such
as
being
able
to
purchase
again
share
it
or
review
it,
and
then
the
associated
order
details
which
would
show
you
other
items
in
the
order
and
any
shipping
payment
and
sort
of
billing
breakdowns.
B
So
here,
with
search
what
being
landed
on
was
clicking
on
the
search,
the
search
would
always
collapse
clicking
on
the
search
icon
with
would
summon
the
search
bar
when
you
enter
the
search
term
into
it.
The
future
vision
is
that
it
would
show
you
keyword,
counted
results.
Do
the
typing,
as
well
as
maybe
any
product
suggestions
for
now.
I
think
we're
just
going
to
the
functionality
is
going
to
be
entering
a
search
term
and
then
sitting
done
and
then
being
landed
on
a
search
results.
B
A
C
B
Specifically,
how
this
works
is
that
the
keyboard
space
up
in
the
area
behind
it
it
scrollable.
So
you
can
see
enough
to
view
suggestions
at
least
that's
how
it
happens.
On
iOS,
I
haven't
really
investigated
how
that
works,
but
Android
I
would
assume
it's
somewhat
similar
cuz.
Otherwise,
it
gives
you
very
little
real
estate
to
show
any
thought
of
suggestions,
and
it
was
vendor
that
kind
of
pointless
unless
that's
what
we
wanted.
B
C
It's
scrollable
in
android
to
this.
You
know
with
the
keyboard
pop
questions
about
what's
gonna
happen
when
you
tap
and
is
it
gonna
blur
the
the
search
field
and
I'm
more
familiar
with
that
in
safari?
Where
you're
absolutely
right,
you
can.
You
can
swipe
without
I'm
focusing
the
search
field,
but
if
you
tap
it
does
and
then
perhaps
the
thing
disappears.
C
B
D
D
F
F
That
is
what
that's
pretty
much.
What
that
covers.
Second
update
from
Doc's
is
update
on
our
homepage,
especially
the
readme
file
to
recognize
our
community
contributors.
We
want
to,
you,
know,
give
them
shoutouts
for
contributing
to
our
project,
and
this
list
I
got
is
from
github
insights
here
and
if
you
think
that
you
know
there
should
be
someone
added
to
this
list,
let
us
know,
and
when
you
get
imagine
yep.
A
So
this
was
great
one
of
the
things
that
I
know:
James
myself
and
others,
and
the
team
talked
a
lot
about
it.
You
know
what
makes
a
maintainer
and
what
really
makes
elevated
community
status
and
what
we're
trying
to
do
it.
We've
had
such
great
contribution
really
from
a
lot
of
success,
either
on
the
call
as
well
themself
establishing
that
and
really
forming
some.
You
know
forming
some
some
likeness
with
what's
happening
on
the
community
engineering
team
I
think
is
really
we
want
to
take
this.
A
A
That's
really
helping
us
pushed
push
the
needle
on
the
shopper,
experience,
menu,
theme
itself,
and
so
this
is
certainly
the
very
least
you
can
do,
but
at
the
beginnings
of
a
program
that
we're
going
to
be
doing,
it's
a
really
kind
of
give
back
a
little
bit
based
on
what
we've
been
given
to
date,
of
course,
be
again
be
consistent
with
some
of
the
other
efforts
like
wraps
you
well
and
others
for
that,
and
so
yeah
James.
Thank
you
for
putting
this
together
and
yeah.
If
there's
any
feedback,
anybody
wouldn't
think.
Please
let
us
know.
A
A
E
G
A
G
Yeah,
so
one
of
the
things
about
the
sign
in
token
is
that
we
still
need
to
actually
make
it
try
a
refresh
if
it
expires
on
the
back
end.
We
didn't
end
up
implementing
that
because
that
seemed
like.
Maybe
that
should
be
a
different
issue.
So,
on
the
safe
side
we
decide
just
to
leave
that
for
now,
and
so
what
can
happen
right
now
is
they
can
actually
expire,
even
though
it
stays
in
local
storage,
and
so
in
that
case
you
kind
of
have
to
clear
local
storage.
C
There's
a
library
though
it
may
be
too
heavy
for
this
use.
You
know
you
might
end
up
just
doing
a
one-off,
but
there's
a
library
that
supports
this.
That
does
TTL
on
local
storage,
I
believe
it's
pretty
small.
The
other
option,
I
suppose,
is
to
just
put
it
in
a
cookie
manually
with
an
expiration
date.
I
mean
the
trouble,
of
course
with
that
is
cookies
being
readable
by
JavaScript.
By
other
things,
don't
never
mind
about
that.
I
don't
know.
D
G
So
I
made
a
generic
form
component
that
basically
renders
its
children
and
then
has
like
an
on
submit.
So
we
can
reuse
that
and
then
we
also
made
generic
input
components
that
have
that
basically
take
a
bunch
of
props
that
style
the
input
and
and
set
you
know
like
required
and
and
other
things
like
that,
I'm
not
going
to
an
HTML
indictment.
G
E
E
C
C
So
it's
a
toasty
little
metaphor
to
refer
to
the
kind
of
two
ways
you
can
be
authenticated
to
kind
of
anything.
But
three
comments
like
when
you
are
hot
authenticated.
You
have
access
to
everything.
When
you
are
warmly
authenticated
you
can
you
see
your
name?
It
knows
who
you
are.
You
can
build
a
cart,
but
as
soon
as
you
get
to
the
point
where
you
would
be
accessing
payment
information
or
if
you
go
to
your
my
account
screen
or
you
you
try
to
you
know,
do
anything
that
involves
PII
or
payments.
G
C
G
I
am
pretty
sure
if
I
decided
to
guess
right
now,
I
believe
we're
doing
just
warm,
because
the
fact
that
we're
just
storing
the
auth
headers
in
the
requests
automatically
I
believe
that
will
carry
over
to
when
you're
actually
checking
out
and
you
you
know,
actually
check
out
your
card.
Yeah,
like
I
said
we
haven't,
we
haven't
really
tested
at
that
deep
sure.
C
Yeah
well,
I
mean
seems
it
seems
like
session-based
authentication.
Yeah
is
warm
authentication
in
Magento
lands,
that's
like
if
yeah
like.
If
you
come
back
and
you
get
re
off
from
a
session,
then
you're
warm
I,
don't
know
if
there
is
an
expiry,
but
you
could
probably
just
see
that
via
introspection.
If
you
look
at
how
Magento
sets
its
cookie
and
like
what
its
expiration
is,
usually
it's
an
hour
or
something
like
that.
E
E
A
This
is
great
now
this
really
pushes
quite
quite
a
bit
into
the
to
the
workaround
off
and
so
I.
You
know
again
can't
be
more
appreciative
of
everything
you
done.
I
think
you're,
starting
we're
starting
stitch
together,
pretty
compelling
you
know
really
KITT
from
from
all
the
way
from
homepage
all
the
way
down
through
a
true
check
out
here,
and
so
thank
you
so
much
for
covering
this,
some
of
the
edge
cases
and
I
think
even
more
so
working
with
Tommy
and
others
to
really
refine
it
and
get
it
get
it
done
right.
A
A
C
Clint,
it's
kind
of
placed
there
we
go.
Let's
just
do
that,
so
perhaps
you
can
see
here
that
I've
begun
to
label
certain
things,
and
this
is
sort
of
my
call,
my
arbitrary
call
which
which
can
which
merits
discussion.
If
you
want
to
argue
with
me,
that's
fine,
but
bottom
line
is
we
are
going
to
switch
from
the
current
states
where
this
repository
and
its
packages
are
only
really
suitable
for
internal
developments
by
cloning.
C
The
whole
mono
repo
we're
switching
from
that
to
a
scheme
where
the
individual
packages
are
published
and
potentially
other
consumers
who
are
not
necessarily
just
making
venía,
would
get
billed
PAC
or
Peregrine
from
NPM.
So
this
also
has
the
side
effect
of
making
it
easier
to
tell
when
you
have
a
version
with
particular
features,
because
there's
a
change
log
for
each
version,
this
all
amounts
to
real
release
management.
C
We
have
them
community
member
named
mark
juste,
who
actually
has
created
a
concept
called
get
ship
which
is
effectively
a
radically
simplified,
get
flow
which,
if
you're
not
familiar
with
get
flow.
It
is
a
branching
and
merging
strategy
designed
for
continuous
delivery
software
that
is
fairly
popular.
C
Amongst
sass
platforms,
because
it's
kind
of
designed
to
let
you
maintain
master
as
whatever
is
in
production
and
then
generate
releases,
release,
candidates
and
hot
fixes,
based
on
branch
names
and
stay
completely
up
to
date
in
master,
and
then
your
release
branches
while
doing
continuous
development
in
the
development
branch,
but
mark
just
observes
here
that's
for
continuous
delivery.
That
seems
to
make
sense,
but
if
you're
doing
regular
releases
but
not
constantly
merging
into
production,
whenever
your
tests
pass,
which
is
what
continuous
delivery
really
is.
C
I'd
like
to
believe,
if
you're
releasing
individual
releases
of
stuff,
maybe
you
don't
need
to
do
so
much
merging
and
his
idea
is
to
use
the
master
branch
for
the
individual
tags
that
indicate
releases
and
otherwise
to
do
all
your
development
in
individual
release
branches,
which
means
that
instead
of
us
all
opening
our
pull
requests
against
master,
we
would
open
a
pull
request
against
whatever
the
most
recent
release.
Branch
is
effectively.
These
branches
replace
the
so
called
developed
branch
and
that
really
really
slings
down
the
number
of
merges
the
amount
of
confusion.
C
So
what
we're
gonna
do
is
retro
actively,
have
a
0.9
release
and
then
create
a
1.0
release
branch
with
an
immediately
tagged,
1.0
our
seat,
one
release
candidate.
So
that's
we
can
push
things
out
to
NPM
for
everybody
and
then
from
that
point
forward,
that
will
actually
be
the
main
branch
of
the
repository.
C
If
you
have
a
change
that
only
applies
to
the
code
from
the
zero
point,
nine
branch,
then
you
can
simply
open
a
pull
requests
against
master
which
will
be
on
0.9,
but
otherwise,
if
you're
working
on
the
current
edge
code,
you
would
open
up
against
release
1.0.
We
would
preserve
earlier
release
branches,
maybe
2
back
in
order
to
do
maintenance
or
hot
fixes
to
two
branches
back,
it's
pretty
straightforward
and
we're
fortunate
enough
that
the
creator
of
this
idea
is
a
member
of
the
Magento
community.
C
So
that
said,
I
have
tagged.
These
pull
requests
with
indicators
of
where
I
would
like
to
merge
them.
If
you
would
like
look
into
your
pull
request
and
examined
it
and
see
why
I
may
have
done
that
and
I'll
leave
comments,
actually,
which
I
need
to
do
the
best
I
think
that's
the
main
thing
that
the
reason
that
we
need
a
one
point
X
release
branch
is
that
we
have
big
significant
code
changes
that
will
make
that
merges
hard
to
future
pull
requests
like
this
default.
C
Pragma
is
not
a
huge
logical
change,
but
it
is
a
huge
amount
code
change,
which
is
why
it's
one
point
X
and
the
switch
from
it
being
a
Magento
theme
in
the
first
place
to
it
being
a
separate
project
that
runs
on
an
upward
server.
Its
back-end
is
a
really
big
change
that
definitely
necessitates
a
major
semantic
version.
C
This
is
going
to
come
in
with
some
more
change,
log
rules
and
some
commit
message
rules,
but
that
will
be
a
phase
two
thing:
we're
just
gonna
start
with
this
release
management
and
then
later
we'll
introduce
the
idea
of
change
log
that
is
auto-generated.
In
the
meantime,
we
will
just
be
asking
that
pull
requests
come
with
a
lot
of
detail
that
can
then
be
added
to
change
locks
when
we
do
releases
and
that's
the
update
I
have
for
that.
C
A
So
that's
really
it
for
this
week,
so
we've
got
again
a
lot
of
good
progress
on
the
US
on
Doc's
front.
You
know
key
contributions,
of
course,
from
the
bar
green
team
continue
to
just
have
been
awesome,
especially
bringing
to
light
some
of
the
venya
theme
and
so
and
of
course,
some
notes
from
James
on
our
release
strategy
right,
especially
as
we
get
more
help,
both
internally
and
externally,
on
the
project,
as
we
make
our
way
to
to
the
to
that
for
release
at
the
end
of
the
year.