►
From YouTube: Community Engineering Hangouts - Project Overview
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. Overview of our planned projects for 2019,
4. Live Q&A section,
During this hangout we will update you on the community engineering progress over 2018 plus we will be looking forward to 2019 by seeing what projects will be running and explaining how you can get involved in them.
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
All
right,
we
are
live
and
welcome
everyone
to
the
first
Magento
community
engineering
hangouts
and
live
stream
for
2019.
It
is
great
to
have
everyone
back
and
I
am
excited
specifically
for
today,
because
we're
gonna
hopefully
give
you
a
taste
of
how
you
can
get
involved
in
community
contribution
this
year.
A
What
options
were
gonna
open
up
for
you
and
how
best
to
use
your
talents
to
help
make
this
system
and
this
ecosystem
a
stronger
place,
so
I've
gathered
as
many
people
as
I,
possibly
could
with
inside
the
limitations
of
Google
Hangouts
that
we
just
found
out
about
and
they're
gonna
join
us
now
add
to
share
through
highlights
to
do
with
projects
and
contribution
in
general
yeah.
Last
year
we
had,
we
had
nearly
5,000
pool
requests
merged,
and
so
the
aim
is
we're
gonna.
A
You
seem
to
love
that
you
guys
you
seem
to
love
enjoying
contributing,
so
we're
gonna,
expand
the
options,
and
so
we're
gonna
gather
everyone
today
and
share
with
it.
So
to
start
with
we're
gonna
hear
a
little
bit
from
stanislav
and
he's
going
to
talk
a
bit
about
the
partner
program,
I'm
so
of
your
partner.
Listen
up
hi.
B
I
should
say
that
it
was
a
great
year
with
a
lot
of
contributions
to
the
magenta
to
open
source
project
was
a
numerous
special
project,
so
most
of
them
is
graph
QL
and
si
bulk
api
and
a
lot
other
projects
so
really
proud
and
appreciate
all
contributions
that
made
by
the
community
and
we
were
trying
to
recognize
and
show
the
most
of
the
top
contributors
of
the
year
and
I
want
to
speak
about
partners,
contributors
and
top
partners,
contributor
computers
of
the
past
year.
So
that's
share
my
screen.
C
B
So
the
first
place,
the
first
place
is
taken
by
our
leader.
It's
really
continued
leader,
its
partner
and
Jesse
called
ethics.
The
team
mate
was
made
incredible,
490
pull
requests
and
was
a
top
contributing
partner
of
the
month
for
tens
months
in
row.
So
it's
really
incredible
result
and
I
think
the
goal
for
the
ad
it's
this
year
to
achieve
12
months
in
a
row
as
a
partner's
achievement
partners
of
the
month.
B
They
participated
in
different
projects
like
graph
here,
like
MSI
CTO
of
the
ethics
Yaroslav
Ragosa
was
a
key
contributor
to
the
Raphael
project,
currently
ethics,
one
of
the
most
contributors
to
this
project,
and
they
have
two
developers
working
full-time
on
this
project.
More
detailed
information
about
Graff
care
will
be
provided
by
O'leary
a
little
bit
later.
B
B
The
second
place
is
taken
by
Jewish
technologies.
It's
our
pretty
new
team.
I
was
enrolled
in
the
middle
of
the
past
year
and
they
did
incredible
results
by
helping
us
with
14
different
solution
solutions
across
Hurley's
lines.
They
submitted
494
pool
request
to
the
magenta
to
open
source
project
and.
B
Projects
like
PW
egg
Raquel
and
especially
to
the
deaf
dogs
project,
deaf
dogs
projects
they
submitted
over
than
100
to
request
this
documentation
exists.
So
the
third
place
is
taken
by
interactive
for
the
guys
from
the
team
also
helped
us
was
fortunate
solutions
across
relays
lines
and
they
have
the
highest
acceptance
rate.
They
created,
70
pool
requests
and
96
full
request
was
merged
very
much.
It's
really
really
cool.
This
is
the
first
place
taken
by
much
much
specialists.
B
It's
our
really
good
friends
from
the
Italy
and
they
meant
made
significant
contribution
by
release,
two-factor
authentication
and
recapture
models
for
magenta
to
also
regard
tempesta,
provided,
really
valuable
contribution
to
msi
project
included
in
relationship
release,
preparation
and
launch
regression.
Testing
and
playing
new
features
to
milestone
3
for
Amazon,
the
faceplates
is
team
called
magenta.
B
They
focused
on
they
focused
on,
say,
magenta
health.
They
fixed
a
lot
of
typos.
If
it's
a
lot
of
useless
bug
lot
with
pork
first
is
conveys
cleanup.
Also,
they
a
zebra
fixed,
a
lot
of
documentation,
typos
and
provided
over
100
full
requests
submitted
to
the
devil
dogs
project.
And
let's
summarize,
we
have
one
goal
for
the
partners
for
the
magenta
team
for
the
all
contributors.
It's
make
magenta
better.
B
On
this
slide.
We
have
just
just
short
information:
how
to
join
us.
We
can
you
can
use
community
engineer
and
slag.
You
can
write
direct
messages
to
one
of
our
team
or
just
may
lose
the
edge
come
at
gentle
calm
and
we
will
guide
you
how
to
enroll
to
the
project
and
help
us
was
this.
Oh,
it's
making
my
job.
Thank
you.
Cool.
A
A
Cool
awesome,
it's
great
to
see
that
it's
not
just
individual
contributors
that
are
getting
rewarded,
but
also
partners.
So
if
you
are
am
part
of
a
partner,
a
team
in
the
ecosystem
feel
free
to
reach
out
to
us
and
we'll
get
you
on
board
as
as
quickly
as
possible,
if
you're,
not
all
right
cool.
So
next
we
have
one
of
the
many
egos
ego
and
G
we're
gonna
call
him
for
this.
Livestream
focuses
and
he's
gonna
give
us
a
general
overview
of
projects
as
well
as
a
little
bit
of
do
with
quality
over
to
you.
A
C
C
C
C
C
Wouldn't
be
me
if
there
weren't
any
technical
issues
hold
on
now,
we
got
it
good.
So
I
wasted
enough
of
your
time
with
my
stupidity.
So
I'm
just
gonna
quickly
highlight
the
results
of
2018,
which
I
was
somewhat
a
part
of
somewhat
wasn't.
We've
got
a
lot
of
stuff
done
guys.
We
contributed
heavily
to
the
2.3
release.
We
have
introduced
graph
QL
into
Magento.
We
have
reached
general
availability
of
an
acai.
We
started
integrating
with
Adobe
experience
platform,
which
was
really
huge
for
us
and
for
Adobe
as
well.
We've
released
the
Magento
functional
testing
framework.
C
We
have
made
huge
progress.
Just
a
lot
of
huge
strides
on
the
PWA
we've
released
bulk
API
we've
got
to
factor
authorization
natively
now,
reCAPTCHA
support.
We
were
working
very
hard
on
Japanese
localization
and
almost
ready
to
push
it
out
to
the
marketplace
in
sort
of
a
first
draft
version.
We
support
elasticsearch
five
and
we've
got
instant
certain
purchase,
which
is
where
we're
getting
one-click
checkout
and
we
wouldn't
be
there
without
all
of
you
guys.
C
Daigo,
so
the
first
thing
that
we
wanted
to
do
is
focus
and
refocus
on
innovation
and
make
sure
that
we
listen
to
you
and
we
listen
to
what
the
customer
needs
and
what
our
partners
need.
We
want
to
double
down
on
quality
Tom
Erskine,
who
is
unfortunately
not
here
today,
because
he
is
out
sick,
is
going
to
be
focusing
very
hard
on
helping
everybody
create
more
quality,
add
more
quality
to
Magento,
make
the
community
projects
and
community
contributions
are
more
high-quality
endeavor.
Overall,
we
want
to
even
increase
our
transparency
this
year.
C
C
We
want
to
develop
and
increase
our
contribution
programs
overall
and
make
sure
everybody
is
happy
contributing
to
Magento
and
get
something
for
it.
We
want
to
double
down
really
on
automation.
Automation
is
very
important
for
us
because
we
are
not
a
huge
team
and
it
will
help
improve
everybody's
experience
and
your
development
experience
and
our
experience
in
our
ability
to
help
you
and
work
with
you
would
be
just
so
much
better,
and
one
thing
that
I
think
is
going
to
be
sort
of
new
for
us
is
an
attempt
to
build
more
consistent,
more
Universal
processes.
C
This
year
we
have
created
a
very
cool,
very
agile
structure,
where
we
are
able
to
squeeze
out
every
bit
of
efficiency
out
of
everybody.
But
what
I
really
want
to
see
this
year
is
just
making
sure
that
every
single
project
works
in
a
consistent
way
and
people
don't
get
lost
when
they
transition
from
project
to
project,
and
that's
going
to
be
really
important
for
us
as
a
team.
C
And
finally,
we
want
to
work
a
lot
more
on
our
community
portal,
which
already
exists
in
a
beta
version.
But
we
want
to
make
it
a
reach
or
communication
tool
for
the
entire
community
and
host
quality
reports,
automation,
metrics,
project
status
and
velocity
reports.
There
and
kind
of
use
it
as
a
more
centralized,
more
rich
source
of
truth
and
then
last,
but
not
the
least.
We
want
to
build
a
universal
quality
process
and
quality
reporting
across
all
of
our
projects.
C
We
are
already
building
it
for
MSI
and
if
you
are
a
part
of
MSI,
you
may
have
already
witnessed
some
of
that
work
that
Tom
Erskine
is
doing
and
presenting
its
it
includes,
but
is
not
limited
to
Universal
metrics
and
Universal
data
presentation
for
our
quality
being
able
to
understand
when,
where
we
need
more
quality,
where
we
need
to
contribute
more
tests.
What
is
our
test
scenario
coverage?
What
will
be
the
impact
of
the
next
release
on
quality
or
performance?
C
We
want
to
show
you
the
test
scenarios
that
we
use
internally,
so
that
we
can
more
closely
collaborate
on
our
test
coverage
and
understand
what
the
coverage
requires
and
what
it
is
and
overall
just
want
to
make
it
a
more
open
and
a
more
transparent
place
for
everybody,
so
that
you
know
this.
This
work
can
continue
and
grow
and
we
can
be
a
better
partner
for
everybody,
and
that
concludes
my
part.
So
I
will
see
if
I
can
break
this
fall
again.
C
The
second
thing
would
be
to
really
work
with
the
community
closer
and
you
know
meeting
everybody
in
person
making
friends
I've
already
have
to
sort
of
reached
out
and
build
some
relationships
in
the
community,
but
to
me
it's
just
so
exciting,
coming
from
the
world
of
software
services
and
software
solutions
into
a
product
company,
especially
in
this
very
weird,
very
interesting,
multicultural
multi
nation,
national
team.
It's
just
you
know
an
incredible
amount
of
fun
for
me
to
touch
everything
to
see
how
you
know
how
everything
works,
how
everything
grows?
C
I'm,
really
looking
forward
to
all
of
the
events
that
we
have
this
year,
I'm
looking
forward
to
people
coming
up
with
more
events
this
year
and
just
being
a
part
of
as
much
stuff
as
I
can
and
bringing
positive
contributions
for
everybody.
So
if
somebody
has
an
idea
of
how
I
can
build
more
help,
please
just
pitch
me
out
and
slack
I'm,
apparently
known
as
Igor
G.
A
D
E
E
First
of
all,
what
I
want
to
say
that
in
2019
we
want
to
her
as
time
goes,
who
will
start
prioritizing
contributions
that
have
automated
test
coverage
and
I'm
talking
about
automated
functional
tests?
Also
for
this
we
have
enough
yet
so
we
we
will
really
appreciate
if
you
will
cover
all
of
your
fixes,
all
of
your
contributions
to
Magento
projects
with
MFE
of
tasks.
F
E
E
So
if,
if
you
would
like
to
participate
in
this
project
and
here
to
America
TFS
conversion,
we
build
a
project,
it
is
located
under
Emma
Kiev.
We
probably
have
a
lot
of
issues
which
were
telling
you
what
what
MPF
tells
of
which
variation
variations,
and
also
this
repo
is
going
to
have
a
really
big
wiki
page
on
how
to
do
how
to
run
and
Kiev
us
see
what
this
test
is
doing
and
how
to
convert
it
to
Katya
and
as
a
part
of
this
conversion.
E
We
we
are
going
to
release
a
special
and
here
version
which
helps
you,
which
helps
you
convert
in
this
test.
So,
basically,
when
you
run
NTFS,
we
will
have
a
draft
of
MFT
of
tests,
and
all
you
need
to
do
after
this
just
to
go
through
this
newly
generated
generated
energy
of
cost,
redo
it
and
make
some
changes
to
Queen
without
any
so
might
make
this
test.
Given.
E
How
you
can
be
involved
in
this
first
of
all,
I
recommend
all
of
you
guys
to
join
our
communities
like
channel,
which
called
an
Ikea,
so
you
will
get
latest
updates
about
automated
functional
tests
and
there,
if
you
have
difficulties
on
how
to
get
started
with
energy,
or
maybe
you
finish
in
a
really
big
and
complex
task.
You
can
also
ask
these
questions
and
MFDs
the
channel,
so
please
go
and
join.
E
It
start
using
nftl
start
automate
tests
with
MF
TF
and
contribute
this
us
in
a
change
of
adjectives,
and
as
I
mentioned,
we
will
have
trainings
for
you
guys
on
how
to
start
using
functional
tests
and
formal.
Please
join
our
upcoming
webinars
and
learn
how
an
activation
works.
So
this
is
pretty
much
it
myself.
A
Awesome
cool.
Thank
you
very
much.
I
think
that'll
be
very
interesting
for
a
lot
of
people
and
I'm
glad
that
we
are
also
adding
in
the
training
side
of
it,
because
it
can
be
if
someone's
not
used
it
before.
It
can
be.
Quite
a
could
be
quite
daunting
to
get
involved
in
so
I'm
training
to
see
so
yeah.
A
We
will
make
sure
that
you
as
a
community
are
updated
and
getting
to
those
webinars
and
jump
into
the
slack
and
ask
questions
when
you
have
them
and
I'm
sure
Alexi
will
be
more
than
happy
to
help
out
when
he
can.
Next,
we
have
a
very
privileged
person
here.
He
is
the
only
non
Magento
employee
in
this
call.
A
C
G
Thank
that
I'm
not
I'm,
doing
the
cargo
that
my
office,
you
know
my
backyard
aerosol,
so
yeah
as
David
said
I'm,
not
a
part
of
the
magenta
itself,
I'm
one
of
the
project
project
maintainer.
So
this
case,
a
stink
import
project,
maintainer
from
one
of
the
partners
named
Corrib
yeah
I,
want
to
just
generally
tell
you
about
our
project
and
I
guess.
I'll
start
with
my
screen
sharing
is
to
see
the
screen,
I,
hope,
yep,
good,
so
yeah.
G
Last
year
we
had
a
project
which
was
named
in
bulk
API
and
we
deliver
it,
the
bulkiness
in
compared
to
magenta,
2.3
and
now
we're
proceeding.
So
we
have
a
new
project
which
called
a
synchronous
import.
You
can
easily
find
it
on
a
Magento
github
and
we
have
such
a
nice
wiki
here
that
give
a
short
overview.
What
we
tried
whatever
trying
to
reach,
we
have
basically
two
tracks.
G
One
of
them
is
like
second
part
of
the
Balch
api
and
a
sink
api
which
is
covering
basically
the
updates
and
improvements
that
a
Simkin
bulk
api
can
take
to
make
even
more
faster
and
with
more
awesome
that
it
is
so.
We
have
some
stuff
like
improvement,
that
it'd
be
right
and
DB
speed
stuff
of
the
general
operations.
G
G
We,
if
you
interesting
to
join,
we
have
a
very
detailed
information
in
get
la
github
of
Magento
architecture.
Github.
It
happen
yeah,
and
we
have
here
like
three
phases
of
this
project,
where
the
first
one
is
covering
the
the
interfaces
service
context
for
upload
the
files
for
process
and
import
itself,
so
I'll
just
give
will
give
a
short
overview,
because
I
can
tell
about
this
like
in
ages,
mi
still
online
yeah.
D
G
Cool
yep,
so
I
just
will
make
it
short.
Overuse
of
idea
is
that
we
have
an
independent
service
or
it
can
be
installed
like
a
part
of
magenta,
or
it
also
can
be
installed
like
like
on
another
server.
Even
and
the
first
version
will
cover
the
same
functionality
as
a
current
Magento
Magento
standard
import
has
so
when
you
can
upload
a
file
and
and
start
an
import,
let's
rendered
CSV
data,
but
the
main
idea
that
this
extension
is
providing
the
fully
cover
with
API.
So
you
don't
need
interfaces
for
that.
G
G
G
If
you
want
to
join
just
ping
me
in
slack
or
we
have
a
channel
there,
which
calls
still
bulk
API,
we
have
a
get
github
project
so
feel
free
to
find
me.
You
can
also
find
me
on
Twitter
yep.
That's
all
I
mean
I
will
finish
now.
Otherwise,
I
can
talk
about
that.
Maybe
like
one
two
hours
and
I
guess
we
don't
have
this
time.
H
A
Love
the
passion
you
have
for
this
topic
and
I've
seen
talks
on
it
from
you,
and
it's
always
always
important
to
see
that
you
you
driven
to
this
and
it
comes
across
really
well,
which
is
which
is
fantastic.
So
thank
you
for
sharing
it
and
today
and
hopefully
your
passion
will
be
contagious
and
some
people
will
help
out
and
join
in
with
you,
which
would
be
awesome.
This.
A
A
A
Be
cold
in
your
car
set
outside
all
right
man.
Thank
you
for
joining
and
I
will
see
you
soon
all
right
this
one
by
my
safe
travels
by
cool
all
right.
Now
we
are
moving
on
to
Igor
mini
yellow
and
he
will
give
us
the
update
on
MSI
as
to
what
2019
will
look
like
in
the
msi
project
so
over
to
you,
ma'am.
I
Hello,
everybody
sorry
for
small
delay.
You
see
that
I
am
not
so
technician.
That's
why
I
have
an
engineers
just
nearby
to
start
my
presentation,
you're
a
high
level
image,
yep
so
I'm
here
to
present
you,
the
update
for
Maltese
or
Santeria,
make
sure
H,
actually
our
plans
for
2019,
and
it's
even
so
that
even
so
that
New
Year
holiday
is
already
finished,
but
MSI's
still
sharing
gifts
among
among
contributors
among
Magento
community
so
forth.
We
prepared
quite
quite
a
lot
of
goodness,
which
would
be
brought
in
2019.
I
So
you
see
that
magenta
Mesa
is
such
a
big
project
that
we
have
even
own
Santa.
Actually,
currently,
our
Santa
was
just
disconnected,
and-
and
here
you
can
see,
the
list
of
the
list
of
pretty
interesting
feature,
pretty
interesting
improvement
that
we're
going
to
to
deliver
in
the
scope
of
all
our
MSI,
goodness
in
2019
and
the
first
of
all,
we
will
start
from
from
independent
releases,
which
we
want
to
so
so
that
we
already
have
the
MSI
of
an
independent
core
bundle
component.
I
So
we
call
that
way
all
the
big
new
features
which
going
to
be
introduced.
A
second
big
core
bundle
feature
a
feature
going
to
be
page
builder,
which
would
be
released
into
the
street
at
1:00,
and
the
idea
would
be
pretty
similar
and
the
infrastructure
for
that
wouldn't
be
pretty
similar
to
what
we
have
with
MSI.
So
it's
going
to
be
pretty
decoupled
and
we'll
have
own
releases,
and
our
nearest
really
is
gonna,
be
one
dot.
I
We
have
seen
all
already
several
store,
pickup
implementations,
implemented
by
third-party
developers
and
extension
developers
and
actually
made
store
guys
from
my
store
even
present
it
right
today,
their
own
implementation
of
store,
pickup
and
the
boss
application,
and
but
this
is
this-
is
not
when
not
limited
with
that,
because
we
have
prayed
in
our
activities
on
b2b
track
and
we
want
to
improve
the
integration
with
the
and
calm.
So
our
enterprise
solution
for
multi-sourcing,
as
well
as
in
2019.
We
have
pretty
bright
bright
fuchsia
for
support
of
all
the
product
types
we
have.
I
I
We
want
to
introduce
the
support
for
the
bundle
product
and
spread
it
for
all
the
different
stocks,
so
that
support
for
all
the
product
ID
will
actually
improve
the
performance,
because
we
would
not
need
any
unneeded
since
that
time,
synchronization
between
the
legacy
inventory
system
and
the
new
inventory
system.
So
this
is
not
just
support
of
the
bundle
product,
but
this
is
kind
of
shift
to
the
new
infrastructure
so
that
we
can.
I
We
can
stop
making
synchronization
on
the
previous
previous
inventory
we
had
before,
and
you
can
can
follow
all
these
updates
and
you
can
see
all
all
these
features
in
the
in
the
in
more
details.
If
you
follow
this
link,
which
you
see
on
the
slide,
MSI
roadmap,
so
now
a
little
bit
more
about
independent
releases,
and
this
is
actually
this
our
killer
idea.
We
want
to
spread
for
all
for
all
the
extensions
for
all
the
features
gonna
be
going
to
be
brought
and
delivered
by
community
engineering
team,
either
by
by
core
team.
I
So,
as
you
can
see
with
these
big
red
triangles,
so
this
is
kind
of
kind
of
happen
when
magenta
make
make
own
releases.
Currently,
we
as
a
magenta
commit
for
at
least
four
patch
releases
per
year,
and
but
you
know
like
for
patch
releases
per
year,
it
is
good
it's
predictable,
but
again,
especially
on
Kenickie
on
projects
which
are
driven
by
community
engineering
team.
It's
appears
that
sometimes
even
unexpectedly,
some
feature
could
appear
very
quickly
and
this
feature
this
feature
already
ready
and
this
feature
is
ready
to
be
delivered
to
the
market.
I
If,
if
you
already
have
one
and
that's
why
you
can
see
how
you
can
see
this
blue
triangles,
and
actually,
these
blue
triangles
are
release
cycles
for
small
features
for
small,
let's
called
streams.
But
we
don't
actually
apply
some
particular
time
frame
and
we
are
just
following
the
feature
driven
development
and
as
soon
as
the
fish
is
ready,
we
we
want
to
drop
it
to
the
market.
I
So
this
is
what
we
do,
this
magenta
one
dot
one
dot
over
release
and
we
believe
that
the
same
the
same
approach
would
be
apply
for
all
other
extensions
and
all
other
projects,
as
well,
so
a
little
bit
more
about
what
what's
gonna
appear
in
a
one
dot,
one
dot
Oh.
So,
as
already
mentioned,
the
distance
based
algorithm
and-
and
here
you
see
the
screenshot
when
Ricardo
made
the
presentation,
so
the
distance
based
algorithm
is
critical
stuff
because
we
simultaneously
have
support
for
both
offline
and
online
calculation
for
online
calculation.
I
We
use
a
Google
Google,
Maps
API.
We
support
several
computation
modes
like
driving,
walking
and
cycling,
and
also
like
different
customization
on
the
level
of
Google.
But
along
with
that,
we
provide
the
offline
calculation
when
merchants,
for
example,
for
some,
for
some
reasons,
don't
want
to
rely
on
a
Google
API
or
she
just
don't
want
to
pay
Google.
This
way
he
can
just
applaud
the
database
of
the
zip
code
and
all
the
calculation
gonna
happen
by
the
by
the
distances
between
the
zip
codes,
so
the
pretty
cool
stuff
and
we
are
preparing
this
release.
I
So
today
we
presented
the
smoke
testing
and
the
test
coverage
for
this
release
is
on
the
way.
Also,
our
the
next
milestone,
gonna
be
store,
pickup
and
the
store.
Pickup
is
really
it's
really
killing.
It's
a
killer
feature
for
I,
believe
next
and
as
I
released.
So
the
name
after
the
one
that
one
at
all-
and
we
already
have
already
have
a
design
document.
I
We
actually
involve
community
to
participate
in
to
provide
feedbacks,
because
we
see
that
MSI
actually
MSI
with
all
its
architecture,
was
a
really
big
step,
but
even
not
a
step,
but
probably
leap
towards
towards
the
store,
pick
up
support,
but
actually
we
need
to
make
the
last
small
final
step
to
complete
this
goal
in
heaven
store
pick
up
support
in
scope
of
magenta.
So
following
this
following
this
link,
you
see
on
the
slide.
I
You
can
see
all
the
all
the
design
and
all
the
all
the
UI
switch
supposed
to
be
implemented
in
the
scope
of
the
store,
pick
up
work
and
the
last,
but
not
the
least.
So
you
see
that
there
is
even
the
confidential
notice
here
on
this
slide.
So
I
do
not
I'm
not
supposed
to
say
that,
and
this
is
actually
for
internal
magenta
used
only.
I
But
there
is
some
leak
from
my
side,
so
I
assure
you
that
the
best
is
yet
to
come,
and
in
2019
we
deliver
even
much
more
interesting
stuff
in
the
scope
of
a
Massiah,
either
in
in
the
scope
of
other
project
as
well,
and
the
2019
gonna
gonna
be
much
much
joyful
year
than
than
the
previous
one.
So
thank
you
and
if
you,
if
you
need
some
more
details,
don't
hesitate
to
think
me
directly
or
or
just
join
the
Messiah
Channel
and
the
raise
any
questions
there.
A
Thank
you
very
much
man.
Thank
you
for
the
that
overview
of.
What's
coming
up,
I
am
a
big
fan
of
the
MSI
project
and
would
highly
recommend
if
people
want
to
get
involved,
that's
a
great
place.
It
might
be
a
little
scary,
but
ego
is
such
a
nice
guy
and
he
will
step
you
through
everything
we
need
to
know
so
don't
hesitate
to
reach
out
to
him
next,
we'll
be
moving
on
to
egos
technician.
I
believe
we
got.
Eugene,
hey
and
he's
gonna
be
sharing
a
little
bit
about
axp
connector.
J
J
J
Launch
expect
with
really
lots
of
features,
main
of
which
would
be
the
tag
management.
It
supports
different
kinds
of
tag
management
you
can
send
over
the
events
you
can
send
over
the
data.
Why
that
data
layers,
you
can
create
custom
extensions
which
would
consume
the
data
and
well
do
whatever
you
need
with
that.
It's
available
for
for
web.
J
Currently,
we
are
focusing
on
like
Magento
extension,
we'll
be
focusing
on
the
web
part,
but
who
knows
what's
gonna
be
in
the
future.
Also
launch
is
pretty
capable
of
capturing
defining,
storing,
sharing
and
whatever
do
doing
whatever
you
need
with
all
the
all
the
data
from
your
website.
So
it's
highly
customizable.
You
can
install
quite
a
lot
of
extensions
from
the
launch
catalog,
but
also
using
the
big
set
of
api's
it's
possible
to
implement
so
an
extension
and
extend
the
launches
feature
with
something
you
need
personally.
I've
included
some
links.
J
What
we
are
working
on
is
the
extension
which
would
allow
to
connect
any
Magento
installation
with
the
Adobe
experience
platform
service
and
basically,
the
main
idea
of
the
extension
is
to
provide
an
easy
way
to
set
set
everything
up
and
get
on
going
with.
Just
a
few
simple
clicks,
so
extension
already
handles
some
of
the
data
and
events
present
in
Magento.
Some
entities
are
covered,
for
example,
products
and
customers
cards
check
out.
All
these
can
be
tracked
and
the
events
attractants
all
of
the
acquired
data
is
sent
in
real
time
to
the
Adobe
Lodge.
J
Some
of
the
features
which
well
the
core
features
of
it
extension
is
like
a
lot
of
what
we
do
these
days.
It's
free
and
open
source
everyone
can
join
the
project
and
participate
or
just
observe
or
maybe
drop
some
ideas
into
the
backlog
completely
up
to
you,
and,
as
always,
we
welcome
individual
developers
and
partners
to
join
the
project.
Why
I
imagine
it
would
be
interesting
to
quite
a
lot
of
you,
so
github
link
is
below
it's
as
simple
as
Magento
/,
XP
connector.
J
C
Can
say
a
few
more
words
just
to
highlight
one
thing:
actually,
the
Adobe
launch
integration
for
us
is
very
important
right
now,
because
it
is
a
way
to
help
Adobe
with
their
first
foray
into
a
truly
open-source
platform
which
a
lot
of
people
miss
that
Adobe
io
is
an
open-source
development
platform.
You
can
register
as
a
developer
for
Adobe
io
and
you
know,
contribute
away,
so
it
is
really
a
huge
deal
for
us
because
it'll
be
folks.
C
You
know
consistently
are
super
impressed
and
happy
about
of
the
state
of
Magento's
open-source
community
and
they
really
want
to
learn.
They
really
want
to
foster
that
relationship
and
really
want
to.
You
know,
increase
their
own
own,
open
presence
using
what
we
have
built
and
what
we
know
so
just
wanted
to
kind
of
highlight
that
and
we'll
see
how
it
all
develops.
It's
really
really
interesting
from
that
perspective
for
sure.
A
Yeah
yeah
exactly
and
it's
a
good
opportunity
to
spread
out
a
little
bit
from
as
a
developer
point
of
view
and
get
involved
into
playing
around
with
some
of
the
Adobe
products
as
well
and
seeing
how
you
can
start
using
them
and
integrating
them
into
your
Magento,
which
is
awesome
great.
So
thank
you,
Eugene
for
that
and
yeah.
Remember
at
any
point.
If
you
have
any
questions,
then
in
the
live
chat
and
we
will
get
them
answered
as
best
as
we
can
with
the
people
that
are
here
available.
F
Enters
each
consumer,
this
tool
recognized
HP,
javascript
CSS
files
and
help
to
detect
violations
of
specific
coding
standards,
so
in
which
people
see
four
terms
coding
standards.
We
said
collection,
collection,
C
files
which
are
combined
in
offset
each
sniff,
can
have
its
own
severity,
also
type.
We
used
this
approach
for
marketplace
checks
so,
for
example,
and
it's
already
done,
and
this
hurt
attend
finding
to
enforce
extension,
failure,
here's
the
tape
problem
or
review,
because,
right
now
we
have
to
you
related
to
withholding
standards.
I
I
F
F
I
think
the
biggest
problem
right
now
is
that
developers
do
not
know
what
extender
to
use
for
stain
of
attribution.
Extension.
They're
here
is
to
make
this
work
consistent.
Here's
the
github,
repo
and
Psyche
channel.
So
this
sake
is
really
interested
and
also
the
church
and
standard
community
extraction
for
more
details.
F
F
F
F
A
To
see
that
you
set
up
the
issue
types
already,
so
if
someone
wants
to
start
a
discussion
on
a
new
coding
standard
or
checker,
they
can
just
start
a
new
issue
with
the
specific
type
I
love
that
I
think
that's
going
to
be
easy
for
people
to
start
discussions
there,
even
if
it's
even
if
for
contribution
what
they're
doing
is
the
discussion
I
think
that's
a
great
way
to
get
into
it.
So
awesome
thanks
for
that
great.
A
H
L
Okay,
so
as
magenta
community
is
pretty
across
the
world,
so
it's
not
surprising
at
some
point
to
and
ends
up
with,
localization
projects.
For
this
moment
we
hear
one
ongoing
and
plan
one
more.
So,
at
the
summer
of
2018,
we
started
to
collaborate
with
our
partner
from
Japan
Japan,
where
he
works
and
with
their
CTO
Nisha
Sun,
on
open
sourcing,
their
models
dedicated
to
cover
features
that
are
acquired
to
Japanese
market,
to
make
magenta
available
for
all
the
system
integrations
that
would
like
to
develop
his
magenta
out-of-the-box.
L
So
our
main
goal
is
to
develop
a
set
of
modules
that
will
bring
all
the
fishes
that
are
acquired
to
magenta.
Marcus
of
any
developer
may
just
start
with
adding
those
extensions
through
one
composer
or
comment
and
then
just
to
develop
some
unique
features
for
their
merchants
for
their
customer
and
just
and
don't
spend
a
lot
of
time
just
to
customize
in
Magento
for
what
is
common
for
for
Japanese
people.
So
we
have
our
github
repository
at
magenta.
L
Magenta
do
GP
and
we
have
Japanese
localization
select
channel
if
you're
interesting,
just
join
to
this
channel
and
contribute,
if
you
have
some
ideas
or
some
critical
features
that
you
so
that
you
think
should
be
implemented.
Just
let
us
know-
and
actually
we
are
now
pretty
close
to
make
some
work
publicly
available.
L
We
are
going
to
publish
our
like
alpha
release
pretty
soon
I
believe
it's
a
matter
of
a
couple
weeks.
This
implementation
will
include
all
the
features
that
we
agree.
It's
required
for
the
Japanese
market,
with
only
limitation
or
two
single
store,
mod
with
Japan
UK,
all
set
for
sister
and
yen
as
a
currency,
and
later
we
are
going
to
prepare
some
extension,
some
improvements
to
to
this
modules
with
support.
L
L
Move
some
improvements
to
the
Magento
course,
so
in
future,
all
the
other
localizations
would
be
made
easier.
If
we
will
see
that
some
features
that
will
implement
in
scope
of
this
project
will
be
available
for
another
for
another
Lucas
to
name
some.
It
may
be
support
of
currencies
without
minor
units,
flexible
management
of.
L
So
another
work
that
we
are
now
planning
related
to
a
localization
is
support
of
an
improvements
of
transit.
It's
like
improvement
and
simplification
of
for
translation
workflow,
as
you
know,
to
do
today.
Magenta
is
crowding
for
to
calibrate
his
community
to
translate
magenta
on
in
different
language
languages.
Unfortunately,
synchronization
of
chrome
in
this
github
now
is
not
transparent
and
we
do
it
from
time
to
time
with
our
automation
screens,
but
it's
still
not
updated
automatically
and
it's
hard
to
check
all
the
changes
during
preparation
of
next
Magento
release.
L
L
So
we
are
going
to
start
this
project
at
February
this
year.
We
don't
have
exact
date
now,
but
also
fall
off.
Community
engineering
Twitter
will
communicate
the
start
date
of
this
project
and
we
will
describe
all
our
plans
and
like
initial
design,
of
all
this
integration,
so
I
believe
it
will
be
a
pretty
interesting
project
not
directly
targeted
to
merchants,
but
building
some
infrastructure
around.
L
Developing
process,
so
it
might
be
some
new
technology
technologies,
some
new
approaches,
so
if
you're
interesting,
it
would
be
nice
if
you
join
our
slide
channel,
which
is
translations,
and
if
you
have
ideas,
some
may
be
pain,
points
related
to
translation
and
work
with
Magento
localization,
just
just
let
us
know,
and
let's
discuss
them
to
find
solutions
that
will
be
suitable
for
most
of
our
community.
Thank
you
for
attention.
That's
all
from
myself
cool.
A
As
we
know,
it's
Magento
is
international,
so
we
need
to
make
it
better
of
being
international
and
how
good
can
it
be
getting
the
community
involved
in
helping
us
out
with
their
special
localization
and
translation?
So
I
think
this
is
a
great
opportunity
for
people
so
yeah.
Thank
you
for
that
and
next
we
have
a
Valeri
and
who
will
be
talking
about
graph
QL
so
yeah
hand
over
D.
H
H
So,
as
was
mentioned
graph
QL
is
our
community
project.
Let's
mean
we
not
only
create
a
writing
code
to
his
community,
but
we
also
work
in
on
requirements
on
acceptance
criteria
and
on
priority
of
kikis
with
community.
We
constantly
have
synchronization
with
the
ballet
track
with
these
guys
from
different
agency
and
guys
from
select
channels.
So
that's
why
we
call
our
project
like
community
driven
development
and
as
a
result,
now
we
have
about
more
than
100
requests
and
few
last
month's.
So
generally,
what
is
graphical?
H
It
sums
structure,
language
which
describe
how
to
get
and
how
to
manipulate
some
data.
On
the
slide,
you
see.
Some
simple
example
like
I
would
like
to
get
some
simple
product
and
I
need
only
screw
and
name
and
I.
Have
this
result,
but
main
idea
if
I
need
more
information.
For
example,
I
would
like
to
show
some
road
to
cart
and
each
images
something
else
on
and
in
this
way
I
need
to
make
only
one
request
so
main
idea
to
load
all
of
the
data
in
one
request
and
a
few
cornerstones
about
rough
material.
H
It's
also
that
girl
provides
a
Giles
him.
We
have
stellar
Ellis
died
objects,
there
are
some
inheritance
of
objects,
custom
types,
so
on
mantra
make
sure
you
can
find
on
visual
graphical
site,
and
now
we
talk
for
our
community
that
always
Hema
its
API.
It's
some
kind
of
entry
point.
If
Magento
does
not
matter
how
its
implemented
on
the
hood.
Now
we
can
use
collection
service
should
be
service
our
own,
but
for
community
we
provide
some
contract
API
how
to
load
all
our
data
and
graph
Gale
is
also
open.
H
H
We
have
some
roadmap
for
2
to
3
1
release
and
it's
absolute
click,
open
link.
Everybody
everyone
can
opens
in
hub
and
discover
what
was
done,
what
will
be
included
in
2
to
3
1
released
also
also,
we
have
some
plans
for
check,
milestone,
also
be
helped
ones
for
to
defeat
to
release
and
generally,
as
I
said,
everybody
can
join
and
can
provide
opinion
can
change
priority
on
some
meetings
in
slack
channel.
So
our
scope
is
related
to
mostly
to
community
requests.
H
So,
oh
man,
oh,
is
finishing
car
check
out
for
flow
and
order
placements
as
its
include
shipping
billing
address
management.
My
others
boost
based
payments
message
and
a
stripping
hand
based
payment
methods.
Also,
we
have,
in
our
plans
some
improvement
in
our
framework,
as
I
mentioned
now
we
have
a
different
ways
for
loading
data,
but
we
think
about
query
PI,
some
internal,
our
framework,
I,
don't
know
how
it
will
be,
but
I
think
in
second
part
of
here.
H
We
will
try
to
unify
our
way
how
to
load
data,
and
yes,
of
course,
we
think
about
performance.
We
are
going
to
expand,
our
performance
builds
and
it
will
be
great
if
it's
different
ways
per
per
page.
So
on
and
as
I
say,
for
example,
also,
we
work
on
frame
work.
We
provide
variable,
separate
variable,
support
our
HTTP
queries.
It
was
request
from
P
EE
track,
so
we
change
our
scope
so
as
it
means
mostly
it's
related
from
request
from
community
for
for
you
and
how
to
join
to
our
project.
H
Absolutely
the
same
like
on
another
project.
We
have
a
sync
up
a
Tuesday.
Each
week
we
have
video
records
of
previous
meetings,
so
everybody
can
see
history,
and
maybe
you
would
like
to
know
more
details
how
to
implement
how
something
was
implemented.
We
have
public
Grumman's
and,
of
course
we
have
our
select
channel
graph
grill.
We
call
it
our
guilt.
H
So
if
you
would
like
to
join
our
guilt
and
we
provide
for
you
some
interest
quest
and
as
I
mentioned,
we
have
public
roadmap
public
portal
chart
and
everybody
can
join
pick
up
some
ticket
and
if
you
need
some
helpful,
you
can
pick
me
directly
on
the
slick
channel.
So
generally,
if
you
would
like
to
learn
more
about
this
innovation
technology
or
changing
limitation,
you
can
join
our
project
and
your
trip
you
started.
Your
journey
will
start
to
come
so
it
since
it's
it's
all
for
me,
I
did
note,
do
is
stop
started.
Screen
exists.
A
A
A
M
I
didn't
see
you
there.
Can
you
guys
hear
me,
you
see
me?
Okay,
yes,
perfect
great,
so
everyone
else's
slides
are
beautiful,
I,
don't
we
don't
have
them
prepared,
but
PWA
studio
is
at
long
last,
going
to
move
from
the
least
candidate
status
to
release
status
and
we
are
targeting
the
end
of
the
month
to
do
so.
M
M
M
That's
happened
to
it
include
that
we
have
optimized
tremendously
the
overall
payloads,
with
some
of
our
brand
new
team
members,
Steven
ruk
contributing
an
enhancements
that
breaks
icons
into
a
much
smaller
package
and
with
image
performance,
optimizations
and
compression
performance
optimization,
so
that
the
separate
development
server
are
much
faster.
Now
let
me
try
to
show
you
the
difference.
If
github
will
load
anything
which
appears,
maybe
it
will
not?
M
Can
you
see
this?
This
is
google
chrome
release
version
which
I'm
just
deploying
separately
for
test
purposes.
On
the
now
sh
quick
node
deployment
platform,
you
can
see
that
the
venía
storefronts
is
mostly
mobile.
Optimized,
though
it
works,
fine
on
desktop
and
you
can
proceed
through
and
you
might
observe
that,
even
though
it
is
still
pretty
fast,
I
am
on
a
laptop
with
a
strong
internet
connection.
It's
a
good
simulation
of
what
it
would
be
like
in
the
mobile
world,
especially
in
emerging
markets
on
3G.
So
we
just
loaded
an
image
that
is
466
kilobytes.
M
Now
that
I
have
vamped
enough
for
the
pull
request
storefront
to
load,
let's
do
a
little
compare
and
contrast.
So
this
version
of
the
venía
storefront
is
loading
optimized
images.
Let's
compare
I'll
go
back
to
the
home
page
and
you
might
observe
that
the
total
amount
of
data
downloaded
is
1.1
megabytes
in
the
current
release
version
and
an
upcoming
requests.
That
adds
image,
optimization,
that's
about
to
be
merged.
M
Two
hundred
and
thirteen
kilobytes
is
the
total
payload.
This
is
the
message,
our
image:
that's
whether
you're
Brett
Zaretsky
ma
I'm,
woman,
P,
Matt
and
Ben
peas,
if
appropriate-
and
maybe
the
images
are
now
art
directed
and
responsive,
so
that
if,
for
instance,
you
are
loading
in
a
screen
of
this
size
that
it's
going
to
load,
480,
pixel
versions
of
category
images,
640
pixel
versions
of
the
large
product
tail
pages-
but
if
you
make
the
same
requests
on
an
even
smaller
device
which
I
can
try
to
demo
here
did
and.
M
Ice
in
a
developing
economy
completion
and
you
might
observe
that
it
knows
to
load
the
smaller
image
even
for
the
large
display.
This
is
a
big
change
and
is
another
example
of
how
the
PWA
studio,
development,
toolkit
and
just
PWA
tools
in
general
in
the
web
standards
world
are
enabling
really
really
great
experiences
that
we
didn't
have
before.
So
in
order
to
contribute
to
PWA
studio,
as
so
many
people
have
done,
you
can
see
them
in
our
kudos
list.
M
You
can
go
to
Magento
Research
PWA
studio,
and
you
can
look
in
our
issues
for
issues
that
have
been
marked
for
sustaining
engineering.
You
can
look
for
issues
that
are
marked
good
first
issues.
You
can
look
for
issues
that
pertain
to
something
that
you've
discovered
and
maybe
most
importantly,
you
can
download
the
code
run
it
yourself
and
see
what
stands
out
to
you
that
you'd
like
to
contribute
to
or
that
you're
interested
in
in
in
just
opening
an
issue
and
telling
us
about
that.
Would
just
that
would
be
just
as
helpful.
M
So
all
that
it
requires
is
no
js'
and
a
unix
e
environment.
Presently
we're
working
on
windows
compatibility
that
should
be
there
soon
so
again,
we're
very
excited
to
release
it
and
make
it
fully
compatible
with
the
Magento
Enterprise
Cloud
by
the
end
of
January,
and
we
welcome
any
feedback
that
you
have.
That's
what
I
got
cool.
A
A
One
thing
or
a
couple
of
other
things
to
note
is
we
have
a
lot
of
events
coming
up
this
year
with
regards
to
contribution,
and
we
have
most
of
them
get
a
lot
of
them
get
tied
to
meet
Magento
events,
for
example,
we've
got
one
up
and
coming
in
meet
Magento
India.
So
if
you're
going
to
be
a
meet
Magento
India
and
would
like
to
start
with
contribution,
then
make
sure
you
sign
up
for
that
event
and
reach
out
the
team
that
will
be
there.
A
I
will
be
over
there
as
well
as
Sergey
and
so
reach
out
to
us,
and
we've
got
up-and-coming
events.
We
also
have
most
projects
we'll
run
weekly
stand-up
meetings,
and
so
you
can
join
in
with
those
and
those,
as
well
as
the
contribution
Day
events
are
available
on
our
public
calendar
and
which
we
we
will
share
by
our
Twitter
account
or
personal
Twitter
accounts,
so
make
sure
you
are
following
us
on
Twitter,
so
you
can
find
out
the
most
up-to-date
information
and
yeah,
like
we've,
said,
feel
free
to
reach
out
to
us.
A
A
So
what
are
the
do?
We
have
any
plans
from
that
point
of
view.
I
guess
this
is
related
to
the
testing
and
the
static
testing,
and
also
specifically
against
ego,
with
regards
to
how
we
are
streamlining
processes
together
with
also
with
the
marketplace
as
well
in
mind,
I,
guess
so.
Yeah,
who
wants
to
go
for
that?
One
I'm.
C
Gonna
address
the
consistency
aspect
of
this
question
for
sure
so
right
now,
one
of
our
focus
areas
for
this
year
is
to
ensure
more
consistency
with
how
we
are
testing
extensions
that
get
into
the
marketplace
versus
how
we
are
testing
the
development
use
case
for
people
who
are
contributing
to
community
projects
and
basically
try
to
create
a
universal
platform
for
testing.
It
is
an
initiative
that
has
been
ongoing
for
a
while
as
a
design
concept,
and
now
it
is
finally
sort
of
becoming
fleshed
out.
C
So
once
we
have
something
more
concrete
to
announce,
we
definitely
will
but
just
keep
in
mind
that
it's
coming,
and
we
really
want
to
provide
you
with
tools
that
you
can
use
for
testing
your
code
and
ensuring
that
it's
getting
tested
in
the
same
environment
as
a
marketplace.
Submissions
are
or
our
internal
development
is
so
that
is
coming
in
and
we
really
are
focused
on
providing
you
with
some
better
Quality
Assurance
tools.
Tom
and
Alexi
kolesnik
will
be
working
really
hard
on
promoting
how
to
create
em
FTF
tests.
C
How
to
you
know,
get
everything
set
up,
how
to
contribute
and
all
that
and
so
keep
your
eyes
peeled
for
those
webinars
they
are
coming
in.
Alexi
kolesnik
specifically,
will
be
running
them
because
he
is
our
I'm
FTF
testing
guru
and
make
sure
that
ya
that
you
jump
on
board
really
because,
as
time
passes,
we
are
really
focusing
on
quality
and
we
will
be
prioritizing
work
that
have
that
is
strongly
covered
with
functional
tests,
and
there
is
no
better
tool
right
now
than
Emmet
yet
right.
A
Okay,
cool
yeah,
I
think,
like
ego,
we
are
looking
to
get
everything
kind
of
streamlined
and
running
under
the
same
sort
of
running
in
the
same
direction.
So
it's
not
like
you
have
one
set
for
marketplace.
One
set
for
this,
but
all
working
together
for
the
same
outcome,
so
I
hope
that's
answered
your
question
and
it
didn't
I'm.
Sorry
reach
out,
join
us
on
slack
to
reach
out,
and
one
of
us
will
hopefully
be
able
to
get
a
better
answer
in
that.
If.
C
A
So
we
know
that
this
is
the
direction
we're
aiming
for
and
please
it
was
the
feedback
to
say
yeah,
that's
a
great
direction
or
correctors,
where
you
think
it
might
not
be
the
best
idea,
but
without
the
feedback
from
the
community,
and
we
need
that
feedback
to
make
sure
we're
going
in
the
right
way.
So
yeah.
Thank
you,
everyone
that
has
presented
and
thank
you
all
for
joining
and
I,
guess
that
pretty
much
wraps
it
up.