Slashdot Mirror

← Back to Stories (view on slashdot.org)

Miro Replies to Mambo Allegations

Posted by CmdrTaco on from the stuff-to-read dept.

Rico! writes "Miro aka The Mambo Foundation has finally provided answers to some thorny questions and also fired back at the Rebel Developer Alliance." Here is the Slashdot story covering the original split where the developers all jumped ship.

5 of 74 comments (clear)

  1. Correct link by Karamchand · · Score: 4, Informative

    Correct link, since the link in the story is to the main page.

    1. Re:Correct link by Trepalium · · Score: 3, Informative
      The only mention I see of this is in the Ars Technica article which is rather sparse on details. Ars only mentions this prior dispute in one paragraph, and is devoid of any links to the full story. Here's what little Ars had to say about this:
      Mambo originated from an Australian company known as Miro who decided to open source their code by putting it up on SourceForge and licensing it under the GPL. The open source community got a nice CMS and Miro had the open source community patching and improving its CMS. Everything went swimmingly for a while until Miro decided that it was taking back "their" code. Access to the code was shut off and the community vociferously objected. Fortunately because the code was GPL'd, the open source community was eventually able to pressure Miro to fork the code. And thus Mambo was born.
      Either way, the last time Miro acted unilaterally in regards to Mambo, the developers objected, why did they think it would be different this time?
      --
      I used up all my sick days, so I'm calling in dead.
  2. For those who don't know what mambo is... by WTBF · · Score: 4, Informative

    Wikipedia entry

  3. Miro and the community by Anonymous Coward · · Score: 1, Informative

    7. The Terms & Conditions for membership provide for a number of penalties which can be invoked against members who run afoul of the rules -- including monetary penalties. What is the thinking behind this? Give me some examples of when those might be invoked.

    In order to build real community, there has to be community rules and guidelines. Rules also need some kind of consequence for not following them, or they become ineffective. Our goal is to make the environment as effective as possible. An Open Source project has to deal with issues from bad forum behavior to vendor / customer performance issues, (in the case of commercial third-party developers). Our rules directly reflect other Foundations and we built a rule-set around universally adopted procedures.

    Oh how I want to be a part of that community...

  4. And for More on the Whole She-bang by sjvn · · Score: 2, Informative

    from both sides see:

    Mambo Executives, Developers Fight for Project Control

    http://www.eweek.com/article2/0,1895,1850298,00.as p

    Steven