►
From YouTube: Magento PWA Backlog Grooming, 2 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
Okay,
hi
I
see
you
have
Jesse
Eisenberg
on
hi
Jesse.
Thank
you
for
coming
and
hello
Demetri,
and
we
are
gathered
here
today
as
Erica,
or
we
might
put
it
in
an
unusual
room.
We
typically
have
a
different
ones,
so
I
will
use
that
to
explain
my
personal
tardiness.
Everyone
else
was
right
on
time.
Let's
do
a
couple
of
introductions.
Do
you
guys
want
to
share
your
video,
but
not
audio,
just
make
sure
that
your
audio
is
muted,
but
your
video
is
not,
and
your
speaker
is
turned
off.
A
A
A
A
A
E
A
Guy,
that's
what
that
mean.
Is
that
hey
where's,
your
video
on
my
views
on
okay?
Let's
look
at
it
go
hello.
The
community
engineering
is
obviously
a
team
of
long-standing
and
they
run
a
lot
of
of
community
projects
up
to
an
including
MSI
and
even
graph,
QL,
now
and
other
really
large
and
important
parts
of
the
ecosystem.
But
up
until
now
our
team
has
run
without
direct
community
engineering
engagement,
just
because
we
are
a
different
program.
A
A
different
suite
of
software
and
the
rules
of
engagement
that
community
engineering
has
set
up
are
very
heavily
adapted
to
Magento
and
and
Magento
extension
type
of
software
dev
cycles.
So
now
we're
getting
into
this-
and
this
is
going
to
be
huge.
So
thank
you
very
much
for
coming.
I,
don't
know
if
anybody
else
here
needs
to
be
introduced
to
mr.
Andrew
Wilcox,
who
has
attended
now
a
couple
of
these,
but
just
in
case
you
haven't
seen
him.
This
is
Andrew
Wilcox.
He
is
a
project
manager,
products.
I
said
that
was
a
cool
pronunciation.
A
I
just
did.
He
is
a
product
manager
who
will
be
taking
over
increasingly
the
the
vision
and
the
focus
for
PW
a
studio,
and
we
are
super
excited
about
that.
Normally
Eric
early
would
be
here
and
he
will
continue
to
come
to
later
ones
he's
not
going
anywhere,
but
today
he
has
conflict.
We
also
have
James
Calcutta
minute
for
docs
and
Samy,
oh
shucks
for
UX,
so
I.
D
A
All
right
can
we
see
it
fantastic,
so
a
grooming.
We
are
very
explicitly
not
assigning
stories.
You
can
feel
free
to
be
interested
in
a
story
and
to
declare
your
interest,
but
we
don't
do
the
assignment
directly.
You
can
feel
free
to
self
assign
afterwards.
What
we're
doing
here
is
identifying
stories
that
need
to
be
sized
and
to
have
extra
detail
added
and
prioritised
in
the
backlog.
Hellobar.
Green,
hey,
are
you
doing?
You
have
superstars
bargaining,
Ellingson
I,
my
videos,
a
bit
blocked,
but
I
think
I,
see
Paul
and
is
Jonathan.
F
A
A
Okay,
folks,
PWA,
studio
and
venĂa
are
completely
JavaScript
powered
applications.
So
there
is
almost
no
data
display
when
javascript
is
disabled.
Let's
kind
of
talk
first
about
the
acceptance
criteria
and
where
this
story
came
from
that
Eric
opened
it,
but
it
came
originally
from
requests
or
a
bit
of
interest
from
I
believe
from
community
am
I
wrong,
or
does
somebody
on
this
call
feel
that
they
brought
this
issue
up
originally
no
well,
most
websites
do
need
to
have
a
JavaScript
fallback.
A
I
think
this
is
an
unusual
case,
because
progressive
web
apps
are
largely
implemented
with
their
progressive
loading
in
JavaScript.
So
what
this
freely
I
think
is,
is
it's
a
proxy
for
discussing
server-side
render
and
we
have
a
server-side
render.
Now,
though,
it
is
partial
and
it
uses
at
least
right
now,
a
different
methodology,
a
different
template
language
and
rendering
system.
Then
the
front-end
does,
that
is
to
say
the
application
is
not
currently
isomorphic
University.
A
A
Yeah
I'd
say
that
that
is
requires
a
combination
of
things.
First,
it's
it
requires
that
the
display
that
occurs
be
completely
server
rendered.
We
know
it
requires
that
the
display
be.
G
G
C
A
G
A
A
G
A
So
before
sizing,
I
will
say
briefly
that
we
have
work
in
progress
to
actually
deliver
critical
CSS
on
the
server-side
extracted
from
all
the
CSS
bundled
and
injected
into
the
application.
Shell,
it's
dependent
right
now
on
webpack
4,
which
is
an
ongoing
project
which
we
put
aside
in
order
to
achieve
just
the
final
scenarios.
So,
if
anyone
wants
to,
we
can
look
at.
A
We
have
I'm
not
going
to
try
to
demo
it,
but
we
have
a
branch
I
believe
down
here
somewhere
we
have
a
critical
CSS
by
filename
branch,
where
I've
implemented
a
basic
notion
that
the
developer
manually
selects.
What
about
their
component
that
they
have
developed,
is
consider
to
be
critical,
for
instance,
page
components,
sort
of
the
outer
bit
of
the
UI.
So
if
you're
gonna
render
anything
even
basic,
you
probably
want
part
of
it
to
be
critical,
so
I
just
separated
the
critical
CSS
and
the
mask
CSS
seemed
less
critical.
A
So
in
page
we
obviously
import
the
file
differently
and
the
reason
that
we
name
these
files.
This
way
is
that
in
this
branch
we
have
added
a
plug-in
in
our
web
pack
tools
to
do
Oh.
Have
we
not
wrong
branch,
we'll
just
go
to
the
whole
web
pack
for
refactor,
we
have
a
critical
CSS
plug-in
and
that
plug-in
actually
injects
a
loader
that
adds
a
regular
expression
detector,
a
test
so
that
when
the
file
name
ends
with
critical
that
it
processes
it
with
an
its
with
an
extractor.
A
The
venĂa
upward
file
then
has
a
critical
CSS
file
that
it
pulls
out
of
an
asset
manifest
that
is
generated
and
then,
when
it
renders
this
application
shell
template
it
actually
pulls
in
the
contents
of
that
file
and
shoves
them
into
a
style
tag
at
the
top
excuse
me,
and
so
then
you
actually
have
a
style
tag
that
injects
the
critical
CSS
that
is
put
together
just
from
those
file
names.
The
reason
I
show
this
off
is
not
because
I
want
you
to
use
this
technique.
It's
not
even
merged,
not
even
vetted
or
code
review.
A
What
I
want
to
make
sure
is
that
we
don't
take
extra
time
in
this
story
to
come
up
with
our
own
critical
CSS
technique.
You
may
have
one
that
is
superior,
which
would
be
fine,
but
we
should
discuss
that
separately.
I,
don't
think
this
is
the
story
to
start
experimenting
with
that,
because
we
have
exceed
our
standing
work
for
so
with
that
in
mind.
Sammy,
if
you
want
to
do
a
version
of
this
comp
that
doesn't
have
the
header
Sam,
you
literally
did
it
during
grooming.
A
Then
that
means
that
we
can
size
this
story
as
though
all
you're
doing
is
again
according
to
the
acceptance
criteria,
you
are
displaying
the
branded
page
and
the
appropriate
message.
If
javascript
is
disabled,
you
are
not
displaying
even
for
a
millisecond
that
page
if
javascript
is
enabled-
and
you
and
you
have
this
thing
rendered
on
the
server-side-
it's
so
that
it
is
well.
Obviously
you
have
to
so
there's
JavaScript,
so
I
guess
it's
down
to
the
two
acceptance
criteria.
Apart
from
what's
written
up
here,
that.
A
Google
lighthouse
needs
to
parse
it.
So
I
would
say
that
part
of
the
acceptance
criteria
for
the
story
is
that
we
run
the
deployed,
pull
request
through
Google
lighthouse
and
make
sure
that
that
box
is
checked.
Does
anyone
have
any
questions
about
the
scope
and
nature
of
this
story?
Now
that
we've
gone
through
that.
A
G
A
What
we
are,
what
I
think
I
recommend
to
say
was
that
we
would
use
the
same
like
visual
design
and
change
only
the
content
and
call
to
action.
I
see
in
this
case
the
content
would
say
instead
of
sorry,
we
could
not
find
the
page
you
requested.
It
would
say
this
site
requires
JavaScript
to
be
enabled
and
the
call
to
action
wouldn't
be
a
button,
because
you
must
do
this
manually,
but
then
there'd
be
another
paragraph
texts
or
another
sentence.
That
said,
you
know
please
enable
JavaScript
in
your
browser.
Okay,.
G
A
G
A
G
G
A
A
A
The
size
of
five
is
something
that
would
take
sorry
size
of
three:
something
would
take
less
than
half
of
a
sprint.
The
size
of
five
is
something
that
would
take
half
of
a
sprint
or
more.
A
size
of
eight
is
a
full
sprint.
The
size
of
13
is
too
large,
and
it
would
mean
that
we
have
to
break
open
the
story
into
smaller
pieces
or,
if
you
say
it's
a
13
and
I
can
take
it.
We'll
talk
offline.
A
I'm
gonna,
second,
that
just
because
the
discovery
on
this
ok
meeting
like
where
do
you
do
this
rendering
and
how
do
you
figure
out
how
to
not
flash
it,
etc?
Yeah,
okay,
well
with
two
fives
and
I,
was
gonna,
guess
lower,
but
you
guys
have
me
second-guessing
myself.
So
I
will
agree
that
it
is
a
five.
A
F
C
A
E
A
The
my
my
my
thought
is
that
we
would
like
to
be
able
to
have
enough
logic
in
there
so
that
it's
not
fully
generic
so
that
you
can
inject
the
name
of
the
store,
but
that's
not
an
acceptance
criterion.
It's
just
an
example,
so
that
message
includes
minimal
if
any
of
branding
and
then
tests
exists,
ad
tests
or.
A
I
A
A
D
A
So
we
also
have
programming
a
forgot
password
implementation.
This
one
I
think
we
should
talk
about
a
little
bit
more
detail.
So
let's
see
Seema
you're
on
the
phone
and
barred
me
and
you
guys
are
on
the
phone
you
have-
and
we
have
talked
about
this
to
some
length
right
like
this
is
already
sort
of
partly
fairly
groomed,
but
it
still
sort
of
needs
to
be
sized
and
it
needs
to
be
understood
as
to
the
acceptance
criteria.
A
G
A
Cool
I'm:
do
you
looking
at
these
mock-ups
think
that
they're
still
current,
oh
yeah,
okay,
so
a
couple
things
worth
mentioning
is
that
the
rest
api
does
support
this
interaction,
though
there
may
be
some
necessary
additions
to
the
rest.
Api
is
functionality.
You
may
have
to
add
a
header,
that's
something
that
you
can
discover
with
our
cool
new
redock
rest
API
documentation,
and
this
story
appears
to
be
blocked
by
my
account
so
that
the
create
an
account
call
to
action.
Can
click
through
so
I
would
say,
don't
wait
just
make
the
button.
A
G
D
A
G
D
G
G
A
I
think
a
lot
of
that
is
is
system
dependent,
la
that's
operating
system
like
so
consider,
first
of
all
that
for
our
acceptance
criteria,
we're
almost
always
focusing
on
the
mobile
use
case,
wherein
it's
fairly
rare
that
somebody
would
accidentally
switch
browsers.
I
know,
personally
that
there's
a
risk
of
doing
it
when
I
am
in
Gmail,
and
it
always
forgets
that
I
want
to
use
Safari
every
time.
Anything
happens
that
it
says.
If
you.
A
It's
just
like
Safari
with
different
branding,
which
is
true
on
iOS,
but
so
that
is
something
to
consider,
but
I
think
that
it's
it's
hard
for
us
to
address
it.
It's
hard
for
us
in
our
own
code,
in
our
own
implementation,
to
address
the
use
case.
What
I
would
prefer
I
think
just
in
terms
of
ordering
is
to
do
this
story
under
the
assumption
that
the
browser
to
email
connection
is
constant
and
then
address
bugs
as
they
occur.
A
A
I
G
I
don't
know
if
I
completely
agree
that
that's
a
common
use
case
but
I
think
it's
good
to
go
with
the
with
the
easiest
to
address
in
a
zoom.
They
would
be
in
the
same
browser
and
then
because
I
can't
say
it
with
certainty.
How
often
the
this
it
happens
with
me
very
often,
but
that's
because
I
use
Chrome
on
my
phone,
but
that
I
would
need
to
have
a
little
bit
better
idea
about
what
the
8020
is.
If
it's
a
50/50.
G
A
A
A
Reset
just
like
sending
the
emails
actually
conducted
by
Magento
and
back-end
so
and
thank
you
actually
I
should
make
that
clear
as
a
shopper.
I
want
to
reset
my
password
with
ania
as
a
shopper
who
forgot
my
password
I
want
to
reset
my
password
for
vinius
that
I
can
access
previous
orders
purchased
using
my
information
file.
A
A
F
A
B
H
A
A
A
I,
like
that,
a
lot,
so
you
know
this
issue
does
not
mean
that
we're
grooming
it
for
you
going
and
learning
Jeckyll
and
adding
it
to
the
PWA
dev
Docs
repository
exactly
that's
that's
mr.
Calkins
job,
but
we
are
grooming.
This
story,
ultimately
for
execution
all
most
likely,
definitely
by
him.
In
doing
so,
we've
got
to
add
some
detail
if
necessary,
like
I
myself
feel
like
we
need
to
consolidate
our
documentation
in
general,
we've
got
a
different
story
for
that,
but
the
explanation
of
it's
no
longer
a
theme.
A
H
A
Got
you
know
gotcha,
so
we
have
these
these
topic
suggestions.
You
know
comparing
and
contrasting
theme
developments
and
PwC
storefront
developments
doing
a
pros
and
cons
list
describing
the
kind
of
overall
idea
of
modularity
and
composing
your
storefront
UI
versus
choosing
a
base
theme
and
then
performing
extensions
or
modifications
on
that.
Like
oh
excuse
me
at
performing
extensions
or
modifications
on
that
single
large
dependency,
we
don't
want
to
do
that.
A
I
think
that's
very
important
to
describe
because
we
get
a
lot
of
I,
think
confusion
from
folks
who
are
accustomed
to
that
being
the
Magento,
a
way
that
you
reuse
code,
right,
compare
and
contrast
out
steam
updates
work.
That's
really
good
list
of
skills
needed
for
either
approach.
That's
really
good
and
I
think
what
I
might
add
here
would
be
dependency
management
yeah
because,
like
in
the
Magento
world,
dependency
management
is
done.
A
I
A
Versus
in
Magento
games
using
the
composer
and
PHP
file,
restoration,
all
right,
crickets
ends,
you
don't
have
to
size
it
right
now.
This
is
more
appropriate
for
people
to
ask
for
more
clarity
or
say
this
is
what
I
would
love
in
Doc's
yeah
sounds
like
you
guys
think
this
is
already
fairly
thorough
and
relevant,
which
what
I've
come
to
expect
so
I'm
gonna.
Do
you
want
to
size
it
or
you
only
leave
it
to
size.
A
G
G
G
A
Well,
no
problem,
it's
a
good
point.
I
think
that
relates
to
the
message
to
be
sent
and
I
think
it's.
It's
actually
a
very,
very
good
idea,
and
it's
either
a
support,
email
or
support
phone
number,
probably
I,
think
it's
something
we
could
leave
up
to
the
implementer
of
the
theme.
The
merchants
in
the
winter
will
probably
be
interacting
I.
Just.
G
Kind
of
want
to
understand
the
context
around
which
this
would
happen
right,
I
mean
from
what
I
understand
from
discussing
this
Virginia
little
earlier
is
that
it's
not
likely
that
somebody
would
purposefully
have
their
javascript
disabled,
especially
not
someone
who's
a
shopper.
So
if
they
do
hit
this
accidently
they're,
not
a
technical
user
and
by
asking
them
to
send
a
support,
email,
we're
potentially
having
them
abandoned
the
shopping
journey.
Instead,
he
showed
me
an
example
from
SoundCloud
mm-hmm.
B
A
G
A
A
Okay,
so
what
I
think
is
interesting
about
this
is
that
I
have
never
thought
along
those
lines
before
about
the
idea
that
somebody
would
have
javascript,
disabled
and
not
know,
and
that's
I,
think
a
terrible
oversight
on
my
part.
Now
it's
just
be
coming
from
coming
from
a
world
where,
like
people
don't
even
like
using
graphical
user
interfaces,
I
sometimes
see
people
saying
I,
I,
disable
JavaScript,
it's
terrible,
it's
the
worst.
The
web
should
be.
You
know
static,
so
my
picture
of
the
persona
of
someone
who
has
javascript
disabled
is
someone
who
means
exactly.
G
A
A
G
Keeps
and
keeps
a
generic
enough.
It's
more
sort
of
a
sound
flow
for
the
type
of
message
you
can
include
when
somebody
runs
into
that
and
it's
up
to
the
the
merchant
based
on
the
the
audience
that
they
have
to
make
that
more
or
less
technical
as
they
feel
suits
their
audience,
but
I
think
for
Benny
I'm,
keeping
it
relatively
simple.
It's
probably
a
good
idea.
Okay,.
A
G
G
A
D
G
C
G
A
A
A
A
H
A
So
yeah
I'll
go
ahead
and
just
move
that
one
over
and
say
that
it
doesn't
have
to
be
groomed
you're
gonna
size.
It.
E
H
I
H
H
A
A
A
And
then
I
would
also
add
for
backends
and
DevOps
and
sysadmin
roles
who
want
to
know
how
Magento
few
ways
are
deployed
and
maintain
and
grow
so
I
mean
there
are
different
theories
of
of
need
for
each
one.
So
right,
it's
probably
a
good
I
I
would
say
that
so
that's
good
split,
yeah,
any
other
suggestions.
I'm.
Sorry,
oh.
H
A
Cuz
like
in
you
know,
core
framework
developers
do
need
to
know
like
what
react.
Router
does
how
it
does
it
they
need.
They
need
to
know
like
what
our
asynchronous
logic.
Edition
concept
is
how
we
are
adding
slices,
how
we
are
adding
action
implementations
slowly
as
you
progressed
through
the
store.
Those
are
fairly
advanced
concepts.
A
Rehna
develops
making
store
fronts.
Ideally
they
would
just
be
able
to
use
the
cool
modules
that
we
provide.
Oh
the
route
handler,
you
just
drop
it
in
a
link.
You
just
drop
it
in
and
even
upward.
Maybe
they
should
be
able
to
just
like
you
know,
adjust
that
by
adding
a
route
as
we've
seen.
People
do
that
evening,
but
then
the
sysadmin
just
needs
to
know,
do
I
use
p.m.
to
or
what
at
NASA
I
didn't
answering
those
questions
offline,
so
so
I
think
that's
a
reasonable
addition.
Oh.
H
H
A
Understood
so
what
you
can
consult
with
me
like
make
it
three,
you
mean
sit
with
me
and
just
say
like
instead
of
having
like
a
huge
guide
for
all
three
of
those
folks
just
be
like,
if
you
are
core
developer
core
framer
developer,
these
are
the
things
you've
probably
know
if
you're
just
doing
development
on
many
other.
These
are
the
things
you
should
probably
know
if
you're
doing
sysadmin,
just
like
don't.
H
A
D
A
A
A
So
the
most
sample
data
and
most
stores,
with
with
actual
image
data,
are
going
to
upload
images
in
a
really
large
format,
maybe
for
zoom,
apps
or
whatever,
because
Magento
automatically
resizes
and
optimizes
those
images
when
you
are
using
a
Magento
rendering
UI
when
you
are
using
the
Magento
block
to
use
a
PHP
call
to
insert
an
image
URL
what
it
does
at
that
time
is.
It
calls
the
controller
that
produces
a
unique
cached
URL
for
a
particular
version
of
an
image
conveniently
that
is
completely
unavailable
in
the
API
service
and
I.
A
Think
that,
given
the
conversations,
we've
had
and
I'll
link
a
couple
of
issues
in
this,
given
the
conversations
we've
had
with
back-end
and
with
ops
and
with
strategy,
they're,
probably
not
gonna-
add
it
to
the
API,
because
that
adds
a
layer
of
responsibility
to
the
API.
That's
you
know
I.
You
can
make
an
argument
that
it's
not
really
for
like
graph
QL
is
for
getting
the
data
not
for
aiding
you
in
doing
view
display.
A
So
if
we
were
to
say
like
get
me
an
image
and
then
put
an
argument
in
the
image
and
graph
QL
for
it
to
optimize
it,
that
would
be
nice
and
that
would
be
a
great
technical
solution,
but
if
it's
coming,
it's
not
coming
for
a
while,
because
they're
still
figuring
out
scope.
So,
let's
just
say
we
cannot
rely
on
the
Magento
back-end
to
optimize
these
images
for
42.3
point
up
or
even
in
the
immediate
future.
Instead,
we
have
two
choices.
A
We
either
accept
that
these
images,
which
are
90%
of
the
payload
of
our
site
and
destroy
our
lighthouse
score.
We
accept
that
they're
large
and
move
forward,
or
we
come
up
with
a
way
to
optimize
them
properly
and
I.
Don't
think
it's
acceptable
to
optimize
the
existing
sample
data
images
and
just
save
them
statically,
because
then,
in
a
demo
situation,
if
you
add
products
and
add
a
new
image
to
that
product,
it's
potentially
still
terrible.
So
we
really
want
this
to
actually
optimize
images.
A
D
A
Kind
of
have
these
options
that
we
suggested
and
I
think
escalating
with
the
API
teams
is
potentially
possible
to
say:
please
do
it,
but
I
don't
know
if
that's
gonna
happen.
My
thinking
is
that
we
would
write
a
middleware
with
with
upward,
that
is
to
say
that
we
add
a
concept
to
upward,
of
transforming
binary
streams.
A
Now
Paul
you
observed
recently,
and
we
I
don't
know
if
that
issue
has
received
enough
attention,
but
you
observe
recently
that
upwards
kind
of
bad
at
streaming,
even
like
the
favicon,
because
and
that's
because
I
deliberately
designed
upward
when
I
when
I
sort
of
came
up
with
the
idea,
is
that
oh,
this
just
manipulates
text.
It's
like
Union
extremes.
A
You
know
we
don't
have
to
think
about
any
of
that,
but
that's
becoming
clear
that
that's
not
really
sufficient,
I
think
there's
two
extra
things
means
add:
one
is
that
it
should
be
able
to
manipulate
hydrated
objects
as
long
as
they
can
be
serialized
like
JSON,
and
that
it
should
be
possible
to
deal
with
binary
data
intelligently.
So
we
need
to
add
these
concepts
to
upward
and,
although
I
think
it's
most
likely
given
the
relative
youth
of
that
codebase
and
the
you
know,
the
youth
is
an
idea.
A
Doing
it,
but
nevertheless
this
is
a
story
and
it
is
groom
a
bull
and
I
would
love
it
for
some
day
soon.
People
to
write
their
own
implementations
of
upward
or
suggestions
for
extension
to
the
spec,
so
I
would
welcome
questions
from
from
people
attending
this
on
on
what
you
would
need
to
participate
more
in
the
development
of
and
the
roadmap
for
upward.
F
A
It's
all
broke
so
yeah,
the
the
Express
middleware
sees
that
it
has
a
content
type
of
image/png,
but
because
it's
not
serving
a
literal
file,
I
think
Express
gets
cocky
and
adds
charset,
utf-8
and
Paul
suggestion
is
to
change
the
actual
data
type
that
we
send
to
Express
and
that's
an
implementation
change
and
up
for
Jas
I
actually
think
that
is
exactly
what
to
do.
We
would
just
need
to
again
thread
the
logic
of
the
three
types
of
data
we
can
deal
with.
A
You
know
JSON
text
and
binary
and
maybe
make
sure
that
at
the
moment
that
we
send
it
that
we
do
the
appropriate
buffer
encoding,
because
this
is
totally
a
good
fix,
but
this
doesn't
answer
the
overall
question
of
how
up
or
would
optimize
images.
It's
just
I
think
some
good
I
think
it's
some
good
context.
Let's
go
ahead
and
say
related
to
408
of
word
needs
to
gain
the.
F
A
Think
the
answer
is
no
right.
Now,
that's
something
we
can
iterate
on
I
think
if
a
business
user
emerges
to
say
like
well
Magento
optimizes
this
way
and
that's
what
I
need,
then
we
can
cover
that
for
now.
I
think
just
there's
a
sanity
aspect
to
this,
where
we
don't
do
any
resizing.
That's
just
these
images
can
stay
the
same
size
and
shrink
like
75%.
That's
what
we
would
do
I
would
just
add.
You
know
the
Express
middleware
for
live
VIPs
and
then
have
upward
thread
through
it.
Okay,
so
sizing
I
know.
A
This
is
tough
for
everyone.
I
would
definitely
size.
I
meant
to
do
this
this
week
and
got
interrupted
that
I
would
definitely
size.
This
is
a
five
and
the
only
reason
that
it's
not
larger
is
again
because
I
suspect
that
I'll
be
the
one
doing
it,
but
but
yeah
I
would
say
this
is
a
five
just
considering
both
the
tasks
have
to
include,
which
I'll
add.
D
A
Yeah
we're
at
time,
okay,
so
I'm
just
finishing
this
up
right
now,
add
resolvers
for
transformation
and
image
compression
two
strategies
and
implement
in
upward
jas
there
we
go
done,
sighs.
Okay,
we
were
done
with
the
room.
People
are
waiting,
we
don't
want
to
be
rude,
but
I
want
to
open
the
floor
quickly
for
any
questions
or
major
concerns
that
people
have
in
terms
of
grooming
sizing
or
what's
in
the
backlog
and
I
closed
and
reopening
the
issue.