KDE 3.1: delayed

[Unai Garro]

I think it could be a good idea (after fixing these problems) to create a new 
website or page under developer.kde.org with guidelines for good practice in 
coding. AFAIK most security bugs are related to "lazy" coding, so it could be 
good to have a reference point on how to code this or that.

I am coding something myself at this moment, but not being really expert in 
security matters, I'm not sure if the code is completely clean and safe... 
what if at some point I added this code to a kde package?