Magento Import/Export Weekly, 9 Nov 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Import/Export Weekly call 9th November 2018

Description

Recording of the import/export weekly call from the 9th of November 2018.

This project focuses on the https://github.com/magento-engcom/imp... repository with the aim to provide some key bug fixes in the 2.3 release of Magento 2.

If you would like to get involved in the project please see the github issues or contact the Magento Community Engineering team for more information.

A

Yeah good I apologize for my cough or the quality of my voice, but yeah. Let me introduce myself I'm your I'm gonna be managing all the special projects in the Magento engineering community, community engineering team, so one of which is the import-export project led by the illustrious David manners here for everybody who is gonna, be watching this recording for posterity.

A

It was better today than it is where you are, and also feel free to reach out to me with any questions about anything that pertains to helping you out, helping you reach somebody or something or any general powwow that you may want to be. A part of I will be working with David on this project, including its long-term plans and any potential changes with it in its direction and also on communicating everything to you guys so I'm here as the facilitator- and you know, ground-level help basically I'm located in the Austin office.

A

So whoever needs to help us in whoever needs to make any decisions that may impact us are the arm's length away. I'm gonna use that hopefully productively to push us forward and that's gonna, be it I. Guess, oh.

B

Nice yeah I think it will be useful to have someone closer to people, so they can push people a little more. To get absolutely is the feedback link I'm all for it. A feedback loop has been a bit slow in certain cases, cool awesome. It is good to have you on board with this, so I would suggest the next update costume. You have an update or I an update on your ticket on your pull request. I just.

C

Saw it like one or two hours ago, I cannot imagine how it happens.

C

Looking at the code, the functional stuff, that's being done, I, don't know how it could happen that yeah, when what you described scenario.

B

So the the feedback from the QA team was that they did that scenario in 2.3 and in the end, you ended up with three products. One called test: one called test one and one called test.

C

B

And then on our branch you had one called test, one called test one and then, when you should have got test, you got the error. So yeah would just be the step through and see see if you can find yeah yeah.

C

B

From from your code review point of view, Alex had a look at it and he was happy with it. So it.

C

B

Just this this testing, and then this is a huge pull request to get in so I'll, be I'll, be very happy when this one's covered yeah.

C

Okay I'm on vacation next week, but I'm not traveling, not travelling somewhere, so I guess I would, if.

B

You get time, please, if you don't don't worry about it. Vacation is important.

B

C

Not coming anyway, the other thing I would do would play vplace. They say: okay,.

B

Then you can probably spare some time for us next week, then yeah.

C

B

Get cool all right cool then.

B

So, if you're gonna look at that cousin that'd be awesome, then, from my side there has been we've had four pull requests merge this week, I think which is pretty cool, and for the last month we had 16, which I think is the highest 16 for birth created, which is the highest we've had a lot of those who are clean up and tasks, and so I went through the import modules and ran some PHP stand over them so that we could get some cleanup tasks and try and do some and issues that were easy for people to or easier for people to start with, because I felt, like a lot of our port issues, were very hard to get involved in and so I wanted to get some to get people interested and involved quicker.

B

I wanted to get some smaller tasks that they could and get their get their teeth into that weren't, so complex, but I think at the moment most of those have been have been picked up. I think there's a few left. So what I'll do is I'll review next week, I'll go through and review and see if I can find some more. That might be easier. Do pick up other than that we had one poor request that was merged to do with actually showing success messages.

B

So at the moment, when you've complete an import, you just get a message thing successful, and so we have one. In the last contribution day in Cologne, we have a contributor provide a PR that showed you, the exact number of products and categories that were imported on the success page, which is a in terms of code. It was like four lines of code, but in terms of usability, it's a huge improvement which is which is awesome, so that should be it's in two three develop and I.

B

Think I can't remember the cutoff day, but that should be in two three one, so that will be a fantastic improvement from a usability point of view. That.

A

Update is behind us just to let you know. Oh okay,.

B

A

You three oh yeah. We.

B

A

Have the RTM version and it's bad already and we're backing it. Yeah.

B

So all the stuff, at the moment, I think, is still in time for 231. Well, I! Guess it's in time, 50 yeah! It is other than that. From my side, the only other feedback was today I'm in comm reps office, so I've been chatting with Alex, who runs the bulk API project and is starting up the asynchronous import project and so I'm trying to get him and the architectural team, with the help of ego here to kind of discuss and decide what the best process is.

B

The long run, I think from Anton krill would be that he would love the import to be replaced with something like the asynchronous import which alex has suggested and what I will do after this is I will post the link to Alex's proof of concept or architectural discussion topic into the slack?

B

So if you want to take a moment to see where the import might be heading I'll post, that in slack, so you can see that we don't know how the projects will run and that's one of the things evil is going to help us organize how best to write and of combine things. If we do or whatever so it's.

A

Early to tell what the timeline on that project or the entire initiative will be, but what would help me in particular is seeing gauging the community interest and moving on and making the async import.

A

The the you know the priority and deprecating, eventually the current import mechanism, so understanding how much interest there is would be awesome and would be would help us a lot in kind of determining the way forward. Also talking about Alex and his bulk API project just may be there, because there is some overlap between what we're doing and that just wanted to tell you guys whoever's on the call will be watching today or soon.

A

We have basically made bulk api c bulk api ii repositories obsolete at this point and all of the bulk api work is going to be in a sync import, I think repository.

A

So basically the from that standpoint we had bulk API and we had async API, which were the same thing, but some of the work we're done in this repository. Some some work was done in that repository, so I've asked volodymyr, complete ski and Alex to go through it and merge all of the.

A

Missing from the async import repository into it, and we will close down bulk api c bulk api e repositories fairly soon, so that we continue with one repository for that project, because that's basically one project at this point, yeah yeah.

B

And I think if we ended up combining the import into the a thinking, what will you do something very similar in that case.

A

As well exactly in my end of the day, we will be shooting for async import, basically being all things async, all things important, yeah.

B

But it's just how how quickly that takes over. So what we'll do is we'll continue at the moment with the import as it is, and but if you want to drop even myself or ego on message and if you have any interest in the async import, then that would be a good one. I will might be. Actually you go if you post I, think you can do poles in the slack.

B

So it might be a good idea to post a little pole or a question in the import slack and just see by Carsten or tag is the other guy that has been contributing quite a bit as well as Stephan from Hamas tena, annecy, yeah I. Think it's a mercy or maybe it's a Twix I can never remember, but he they they're kind of the guys that have been consistently contributing.

B

So they're probably I mean we could ask caste and now, since he's in my call, no pressure or feel free to feel free to think about it and like what we're doing at the moment is kind of like the planning and architectural side of it. And it's just whether you would like to the I think for me. The main question is whether we get the community more involved now with the architectural and the design part of before, there's actual coding involved or whether we just wait and then go okay.

B

Now this coding involved, let's, let's kind of combine all the import projects together under this new important I, would.

C

Be interested to be involved early I'm, not sure if I can contribute that much, but yeah I would be interested. Oh.

B

Nice, okay, all right all right, then I think that's everything for today. So that's good though thanks for coming in and yeah feel free to reach out to either myself or ego. If you have any questions and yeah Carsten, if you have any problems or you can't reproduce that issue, let me know and I can ask our QA team for some more information on that all right. Thanks, guys, bye, bye, bye,.