Doing the Mambo over open source

No doubt, the open source development process works (see Linux, Apache, Firefox and many, many other examples). Even Microsoft--the most strident of open source critics not so long ago--says it sees some value in community development.

But when commercial interests and developer passions mix, the results aren't always pretty. Take the ongoing spat between a group of developers and Miro, an Australian software company behind a popular open-source content-management system called Mambo that's used to publish Web sites.

Miro decided way back in 2000 to release Mambo as an open-source project, with volunteer programmers in charge of the software's development. Fast forward to earlier this month, when Miro announced the Mambo Foundation, an organization that Miro says will govern the software's development.

That move has angered developers who claim they no longer have a voice in Mambo's development or in shaping its future direction. They've formed their own group, called OpenSourceMatters.

Both sides say they will continue to develop Mambo. While there's been some resolution on Monday, the stage seems set for a worst-case-scenario: a code "fork" that could result in two incompatible versions of the software.

Blog community response:

"The smoke and mirrors tactics of the new Mambo Foundation is (a) sad example of how to destroy a community of loyal followers. They must realize now they are in deep trouble, as people have in mass moved to the developers website at OpenSourceMatters.org"
--Geek News Central.com

"When there is a struggle between the founders and the community in a mature project, I have to believe the community will win in the long run."
--CMS Watch

"What can you do about this injustice? Stop using Mambo and stop suggesting it to your clients. Don't support corporate takeovers of open source software."
-- Max Kiesler - Strategic Designer