In my opinion, the key benefit is that Melody will be developed completely by the community, with no direct ties to a commercial for-profit enterprise. While core MT has been open source licensed, the product planning process and much (but not all) of the discussion, prioritization, and release planning and scheduling were closed to those outside of Six Apart. Six Apart also acted as a gatekeeper to code contributions, with final say over what made into the final product. Both of these may be common for open source projects lead by commercial entities, and are fair enough — Six Apart is a business and like any business they can and should make decisions based on the commercial interests of the company. But for the community of developers, consultants, and users, this didn’t feel very open, at least in my opinion. The feature roadmap was being driven internally at Six Apart, not in a collaborative way with the community at large. [This is not to say that Six Apart did not listen to feature suggestions of the community — many of the features added to the product were in response to community requests] The reality, I think, is that the internal business objectives that informed the development and product planning process are not fully aligned with the objectives of the broader community. This is an unavoidable reality, there is no right or wrong here, only different contexts and thus different perspectives and goals. For these reasons, I think many developers and end-users shied away from Movable Type — despite the open source license, the product was controlled by a single for-profit company, and the ability of the external community to contribute and collaborate was limited. [Mark Carey: “Open Melody: Movable Type Forked”.]
My own vision for Melody is a code base that’s very focused on publishing and content management, with all the infrastructure outsourced to CPAN modules that are well-written, well-documented, and well-tested. The collaboration between Melody and CPAN would be a two-way code flow. While there are more CPAN modules that Melody could make use of, there are number of pieces of Melody which should be packaged as independent modules on their own and released to CPAN. [Mark Stosberg: “Movable Type fork is an opportunity to harness CPAN”.]
Version α dans les prochains jours, 1.0 prévue pour cet automne. Il n’y a plus qu’à attendre l’arrivée de Nelson.