►
Description
What we did:
- discussed the recent PRs
- did a quick check-in on the async import module
- were generally intelligent and handsome
B
A
A
B
A
A
A
Before
fine
yeah,
then
we
can
turn
against
merge
it
good
that
was
related
to
this
one.
So
from
a
synchronous,
import,
module,
I
worked
it
out
on
a
base
extension
for
it.
I
had
several
topics
for
it
to
discuss,
but
not
related
to
the
code,
development,
more
related
to
the
architecture
of
our
repositories,
as
currently
we
have
our
import
repository
and
I
would
say
that
if
I
want
to
invite
like
more
people
to
the
contribution
to
this
project,
so
my
idea
was
to
build
the
base
extension
kind
of
with
minimal
functionality
like
first
endpoint
interfaces.
A
Registration,
page
peel,
also
the
basics,
and
if
we
can
build
it
and
merge
it,
then
then
other
people
can
work
on
some
smaller
part
of
it.
So
they
can
then
continue
to
make
pull
requests
into
it
in
the
smaller
parts
and
they're
not
blocked
by
me
or
by
a
base
implementation.
So
that
was
my
idea.
I
I'm,
quite
close
to.
A
So
yeah
from
the
beginning
is
the
extension
called
import
service.
If,
if
you
already
have
some
complaints
about
names,
you
are
welcome,
so
it
call
Magento
import
service,
which
is
currently
only
the
basic
implementation
which
is
glued
one
endpoint
for
post
start
import,
which
is
generally
just
be
one
import.
Then
we
have
the
database
schema,
which
is
also
only
one
table,
so
it
will,
it
can
be
extended
in
the
future.
A
Api
can
be
extended
in
the
future,
but
it's
not
about
to
make
it
leave
the
base
extensions
that
people
can
contribute
or
propose
the
ideas
there,
which
I
guess
will
be
quite
nice
yeah
so,
and
what
we
hear
here
journal
is
some
kind
couple
of
interfaces,
so
we
changed
by
the
way
Appy.
So
we
first
had
an
idea
to
have
it
like
here
the
file
entity,
so
we
import
the
file
entity.
A
We
had
some
discussion
and
I
also
want
to
know
your
opinion
on
it
or
we
change
it
to
the
source
because
generally
file,
finally,
is
a
basic
you
need
for
import
so
to
make
an
important.
It
says
V
file,
XML
files
or
base64
input
data,
but
also
it
can
be
possible
by
developer
in
the
future,
to
add
the
old
processor
and
to
process
our
FTP
connections,
or
maybe
even
some
small,
simple
API
connections
which
deliver
your
file
RSS
feeds
whatever.
So
in
this
case,
I
wanted
to
go
away
a
bit
from
the
file
naming.
A
Okay,
good,
then,
then
yeah,
then
what
I
will
do
I
will
made
a
pull
request
is
a
base.
Implementation
will
be
happy
that
we
can
maybe
remove
it
together
and
to
merge
to
have
the
basics,
and
then
we
can
already
invite
the
people
to
make
the
test.
V,
import
processors,
remote
source
basics,
before
import
and
so
on,
so
to
have
more
small
parts
can
be
contributed
inside
of
the
project.
I
would
also
by
the
way.
What
would
we
know
if
we
merge
something
in
2.3
here?
It's
not
automatically
synced
with
the
main
red
power.
C
A
Already
I
mean
journey
I
guess
from
Magento.
It
seems
here
yes,
I
guess
it
seems.
Yes,
it's
all
it's
already
sink.
You
see
it's
like
20
hours
ago
changes
here.
That's
good
I'm
all
think
that
what
I
want
to
do
I
want
to
merge
the
base
extension
with
two
points,
three
but
I'm
sure
like
100%
sure
it
will
not
be
found
final.
It
still
may
change
interfaces
may
change.
Api
may
change
so
I
want
that
this
repository
will
not
be
sync
as
much
with
main
much
answer
repository
those
that
we
will
sync
it
manually.
C
If
you
will
split
changes
to
several
folders,
it
will
be
much
more
complex
and
for
a
messiah,
for
example,
we
were
unable
to
do
to
face
all
the
histories
from
that
repository
because
it's
like
it
has
a
lot
of
folders
and
it's
just
just
a
complex
so
and
in
in
future.
We
would
like
to
like
you
need
to
have
separate
a
repository
for
this
particular.
A
C
A
He
also
told
me
that
when
they
had
some
sense,
its
have
to
be
edited
in
in
Magento
modules
or
other
one.
They
asked
to
make
a
pull
request
first,
in
Magento
main
line,
and
you
know
to
make
me
make
a
call
changes
in
them
aside,
for
example,
yeah,
yes
good,
then,
for
today,
from
my
side.
That's
all
if
somebody
has
a
questions,
ideas,
complaints,
let
me
know
I.