Re: Open letter to the Magento Community
Guido X Jansen ?? ?? ???
Global Evangelist @ Spryker | Applied Cognitive Psychologist
This is my personal perspective on "The Future of Magento Open Source" as written down at https://www.mage-os.community/blog/the-future-of-magento + https://hyva.io/blog/news/the-future-of-magento-open-source.html* and why I haven't signed the petition.
Disclaimer/Context:
I've been part of the Magento community since founding the local Dutchento.org community in the summer of 2008, organized many Meet Magento events, attended even more, Magento Master 2019, etc. etc.
Specifically relevant for this is that I've been part of the founding task force and subsequent inaugural board of the Magento Association. I've resigned from that position this month. I'm leaving because next month I will be joining Spryker, not because I don't believe in what the MA stands for. To prevent any potential conflict of interest I decided to step down from my board position at the Magento Association. This - again - means that this is my personal reaction and it does not reflect the viewpoint of the MA board.
Forking: I'm not saying it can't be done...
... but it's not easy. Not many have become a success and you'll need quite a bit more than an open letter and people signing it. I've witnessed a very successful fork up close in the early 2000's when Joomla! was formed from Mambo. But in that case, all core developers resigned (taking away all of the momentum from the original project), they incorporated quickly, brought over the majority of the community (including many paying customers) and kept the momentum going.
Reading the letter I feel "forking" is very much underestimated and overvalued. I've lived through it with Mambo/Joomla! before and although that was a decent success in the end, it was a huge undertaking and success if far from guaranteed. We've tried a better way through the Magento Association for the last couple of years. These experiences have inevitably biased me in many ways, but hopefully I can give you a useful perspective on this.
What I agree with
I share similar worries mentioned in these posts. In the past 13 years a lot of merchants, agencies and other additional services have built their livelihoods on the Magento platform. Seeing it not getting the love that it did before, not only hurts in your soul, it might even threaten the future of your company.
It's also disappointing to see that Adobe hasn't handed over more control of the open source project to the community / Magento Association (yet). A lot has happened behind the scenes, but there’s a lot of red tape to go through and it seems there is little incentive for Adobe to make any haste with this. I see many benefits in this, including benefits for Adobe, so to keep pushing this point through the right channels is definitely important.
Challenges I see
TL;DR: Open letters and signing them don't change anything, How is the Allience different from what we have now and finally: Forking brings A LOT of challenges
1) Open letters and signing them don't change anything
Awesome, you have 1000+ signed up. Maybe 10.000 in a month. It's a vanity metric. How is this going to incentivize Adobe? How is this going to incentivize any? merchant or? developer to switch to your fork?
Magento "lost it's way" before. I literally stated this in a presentation in 2014. Replace "eBay" with "Adobe" and update the logo and it's like nothing changed. That's 7 years ago and many of us are still here. There have also been other open letters addressing similar things by Alan Storm in 2016, by Muliadi Jeo and Sonal Puri in 2019.? Pointing out that Magento has lost its way as a community didn't have much - if any - impact on Magento's governance or direction of the product.
2) How is the Alliance different?
It's unclear to me what is different with this initiative compared to what is already available in the Magento community.
What does “We invite you to join us.” mean in this case? Join what? To be fair: I've heard outsiders say the same about the Magento Association, but for an Alliance that apparently wants to set itself apart... please then tell us how this is different and what "joining you" means.
In terms of forking: there already are forks for both M1 and M2. How is this different?
There is now also an Open Source Task Force within the Magento Association (open applications to participate as a group member ran until Sept 10th). The Alliance says it intends to work with MA and Adobe so again: how is this different then? I mean: glad to hear that you want to cooperate, but then what's the need of a separate Alliance?
3) Forking brings A LOT of challenges
Forking an existing code base is a weighty decision: one that forces the many parties reliant on the software to choose one option or the other (Examples of successful open source forks). The Joomla! team did it in a remarkable way, but that is not what I see happening here. You only fork when you have exhausted all other options.
领英推荐
A) You can bring the code, but everything else will have to start from scratch.
If you want others to take it seriously, it can't just be a group of friends coding together. You'll need to incorporate, register (and defend) trademarks, create your bylaws, arrange project governance, and get funding. How do I know this? We did all of that with the Magento Association.
Included in this: You won't be able to call it "Magento"
Adobe owns the global trademark for Magento. Adobe has granted use of that name to the Magento Association.
You can copy it, but you'll need to rename it. Massive marketing/branding/legal challenge if you ask me (I've seen this happen with Joomla! and it wasn't easy).
B) You're fragmenting the community
Magento is a mature product with thousands of websites, agencies and individuals relying on it working properly. Fragmenting the landscape is not in their favor. It might be great for developers, but what’s the business case/benefit right now for all those companies out there making money with Magento? What assurances can you give them right now that is better than what Adobe can do? How will you build that momentum? Even if the fork becomes a viable option, you'll inevitably be forcing people to choose which platform they're running and thereby fragment the landscape.
Continuing the current open source project is still your best option
What any open source project (or a fork) needs for continued success:
For now, I think the ideal way forward is still through Adobe letting go of Magento Open Source and the community picking that up. And the Magento Association is still the best vehicle to facilitate this. The legal entity is already there. The link with Adobe is already there. And you don't have all the issues and struggles that come with creating a fork.
I get that many currently have an issue with Adobe mainly focussing on Adobe Commerce for Enterprise clients and feel that there is no future for open source within Adobe. Even if that is the case: have you tried everything within your power to try to continue the current open source project in a way that doesn't include a fork?
You are already a part of the community and the association. You already have multiple ways to try to make this happen, before forking.
Most of the people that wrote or signed the letter never tried doing this through the Magento Association. And if they didn't stand-up through the entity we created to do things like this, why should I have more trust in them doing it through... writing open letters?
Some suggestions for next steps:
Conclusion
If you co-wrote or signed the original open letter and my words made you feel things: awesome! You all love e-commerce. You all love Magento. I wish you the best of luck in creating your future with Magento.
Make it an upside-down-fork, bringing everyone together instead of fragmenting. From the bottom of my heart, I hope you'll succeed.
__________________________________
FYI, here are some other reaction posts:
* The Alliance announcement is split over multiple websites/posts posted on the same day but with different information in it? This doesn't really help to get a clear picture of what the Alliance wants and to clearly respond to it. Looks like the group agreed on one text and then a subgroup wrote a different version with another plan ????♂?
Founder @ Content Basis | Founder at Wagento (Acquired) | eCommerce Maestro | AI Dabbler | LinkedIn Top Voice | EO Member | 30x Marathoner (Still Slower Than I'd Like) | Recovering Mullet Enthusiast
3 年Thank you, Guido, I think part of the letter is to put pressure on Adobe to share more with the community about the open-source platform. I do agree with not forking.
CEO @MGI Markets
3 年There isn't much to add. From the both first Meet Magento events in GER and NL, followed by the unparalleled expansion into >50 countries, Developer Paradise events, myriads of meetups and hackathons in every place of the world, Meet Magento Association and then the transition into the Magento Association. The challenges and topics you are discussing today aren't different from those of of 2010 and 2017. When we worked in 2017 and 2019 with the Magento management on the concept of a new association and transforming Meet Magento into it, there was reasonable hope to create an organization capable to balance the Magento world and to become responsible for Magento Open Source. You all are aware about the following steps until Magento Association was ready to work. Beside on the shining mission and vision statements there is and was always a few major purposes for the association: Being the interface between Adobe and the ecosystem, representing the interests of the entire community to Adobe and connecting the entire global ecosystem. Without the pursuit of these purposes, all the Association's activities are more or less meaningless in relation to the long-term economic interests of the individual actors and the entire ecosystem. The formation of alliances may be an expression of weakness in the Association, but they do not eliminate the problems they identify. The existing association is still a rather unusual way of looking after the whole ecosystem and reanimating the Magento world. Building a new alliance that matches the global importance of the Magento ecosystem requires a high level of investment. Restructuring the association, if it is possible, is the smoother way.
B2B Magento webshop zonder gedoe? Ik help je meer uit je webshop te halen door goede support en doorontwikkeling.
3 年Interesting insights and some good questions. Well, let’s hope this all sets things in motion for the benefit of the community as whole. We’ll see how it will develop.
Adobe Commerce Architect / Project Lead
3 年You mention that people who signed the letter "didn't try doing this through the Association" - but the CTA there is unclear. I'm a member of the association. I submitted an entry to join the Open Source Task Force. I've heard zero updates about the task force, and the Association hasn't really been forthcoming about its various committees and task forces. I don't see any channels in their Slack to keep up to date with them. This is in stark contrast to my experiences attempting to contribute to the PHP-FIG. Now to be clear, while I have signed the letter, I'm not against Magento Open Source lead by the MA - I just have yet to see it. It is my deeply held opinion that the MA is the way forward, but I'm certainly not seeing it do that at current. MA is slow, and while that is fine - it's only fine so long as communication channels are open and people know why its slow.
Bedrijfsgroei voor ecommerce ondernemers van 1 tot 20 miljoen jaaromzet. Marketing @ FRMWRK
3 年This feels authentic and realistic. Let go of the sentimental and look at what’s actually possible. Love the insights!