I was just reading the KIWI Documention and I found some parts that need to be renewed since nothing has been done there since 11.3.
Great idea! :-) In the past, Marcus wrote the documentation and I've converted it to DocBook and contributed some text and ideas.
I don't know the current state of the KIWI documentation, but I assume you are right. As far as I know, from time to time small parts were added or updated to the documentation. However, I guess it wouldn't hurt to give some parts more love and dedication.
Now I am thinking that I could give it a try and renew it but is there someone who is more relevant from me to do that so that I will not risk destroy anything?
No need to worry, KIWI has a repo; you can't destory anything. :)
First, I would recommend to talk to Marcus and the other friendly developers on the KIWI mailinglist. They can give you more hints than I and are more up-to-date about KIWI and its documentation.
Second, the usual steps are cloning the KIWI Git repository, correct the documentation, and send the patches to Marcus. If he thinks it is ok, he will integrate it into the main repo. In most cases, he accepted my patches. ;)
I don't think they changed this approach, but they can tell you on the mailinglist.
I am more specifically refering to the repositories and also if there are any additions to KIWI since the last time. If someone has that kind of information but hasn't got the time to write it down but he/she could give me informations/guidelines on this, I would gladly do that.
As I said, better ask all the details on the KIWI mailinglist as they have all the specialists there. :)
-----  http://groups.google.com/group/kiwi-images