Magento Community Update #1

Introduction

Well, here we are, finally: the first of many monthly updates. I’ll start by stating that I have two goals for these updates:

  • Inform the Magento community about the things & thoughts that are happening inside my head as well as inside the mighty orange towers
  • Give some additional visibility to the things & thoughts which are happening within the community itself

That said, by no means should I or these reports be considered a final/ultimate voice of either the community or of Magento itself. Magento is different from a lot of software & service companies in that our community has direct access to various people in the organization, which includes talking with our developers and project managers via GitHub and Twitter. You can find me on Twitter at @benmarks and you can send me email at community@magento.com.

Community Evangelism

Many of you don’t know me, or don’t know much about me. For the past six years I’ve served as a Magento developer, educator, certification consultant, and active community participant. I joined Magento in April of 2014 to serve as the Magento Evangelist. Developer evangelism is a recent concept in the programming world, and it’s a vital thing for a big company with an open source product and highly active community. My job has two main functions: to make sure you all know what you need to know about Magento (both the company and the software), and to ensure that Magento knows what is important to you all.

Update

Magento 2

In all of my travels across most of the world, the question which I’m asked most frequently is, “When is Magento 2 coming out?” I’ve noticed that there are two reasons why I’m asked this question. The first reason is out of a healthy mistrust of our stated timelines: as many of you know, Magento 2 was announced quite a while ago, and there are various reasons why we are still talking about its pending release today. The second reason is that many people have missed our numerous announcements of the “new” release timeline. I’ll answer both of these reasons at once. The stated timeline follows:

  • 2014 Q4: M2 Dev Platform Beta
  • 2015 Q1: M2 Dev Platform Release Candidate
  • 2015 Q3/Q4: M2 Merchant Beta
  • 2015 Q4: M2 General Availability

This timeline was first announced in May of 2014 at Magento Imagine, and it has been consistently repeated at every official Magento event since. Everyone in the company is focused on delivering against these expectations which we’ve set. It’s important that we do deliver, as it is important to have your faith and confidence as well as the confidence of the eCommerce space that we can deliver as promised. Disregard that I am very much an optimist when I state with confidence that we will deliver according to this timeline. You don’t have to take my word for it though: our distinguished Chief Architect, Alan Kent, committed to this timeline (or an even earlier delivery) back in September at the community-run Meet Magento event in New York. And guess what…?

The code for the Magento 2 Dev Beta is live… go check it out at GitHub right now!

Magento, “open source,” and GitHub

I’m also frequently asked about / frequently hear about the nature of Magento’s “open source” approach and commitment. While there’s no doubt that Magento CE is by definition open source software (the OFL & AFL licensing mandate it as such), the questions and concerns I’ve heard are in regards to how Magento satisfies the open source development model itself. For the record, these concerns predate the Magento 2 era, going all the way back to the initial release of the platform (and probably earlier, but I only started paying attention in 2008). For example, in Magento 1 there were no nightly or weekly builds as there are in some other open source projects. Rather, code pushes to Magento’s public SVN repository were infrequent and certainly not intended to be a regular, transparent update for the community. Also, the roadmap for Magento 1 was mostly focused on issues being resolved rather than features being released. Issues themselves were inconsistently updated in the bug tracker. And the most significant deviation for Magento from open source development was the cumbersome mechanism by which our community of developers and users contributed feedback, features, and patches to the product. This was the old way of doing things though. Magento has been improving in its openness even before my arrival, and I am delighted to say that we have many actions to point to our increasing openness as open source stewards of the Magento 2 project. I’ll be posting more about this really, really good news tomorrow following the Magento 2 Dev Beta webinar.

What happened to the forums?

One of the first things I wanted to fix after joining Magento this year were the forums. I joined the forums as a member back in 2008, seeking information and occasionally finding some. Before too much time I was answering questions myself, and I soon became a moderator. Eventually though a combination of work, spam, and progressive degradation in forum moderation features ran me off (as it ran off many others). Others stuck around, but the fight against spam was ceaseless. Earlier this year the spam problem really came to a head and we placed the forums in archive mode. When we did this I added an email alias of mine to the archived forum pages as a stopgap… and have since personally responded to hundreds of inquiries for help!

I’m glad to report that we are integrating a SaaS platform which will replace the forums and provide additional community-focused/community-enabling tools. Using a SaaS solution allows us to focus our efforts on interaction rather than maintenance. Gone will be the days of fighting spam and tolerating bugs: our SaaS vendor has dedicated anti-spam and support teams. We’re currently working with our existing community moderators, and we will have an update on the launch sometime in the next few months.

What happened to translations?

I happened upon the old translations page/tool at magentocommerce.com back in August, and I was immediately struck by the four things: the number of locales present, the lack of usability, the lack of completeness for most translations, and the fact that we were not linking to this page anywhere. Clearly a better solution is called for. I took the functionality offline and added the same community@ email  so I could still help anyone needing translations. Shockingly, I started receiving 3-4 emails per day from people literally all over the world (save Antarctica) needing translations. To my horror I realize that people have been downloading very, very incomplete translation packs for some time now! So, I’ve been regularly responding to these emails explaining how to find translation packs in Connect (link), and requesting help with future translation efforts. This should help us seed the new crowdsourced translation tool when it comes online. As is the case with the forums, I don’t have a firm timeline to announce for this yet, but I will announce it as soon as I do.

What’s up with Connect?

Speaking of Connect, I would like to share that we in Small Business are working on a new implementation of this facility. This is a massive project, as we are incorporating years of feedback regarding extension quality, searchability, as well as the need to prepare Connect for the Magento 2 era. Details and timeline for these changes are going to be announced by my boss Ryan Thompson very soon, so stay tuned for that. Of course, your feedback on Connect is always welcome at community@magento.com.

Conclusion

There is a lot going on in the world of Magento and there is much to talk about – in fact, this post was a lot longer before wiser heads suggested I condense it. If you are an established community member, you will be thrilled by our announcements over the next month. If you are new, you are coming into the community at an exciting time. There’s an amazing future ahead of all of us, and the real winners are the merchants and customers who will benefit from our collective efforts.

One thought on “Magento Community Update #1”

Leave a Reply

Your email address will not be published.