In response to:
sorry you feel that way. it's not hard to work with others, particularly the developers in this project. but one has to actually try to do so.
with regards to the HIG, you stormed in and started a fork, including changes to the text that were not done in coordination with the rest of the project. this defeats the purpose of guidelines. you were very much aware that vital people who wanted to be involved in working on guidelines in KDE were about to have a large meeting, to which you were invited. you decided to go ahead ANYway, despite the meeting being weeks or even just days away. that was your choice. i'm sorry you can't work with others, but that's not my fault. your efforts may well end up being wasted due to stubbornly going your own way. so be it.
but KDE now has progress to show on a combined Accessability, Human Interface and Corporate/Community set of Guidelines. your efforts were not in line with this, no matter how much we needed it. what you were doing would not have produced what has been started, either. you were not blocked from participating in these exciting developments by anyone but you.
with regards to KControl, i'm sorry if the media decided to pick up on an illustration i used (how much better google is at indexing 4 billion+ documents globally than we are at index a few thousand locally), but that doesn't change much of anything.
facts are that a hierarchical KControl has problems. period. how can i prevent other people from repeatedly trying to fix an unfixable problem? i can't. but that doesn't mean it belongs in KDE, especially not when there are more interesting ideas out there that also have a large amount of supoprt.
there is active, engaged discussion by many people about this on kde-usability right now and it seems we are arriving at some very good concepts via consensus. this discussion is fueled by other discussions had at aKademy which are now continuing on after it.
i invite you to join in the process rather than try and fight it at every step.