►
From YouTube: Magento MSI Open Demo. June 15, 2018
Description
Today’s agenda:
-) MSI release updates. Burndown chart
-) "Only X left" functionality
-) Different fixes from Riccardo Tempesta
-) MSI-beta installation updates
A
B
Okay,
let's
start
as
I
talked
on
previous
demo,
we
are
going
to
have
a
mistake,
but
I
released
at
1920
June,
so
general
updates
from
us.
During
this
week
we
may
processor
technologists
almost
all
pull
request
from
Perugia.
Also
we
fix
that
all
will
fail
at
up
a
functional
past,
but
some
of
the
requests
you
what
matters
with
some
fixes.
Also
we
work
it
on
valid
functional
tests,
and
now
we
have
only
one
fail:
a
test,
I
skipped
it.
This
test
is
not
related
to
some
problem
dysfunctionality.
B
B
C
Versailles
Road
map,
so
here
you
you,
for
example,
can
see
that
all
the
schools
and
all
the
features
which
we
we
going
to
implement
in
the
scope
of
the
MVP
functionality
of
MSI
are
finished
and
delivered.
So
currently
we
have
actually
the
burndown
if
open.
So
everybody
can
come
on
Zen
hub
to
MSI
project
and
see
and
see
they
burn
down.
So
you
can
go
to
following
the
link,
then
hop
on
a
side
board
from
the
wiki
and
in
the
report.
Just
choose
the
burn
down
report.
C
C
Imagine
the
contribution
day
in
Leipzig,
and
we
expected
that
these
developers
will
help
us
to
finalize
and
finish
our
backlog
and
make
it
make
the
progress
get
to
the
zero
opens
for
pouring
opponents
and
to
finalize
the
Coco
for
MSI
MVP.
For
us,
it
is
really
symbolic
that
we
around
the
project
year
goal
actually
run
it
in
the
same
place.
We
run
it
in
Depok
before
meet
Magento
German
during
the
hackathon.
C
C
This
is
all
from
my
side,
I
believe
it
will
be
more
interesting
update
from
from
Alessandra
and
from
Ricardo.
We
will
show
you
the
real
real
demo
and
the
the
stories
which
were
implemented
with
examine
the
Constitution
Day
in
corrosion
and
after
that,
well
volodymyr
completes
key.
We
will
describe
you
the
process
of
religion
and
the
metadata
package
which
won't
be
released
for
component.
B
A
Hello,
yes,
let
me
let
me
show
you
what
happens
when
we
we
use.
We
enable
the
threshold
functionality.
We
currently
have
this
just
duffel
bag
with
10,
with
10
quantities
and
I
already
made
an
order
and
ordered
five
of
them.
So
I
have
five
less
left
in
stock.
You
can
see
here
the
reservation
that
reserves
the
fired
quantity
for
this
duffel
bag.
Let
me,
let
me
show
you
this
thing
in
the
catalog
list.
A
A
A
A
Let's
see
what
happens
here
and
the
only
left
message.
Well,
we
have
a
regression
here,
the
the
is
counted
twice,
so
we
expected
to
have
only
three
left,
but
we
have
only
one-
and
this
is
a
regression
introduced
by
MSI
itself,
because
in
the
code
that
counts
the
the
quantity
left
for
this
product,
we
we
already
take
into
account
them
in
quantity,
and
then
we
show
you
this
legacy
code.
A
A
A
A
And
now
we
don't
see
the
message
because
we
have
the
baqar
that's
enabled,
so
this
correctly
applies
with
logic
and
let's
go
to
the
invention,
inventory
and
remove
the
back
orders
and
save
the
product.
What
we
expect
now
is
to
see
again
the
message
this
time
with
the
correct
quantity
which
is
3,
remember,
was
10-5
reserved.
A
A
B
Our
next
presenter
is
Ricardo
during
he'll
few
last
week's
regard
to
create
a
lot
of
requests
and
two
loops
like
he
became
sour
top
contributors
of
last
month
at
what
is
interesting.
We
he
fixed
it
box
not
only
from
a
side
side.
She
created
a
request
to
Magento
pore
and
looks
like
we
fix
that
generally
giantesses
problem,
so
Ricardo,
please
fair
and
fairest
us.
D
Okay,
can
you
see
my
screen
just
okay?
So,
yes,
I
created
the
punch-out
for
request
of
a
we
start
from
the
most
oppressed
ones,
so
I
think
we
can
start
from
yeah
sure
just
roll
in
front
of
this
one,
but
basically
this
this
was
a
quite
simple
pull
request,
because
what
happen
is
that
we
we
had
some
mass
in
the
API
names
because
usually
in
Magento
blck
we're
not
using
similar
name
to
reduce.
D
He
told
us,
and
here
I
had
to
change
a
lot
of
so
basically
this
was
just
a
code
monkey
for
request,
but
I
think
is
quite
interesting
and
what
it
is
called
actually
were
run
English.
This
pull
request
is
that
we
are.
We
are
the
part
inside
he
in
magenta
work.
That
Palais
was
explaining
before
so
I
discovered
that,
depending
on
the
light
and
in
code,
you
are
using
when
coding
your
classes,
you
may
have
problems
by
finding
the
API,
so
this
should
be
fixed
in
my
request
that
I
did
in
accord.
D
D
Yes,
another
one
burning
pressing
was
this
one,
so
there
was
an
issue
in
which,
that's
probably
you
know
so
when
you
rename
a
website
in
MSI,
because
basically,
these
breaks
all
degree
it's
for
for
this
sources,
and
that
is
core
basically
a
problem
for
data
consistency,
because
the
website
code
was
not
updated
in
every
a
table.
So
because,
as
you
probably
know,
we
are
not
using
foreign
keys,
so
we
had
no
control
over
changes
in
other
tables.
D
D
So
basically,
we
created
around
plugin
for
the
website
and
when
is
this
a
it?
Ok,
this
is
the
right
foot.
So
we
check
the
previous
code.
We
check
the
new
code
and
we
update
the
state's
on
our
website
new
table
and
that's
it.
Of
course.
We
had
to
use
an
around
safe
plugin
instead
of
on
server
or
before
an
after
planning,
because
we
had
to
know
the
previous
state
and
the
state
after
the
same
and,
of
course,
all
the
integration
just
connected
could.
D
F
C
Rely
rely
on
the
natural
identity,
so
we
rely
on
a
website
code,
but
not
I.
Don't
remember
the
table
name
actually.
Is
you
remember,
and
actually
we
start
with
a
single
issue
like
update
in
natural
identity,
for
example
a
product
like
a
date
and
ask
you
so
actually
here
was
an
issue
with
a
updating
website,
Kotick
sure
the
brake
linkage
between
the
website
and
the
stock.
C
E
D
D
And
yeah,
because
the
polling
why
she
was
the
duplication
of
the
website,
because
when
you,
when
you
were
creating
when
you
were
updating
the
website
code,
basically
the
system
was
creating
the
new
entrants
that
disabled.
So
that
was
a
problem,
and
since
this
Center
it
was
not
connected
to
any
real
website.
D
The
website
repository
was
giving
them
whenever
well,
when
we
first
triggered
by
the
provider
of
the
green
tables,
that
of
the
issues.
So
we
are
ways
to
fix
it.
One
was
to
just
a
moment
exception,
but
was
not
a
great
idea.
So
we
decided
to
make
this
kind
of
synchronization
between
the
website
and
leave
devil
itself.
D
C
Interruption
can
I.
Please
ask
you
to
show
you
your
pool
request
with
the
mass
delete
operation.
I
believe
this
work
would
be
interested
to
intone,
because
we
don't
have
similar
similar
API
to
the
poor.
So
not
the
one
and
I'm
in
one
rest
must
delete
operation
and
that
you
decided
to
use
post
instead
of
so.
D
If
I
delete
was
not
accepting,
of
course,
a
body
well,
actually
it
is
not
a
forbidden,
but
I
think
it's
not
best
practice
and
it
was
a
month
delete
operation.
So
we
couldn't
rely
on
a
single
parameter.
We
could
eject
accepted
URL
and
what
I
decided
to
do
is
to
create
a
new,
a
new
call,
because
the
previous
one
was
simple.
For
example,
a
stick.
D
C
Yes,
so
the
main
reason
is
the
mass
operation
for
the
living,
because
currently
in
magenta,
all
the
way,
a
web
api
which
preceded
delete
method
actually
apply
for
the
single
entity.
That's
why
the
ID
of
this
entity
is
passed
as
a
parameter
as
a
part
of
the
uri,
but
as
soon
as
we
apply
mouse
operation.
C
E
D
E
Okay
and
by
the
way,
II
Jean,
so
did
you
participate
in
the
discussion
of
this
item
because
it's
it
has
intersects.
There
is
about
API,
so
I
understand
that
it's
probably
the
difference
is
that
you
are.
The
repository
operation
is
a
key
persecute
at
once.
Hopefully
right
so
it's
only
one
operation,
four
thousand
entities,
or
do
you
call
the
repository
multiple
times
yeah
the
repository
are
so
small
or
same
operation
multiple
times.
C
E
Our
story
of
mass
of
bulk
api
is
because
we
had
bulk
API
for
multiple
operation,
calls
in
syndication
request,
and
this
adds
a
single
call
for
multiple
operations,
but
I
think
we
also
discussed
the
design
for
such
API
in
that
epoch
of
bulk
API
si
Jin
right
am
I
mistaken
and
it
was
described
I
saying
there
just
cause,
but
I
don't
see
how
it's
intersects.
So
there
we
were
talking
more
efficient
work
where
you
have
requests
which
of
course,
just
one
entity
and
you'd
like
to
send
a
bulk
of
entities.
E
This
action
informed
the
produced
separate.
So
we
have.
We
have
two
types
of
bulk
operations.
One
one
part
about
reparation
was
implemented
about
API
epoch,
where
you
call
RS
and
point
to
cooperation
multiple
times
right
and
this.
This
pipe,
which
is
implemented
here,
is
where
you
call
operation
once
with
multiple
entities
right
yeah,.
C
E
I,
remember
that
we
discussed
both
operations
and
I
thought
that
we
discussed
the
design
of
API
endpoints
for
both
operation,
but
I
might
be
mistaken.
It
was
so
so
we
discussed
that
first
requires
framework
support
and
that
should
be
implemented
and
that
had
had
been
implemented
and
second
does
not
require
any
special
framework
support
like
this
type,
which
we
see
on
the
screen
it's
already
supported,
and
if
you'd
like
to
send
more
requests,
you
just
use
well,
if
it's
supported
it
is
supported
in
the
form
where
you
have
where
you
have,
but
you
use
post-operation.
E
So
it's
a
somewhat.
So
it's
a
not
problematic.
It's
a
good
implementation.
It
will
work
great.
Just
one
thing
that
might
some
arrests
ID
list
might
not
like
the
fact
that
it
uses
such
design
requires
using
post
operations
for
any
for
any
entity
and
I
think
we
discussed
it,
but
I
again,
I
might
be
mistaken
anyway.
This
looks
good
and
we
can
discuss
it
later
on
grooming,
especially
on
bulky
guys
yeah.
C
C
E
C
E
I,
don't
have
strong
opinion
that
we
should
implement
it
this
way,
but
this
is
interesting
topic
and
they
haven't
discussed
it.
I
had
a
separate
call
with
Ricardo
and
woods
ever
from
community
wants
to
join
this.
Let's
discuss
it.
I'm
sorry,
if
I
miss
the
grooming,
where
you
discussed
it
but
I
think
it
makes
sense
to
you
know
we'll
do
final
discussion
and
decide
on
how
we
add
such
operations
in
the
future.
E
D
You,
okay!
Yes,
let's
go
back,
not
this
one,
okay,
and
this
is
probably
one
of
the
most
interesting
from
my
point
of
view,
and
it
is
I
think
last
one.
So
basically
we
had
a
problem
named
aside
because,
as
you
probably
know
when
you
use
the
legacy
API,
the
deities
for
a
stock
are
going
to
to
be
connected
with
the
the
foss
foss.
D
Basically,
what
we
had
is
that
we
had
all
the
products
connected
to
the
full
source,
even
if
we
wanted
something
different
so
for
us
connected
to
other
sources,
and
the
most
annoying
part
was
actually
that
the
source
item
entity
was
created
and
then
deleted.
So,
basically,
you
had
the
incremented
e
going
every
time
you
save
the
product
incrementally
in
the
table,
so
we
had
to
find
a
solution,
because
this
was
a
kind
of
saving
section
again
because
we
were,
we
were
recognizing.
The
legacy
legacy
update
the
false
words
and
vice
versa.
So
it
was.
D
D
D
E
E
D
B
F
Okay,
so,
as
you
may
already
know,
we're
not
going
to
match
all
the
msi
code
to
Magento
mainline
repository
and
we
are
going
to
distribute
inventory
models
as
separate
set
of
extensions
and
to
provide
simple
path
to
simple
installation
of
all
these
models.
We
develop
at
a
single
additional
tool,
which
is
actually
composer
plug-in
that
allows
to
install
and
update
all
inventory
models.
So
what
this
module?
Actually
please
do
as
I
saw.
F
You
say
this
is
composer
plugin,
which
will
be
added
as
a
dependency
to
magenta,
open
source
and
magenta
commerce
method
packages
and
will
be
included
in
magenta
2.3
and
eventually
it
will
be
included
at
some
alfalfa
or
better
release
of
magenta
2.3.
But
for
now
it's
a
standalone
composer
package,
so
it's
called
magenta
invent,
inventory,
composer
installer
and
what
this
plugin
actually
do
it
finds
detect,
is
magenta
already
installed
or
not.
It
does
magenta.
We
have
predefined
it
set
of
models.
F
F
F
F
F
F
F
F
F
E
F
F
E
I
started
to
answer
the
question
in
chapter
so
I
want
to
clarify
there
is
you
cannot
say
that
they
will
not
be
in
core.
There
is
a
lot
of
confusion
now
between
composer
and
gates,
and
many
people
saying
that
git
repository
is
magenta.
Core
git
repository
is
not
magenta.
Core
is
just
a
git
repository
that
contains
at
least
a
subset
of
Magento
modules
right.
The
important
thing
for
merchants
is
the
packages
that
are
on
composer
package,
not
in
git
and
the
meta
package.
E
E
So
that's
a
qualification
and
and
I
have
a
couple
more
questions.
Ok,
so,
first
this
tool,
I
have
a
couple
questions
for
implementation,
but
even
before,
even
before
we
discuss
implementation,
it
makes
sense
to
have
such
tool.
Generic
I
wouldn't
put
a
dependency
on
inventory
here,
because
we,
if
we
follow
this
model
in
future,
we
would.
This
would
be
the
way
we
discussed
multiple
times
how
we
will
be
releasing
market
multi-source
inventory,
and
ideally
this
should
be
the
way
how
we
will
release
or
our
products
in
future
our
breaking
changes
in
future
with
parallel
implementation.
E
So
this
tool
will
make
sense.
It
will
make
sense
to
use
it
in
future
right
so
I
wouldn't
call
it
inventory.
Composite
installer
I
would
think
about
a
more
generic
name
and
not
focus
only
multi-source
inventory
right,
so
naughty.
Sauce
inventor
is
the
first
project
to
release
this
way,
but
we
want
to
use
it
in
future
too.
So
again,
I
don't
know
about
the
lot
of
details,
but
I
would
at
least
not
call
it
inventory,
composure
and
style
if
it's
a
tool
or
special
plugin
right.
E
F
Right,
but
for
now
just
to
have
simple
approach
to
religion
and
maintain
all
the
things
it
actually
have.
Two
responsibilities
of
responsibilities
is
empowerment,
all
the
models
and
disabling
disciplines
for
the
that
users
that
applied
magenta
and
the
second
responsibility
is
to
provide
meta
package.
So
all
the
people
may
just
depend
on
the
single
composer
package:
okay,.
E
Again,
I
don't
want
to
dive
deeply
into
that.
We
can
discuss
separately,
but
it
makes
sense
to
separate
the
generic
part
from
inventory
specific
part
like
inventive
meta
packaged,
okay,
but
the
tool
that
the
pivots
are
Composer
plugin
and
if
you
decide
to
keep
it
a
composer
plugin,
it
makes
sense
to
have
it
generics.
E
F
E
Updates
of
magenta
okay,
so
in
that
case,
if
it
uses
magenta
mechanism
for
disabling
modules
and
not
users,
composite
mechanism
of
just
non,
not
installing
modules,
why?
Why
do
we
do
it?
So,
what's
the
benefit
of
doing
it
on
composer
level
as
a
plug-in
to
compose
that
not
not
in
Magento
application
of
configuration?
There
are
something
like
that.
F
E
Okay,
let
me
discuss
it
with
all
teams
called
him
the
ideal.
A
cloud
infrastructure
should
not
limit
you
in
a
way
that
you
install
disable
Moodle.
So,
basically
it
should.
It
should
not
dictate
at
all.
Let
me
double
check
that
my
understanding
was
that
it
wouldn't
interfere,
but
if
you
say
that
interferes
that.
E
Run
this
command?
Yes,
now:
okay,
working
this
fossil
fuels
in
the
assembly,
the
the
different
difference-
I
didn't
run
it.
But
okay,
it
sounds
a
bit
strange
to
me.
I
will
figure
out.
Ideally,
ideally
cloud
should
not
enforce,
should
not
force
you
enable
or
disable
any
models,
because
you
control
code
base
and
route.
E
E
Suggestion
yeah,
so
it
looks
like
this
demo.
Sometimes
they
go
short.
Sometimes
we
have
a
lot
of
discussions,
so
my
only
suggestion
is
to
for
every
week
to
review
the
agenda
and
if
it
there
will
be,
if
we
can
see
that
there
will
be
lot
of
discussion
to
make
demo
45-minute
of
one
hour
and
that's
it.
Thank
you.
Thank
you.