It's fairly clear that one cannot code from the ground up in bazaar style. One can test, debug and improve in bazaar style, but it would be very hard to originate a project in bazaar mode. Linus didn't try it. I didn't either. Your nascent developer community needs to have something runnable and testable to play with.
- The Cathedral and the Bazaar by Eric Raymond
Congratulations!
Yesterday in Pittsburg Tim Appnel announced Melody, an open source fork of MovableType. I would like to congratulate everyone who has worked very hard to make this happen. I am uncharateristically excited about this project. The main reason for the excitement is that I have never witnessed a fork up close before. I know some of the players, and I am familiar in passing with most of the rest. I have wanted to see this happen since I first read about the evolution of fetchmail in The Cathedral and the Bazaar .
Byond the fanfare of Fork and hype of Community
At this time, the code of Melody is not stable and can only be obtained though GitHub. Information about obtaining the code is available on the download page. The web site states that they hope to have a consumer release in the "Fall of 09".
Melody is for those who find value in belonging to, supporting and contributing to a community of helpful, passionate and devoted users, but it is also for people who want a secure, proven and high quality publishing environment for their personal web site or their business.
Ah. "C-O-M-M-U-N-I-T-Y" Great. Yes, a community of users is required for open source projects to make sense. But the details of Melody's goals seem to be the same thing that MovableType.org promised .
What will make Melody different from Movable Type Open Source?
Well, to hear Ben Trott, the original author of Movable Type tell it, MT is stable and Melody is experimental. But Ben also acknowledges what I find to be an intriguing, if under-publicized, aspect of the project, "integration with the code of other open source projects".
In February of 2008, Tim Appnel argued eloquently on the MTOS mailing list, "...there are other more important reasons for migrating away from homebrew solutions and to module in CPAN that exist beyond MTOS." One of the specific open source modules that was being discussed in that post was CGI::Application . cgiapp is a framework for constructing CGI applications. (Movable Type is a CGI program.)
Tim's stated benefits included:
- "effectively leveraging resources" He wants to use existing CPAN code instead of inventing every function and subroutine in-house.
- "better embracing open source" He thinks that if we contribute parts of the system to CPAN, some new people will use the parts, and some of those will become part of our community.
And so it starts.
Although I knew in advance that Melody was being announced on Tuesday, the first time I was made aware that it had actually happened was on the CGI::Application mailing list. Mark Stosberg, advocate of simplicity (I think I like this guy, I hope I get to meet him sometime) and technology, and (one of ?) the lead CGI::Application developers has given Melody a positive write up. on his blog.
I can't wait to see what happens next.
Recent Comments