@mekk: Version control is a good goal, even though I personally do not have the need for that. I simply created the "proof of concept" plugin, and I'd be happy if other developers can flesh it out with adding notes, support for staticpages and version comparison.
I like your second idea, but I'm afraid it is an awful lot of core code with very little reward for the end user, because usually people simply tune their layout incrementally until the find their best variant. I have rarely had the request for people that often want to switch into different "presets" of their former layouts. I do think this would be a nice feature, but the general use of it might be very, very little. Your third idea about config staging would go hand in hand with it, and this I see more use to people because their testing would not affect the 'live' blog.
- let me "activate plugin only for category X" (plugin is active when I view article belonging to given category, or index of this category, otherwise it is not run)
The "sidebarhider" plugin allows you to hide specific sidebar plugins based on author login or category mode...
About your idea #5, I've already stated my personal thought on this, that I do not want to mess with the "credibility" of trackbacks by allowing seperate text to it.
Thanks for your input, much appreciated!
@abdussamad: The comptetition for the last time was VERY little rewarding. The layouts we got were nearly only from core members. I do not think the bar of contributing users to serendipity is high enough that a new contest would proove effective. Instead, maybe asking those "usual suspects" like Dan, you or others should proove much more rewarding.
About the FF issue, I'm a bit stumped. Did you try with FF2, just to see if it works there? I find that FF3 has changed in many respects that break compatibility...