Comments on: Open-source Mambo project faces rift
Struggle over who steers development of the content management software underlines the promise and the pitfalls of collaborative work.
Struggle over who steers development of the content management software underlines the promise and the pitfalls of collaborative work.
January 6, 2010 6:30 PM PST
January 6, 2010 6:30 PM PST
January 6, 2010 6:30 PM PST
Add headlines from CNET News to your homepage or feedreader.
More feeds available in our RSS feed index.
Related quotes
This, taken directly from archives of the Mambo web site, seems to be the continuing motivation for Miro in regards to the Mambo project.
Not really. It can mean a division of effort in an energy-impoverished ecosystem such that weaker competitors eventually win. The web is not Darwinian (that's too simplistic) and code is not an evolving organism (self-directed). He is confusing community and product.
A code fork is bad. A community fork can be worse depending on the size of the available and willing labor pool. The web is not an inexhaustible source of labor although it is replenishable.
The Mambo development team did not resign from the project. They simply moved the project to a different server. The project remains on track. The Mambo community has followed suit. Now, the project, it's award winning development team, and the active community are busy setting up temporary quarters at www.opensourcematters.org.
Soon Mambo will have a new name and a new permanent home devoid of corporate greed. And Miro's shadow foundation and *ambo web sites will soon be nothing more than an empty shell.
These are indeed exciting times. Something wonderful is about to happen. Stay tuned.
They're nothing more than a bunch of hypocritic power-starved children.
With open source when there is a disagreement then the code can be forked and both parties can continue to develop it. While it may make for uncertain times for the customers while they decide which fork to chose they will still have a choice. In fact they have the choice to follow the forks or even take the code and hire their own programmers to maintain their investment.
Forks are not always bad, they can be painful and they can lead to uncertain times but they give the consumer/customer that is actually using the code the greatest opurtunity for success in the long run.
BTW, I use Mambo on several sites. Good luck guys!
I don't think there should be a fork. There should be an agreement of the core version with which the two groups may use as base for their respective brands.
There should, therefore, be a committee or body concerned in making sure that the core is maintained and managed... if I am seeing it right, I think this is just like how Linux is doing it.
- Developers Acted Hasitly
- by August 23, 2005 2:16 AM PDT
- The Development Team had no right to unilaterally decide to derail an entire community with their decision to abandon the Foundation. They have acted in a childish manner, instead of restraining their youthful enthusiasm and trying to work together with Miro for a result that would best benefit the community. This sets back the commercial development of Mambo in a big way and hurts all commercial developers who have invested in the system.
- Like this Reply to this comment
-
-
- A smoother track
- by August 23, 2005 10:59 AM PDT
- "The Development Team had no right to unilaterally decide to derail an entire community with their decision to abandon the Foundation."
- Like this
-
- "Abandonment"???
- by August 23, 2005 5:21 PM PDT
- How can you chastize the development team for "abandoning" something they were never a part of?
- Like this
-
(10 Comments)The team had every right to do what they did, and did so because they felt it was in the best interest of the community and the team. Their decision has not derailed the community, it's simply moved it to a smoother track.
"They have acted in a childish manner, instead of restraining their youthful enthusiasm and trying to work together with Miro for a result that would best benefit the community."
Outside of providing infrastructure support for the project, Miro has (in my opinion) done little or nothing for this project. Removing Miro, the overbearing parent of a child they abandoned in hopes it would grow up stronger if raised by others, will have little or no negative effect on the project.
"This sets back the commercial development of Mambo in a big way and hurts all commercial developers who have invested in the system."
I don't think commercial development is the primary goal of the project, just a welcomed side-effect.
The bottom line is that the developers listened to the community, they provided the talent and time to create what the community wanted, and they'll continue to develop a successful, award winning, project - without the dead-weight of Miro to drag along for the ride.
The only "invitation" they got to be a part of the "Foundation" came with hefty price tags - that's not something you do to a group of people who FREELY gave their time to the development of this project.
To assume they abandoned the foundation (which again I state they were not welcomed to be a part of without paying fees) and derailed the project is not only incorrect, it's ignorant of the facts behind this story.