Mambo Foundation Gets Copyright, After All

daria42 writes "Responding to the concerns of developers and backflipping on a previous policy in the process, Miro, the commercial company which owns the copyright to the GPL'd Mambo content management system has decided to assign all intellectual property rights to the Mambo Foundation, which it created to manage the CMS. The company has been at the centre of a storm of controversy previously reported here on Slashdot, which has seen the core developers of the CMS fork the project."

Comments

Empty gesture

[Deffexor]

This gesture by Miro is an empty one. It seems to me that Miro has shot themselves in the foot over this Mambo Foundation and made themselves look awfully foolish. Right now they are attempting damage control by trying to appear like "good guys" with all these disingenuous gestures.

All the coding talent that was behind Mambo has since left to form their own foundation. To find out what the ex-developers of Mambo are up to, visit OpenSourceMatters

Disclosure: Yes, I'm the one who wrote the Mambo developer exodus report on Ars Technica.

forking....

[rd4tech]

kids, it's the true power the developers have in the open source projects... now for the next lesson: sales.

This is too little too late

[pasamio]

If the Foundation had of been set up the way the MSC and the Core Devs wanted, this would have been good, but the damage has been done by Miro. They can't take it back and they are only trying to make ammends. They aren't transferring the copyright far, considering that they control the Mambo Foundation, so who is the real winner? Not open source. OpenSourceMatters is where the new work is going and that is where I am going to stake my claim and pitch my tent.

I don't Mambo

[Ranger]

I think PHP is great, but I don't think it's quite ready for a robust content management system. The PHP CMS community is very fragmented. When shopping around for a good open source CMS, I found a profileration of nukes. The two CMSes I considered seriously were Mambo and Drupal. Both of them have had some recent issues that made me glad I didn't pick them. Not only that there were some serious PHP security issues. I've been a fan of Perl far longer, but was amazed at how quickly I could slap together usable stuff in PHP. And I didn't choose a Perl based CMS either.

Ultimately, I chose Plone which sits on top of Zope which sits on top of Python. It can sit behind Apache, You can use it with other other databases than it's own weird object db, but it's not easy. It also has a steep learning curve. Despite all these drawbacks and concerns, Plone is the most robust, secure, and ready to use out of the box CMS I've found.

Maybe it was just dumb luck and the recent problems with Mambo, Drupal, and PHP made me feel better about my decision. I'm still learning Zope and Plone, but I'm impressed that I can throw stuff together pretty quickly with it, even though hides stuff in non-intuitive locations.