Mambo fork Joomla

It may be of some interest to the Drupal community to know about recent events in the Mambo community. It seems that less than a month ago the majority of the core development team left Mambo to form Joomla, in a response to some events regarding control of the development path/Mambo community etc. As it may be known to some of you, Mambo is "hosted"/sponsored - and now probably controlled - by a company called Miro. I don't know the details, but some of it can be found here:
http://forum.joomla.org/index.php/topic,72.0.html

This is not the first time I've seen forks happen. Some of you may remember the Php-Nuke to PostNuke split, and the subsequent PostNuke to Xaraya split/fork (and some other PostNuke to something forks that I don't recall now....). It is not often that such forks have good endings, Xaraya is an exeption I think.

In my opinion forks often happen when the leading developers get tired of people fighting for power and influence - and decide to take the code and walk away (in good compliance with the ideas that Richard Stallman preaches..). This is what it means when we say that "software wants to be free".
It happens when a project grows and becomes so succesfull that the community cannot stay one. When forces driving people away from each other, overpowers the opposite forces.

What can we learn from these events? Drupal has not yet experienced the pains related to such a fork. But that does not mean it will not happen. Can the Drupal community prepare itself for this?
CivicSpace may be a fork, but it has been dealt with in an elegant manner I think.

The worst thing about forks and the split up of a developer team is the bad vibes, mutual accusations etc. (Just take a look in the Mambo/Joomla fora...).

But I'm beginning to rant. I just thought you should know.

Best
Gunnar