Magento Community Engineering Hangouts, 16 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Community Engineering Hangouts. Jun 16, 2021.

Description

Agenda:
-0 New Community Contributions Delivery Channel by Gabriel da Gama and Stanislav Idolov

A

Okay, hello: everyone welcome to our regular community hangouts. Today we have only one but pretty much interesting topic to share with you and to discuss with you myself at gabrielle, where we'll share the news. So, let's begin.

B

Okay um stars will share your screen. I would like me to share believe it will be more convenient if you will share it sure. One second, now.

B

Okay, let me know when you can see it yeah yeah. We can see it okay, good, um so hello, everybody, um my name is gabriel, and um today we will be sharing myself and stanzlov, we'll be sharing some news about a new delivery channel for the community contributions.

B

So uh before, starting on talking about this new delivery channel, um I think it's important to talk about a tool that will be used on this new channel. Some of you guys may be familiar with it. It's called magento quality patches so as often used and referred as mqp, so mqp was introduced last year. I'm not sure if you guys have the chance to to use it, but uh was designed to distribute quality patches for magento customers, and it is available, I think, by default, if I'm not mistaken on uh for cloud customers.

B

So it's already part of the ece tools and you can used um on your instances but is also available for on-premises customers and you can install uh via composer um and also what like, what the tool does. It's basically allow the customers um to get the latest available patches um select, which one are required for their magento version and install them.

B

The usage is pretty simple: it's uh it's a command line, so, as you can see on the on the print screen um that I have there, um there are some other commands you can check it out on the on the repo or dev docs. There are also documentations about it. uh One of the commands, for example, is status which shows some details about which patches are available for your uh magenta version and which ones are applied on your instance.

B

So this one I I took from a cloud that we use and some of the patches were already applied, and you can also see some patches that are not applied and you can apply them and so on. So you basically it's uh it's a tool to manage your pat, the patches that are available from the the support team.

B

So some highlights of this too. Basically, it's pretty easy to install and it's just like a composer package and it can be used by cloud and a non-cloud on-premises customers, and it gives the allows the customers to have access uh pretty quickly to car fixes. So sometimes these fixes will be part of the next release, but you know releases takes a little bit of time. So if you want to get the fix a little bit earlier, these two will be the way to go.

B

Okay, so talking about the new delivery channel, so um we'll be starting with this new delivery channel introducing to the release line of 2.3.

B

So here on this example that I will use to explain this um new contribution channel. We will take as an example the the release 237, so I will make some comparison with the the current process that we have uh well for 2.3 release line. Currently we do not accept contributions, but I will make some comparisons to the process that we have for the 2.4 release line, because it's slightly different.

B

So, um first of all, uh we will have the community that we report an issue for that version of magento. So, as the usual same same template that we use currently on our um contributions uh from that issue, after being confirmed, a developer from the community will create a pull request that fixes that issue.

B

um Some of you guys may be aware. We have a pretty uh extensible test suit that tests several areas of the application and the pull request will be tested by that automate by those automated tests and all the tests will have to be green and then we'll move to the next stage, where um pull request is verified by maintainer, so our maintainers will just analyze which changes are are being made on that um and approve it or request some changes usual process. So far.

B

So until this point, there's really no difference from the current uh contribution model that is being uh used on the 2.4 release line. So on this one that is being introduced recently, we will, it will be introduced soon on the 2.3 release line. Here's where some changes happens, so um the release notes will be reviewed by maintainer.

B

So, on the pull request, uh there will be some uh release, notes which you basically describe uh what the patch, what the pull request is fixing, which is the issue with some more details or like a sentence, something like that so maintainer. We will be also responsible for reviewing that, after that happens, and everything is fine, the fix is fine. The description and release notes are fine. Tests are green, maintainer will approve and will kind of trigger the merge button for that uh pull request.

B

So that's when you will kick in some automations that we we have been developing, so uh the pull requests will be merged and uh will be converted into a mqp patch so um that community patch uh will be automatically published to the mqp pool patch pool. So um if you like try to run status command from the community, the mqp command line, you will be able to see the patch that has been merged recently so and the merchant will be able to apply that patch on their magento version 237 in this case.

B

So some highlights on this. The community fix are delivered to merchants in this case as patches.

B

There will be this integration uh with mqp and magento cloud in this case and and the patches are delivered and handled by the community so in in this example, in this new contribution channel, there is no intervention from um internal team. um The community can handle the process by themselves.

B

Now, let's talk about some pros and cons of this model, let's start with the pros, then so potential support for any magento version. As mentioned previously, we are starting with the 2.3 release line and the community can patch any supported, magento version. So currently that's not possible. We do not have any uh intervention from the community on the 2.3 release line uh a streamlined delivery process, so fixed uh delivery process will be supported by community maintainers and boosted by 10 times. So, um as you may be aware, some I see some contributors here.

B

Our delivery process takes a little bit of time. uh It is a complex process. There's a lot of people working on on the monoliths, it's a big application, so it does take a little bit of time.

B

So, with this new process, it will be way faster for the um community to have access to those fixes. So here we are, we are empowering the community, um so the maintainers uh will be empowered to accept these contributions.

B

Critical fixes for business, so ability to apply only necessary critical for your business fixes and apply them as soon as they are ready. So, um as mentioned previously, as as soon as the patch gets merged, um it gets uh available through mqp. So it should be pretty fast for you to have access to those fixes.

B

uh It will be a unified experiences, so supported uh integration with mqp integrated with the cloud ec tools. So for the cloud customers they will have mqp already installed on their instance, so they don't need to install anything really so yeah, that's very good and automated release process. So all the packaging and new mqp version it will be uh done regularly.

B

So we there will be no interpretation. It's everything automated uh and some cons of this specific um channel. There will be no direct core contributions on this uh with this model on the the release line 2.3, so community cannot deliver fixes directly to magento core, but that doesn't mean that community will not uh contribute to the core with those fixes, because our team will still uh keep an eye on those, and some of those fixes will be incorporated into the core, the ones that are really important in this case, um there's no cumulative patches.

B

So at the moment there will be no guarantee on multiple patches compatibility patches are tested individually, so we highly recommend you to before applying any patch to it. uh Mqp actually already does this recommendation.

B

So if you read the docs, you will see, but we recommend you to apply the patches in the stage environment, test everything and make sure they are compatible if you are using more than one community patch, which may be some cases um also no general refactoring test coverage or cleanups contributions, so um community won't be able to deliver general code refactoring and- um and this kind of contributions uh will not be possible through this model, but they are possible on the current model that is being used on the 2.4 release line.

B

So this is the overview basically of this new model and some pros and cons so yeah. I will pass now to to stars to continue talking about the community maintainers.

A

Okay, thank you gabriel. uh Could you please go to the next slide uh so guys? uh I believe you definitely know about our lovely maintainer team, maintainers team. We have a lot of really active community members who are helping us a lot with full request review uh on. Like this current slide, you may see all the activities the guys are helping us with uh like handling a lot of a lot of stuff there.

A

So, first of all, they're reviewing the quote on the public, like public github repositories in scope of different projects like the main project. It's definitely magento too, but also we have a lot of other projects like msi adobe stock, so maintainers team helping us uh in like all of the projects so also they're, helping us to charge the backlog. We have public meetings uh for the triage and guys also helping us to try some really like interesting uh like uh interesting and uh high priority issues.

A

So also we have quality assurance maintainers who are helping us with issue, verification uh like they are providing some feedback to the contributors, trying to verify the issues, uh clarify the steps and so on so like in the end of this process. We are, we will have like issues that are ready for the development and any developer can pick up it and start to fix it. So it's basically a really good issue. Reports that are ready for for pickup and development.

A

uh Also guys are like up to date with our guidelines with our requirements, uh our processes and like during the code reviews. They are following all the processes and guide contributors how to properly develop the code. How to you know, deliver the code, explain the processes and so on also a huge part, its support uh in scope of public events.

A

So, during the contribution days during the hackathons uh maintainers team, helping like all the contributors to stars that contribute to the magento for, like first-time contributors, they're uh like helping to uh understand the processes uh like to clarify some development details, and so on. uh Also like we have, we have different communication channels in scope of magento project like the first, maybe like the biggest part.

A

It's a github so guys providing like support us to like, in collaboration on the github, on the forums on the stack exchange and so on and like in addition to all these activities.

A

The guys already already providing for us, we will grant them those permissions to deliver community fixes right now in scope of nqp mkp2, so, like uh maintainers team, will review the contributions and will be able actually to deliver such contributions to the mkp team as a patches and as gabriel mentioned before, we will have automated packaging process for the mkp2 right now we are planning to package uh like to have the new versions of the mtp2 uh daily and uh let's say once the pull request uh like some fix uh will be delivered today to the nqp patch.

A

It will be available in scope of the new version of mkp2 tomorrow. So it's it's really like a fast way to deliver and actually use the fix. So merchants who are like struggling with some some issues on the production will be able to like get these fixes as soon as possible.

A

Gabriel, can you move this to the next one uh yeah, uh as gabriel mentioned before it doesn't mean that we will not accept uh community contributions to the core, so we will constantly monitor all the patches that are that were delivered to the npt tool and the most critical patches. The most uh useful patches will be incorporated to the core itself uh and, like their second, the biggest part is joint development projects. So in scope of joint development projects, uh I mean you also can contribute to the magento query.

A

uh What is joint development project itself? So, as a really good example examples we had such projects as msi as adobe stock security package and so on.

A

So we already had a good experience with such projects when we have predefined backlog from let's say, magento site, adobe commerce, site and then like such projects, always contains like from the from two parts, is internal team, internal magenta team who will support this project, providing some backlog, explanation, designs, resolving the questions and so on, and the second part is, of course, community members who are willing to contribute to this project and work on the issues from this project.

A

Backlog so like, like we had, let's say with msi projects, will be fully supported by the internal team and will work along with the community on some features, some new functionality and so on uh recently, I believe. Last week we already announced the new project. It called platform health. So in scope of this project, uh like a lot of dependencies to like third party libraries, some technologies can be updated. So we really need to need your help there right now and also we will have more projects in there like next few months.

A

We will be announcing them and yep. You will be able to join them and work on those projects too.

A

Okay, I believe that's it from our side. We have 10 minutes left for.

A

B

Come on guys, hi yeah, I can't see any any questions on the chat. The microsoft themes. Chat is isn't great. Sometimes I'm trying to check on my phone.

B

Any questions guys anything is not clear or need some. Some clarification.

A

Okay, I believe we have the first time.

B

Okay, um let's start then so the first question was what was the announcement today, so um we were announcing about uh a new contribution channel. uh We will share the recording of this meeting later so you'll be able to to watch it fully um so going to the next one, some mq pet mqp patches, don't make it into the next release. Will this be changing with this process?.

A

uh Yeah, then, could you please clarify? Does it mean that, like some of the pages uh that like exist in scope of mqp2, uh were not delivered to the next magento version and exist in mkpito only.

C

uh Yes, so sometimes there's a patch that shows up in the mqp tool that takes one two or three or sometimes four minor versions until it lands in an actually released version. Is that is that changing with this process? Or is this process going to be supplementary to the existing mqp.

A

uh Yeah in scope of the community patches uh like process will remain the same, so the most, the most like high priority patches that were delivered to the mqp will be incorporated to the core, but some of the patches that are not not so critical. Let's say it's like low priority files that can affect only I don't know. Let's say one percent of the merchants, so most likely it will not be incorporated to the magento core and will exist as a part of mkp2. Only but still like.

A

Every merchant who is struggling with such issue will be able to apply it via mkp tool.

C

Okay, cool. Thank you. I was mostly asking about if we need to change our process in terms of reviewing all the mqp batteries that come out, but it sounds like we should continue reviewing them all individually for all of our merchants.

C

B

Okay, next one from navarre, so you said that with the new delivery channel, that refactors and so on, could not be submitted to clarify. Is this new delivery channel the only delivered channel for contributions.

A

uh So, uh as we mentioned before, we will have like uh several delivery channels. First of all, it's joint development project. So in scope of the projects, uh all the core will be incorporated to their to the core uh and in scope of their patches.

A

uh It means like we cannot, cannot accept the refactoring some cleanups, because, uh to be honest, it doesn't make sense to deliver such contribution as a patches. So let's say uh some merchant with production store will apply refactoring.

A

It doesn't like change functionality at all and like it doesn't make sense to apply such patch because it will add more complexity and will not resolve any functional issue in case. If some refactoring will bring, let's say some performance improvement. So yes, in this case it's definitely worse to have such patch, and you know merchant can apply it to improve some performance of some scenarios and yeah. It definitely makes sense. So it's the same for the cleanups.

A

uh It doesn't make sense to apply patch on production work environment that will fix uh dog block because it doesn't make like really sense because it doesn't change functionality at all, and it's like strictly a development experience that, like can be avoided on production environments,.

B

Okay, um any any other questions guys.

B

Okay, if no other questions, I would like to thank you all for participating and joining us today.

B

Again, if you have any questions later or anything that come up, I think I just received one your message: what will happen to currently open pull requests.

A

B

A

Yeah would you like to handle it.

B

Oh so, firstly, um as mentioned, uh we are opening this new delivery channel to the 2.3 release line, um so there's no open contributions to to the tree. So that's that's not possible. We are still processing at the moment. We are still processing um contributions to 2.4 releases.

A

B

Usual for now,.

B

I would like to add something: it's us.

A

uh Yeah, like, as gabriel mentioned, we will open 237 for for start, and then we will consider to open, like other releases, for patch deliveries as well. Let's say like 241, 242 and so on and yeah, like all the contributions can be targeted to this. Really this as well and yeah. We will be processing too good for develop as usual.

B

Yeah and one more question from dan, it was suggested. These are regular meetings, there's only one in the calendar. When is the next meeting, so these hangouts, I believe they um well a lot of people from internal, they speak on it and we just I think we announced it one week or so before the the next one happens. Correct me if I'm wrong um stars.

A

Yeah yeah you're right and usually we have like one two meetings per month uh and yeah. We are trying to announce like several days before the meeting with agenda with the speakers and so on. uh Also, I will share with you the link to our community portal when you can find uh all the information about community handouts about previous meetings about upcoming meetings, so yeah, and also of course you can, you can add the calendar and track track. The meetings in scope of the calendar as well.

B

Yeah yeah. We also uh use zlac and twitter at the moment as um communication channels to um publish when these events will happen. So um stay tuned.

B

Okay, guys, um so if no no other questions, um thank you all for participating and hope. You have a nice day nice evening and chat to you on the next one.

A

See you guys thank.

A