Magento is the number one eCommerce software in the marketplace today. Magento offers flexibility and extensibility like no other open source eCommerce system. We truly love working with the software and love being part of the Magento community and helping it grow.
That being said, we have some concerns regarding the Magento Community Advisory Board.
The CAB was an incredible idea – Koby Oz (Member of the Magento Team) was the project leader. Community members were selected to be on a board that would determine the future roadmap of Magento. The meeting overviews were posted in the blog, and we would follow very closely to keep up with what was going on.
There have been some great changes to the community site, specifically the knowledgebase and wiki – the new formats are more organized and easier to navigate. Inviting guest authors such as Alan Storm is a tremendous help to Magento developers. The problem we see is that the Community Edition development is scattered and misguided with all the internal changes and new products launching.
We generally run three local installs for testing:
- Stable
- Development
- Beta (if available)
Our Recommendations:
Move to GitHub
Development was all done in subversion, which didn’t seem to be doing the trick, so in December 2009 it was announced that development would be moving to GitHub with weekly commits. Sadly, this never happened, and right now there is one person (who is not part of the Magento team) responsible for downloading the latest version and uploads to GitHub. This doesn’t work simply because commits lose their messages.
One problem with the current abstract development setup the dev team is using for Magento CE is that there are sometimes more features in a development version than the beta version. For example, the latest svn commit at version 1.4.x-devel-77328 has newer features than the latest beta at version 1.4.2-beta. The svn commit has it’s own release notes with missing features such as built-in StrikeIron integration. That’s huge. A move to GitHub would be one of the most effective moves possible. Branching would be easier, and everyone could develop locally since it’s made for distributed development.
Keep Up With the Public Issue Tracker
The public issue tracker is great, but often it is not kept up with. Bugs are fixed and not crossed out. This could easily be fixed by looking at the development process from a project management point of view.
Make MagentoConnect Channels Easier to Find
All MagentoConnect channels are supposed to be reflected in MagentoConnect 2.0, but sometimes we can’t download modules because they can’t be found. We could download modules in a different version and then copy the files to the development version, but that breaks the process of testing MagentoConnect Manager 2.0.
Public Announcements
The people of the Magento community want to know what’s going on with the product they are using to support their clients. If a new community leader leaves or one is hired, we’d like to know about it. Not only would we like to know about the face of the community, but also where these changes will take us.
More Error Detail
Uploading to MagentoConnect channels often throws an error with minimal detail. I sent a PM to someone who previously handled a similar issue, and they told me to put it in the issue tracker. There is no category in the issue tracker for MagentoConnect issues (Magento’s server-side), just MagentoConnect Manager (client-side).
We understand that Magento is growing faster than anticipated, but we have concerns. It is a great product but without proper management it could be a disaster. We care deeply about the community product – it’s one of the best things to happen to eCommerce in years, but it seems as though management of the project is falling apart. People don’t know which department handles what product, development branches are all over the place, and bug tracking is lagging. Many of these issues could be easy fixes, and we would love to help. With the right systems and processes in place, development could be much smoother and the community could be much more involved, and that’s what it’s all about.
Perhaps a new spot for the Magento CAB is in order. The simple addition of a category in the blog would be a step forward, but a new portion of the site would be best.
Some relevant links to Magento CAB blog posts:
http://www.magentocommerce.com/blog/comments/introducing-the-magento-community-advisory-board-and-first-meeting/
http://www.magentocommerce.com/blog/comments/directions-directions-1/
http://www.magentocommerce.com/blog/comments/cab-meeting-2-wrap-up/
http://www.magentocommerce.com/blog/comments/community-edition-roadmap-vote/
http://www.magentocommerce.com/blog/comments/august-2009-cab-meeting-wrap-up/
http://www.magentocommerce.com/blog/comments/december-2009-cab-meeting/
http://www.magentocommerce.com/blog/march-22-2010-cab-meeting-wrapup/