open source

Talk-Commerce Matthias Schreiber

Navigating Challenges and Embracing Collaboration: Insights from Matthias Schreiber

Join the insightful journey with Matthias Schreiber on “Talk Commerce” as we delve into the open source ecosystem, Magento’s evolution, and the collaborative future of e-commerce.

The 411 on the Magento Community

The Magento community provides a rock-solid foundation for the continued success of the platform. The connections, collaboration, and shared vision of community members give Magento unique advantages.

Jisse Reitsma

Mage Open Source Community Alliance with Jisse Reitsma

Today I have Jisse Reitsma from Yireo. Jisse and I have an open conversation around Mage Open Source Community Alliance and some reactions to the letter. We talk about the reaction from the Magento Association and talk a little about what could make it better. If you are interested in talking about this subject, please reach out to brent@brentwpeterson

The community is in charge of the innovation, and the Magento association should bring it out. @jissereitsma #MOSCA Click To Tweet Brent Peterson: “The real beauty of our community is the innovations that happen.” @jissereitsma #MOSCA Click To Tweet


The discussion on this week’s podcast focuses on the current issues developers are facing with Adobe and Magento. Two main issues discussed were the transparency of Adobe and the monolith and modularity dichotomy.

The MOSCA open letter challenges them to make the changes they want to see now instead of waiting and talking. @JisseReitsma #MOSCA Click To Tweet

The Mage Open Source Community Alliance (MOSCA) open letter to the community sought to show that developers care about the Adobe products and believe that the open-source code that drives their products is neglected. Developers are accustomed to accessing a roadmap of the software shared with the broader community, which shows transparency, and some don’t believe that they are receiving that transparency with Magento.

It is believed that open source development lies in the hands of developers, and instead of just talking about the changes that they want to see, they can make it happen. That is one point that the open letter drove home. However, at this point, the change seems to be happening without actually any organization.

An important question in all this discussion is if there is indeed a split, who would own the trademark? Who is going to be the owner of the source codes? Who will be responsible for fixing the bugs as they arise?

If Adobe is not becoming more transparent in their decision-making, if there’s not a roadmap being published upon opensource, assuming that there is one, then actually the community will not see which way the whole Magento opensource thing is growing. Then, in the end, that’s going to mean that many people are just so unsure about a fundamental something that they’re either going to leave or create a fork or are going to stick with even Magento one. And that’s the direction we don’t want to go to. Something needs to change.

If Adobe is not becoming more transparent in their decision-making, if there's not a roadmap being published upon opensource, the community will not see how Magento is going. In the end, that's going to mean that a lot of people are… Click To Tweet

While some developers believe there is no need for a monolith, others believe it is functional. The proposed decomposition of the monolith by Magento does not leave developers with a choice. It is suggested that developers be given an option to decide whether or not they want to go the route of the monolith or modularity. It boils down to deprecating or not deprecating.

There are a lot of Magento merchants that use the software, and a lot of those merchants feel uneasy about where their version of Magento is going. A question that they have is if Magento gets more complicated, does that mean that it would get more expensive for them to run their store?

Some proposed solutions to having Adobe communicate and be more transparent with the community are having a monthly bulletin, utilizing social media, and employing a social media and marketing committee to keep the community informed. This way, developers could openly share their ideas and grow on them like trading at a bazaar. What is currently happening is that the discussion is taking place in a cathedral manner. There’s a lot of conversing and what comes out is a filtered down smooth message that doesn’t have teeth and is unopinionated. The beauty is that the community is in charge of the innovation, and the Magento association should bring it out.

What it comes down to is just more communication and transparency from Adobe would solve these problems.

More quotes from the Podcast:

Please tweet:

The modularity is like the solution to the decomposition of the monolith. @jissereitsma #MOSCA Click To Tweet Brent Peterson: "What we're coming down to is more communication and transparency from Adobe." @jissereitsma #MOSCA Click To Tweet The goal shouldn't be to make Magento more complex by adding new architectures and whatever, but rather to make it less complex @jissereitsma #MOSCA Click To Tweet Brent Peterson: "The open-source, which is the bulk of the installs of Magento, has a large influence on where the code is going. Adobe cannot continue to influence the code in an enterprise manner. That further alienates the… Click To Tweet Adobe needs to listen to all of this feedback and see how that could be fitting into the more significant board portion of the story. @jissereitsma #MOSCA Click To Tweet If the source code is not living up to its expectations, everyone will simply leave. @jissereitsma #MOSCA Click To Tweet Brent Peterson: “Let's educate people about monolith, microservices, and isolated services. Let's help people make educated decisions about these things, point them in the right direction, and start building content around that.”… Click To Tweet