Topic: Suggestions for features
First I must say that I am not at all pleased with all this forking and spawning that you web CMS implementors are constantly doing. There seems to be no other types of open source projects that has the same frequency of splitting and forking. I am not saying that the reasons that you felt compelled you to do it are invalid. I am just saying that as a Mambo user for many years I get confused, unsecure, and more inclined to look at other CMS:s, every time this happens. The instability that is the result also affect the usefulness of the CMS:s. For example the multi-language component MambelFish has been on the top of my wish list for 5 years. It just started working for Mambo, when Joomla split off resulting in an incompatible JoomlaFish. I didn't want to switch because of other incompatible changes, so I was left with no multi-language support. Nookaew woke up and has recently started to work, when MiaCMS is split of. Furtunately Nookaew seems to be determined to stay with the Mambo-line. The same goes for different components for files, documents, calendars etc. etc. In short, it seems that a stable product could grow in features and user support, where as constantly splitting off always sets the product in a state of less features than it started out with.
So, in order for MiaCMS to become *my* CMS, it needs to show a stable set of add-on components supporting at least mult-language, calendar and file repositories. I could detail these if anyone is interested.
As a last comment, there where some indications on the MiaCMS web site that the forums would welcome any suggestions for features and improvements, but the forum index does not have any topic that corresponds to this indication. So I suggest a new topic, "Suggestions for improvements and features".
I appreciate the work that you all put into this, I'm a OS-developer myself, so I know... This time I just articulate what I feel as a user of the Mambo-family of CMS.