►
From YouTube: Community Engineering Hangouts - MSI
Description
Community Engineering Hangouts.
The aim of these hangouts is to update the community on all our progress and demo some new tools and features. For this live stream we have the following agenda.
1. News and updates from the Community Engineering team,
2. MSI demo from contributors and the MSI team,
4. Live Q&A section,
During this hangout we will update you on the community engineering progress over the month of October plus we will be meeting some of the core contributors to the MSI project.
Feel free to join in, comment and ask questions. The aim of these hangouts is to provide a platform for Magento to give the community regular updates but also for the community to give feedback to Magento.
For any more information feel free to reach us at engcom@magento.com
A
Cool
all
right
we
are
live.
This
is
the
community
engineering
amateur
team
in
the
engineering
hangout.
This
is
MSI's
specific.
We
are
going
to
have
a
great
evening
or
morning
or
afternoon,
depending
on
your
kind
dog,
and
we've
got
some
great
topics
that
talk
about
MSI
and
we've
got
some
actual
real
live
live
then
you
can
use
them
and
buy
stuff
from
them.
Demos
or
MSI,
and
we've
got
a
lot
of
our
contributors
here
to
get
their
opinions
and
their
feedback.
A
Is
you
know
we
are
squashed
over
Fest,
which
happens
every
year
and
the
challenge
this
year
was
five
for
requests
for
10
issues
or
combination
of
both
and
then
in
the
end,
you
will
get
a
special
squashed
public
bath
feature
and
I'm
happy
no
rounds
that
we
have
to
seven
people
who
I've
been
contacting
in
the
last
couple
of
weeks
trying
to
get
the
information
about
where
December
t-shirts
do
and
that
sort
of
stuff.
But
these
people
will
begin
explore
still
with
their
futures
and
yeah.
A
We
thank
you
so
much
for
taking
getting
involved
and
taking
your
time
to
continue
and
make
Magento
healthier
and
a
better
place.
Over
the
whole
month
we
had
796
for
requests
created
across
all
our
repositories
and
which
is
fantastic,
and
that
was
from
235
contributors.
Those
stats
are
staggering
and
I
still
struggle
to
contemplate
how
many
people
and
how
many
progress.
A
That
is,
it's
it's
pretty
amazing
and
and
one
of
the
big
things
one
of
the
big
projects
we've
been
running
for
a
while
now
is
MSI
and
because
it
is
on
its
way-
and
pretty
close
angle
will
correct
me
later
on
about
this.
But
we
thought
we'd
get
everyone
together.
It's
been
involved
in
the
project
on
a
few
of
the
people
being
involved
in
project,
share
their
experience
and
give
you
a
few
tips
and
tricks
if
you
want
to
start
using
and
getting
involved,
so
our
project
yeah,
so
we've
gathered
quite
a
few
people
get.
A
So
let's
have
a
quick
round
of
introductions.
So
I'll
start
with
myself.
My
name
is
David
and
I
have
nothing
to
do
with
Emma.
Sorry,
I
will
take
no
credit,
but
I
am
involved
with
community
engineering.
So
you
are
interested
in
getting
started
with
contribution,
feel
free
to
reach
out
me
and
slag,
or
in
over
Twitter
and
I
will
do
my
best
to
help
you
out
and
get
you
involved
with
contribution.
B
A
C
B
D
So
I'm
glory
Krell.
You
may
see
me
over
in
dev
Docs
I
work
on
the
documentation
side
of
Magento
in
dev
Docs,
as
well
as
the
merchant
admin
guides.
I
pretty
much
touch
every
project,
but
I
am
100%
focused
on
community
engineering
and
I've,
been
working
on
all
of
the
documentation.
You've
been
seeing
in
the
wiki
and
abducts
awesome.
E
This
is
my
kitchen
I'm
based
in
our
office
in
Austin,
and
it's
oversubscribed
right
now.
So
desks
are
very
hard
to
come
by,
but
I'm
the
product
manager
on
MSI,
so
I
have
kind
of
a
long
history.
On
this
project
we
initially
tried
to
develop
this
internally
for
a
while,
before
it
became
a
community
project
and
I
know.
It's
great
Iger
mentioned
all
the
contributions
we've
received
and
we're
very
excited
for
that.
E
F
Hey
everybody,
not
a
lot
of
you.
Some
of
you
probably
had
a
chance
to
work
with
me
already,
but
I've
just
recently
joined
the
magenta
engineering
community,
community
engineering
team
and
I
am
coordinating
all
the
separate
special
little
projects
and
big
projects,
including
MSI.
But
please
don't
confuse
me
with
egomania
here,
because
he
actually
does
the
actual
work.
F
A
G
A
H
So
well,
you
know
my
name
is
Ricardo.
The
best
I
am
the
CTO
I
mean
specialist,
am
I
an
MSI
contributor,
I
think
my
very
first
contribution
of
MSI
was
well
actually
a
few
months
ago.
So
I'm
not
a
TMS
I
can
very
beginning
but
I'm
enjoying
them
site.
Pretty
much
I
think
I'm
quite
tight
a
contributor
on
an
aside.
Oh.
A
I
A
C
A
E
B
So
actually,
good
news
for
us
that,
yes,
not
yesterday,
but
the
day
before
yesterday,
we
our
final
package,
which
gonna
be,
which
is
gonna,
be
bundled
as
a
part
of
magenta
to
this
videos
Oh.
So
we
already
up
and
running
and
that's
why
today
I
even
closed
the
milestone
to
you
know
I
get
hub
so
because
we
are
not
accepting
any
changes,
any
pull
requests,
even
with
the
bug
fixes
for
milestone,
3.
B
So
every
single
everything
we
already
have
going
to
be
delivered
to
to
as
a
part
of
magenta
to
defeat
at
all,
and
it's
a
good
news
for
us
that
heaven,
the
new
approach
of
the
references,
so
magenta
will
have
not
a
streak
reference
to
MSI
modulus.
So
we,
as
you
aware
regarding
the
composer,
we
have
the
reference
with
the
with
the
carrot,
and
actually
it
means
for
us
that
we
can.
B
We
can
have
the
independent
lifecycle
of
MSI
releases
and
the
release
in
the
MSI.
We
are
not
affecting
the
magenta
releases,
so
the
main
package
of
magenta
should
not
be
recomposed.
That
actually
means
that
we
can
keep
our
temp
and
the
release
MSI
as
as
frequent
as
we
want,
and
we
already
already
plan
the
milestone,
3
and
the
actually
I
believe
will
present
the
scope
of
the
milestone
3
closer
to
the
end
of
the
of
the
today's
dream.
E
Know
I
mean
we
will
have
on
this
hangout
as
well
some
demos,
the
great
parties,
will
have
many
of
the
contributors
doing
the
demo,
so
people
will
get
to
see
the
features
internally
its
what
people
are
not
aware
of.
So
on
the
magenta
side,
we've
been
demoing.
Msi
2
are
like
our
support
team,
our
sales
teams,
all
our
internal
teams,
that
will
need
to
be
ready
for
the
release
and
everybody's
very
excited
about
the
feature
set
and
the
capability
within
MSI.
E
Think
just
the
most
exciting
thing
is
the
sheer
number
of
people
that
have
contributed
and,
like
I
said
at
the
beginning,
we
just
didn't
really
know
how
this
would
go
I.
We
had
an
idea
when
we
first
started
in
Leipzig,
we
had
to
pitch
the
product
and
try
a
pitch
the
project
and
try
and
get
you
know
developers
interested
in
it.
So
for
me,
that's
the
most
exciting.
It's
just
that
we
had
so
many
people
contribute
and
and
in
a
sustained
contribution
for
people
who
have
been
with
the
project
for
a
long
time.
E
I
think
one
thing
we've
seen
is
once
they
get
involved
and
find
an
area
that
interests
them
that
it's
something
that
they
can,
they
can
really
work
on
and
that's
one
of
the
great
part
of
community
engineering
projects
is
devs.
Have
the
ability
to
you
know
pick
where
they're
going
to
contribute
on
stories
and
features
that
either
they
have
a
particular
skill
or
they
find
the
most
interesting.
A
I
Thank
you
so
I
prepare
a
quick,
quick
review
and
share
on
my
screen
right
now.
Okay,
so
this
is
how
we
implemented
magento,
2.3,
plus
MSI,
and
go
live
yes,
we
are
go
live
about
one
week
ago,
so
it's
working
proof
that
everything
is
ok.
This
is
the
company
who
accept
our
our
solution,
for
the
business
needs
that
we
can.
We
can
use
MSI
in.
I
We
started
with
alpha
version.
We
are
on
bettas
version
with
Magento
and
release
candidate
with
MSI.
So
this
is
a
toast.
Toast
is
a
famous
Spanish,
jewellery,
accessories
and
fashion
company
based
in
Spain.
They
have
about
600
stores
worldwide,
but
I
focus
on
Poland
market
and
quick
numbers.
They
have
free
websites,
Poland,
Slovakia
and
Czech
Republic.
I
F
I
120
categories
and
what
is
more,
most
important:
we
have
over
1.5
million
products
quantities
during
import,
so
it's
a
great
number
and
how
it
performed
with
Magento,
2.3
and
MSI.
So
this
1.45
million
products
quantities
import
takes
about
2
hours,
so
approximately
we
have
350
quantities
per
minute
using
native
API.
I
So
it's
a
it's
a
great
for
our
perspective.
For
our
client
perspective,
it's
it's
great
all
imports
its
on
demand
and
takes
place
almost
during
all
day,
all
weeks
and
what
it
most
important.
With
that
it's
it
work
without
front-end
performance
impact.
We
have
a
separate
machine
that
import
all
over
and
over
and
over.
We
use,
of
course,
my
favorite
declarative,
DB,
schema
and
I
think
a
PR
request
and
we
take
benefits
from
2.3
speed
improvements.
I
I
Yes,
this
is
the
life
side
with
life
view
of
product
grid,
with
sellable
quantity
set
on
every
Apple
product
on
this
grid.
So
this
is
working
proof
that
everyone
who
participate
in
contribution-
it's
it's
makes
sense,
because
this
is
a
life
side
with
with
life
chance
of
every
product
quantity-
and
this
is
a
great
of
course.
We
have
free
aggregates
representations
of
stocks
in
each
country.
Of
course,
I
can
show
you
additional
columns,
quantity
per
source
and
ok,
there
is
it.
You
can
see
right
now.
I
Every
source
is
representing
every
every
physical
warehouse
in
Poland,
in
Czech
Republic
and
in
Slovak.
So
you
can
see
there's
a
lot
of
a
lot
of
sources
and
a
loaf
of
stocks.
You
can
go
to
the
product.
Details
and
I
can
show
you
impression
from
from
representing
of
each
each
each
quantity
in
each
sources
for
particular
products.
So
it's
it's
works
right
now.
It's
live
proof
that
everything
will
be
good.
So
thank
you
for
attention.
You
questions
or,
regarding
our
experience,
feel
free
to
ask
me.
I
have.
I
It
is
because
our
calculation
based
on
main
source
in
particle
warehouse
and
these
algorithms
calculate
sin-
it's
not
not
so
complicated,
but
it's
very
sophisticated
because
we
have
to
calculate
each
other
sources,
excluding
main
warehouse
and
check
that
a
quantity
in
that
sources
is
a
greater
or
equal
number
specific
number.
And
if
yes,
we
can
check
that
this
is
this
canvas,
so
it
is
available
for
clients
and
can
be
shown
on
a
front-end.
So
we
have
to
change
something
in
in
that
way.
B
I
Our
implementation,
our
our
modules
in
MSI,
it's
it's,
it's
separated
to
specific
models
that
I
don't
know
how
to
say
it
at.
It
was
simple
because
we
I
I
know
where
to
exactly
find
this
piece
of
code.
This
is
very
into
it
intuitive
to
manipulate
with
source
calculation.
So
we
we
just
changed
some
SQL
and
that's
all
it's.
It's
works.
A
I
As
I
said
before,
I
very
proud
of
it
that
I
can
be
part
of
this
project
and
I
can
contribute
to
it
and
after
it,
I
can
implement
it
in
only
on
life,
before
official
release
and
yeah.
It's
it's
it's
a
great
feelings
about
it,
one
of
the
reason
that
we
started
it.
It's
because,
hey
hey,
we
have
a
one
guy
who
already
contributed:
let's
try
it
yeah.
B
E
I
A
Cool,
thank
you
so
much
for
that
and
if
you
have
any
questions,
if
you
want,
if
you
have
questions
about
it,
please
add
them
to
the
chat
and
we
will
make
sure
we
get
them
to
him
before
the
air
and
but
I
think
it's
good
to
move
on
to
another
kind
of
use
case
and
if
therefore,
we
wanted
to
talk
with
Vadim.
What
my
name
is
gonna
share
a
little
bit
about
how
MSI
and
and
the
b2b
world
can
work.
A
G
Yeah
this
can
you
see
my
screen
yeah
yeah,
so
let's
talk
about
project
we
just
started
with,
so
it's
not.
Finally,
so
I
cannot
show
you
any
live
presentation,
but
here's
some
some
basic
components
we
use
in
this
project
is
Commerce
2.3
version
with
b2b
page
builder
and
of
course,
Moochie
sauce
inventory.
G
So
I
will
just
show
you
a
little
bit
about
the
requirements
behind
this
project
and
the
decision
for
us
to
choose
MSI
as
a
solution
for
this
requirements,
which
is
probably
not
the
the
first
thing
you
would
think
this
is
MSI
is
the
feature
for
but
we'd
ride
it,
and
it
was
a
good
deal
so
far.
So
the
customer
presenters
wireframe,
which
is
looking
like
this,
is
some
kind
of
product
detail
page
it's
it's
a
b2b
page
at
all
so
tall.
G
So
you
can
see
here
there
are
configurable
products,
but
the
customer
can
buy
many
many
kinds
of
this
product
because
as
some
kind
of
dealers
who
buying
here
from
from
the
merchants
so
and
at
the
first
look,
it's
it's
quite
easy
just
to
display
the
configurable
product
and
another
way
we
have
sizes
here
and
colors
on
the
other
side.
But
the
requirement
was
also
that
we
need
to
represent
different
the
merchants
call
it
availability
groups.
G
This
would
mean,
for
example,
here
we
have
a
representation
of
the
same
SKU,
but
it's
it's
from
different
words
for
surveillance
or
one
is
immediately
available
and
another
one,
just
in
a
few
weeks,
for
example,
so
the
same
or
we
have
on
the
cart
or
check
out
parts.
So
we
also
have
to
get
representation
of
availabilities
group
and
what
was
shown
this
mock-ups
the
first
time
to
our
developers.
G
They
start
to
think
about
how
to
how
could
our
solution
look
like,
and
they
were
lots
of
great
ideas
and
at
least
a
very,
very
big
estimation,
and
after
so
I
told
them
and
show
them
how
MSI
works,
and
this
this
was
leading
into
a
some
kind
of
from
very
low
estimation,
at
least
because
our
solution
is
currently
look
a
little
bit
like
this.
So
we
we
have
different
sources
and
in
the
real
world
the
merchant
has
only
one
warehouse,
but
it's
splitted
into
different
availability
groups.
G
There
are
currently
four
and
in
this
drawing
only
but
does
not
matter,
and
we
used
native
functionality
of
an
assign
order
to
aggregate
some
main
stock
and
also
we
create
a
stocks
which
are
representing
each
and
variable
ability.
So
in
the
end
it
ends
up
in
aggregated
stock
of
our
availability.
So
we
can
use
all
all
the
websites
which
are
up
to
90
in
this
project.
G
They
use
the
main
stock
and
we
can
use
a
lot
about
all
the
default
functionality
of
Magento.
Like
is
the
product
saleable
at
all,
or
should
I
display
it
in
the
catalog
page,
and
so
on,
works
like
like
all
the
time,
because
it's
enough
if
this
product
is
available
in
any
of
this
availability
groups,
and
then
we
introduced
a
completely
new
type
of
sales
channel.
So
in
the
MSI
scope,
probably
I
need
to
say
website
is
a
size
Channel,
and
this
is
the
default
sales
channel.
G
We
have
there
and
to
introduce
a
new
type
of
sales
channel
recorded
availability
group
because
it
was
the
language
of
the
merchant
and
we
assign
for
availability
groups
to
our
for
availability
stocks,
for
example
in
the
in
the
back
end
of
MSI.
If
you
know
there
was
normally
just
sales
channel
and
websites,
and
now
we
have
also
availability
group,
there's
also
a
pretty
cool
experience
for
us,
because
I
was
involved
into
a
country.
I
was
contributing
to
MSI.
G
So
I
know
that
this
pretty
cool
stuff
and
easy
to
extend
and
now
guys
from
our
team
who
never
worked
with
MSI
did
this
implementation
here
and
they
were
that
excited
that
it
was
at
least
only
a
50%
of
the
estimated
time.
So
pretty
cool,
so
that's
it
from
my
side.
So
far,
I
hope
it
was
clear.
Any
questions
I.
A
F
A
Than
actual
you
know,
so,
I
love,
I,
love
them
thinking
outside
the
box
like
this
is
the
best
way
and
I
have
a
question
more
about
your
own
involvement
and
everything
new
you've
been
heavily
involved
from
the
beginning.
As
far
as
I
remember,
what
were
you?
Why
did
you
get
involved,
and
why
did
you
stay
involved?
A
G
I
think
it
was
happened
by
accident.
If
I
can't
say
it's
also,
it
was
just
part
of
the
hackathon
and
in
Leipzig
and
then
there
were
some
guys
like
Igor
and
Max
and
they
told
something
about
ejecta
contributing
instead
of
doing
some
stuff
in
an
hackathon
and
I
I
thought
sounds
interesting,
so
I
I
joined
joined
this
group
and
then
I
figure
also
out
that
eager
and
all
the
other
guys,
also
speaking
Russian,
which
was
much
easier
for
also
communicate.
G
That
was
also
I
think
a
good
start
for
me
yeah,
but
at
least
we
are
still
in
there,
because
it's
a
really
interesting
project
and
at
least
I,
think
Ricardo
will
told
you
a
little
bit
about
what
is
behind
this
project
and
what
are
the
big
part
here
and
I
learned
that
much
and
so
short
time.
So
it's
just
virtus,
so
it's
learning,
I
think
I
think
it's
learning
it
cool.
A
G
Of
course,
since
I
had
to
adhere
to
use
MSI
in
order
to
fulfill
this
requirement,
only
I
just
sent
eager
there's
some
of
the
screenshots.
You
already
saw
right
now
and
thought
so
my
idea
is
to
use
sales
channels
additional
type
of
sales
channels
in
order
to
represent
this
availability
groups,
and
here
you
said
that
good
work
should
work
so
yeah.
A
G
E
I
just
wanted
to
say
one
thing:
it's
interesting,
so
ideas
like
what
he's
described
here,
it's
great
as
well
to
get
that
feedback
from
the
community.
So
not
just
you
know,
code
contributions
or
Doc
contributions,
but
we
have
so
many
people
in
the
community
that
are
working
with
merchants
on
a
daily
basis
and
they're
able
to
give
us
a
real
frontline
perspective
on
what
the
future
shet
set
should
do.
A
You
can
get
that
feedback
cool
all
right
awesome.
Thank
you!
So
much
buddy
yeah!
If
you
have
questions
for
ludie
when
you're
watching
this
feel
free
to
drop
them
in
the
chat,
come
through
get
them
over
Q&A
section
next,
if
his
microphone
is
working
now,
let's
hope
it
is
we're
going
to
move
over
to
Alex.
Who
also
has
an
MSI
story
that
we
would
like
to
do.
A
C
A
C
C
Because
that
project
have
a
lot
of
customization,
it
was
first
point
so
existing
solutions
that
we
checked
was
updated
not
about.
It
was
about
one
one
three
times
per
year,
so
it
was
July
with
two
three
versions
of
magenta,
so
we
can't
use
as
a
new
community,
new
versions
of
magenta
and,
of
course,
and
because
the
MSI
is
a
core
solution
and
develop
it
by
by
community,
and
it
looks
already
good
when
we
when
I
review
it
in
in
mine.
C
So
we
started
from
the
composer
or
with
MSI,
with
a
magenta
2.3
alpha
and
MSI
and
I'd
like
talk
about
project
numbers.
So
in
the
project
we
have
about
32
K
of
products
which
connected
with
about
2000
of
sources
or
warehouses,
and
we
for
now
we
have
only
one
stocks,
but
it
will
be
more
so
about
other
patiska
for
1025
products
per
store
and.
C
C
C
Source
so
from
admin
account,
admin
can
approve,
sup,
suppliers,
import
or
said
out,
approve,
assign
products
to
stop
there,
I
sign
sources,
saboteurs,
etc.
And
now
we
working
on
the
code
pot,
which
not
finished
but
will
be,
will
be
soon.
So
after
these
changes
we
will
have.
We
had
this
schema
of
the
project,
so
we
have
suppliers.
Then
we
have
products
and
we
have
sources
so
each
supplier
connected
to
their
products.
It
can
be
10,
20
or
more
and
each
supplier
cup
connected
to
sources.
C
C
Each
source
can
contain
it.
Each
source
item
can
contain
quantity
and
price
also,
so
all
other
stay
the
same,
except
this
part
of
for
that
it
was
changing
changed
and
with
this
amount
of
the
of
the
sources
we
just
face
it
with
issues
that
we
can
say
from
admin
stock
with
2000
sources
in
one
stops.
Oh
is
that
so
all
other
works
fine.
Also,
we
didn't
finished
the
shipping
and
I'm
happy
for
selecting
the
products.
So
it's
a
fart
for
about
this
project.
C
A
C
Didn't
taste
it
now,
but
we
have
large
number
of
sources,
but
it's
connected
to
the
small
numbers
of
products
and
we
have
small
numbers
of
connections
between
products
ends
and
sources.
So
and
now
it
works
fine
with
all
that
is
it
we
imported
from
you.
Do
you
project
so
so
far,
it's
fine
I
can
say
now
the
performance
because
I
didn't
didn't
tested
it.
Yet.
A
F
C
F
C
A
A
J
Yeah
I
work,
yeah
I
work
as
a
part
of
a
almost
a
team,
I'm,
a
still
team,
let's
say
correct,
so
our
guys
have
contributed
to
MSI
as
well
and-
and
we
are
developing
a
new
extension
called
advanced
MSI
and
last
an
aside
so
now
I'm
going
to
tell
you
about
the
extension
to
show
some
part.
We
tend
to
tell
you
about
the
future
plans.
Regarding
this
extension.
J
This
extension
is
complicated
kind
of
complicated
and
we
reached
the
edge
when
it
is
very
hard
to
develop
of
this
extension
further
to
fill
it
with
new
features
and
so
on.
So
for
us,
MSI
now
is
a
great
chance
to
move
forward
to
create
a
new
extension
and
fill
it
with
new
features
in
to
create
a
big
big
new
product.
J
So
we
have
created
two
new
basic
algorithms,
one
that
detects
the
nearest
source
and
the
other
that
finds
every
house
with
all
ordered
items.
So
you
can
make
a
single
shipment.
This
algorithm
helps
us
to
to
avoid
multiple
shipments
for
one
order,
so
we
have
an
option
to
set
the
default
algorithm
and
when
you
go
to.
J
The
only
thing
you
are
to
do
now
is
to
recheck
and
to
click
proceed
to
shipment
button.
How
it
worked.
You
see
that
we
have
ordered
two
items
and
only
two
warehouses,
New
York
and
Berlin
can
ship
both
items,
so
that
was
the
first
step
of
our
algorithm
bind
algorithm,
yeah
I've
forgotten
to
say
that
we
combined
all
basic
algorithms
in
one
in
one
combined
and
all
warehouses
go
through
one
step
to
the
second
and
to
the
side,
and
so
on.
J
So
at
the
first
step,
our
algorithm
detected
two
warehouses
with
all
stock
with
all
items
in
stock,
in
New,
York
and
Berlin,
and
second
step
was
to
find
the
nearest
one.
As
the
shipping
address
is
California
USA,
the
closest
one
is
New
York
yeah.
That
happens.
So
we
see
that
the
needed
source
is
already
chosen
and
the
quantity
is
filled.
The
only
thing
I
need
to
do
is
to
click
proceed,
shipment
or
a
it
worked
yep.
That's
it.
J
B
F
J
A
Awesome's,
we
will
have
time
for
questions.
Mark
has
to
head
out
in
in
a
few
minutes,
so
we'll
come
back
to
questions
if
that's
all
right
and
I'll
just
want
to
pass
on
to
mark
at
the
moment.
So
we've
seen
what's
possible
with
the
current
state,
an
aside
with
the
different
examples
and
Mark's
going
to
share
a
little
bit
about
like
the
next
steps
and
what's
coming
with
a
micelle
yeah.
E
Great
thanks
David,
so
if
anybody
doesn't
already
know
or
is,
is
new
to
the
project,
so
we
have
of
everything
everything
that
we're
doing
here
on
the
project
is
managed
publicly
for
everybody
to
see
so
I'll
just
show
you.
We
have
our
main
repo
here,
which
has,
of
course
you
can
download
the
code
anytime.
You
want
you
can
post
issues
so
anything
that's
found.
This
is
where
we
get.
E
You
know,
bug
reports
and
follow
those
through
to
resolution,
pull
requests,
of
course,
against
the
repo,
and
then
we
have
an
extensive
wiki
here
where
we
document
you
can
see
all
these
links
on
the
side.
If
you
know
what
we're
working
on,
how
those
things
work,
our
documentation,
all
those
things
go
up
here
and
then
we
use
a
tool
called
Zen
hub
to
manage
development
on
the
project
itself.
E
So
we
can
see
stories
move
through
the
board
here
from
being
in
a
backlog
being
worked
on
and
in
progress
through
to
review
and
being
deployed,
so
we
just
completed
or
are
in
the
process
of
completing
what
we
call
milestone,
2,
which
will
release
in
the
2.3
release,
as
you
can
see
here,
and
we've
seen
many
great
features
there
demoed.
So
next
up
for
us,
we
intend,
to
you,
know,
keep
going
on
this,
not
that
lose
our
momentum,
but
we
have
lots
of
great
things
that
we
want
to
keep
adding
to
MSI.
E
So
here's
just
a
draft
look
at
what
we're
considering
for
milestone.
3.
First
two
items
are
just
continuing
to
build
out.
You
know
an
API
functionality
for
both
source
item
in
stock
item
to
make
sure
those
are
in
line
with
our
technical
vision
for
inventory,
Magento
modularity
and
an
inventory
management
that
one
after
that
is.
We
call
full
support
of
msi
in
the
b2b
edition,
so
we
have
a
set
of
b2b
features
for
Magento
commerce
and
those
have
some
elements
that
use
inventory.
E
For
example,
here
the
quick
order
form
which
is
available
in
the
b2b
modules,
allows
people
to
enter
SKUs
or
product
names,
and
then
on
that
form
they
can
get
information
back
everything
they
click
there.
The
quantity
that
they're
trying
to
order
is
going
to
be
checked
against
stock,
to
make
sure
that,
of
course,
there's
sufficient
quantity
in
stock
for
them
to
place
the
order
for
the
number
that
they
want
to
get.
E
So
this
is
an
example
of
one
part
of
b2b
here
that
needs
to
be
refactored
to
make
sure
it's
using
new
msi
methods
and
api's
to
get
that
inventory,
availability
and
there's
actually
two
other
areas
within
within
b2b
that
are
similar.
That
need
to
be
updated
to
use
the
new
way
of
doing
things
with
inventory,
with
msi,
also
similar,
with
that
making
sure
that
we
fully
support
msi
within
the
elasticsearch
adapter
in
Magento,
so
very
similar
to
b2b
the
next
one
which,
as
you
can
see,
our
estimate
for
is
extra-large.
But
it's
super
important.
E
So
right
now
in
MSI
we
support
nearly
every
single
kind
of
product,
so
we'd
have
full
support
for
configurable
products,
simples
even
virtual
products,
but
we
don't
yet
have
full
MSI
support
for
bundle
products.
So
that's
a
really
important
initiative
for
us
in
milestone
3.
Once
this
epic
is
complete,
then
we
will
be
able
to
support
every
product
type
in
Magento
and
those
will
be
fully
compatible
with
MSI.
E
So
we'll
maintain
a
database
of
distances
between
pairs
of
postcodes
or
zip
codes.
So
we
can
calculate
very
rapidly
a
distance
between
the
source
locations
and
the
customers
shipping
address
without
having
to
make
API
calls
to
shipping
carriers
or
other
third
party
sources
that
were
reliant
on.
So
it
will
be
performant
and
also
doesn't
need
to
make
a
call
out,
and
then
we
will
use
those
distances
as
a
proxy
for
a
cost.
E
So
we
make
an
assumption
that
shorter
distance
is
also
a
lower
cost
to
ship
the
package,
and
that
will
use
us
to
allow
us
to
very
quickly
deliver
those
those
back
to
the
you
know.
Back
to
the
front
end,
we
will
continue
to
mist
answer
a
Magento
functional
test
framework,
so
continuing
to
have
as
many
automated
tests
as
possible
as
we
can
on
the
MSI
project.
E
That's
not
just
a
benefit
MSI,
but
also
helps
with,
of
course,
all
the
rest
of
Magento
we'll
be
able
to
leverage
those
tests
making
sure
that
nothing
gets
broken
in
MSI
from
a
change
anywhere
else
in
the
platform
and
then
the
last
one
on
here,
but
very
much,
not
least,
it's
also
high
level
estimate
at
extra-large
is
having
a
store.
Pickup
support
right
now
in
core
MSI.
We
don't
expose
any
of
the
inventory
for
stocks
or
sources
on
the
front
end
to
the
to
the
customer
by
location.
E
So
it's
not
possible
for
a
customer
on
the
front
end
to
see
you
know,
there's
10
in
this
warehouse
and
25
in
second
warehouse,
etc.
Much
less
make
a
reservation
for
inventory
from
a
particular
source.
So
our
ambition
with
the
store
pick
up
support,
is
enabling
those
scenarios
so
allowing
customers
on
the
front
end
to
view
inventory
available
in
sources
and
actually
select
the
inventory
that
they
would
like
to
reserve
when
they're
making
their
order
for
pickup.
So,
as
you
can
imagine,
that
feature
has
a
lot.
E
That's
required
both
on
the
front
end
on
the
admin
side
and
UX,
etc.
To
make
it
happen,
so
it's
pretty
big,
but
it's
also
very
exciting
for
merchants
to
be
able
to
offer
that
that
functionality.
So
that's
kind
of
a
summary
of
what
we're
doing
in
milestone.
3,
like
I,
said
before
we
use
Zen
hub.
So
here
you
can
see
just
a
burned-down
Zen
hub
obviously
hasn't
started.
But
if
you
go
into
this
screen,
you
can
see
all
the
different
stories
here
as
they
become.
E
You
know,
updated,
more
detailed
filled
in
on
them
and
we
start
working
on
them.
You
can
follow
the
status
on
all
of
those,
and
then
we
do
have
additional
information.
For
example,
I
mentioned
some
of
the
API
work
at
the
beginning.
Igor's
done
a
ton
of
great
work
to
have
a
lot
of
detail
and
background
here
on
what
we're
trying
to
accomplish
and
how
that
would
work.
E
So
not
just
for
people
that
are,
you
know,
want
to
have
a
reference
on
the
project,
but
for
new
people
that
join
the
project,
they
can
come
up
to
speed
and
understand
what
we've
already
done
and
what
is
our
technical
vision
for
making
these
changes.
So
that's
really
great
and
encourage
anybody
who
has
questions
about
this.
To
take
a
look
at
this
and
of
course
you
can
always
ask
us
questions
at
any
time
in
in
slacker
or
by
email
as
well
on
on
what
we're
gonna
do
in
milestone.
3.
A
I
appreciate
that
mark
I
know
you
have
another
call
to
get
to
now.
So
I
appreciate
you
at
the
time
and
if
you
have
any
questions
directly
for
mark
feel
free
to
reach
out
in
the
slack
on
Twitter
or
whatever,
and
then
try
and
reach
other
possible.
But
yeah
I
appreciate
you
joining
us
with
today
and
I
hope.
We
have
no.
E
A
So
Ricardo
is
going
to
share
a
little
bit
about
his
I
guess
his
journey
with
contribution
and
maybe
how
he
got
started.
So,
if
you're
watching
this-
and
you
think
that's
a
lot
of
interesting
stuff
and
I
want
to
get
started,
but
I'm,
not
a
hundred
percent
sure
he'll
at
this,
probably
the
section
for
you
so
Ricardo.
Why
don't
you
take
it
away
by
telling
them
to
your
contribution
story?
Name.
H
H
H
H
You
know
I'm
using
CQRS,
because
it's
cool
not
because
I
actually
need
it,
and
this
is
wrong
from
my
perspective,
but
he'd
MSI's
different
because
actually
was
one
of
the
first
project
in
which
a
soul,
CQRS
and
it
be
usin,
because
actually
they
were
needed
for
the
project.
So
it's
very
uncommon
to
find
a
project
with
this
kind
of
characteristics
and
another
good
part
from
the
developers
perspective
is
that
you
can
even
join
other
community
projects.
H
So,
for
example,
I
have
been
involved
in
one
of
the
features
that
was
basically
handling
bulk
operations
in
in
the
source
system.
So,
basically,
when
you
want
to
transfer,
for
example,
one
quantity
from
one
source
to
another
one-
and
you
have
a
very
huge
catalog
and
I've
been
involved
in
developing
this
feature
and
I
had
the
opportunity
to
work
with
the
synchronous
API,
a
system
that
is
coming
from
another
community
project.
So
it's
pretty
cool
from
this
perspective
and
I
think
it
was
a
feature
that
was
that
part
part
that
was
talking
about
before.
H
Actually
and
I
also
think
that
it's
very
good
on
the
developer
specific
perspective.
When
you
talk
about
trading
because
I
see
as
bad
in
was
was
same
before,
I
see
a
mess,
I
contributing
a
mess
is
a
very
good
opportunity
to
to
learn
something
and
then,
as
a
tool
before
you
can
even
see
from
the
merchants
perspective
and
from
the
side.
H
You
see
the
feature
and
well,
of
course
we
does
no
need
to
say
that
the
feature
is
amazing,
but
I
think
the
most
amazing
part
is
something
that
is
not
visible
immediately
from
the
measurement
perspective.
That
is
the
the
fact
that
Emma
size
is
handling.
The
inventory
like
you
handle
in
real
life.
I
want
to
show
you
just
a
couple
of
slides
where
I
think
your
mode
and
a
capital,
but
very
few
slice
use
I
want
to
show
you
something
about
all
of
this.
So
let
me
share
my
screen.
H
Can
you
see
it?
Tell
me
yeah,
okay,
great,
are
you
saying
yes?
So
this
is
just
an
example
and
I
think
is
one
of
the
most
amazing
example,
because
you
can
see
immediately
the
difference
between
the
old
approach
of
much
Antoine
and
the
umsi
approach.
I'm
talking
about
it's
called
preservation
inside
MSI.
So
you
know
when
you,
you
have
two
products.
Okay,
this
is
just
an
example.
You
have
two
products
in
your
in
your
stocks.
You
receive
100k.
H
1
order
and
someone
is
asking
for
its
products,
so
you
you
have
an
order
with
products
the
Ottoman
sent.
One
was
probably
deducting
the
quantity
immediately
and
then
you
had
ten
products
available
in
your
inventory.
But
the
problem
is
here
is
that
in
the
real
life
you
still
have
ten
products
in
your
inventory.
So
you.
H
It
was
actually
drawn
from
that
perspective,
but
you
can
only
sell,
of
course,
at
products
because
you
have
a
conservation
of
the
products
and
then,
when
you
ship,
you
actually
add
eight
products
in
your
inventory,
but
the
problem
is
that
you,
it
can
takes
a
quite
big
amount
of
time
between
the
order
and
the
shipping.
So
actually
we
have
to
find
a
solution,
because
if
you
want
to
model
our
software
looking
at
reality,
we
still
apps
and
products
until
we
ship
them.
So
the
solution
was
based
on
events
or
thing.
H
I
will
not
go
too
deep
in
technical
aspects,
but
if
you
want
to
see
whatever
the
thing
is,
it's
full
of
articles,
you
name
in
the
Internet,
so
feel
free
to
go
deeper.
But
the
idea
is
this
one.
So
we
have
an
initial
status
in
which
we
have
one
product
that
is
ABC
with
quantity
tan.
This
is
our
initial
status.
Then
we
will
receive
one
order.
Then
we
do
not
say
we
are
decreasing
the
quantity
immediately,
but
we
say
we're
selling
two
products.
So
as
you
as
you
can
see
here,
we
have
a.
H
We
have
two
different
words.
We
have
quantity
and
availability
before
you
magenta.
Basically
just
you
had
all
the
quantity
at
the
very
end.
So
here
you
have
quantity
and
availability
and
what
it
is
tan,
because
you
still
have
ten
products
and
availability
is
a
kind
of
dynamic
value
that
is
computed,
taking
the
actual
quantity
in
your
stock.
H
There's
a
bed
quantity
of
course
I'm
simplifying.
It's
not
exactly
like
like
this,
but
just
to
let
you
understand
how
how
it
works.
Then,
when
you
see
we
actually
decrease
the
quantity,
so
the
quantity
now
is
eight
because
we
moved
away
products
from
our
stock
and
then
we
create
what
we
call
compensations
reservation.
Of
course.
Otherwise
you
could
give
these
value
is
before
our
availability
would
be
six.
Actually
that
is
wrong,
so
we
create
a
compensation
here.
So
this
is
the
idea
behind.
H
So
quantity
is
quantity,
availabilities,
quantity,
auto
reservations,
it's
very
simple,
of
course,
if
you,
if
you
see
in
this
way,
but
it's
very
powerful,
because
it's
just
an
example,
if
you
want
to
update
your
inventory,
your
online
inventory
and
you
want
update-
is
accordingly
to
your
actual
quantity.
In
your
inventory,
you
can
directly
update
the
quantity
without
affecting
the
ability.
H
I'm,
sorry,
I,
don't
remember
your
name,
but
you
were
talking
about
the
new
system
to
select
the
sources
and
mark
said
before
the
temas
I
will
provide
most
likely
one
of
these
systems
and
I
know
for
sure,
because
I've
been
involved
in
creating
them
and
I
want
to
show
you
just
something
so,
first
of
all:
well
the
source
selection,
algorithm
Stan.
What
is
exactly
is
system
allowing
you
to
pick
the
products
from
a
specific
warehouse.
So
if
you
have
multiple
warehouses,
you
even
have
to
understand
what
is
the
source.
H
Where
else
you
have
to
pick
the
product
the
product
from
so
the
very
best
one
is
the
is
the
one
out
of
the
box
with
the
msi
different
version
of
a
messiah.
It's
called
priority
is
to
selection
algorithm.
That
is
very
simple,
so
I
will
take
as
much
as
possible
products
from
the
first
source,
then
the
second
source
and
so
on.
So
if
we
have
an
order
of
ten
products,
for
example,
we
take
and
we
have
an
availability
of
six
in
a
first
sourcing
priority.
H
We
take
six
from
that
source,
then
we
take
all
dress
from
the
other
source
and
then
we
fall
back
until
we
we
find
out
available
products
and
I'll
be
working
to
change
this
behavior.
That
is
very
simple,
too
much
simple,
sometimes
converting
to
a
distance
base
based
shipping
sees
as
social
selection
system.
So
basically
we
do
not
work
anymore
talking
about
priorities,
but
we
talk
about
distance
because
you
know
shipping
may
cost.
Actually
we
cause
differently,
depending
on
the
distance,
so
may
be
a
good
idea.
H
A
good
idea
could
be
sorting
the
sources
using
distance,
and
this
is
a
coming
feature.
I'm
still
working
on
that
there
is
a
who
requests
it's
working
well,
actually,
almost
working,
but
I
think
it
will
be
ready
quite
soon,
I,
don't
know
when
it
will
be
a
real
section
and
the
cool
part
is
that
you
have
two
ways
of
computing
distance.
So
you
have
no
flying.
Let's
go
offline,
of
course
you
cannot
say
you're
flying
when
you
when
you
talk
about
a
website,
but
it's
a
kind
of
offline
database.
H
You
can
download
from
from
Internet,
and
you
have
a
database
of
postcodes
and
for
each
postcodes
you
have
a
virtual
reference.
So
basically
we
can
compute
the
surface
distance
between
one
point
and
another
one.
Of
course
it's
very
it's
not
so
accurate,
because
the
best
one
is
the
street
distance.
Actually,
so
here
you
just
use
the
the
postcode
that
can
be
even
a
quite
huge
area
and
you
compute
the
distance
between
them.
But
it's
something
you
you
can
start
with,
and
the
postcode
database
can
be
retrieved
online
and
download
to
local
d-beam.
H
A
F
D
Awesome,
hello,
everybody!
So
if
you
just
are
joining
in
a
little
late,
I'm,
Laurie
and
I,
am
your
community
engineering,
tech,
writer,
I
work
on
everything
from
dev
docks
to
merchants
docks
and
wiki's,
and
everything
in
between
so
MSI
has
been
fantastic
to
document,
not
only
the
Magento
team
helping
out
with
incredible
info,
but
a
massive
amount
of
information
coming
from
all
of
you
in
the
community
as
well.
D
I
have
been
focusing
on
leading
the
documentation,
doing
reviews
as
well
as
helping
out
in
dev
Docs,
but
Kevin
Harper
has
been
the
lead
on
writing
that
content.
We've
been
working
together
as
we
can
and
I've
been
focused
more
on
the
user
guide.
Merchant
content,
as
well
as
the
wiki,
so
I'll
show
you
really
quick
where
you
can
find
everything,
and
yes
for
the
first
time
ever
because
of
MSI's
awesomeness,
we
do
have
merchants
and
user
guides
beta
version.
D
First
time
ever
for
Magento,
you
will
be
able
to
find
all
of
these
through
the
tech
resources.
So
if
you
have
merchants
that
are
interested
in
MSI,
this
is
a
great
polished
way
of
showing
them
what
the
product
does.
You
can
click
on
any
of
these
two
threes
and
I'll
show
you,
where
you'll
find
the
content
it's
right
under
catalogue,
managing
inventory,
because
that's
what
MSI
is
all
about.
You
won't
find
the
word
MSI
easily
in
here,
because
it's
Emma
sized,
replacing
or
enhancing
inventory
management.
D
D
If
anyone
wants
to
learn
about
MSI,
these
give
deeper
information
into
every
aspect.
It
took
pride,
but
it
provides
definitions
gives
really
enhanced
diagrams
walks.
You
through
everything,
including
every
step
that
would
be
record
required
for
adding
sources
managing
your
products.
I
tried
to
put
in
as
much
concepts
and
in
examples
beyond
just
where
do
I
click
for
developer
documentation?
We
do
have
REST
API
content,
a
order
tutorial
from
beginning
to
end,
as
well
as
some
introductory
info
how
to
find
it.
So
if
you
go
to
dev
Docs,
you
go
to
the
2/3
beta.
D
You
want
to
make
sure
you're
on
2/3
up
here
in
functional
areas.
You'll
see
inventory
management.
You
dig
in
here
and
you're
gonna
find
the
quick
overview.
We
are
trying
to
keep
up-to-date
information
on,
what's
been
deprecated
from
core
and
being
replaced
with
from
MSI
as
well
as
some
you
know,
quick,
deeper
info
to
get.
You
started
on
the
more
technical
aspects
of
MSI
and
then,
of
course,
you
can
also
from
this
overview.
If
you
hit
all
the
way
to
the
bottom,
it
will
give
you
all
the
links
for
the
better
juicier
content,
for
example.
D
This
is
the
tutorial.
It'll
walk
you,
through
literally
every
single
step,
using
rest
to
make
your
changes
with
each
step.
We'll
have
info
that
you
can
verify
things
either
in
the
code
or
in
the
actual
admin.
So
you
can
also
help
merchants
understand
this
process.
It's
also
really
great
for
partners
and
developers
and
then
the
rest
tutorials
start
with
managing
resources,
and
we
just
added
this
source
selection
algorithm.
So
if
you
wanted
to
do
like
these
awesome
guys
have
just
described,
create
your
own
SSAS.
D
You
can
do
that
through.
Looking
at
this
information,
we
are
working
extremely
hard
to
keep
this
information
up
to
date
on
a
weekly,
if
not
some
days
daily
basis,
so
that
you
guys
have
the
latest.
With
that
in
mind,
you
get
more
I
know.
This
is
crazy.
If
you
go
to
the
wiki
area,
ms:I
I
am
working
extremely
hard
to
also
keep
this
user
guide
in
here
up-to-date
with
the
develop
branch
you've
heard
me
right,
you
will
have
eternal
beta
sort
of
develop
in
progress
content
as
much
as
I
possibly
can
provide.
D
So
as
you
submit
PRS
I
am
reviewing
these
for
UX
text,
helping
out
with
error
messages
anytime,
you
need
that
help.
I've
been
providing
I'm
working
on
one
for
the
Rick
right
now,
and
this
guide
will
keep
you
up
to
date
on
MSI,
it's
going
to
also
have
all
of
that
in
progress,
work
that
will
eventually
move
into
the
final
user
guides
and
the
final
dev
Docs.
D
You
can
also
find
really
quick
info
on
installing
and
upgrading
MSI,
and
this
is
under
that
user
guide
overview
and
click.
This
it'll
give
you
all.
The
latest
I
am
endeavoring
to
keep
this
updated
based
on
the
latest
betas,
the
latest
rtems,
and
when
it
goes,
GA
I'm
going
to
try
and
always
keep
these
versions
up-to-date.
So
you
don't
have
to
hunt
to
find
that
kind
of
info
and
also
all
of
the
info.
D
That's
in
that
other
user
guide
is
in
here
a
little
easier
and
faster
to
read,
so
you
can
use
either
way,
but
this
content
will
eventually
include
stuff.
That's
in
milestone,
3,
so
bear
that
in
mind.
I
have
little
notes
at
the
top
that,
let
you
know
we
also
have
links
to
the
live
user
guides,
as
well
as
all
the
dev
Doc's
info
all
in
one
place.
So
no
matter
where
you
go,
you
will
find
it.
That's
pretty
much
everything
if
you
are
ever
looking
for
info
or
you
want
some
help
on
writing
or
hey.
D
You
want
to
come
work
with
me
and
contribute
some
content.
I
am
always
in
the
slack
you
can
hit
me
up
in
the
MSI
slack
or
directly
I'm.
Also
on
Twitter
I've
worked
with
quite
a
few
of
the
developers
hand-in-hand
to
review
some
P
like
the
Reid
nice,
with
the
name
we've
been
updating
some
of
the
Reid
means
for
the
modules
anything
like
that.
Just
feel
free
to
reach
out,
and
if
anyone
has
questions
happy
to
answer
them.
B
Actually,
I
don't
have
any
questions,
but
I
just
want
to
make
a
statement.
So
I
am
this
magenta
more
than
70
years
for
now
and
I
have
never
seen
as
this
experience
before
when
we
have
like
code
and
documentation
like
go
and
like
step
by
step,
and
sometimes
even
documentation
go
and
before
the
code.
So
we
have
not
had
any
experience
like
that
before
when
the
fish
is
not
yet
released,
but
we
already
have
so
well
documented
on
the
dev
dot.
So
this
is
really
great.
B
This
is
awesome,
and
this
is
like
a
real
like
like
it's
supposed
to
be
because
you
know
like
this
is
the
main
problem
when
we
have
the
gap
between
the
documentation
and
encode,
and
sometimes
code
goes
really
fast
and
documentation
don't
have
time
to
be
updated
properly.
But
here
it's
a
totally
different
story
and
thank
you
very
much
you
you
did
awesome
job
and
we're
and
I
actually
I
believe
so
many
people
already
get
their
hands
dirty
in
a
different
Messiah
customization
because
of
the
feature
is
so
well
documented.
D
Thank
you
very
much
and
I'm
always
open
to
more
ideas.
Just
listening
to
some
of
the
things
everyone
here
has
had
to
say,
I've
been
taking
notes
of
things,
I
want
to
add
to
the
docs
and
if
you
ever
do
check
out
the
wiki
you're
gonna
see
commented
out
stuff
already
for
some
milestone.
3
talks
that
I
had
because
the
PRS
haven't
merged
yet
so
I'll
keep
updates
in
the
slack
Channel
too,
when
Doc's
get
updated.
A
A
We
have
some
time
now
for
kind
of
a
Q&A
section
if
we
have,
but
while
we
wait
for
questions
so
if
you
have
a
question,
drop
them
in
the
the
YouTube
chat
and
we
will
get
them
to
the
to
the
team
here.
But
while
we
wait,
I
love,
Igor,
just
to
say
ego
of
milena
M&A
11
would
just
to
say
a
little
bit
about
why
he
loves
them
as
I.
Why
he
loves
doing
this
and
anything
else
you'd
like
to
say
about
it,
to
put
you
on
the
spot.
B
B
So
it
was
a
mountain
not
inventory
after
that
we
changed
in
the
name
of
the
project
to
mount
allocation
inventory
and
actually
the
MSI
is
a
short
name
for
the
project,
so
we
started
it
two
times
and
actually,
after
some
after
some
time,
we
have
to
postpone
the
project
we
because
from
from
one
side,
we
do
not
have
enough
resources
to
proceed
with
implementation.
From
another
side
we
had,
we
had
our
design.
I
would
say
that
it
was.
It
was
not
good
enough
to
fulfill
all
the
product
requirements
so
actually
zero.
B
This
this
architectural
design
was
the
third
one
which
I
created
for
the
project
and
for
me
initially,
it
was
a
pretty
bigger,
like
technical
challenge,
to
to
a
completion
to
solve
this
issue.
But
after
we
started
started
to
involve
the
community,
actually
my
vector
will
be
changed
because
I
got
quite
a
lot
of
quite
a
lot
of
friends.
B
So
we
because
initially
for
me
that
was
totally
unclear
how
we
can
how
we
can
orchestrate
such
a
biginsight
such
a
sophisticated
project
among
among
really
distributed
team
among
the
team
where
none
of
the
developers
except
me
and
Valerie
I'm,
not
sure
whether
earlier
on
on
the
code,
because
currently
he's
deeply
involved
into
the
graphical
project,
but
actually
from
the
beginning.
They
were
just
two
people
me
and
Valerie,
who
can
who
could
committed
for
their
time?
All
these
people
are
really
busy
people,
so
you
see
that
sitios,
co-founders.
B
Magenta,
ecommerce
head
of
e-commerce
and
head
of
magenta
on
the
call,
so
you
know
like
Vadim's
title
was
head
of
magenta
when
we,
when
we
met
him
initially,
so
so
so
really
busy
people-
and
you
know
they
can
just
commit
for
particular
time
they
can
allocate
for
MSI
development,
but
a
long
visit.
These
people
are
because
they
have
such
a
high
grades
and
their
grades
and
the
titles
and
their
companies
they're
very
smart,
and
even
so,
you
get
just
limited
time
to
conversate
and
to
work
with
them.
B
They
they
provide
just
brilliant
brilliant
ideas,
so,
even
in
during
this
call,
I
go
quite
a
lot
of
quite
a
lot
of
interesting
ideas.
For
example,
like
there,
the
idea
shown
by
by
Alex
from
a
messages
just
to
make
the
algorithm
like,
like
a
price
rule
where
all
this
particular
criteria
could
be
edit.
It's
a
brilliant
idea,
like
volume
who
demonstrated
how
they
how
they
decided
to
introduce
custom
additional
sales
channel.
So
this
is
always
a
key.
We
want
to
try
to
persuade
on
MSI's
that
sales
channel
is
another
extension
point.
B
A
B
Jump
first
of
all
jump
int
into
the
communities
flag,
so
we
have
a
flag
and
if
you
are
still
not
in
slack,
you
can
drop
an
email
to
the
m's
comb
at
adobe.com
and
just
ask
to
be
to
be
invited
to
this
community
slack
and
if
you
want
to
be
part
of
the
msi
project,
just
mentioned
that
in
this
email
that
you
want
to
be
joined
to
the
msi
msi
chat,
and
you
would
be
you,
you
get
a
particular
invitation
to
the
msi
slack
channel.
So
currently
we
have
more
than
so.
B
Currently
we
have
about
400
contributors
there
and
we
have
the
continuous
and
the
constant
collaboration
between
different
people.
So
and
if
you
have
just
any
question,
just
just
drop
a
message
in
in
Emma
sites
like
channel
like
I,
it
could
be
different
messages.
It
could
be
I
want
to
customize
the
algorithm.
B
If
you
already
work
in
with
MSI-
and
somebody
will
definitely
answer
that
and
or
you
can,
you
can
ask
like
I
want
I
want
to
start
contributing
to
MSI,
for
example,
you
and
this
week
we
got
two
new
contributors
and
one
of
these
contributors
Sergei
actually
made
the
demonstration
two
hours
early
on
our
weekly
MSI
Jima
meeting
so
sure
he
made
the
presentation
of
his
pool
request.
So
don't
hesitate,
just
drop
a
message
and
the
will
will
accompany
and
will
assist
you
with
everything
else.
A
To
reiterate,
it's
like
the
team
is
here
to
help
you
out
and
that's
that's
what
they
here
for
so
feel
free
the
user's
reach
out
towards
or
maybe
not
reach
out
to
each
other.
You
go
get
in
the
slack
dr.
Lori.
If
it's
docks
related
and
we're
here,
and
we
were
here
to
help
you,
and
so
that
is
kind
of
all
the
topics
I
think
for
today,
and
as
far
as
I
can
see,
there
are
no
questions
that
come
into
the
chat.
A
The
moment
that
haven't
already
been
answered,
and
since
we
are
a
little
over
the
time,
I
think
this
is
probably
a
good
place
to
cover.
So
I
just
wanted
to
say
thank
you
everyone
for
joining
this
call
ago,
and
it's
Devin
something.
Today.
It's
really
been
beneficial
and
I
think
it's
great
for
people
to
see
MSI
solutions
or
options
out
there
in
the
real
world
and
and
I
think
that
was
fantastic.
A
D
They
do
so,
if
you
have
not
checked
this
out
yet,
and
this
can
help
for
anyone-
that's
new
to
contributing.
If
you
go
to
and
search
for
the
Magento
dev
blog,
we
keep
a
a
weekly
contributor.
Look
at
everything.
That's
happened
every
single
week
in
every
single
special
project.
Each
of
those
projects
include
links
to
the
github,
the
Zen
hub,
the
slack
channel
documentation
and
anything
else
you
can
think
of
including
an
invite
to
the
community
engineering
slack
channel.
If
you
need
it
so
highly
recommend
check
those
out.
A
Great
and
yeah,
with
that
information
we
also,
we
have
a
Twitter
account,
Magento
engine
come,
and
so
we
will
tweet
out
about
announcements
such
as
these
live
streams
or
blogs
and
any
new
information.
So
that's
probably
also
a
great
thing
if
you're
using
Twitter
and
yeah
other
than
that.
Thank
you
so
much
for
joining
us.
A
Thank
you
for
watching
and
thank
you
for
taking
part
guys
and
showing
demoing
and
stuff
to
us,
and
we
will
have
our
next
live
stream
will
be
at
some
point
in
December
and
we
will
be
talking
about
another
project
coming
up,
so
that
will
be
in
yeah
in
December
and
so
followed
with
a
look
at
the
weekly
updates,
and
we
will
let
you
know
when
more
information
is
already
on
that
and
but
yeah.
Thank
you
for
joining
and
have
a
great
Friday.