This document discusses a new delivery channel for community contributions to Magento called the Magento Quality Patches (MQP). The MQP allows community developers to submit fixes via pull requests that are then tested, verified by maintainers, merged and published as patches that merchants can easily install. This streamlines the process of delivering community fixes. The role of community maintainers is also outlined, such as code reviewing contributions and managing the delivery of patches to merchants. Potential benefits include empowering the community and providing critical fixes, though there are also risks like a lack of refactoring or cumulative testing of patches.

1. New Delivery Channel for
Community Contributions
Stanislav Idolov
Gabriel Galvao da Gama

2. Magento Quality Patches

3. ©2020 Adobe. All Rights Reserved. Adobe Confidential.
MQP Overview
Highlights
• Easy installation via
composer for all
installations types
• Allows customers to have
quick access to core fixes
 Designed to distribute quality patches
 Available on Cloud and for OnPrem Magento customers
 Customers can get the latest available patches, select
the required, and apply them

4. New Delivery Channel Overview

5. ©2020 Adobe. All Rights Reserved. Adobe Confidential.
Contribution Channel Overview
5
Release notes
reviewed by
Maintainer
Community reports
an issue for
Magento 2.3.7
Community
developer creates
Pull Request to fix
an issue for 2.3.7
Pull Request is
tested automatically
via GitHub App
Pull Request is
verified by
Maintainers
Pull Request is
merged and
converted into MQP
patch
Community patch is
automatically
published in MQP
Merchant applies
community patch
on Magento 2.3.7
• Community fixes delivered
to merchants as patches
• Integration with MQP and
Magento Cloud
• Patches delivery handled
by the community

6. ©2020 Adobe. All Rights Reserved. Adobe Confidential.
New Delivery Channel Benefits
Pros Cons
Potential Support for any Magento
version
Community can patch any supported Magento
versions
Streamlined delivery process
Fix delivery process will be supported by
community maintainers and boosted 10x time
Empower Community
Community maintainers are empowered to
accept the community patch
No direct core contributions
Community cannot deliver fixes directly to the
Magento core. Core team will incorporate important
fixes
Non-cumulative patches
No guarantee on multiple patches compatibility.
Patches are tested individually
No general refactoring, test coverage, cleanups
Community won’t be able to deliver general code refactoring,
additional test coverage, cleanups, etc.
Critical fixes for business
Ability to apply only necessary, critical for your
business fixes and apply them as soon as they
are ready
Unified experience
Supported integration with MQP tool.
Integrated with Magento Cloud ECE tools
Automated release process
Automated packaging of new version of MQP on
schedule

7. Community Maintainers
Community maintainer role in supporting Magento Open-Source
ecosystem

8. ©2020 Adobe. All Rights Reserved. Adobe Confidential.
Community Maintainer Role in Magento Ecosystem
Magento Community Advocates
Follow Magento processes, use tools to provide
clear, transparent contribution flow
Communication
Maintainers team helps in collaboration with the
community members on public channels
Code Review
Review community contributions according to
the Magento technical requirements and
guidelines
Community Fixes Delivery
• MQP patches delivery based on the contribution.
• PatchQA handled by UNUM automatically.
• Automatic MQP releases and fast availability for
merchants
• Ability to apply patch for everyone, ASAP.
• Patch release note review
Issue reports verification
Verify and confirm submitted issues, collaborate
with contributors to clarify on issue details.
BacklogTriage
Prioritize community contributions according to
the issue severity and potential impact on the
platform Public Events Support
Participate and help Magento teams on public
events

9. Joint Development
Community Driver Projects

10. ©2020 Adobe. All Rights Reserved. Adobe Confidential.
Joint Development
Joint project backlog is predefined by Adobe Commerce
product engineering
Joint project development team consist of two parts –
Internal team and Community members
Joint projects are supported by Adobe Commerce
internal team including product organization, UX, quality
assurance, documentation, etc.
Magento Open-Source projects shared with the community
Internal team – provides backlog and
project coordination.
Community members – provides
solutions to resolve issues from the
backlog.