Well... IMHO 27a puts ICY now at a "almost finished state"

. There are a lot of things that really should be changed / tweaked. For instance an improvement of the template system to make it easier to make a new themes, for example
this discussion - this has always bugged me that some things in the templates could and should be made a lot easier, so it would encourage a lot more innovative themes for Icy (i.e. different layouts and mouse hover effects, rather than just replacing the standard table header pics). I mean, by default, the actual appearance of Icy (and of XS) is too much of a forum, when the idea was to have a CMS style site management system - more than just a forum (lets not forget the CMS system is an overhaul of Importal that was already in XS - thats not to deny that MG has done a great job with it). Presently, by default it still looks just like a heavy modded forum, not a website, with too much forum related clutter on the homepage, which should just be kept to the forum area. OK users can change that themselves, but we should be providing a default template that has a website look to it, not a modded forum look. When most users show off their "websites" here, mostly all they have is a duplicate of Icy, and perhaps a different header image, and if they're really pushed the boat out, different table header pics. But it still looks like what they are showing is not really a website, but a modded forum. And we should be worried about that, because with CMS, Icy is meant to be much more than just a heavily modded forum (even if that is the ultimate reality, its now at the stage where under the bonnet it has a lot more in common (in principle, not the literal coding) with Drupal than phpbb).
Then there is the fact about some of the inefficiencies of the logins and sessions tables handling, as per
Here. The system is really a little stupid at present - why keep a record of several thousand dead sessions in your database, so that when you access the site, mysql server has to do more work to search through thousands of rows of dead sessions and data in the logins table, slowing down site loading? Also as I said there, certain tables, especially sessions, are better installed as ENGINE=HEAP, not myisam/Innodb, provided the sessions table is pruned regularly / automatically. A dream system would have a dual table structure, using disk-based tables for permanent record of data, and semi-duplicate tables in HEAP for speedy retrieval from RAM. (semi-, in that for posts/posts_text, only 2000 or so of the most recent posts should be in HEAP). Only if mysql crashes does the disk based tables get read, and only then to repopulate the heap tables. This would be at least 10 times quicker than simply caching "static page" sql data to disk, and probably 100 times or more on building the dynamic content like the forum.
These are things that have concerned me (a little bit) since XS, perhaps I will resolve them myself (although if I went far down the HEAP route, it would probably be a fork from Icy, as a lot would be changed), although I'm working on some other mods at the moment - most of the above is not hard at any rate, just laborious. I do also like the idea of a WYSIWYG editor, again something I might consider working on myself, but not enough time at present. We should not suddenly stop being creative (not that any of you guys have ceased to do a great job), but come up with new features - although if we want to see something added, then really we should have a go at doing it ourselves, not just demand it from somebody else - thats one of the seldom-written rules of open source.
And that leads me to the final point about XS and Icy - I thought MG (and also Bicet) said in the past, these are open projects, people should be encouraged to come up with modifications and alterations to Icy themselves, and if they are good / useful / high demand, then they might be implemented in a next release. Its not just for MG to make the changes, its for all of us to
