ImpressCMS is controversial, because that's not under XOOPS official control. And, because a developer who has joined the XOOPS project joins also the ImpressCMS project, some users point allegations that the XOOPS foundation may misappropriate. (I think that's quibble.)
Anyway, it is a fate that a forked project is born to cover a semi-retirement project having the following factors:
- Developers who don't program.
- Administrators who don't administer.
- Publicists who don't write news.
- Moderators who don't see forums.
- Leaders who lead to collapse.
"Fork" is good solution for stalled projects, because "Fork" is not limited by existing retirement members and existing team governance. The only mission that semi-retirement members do is resisting new movement. They have lost a passion to do actual activity, so they try to damn new movements by using dummy official announcements and political fighting.
But, 2007 will soon be past. You can check how much missions each project and each member have completed. After that you can check whether existing announcements are dummy or not. Well, I am not in no position to talk.