What would motivate you to contribute to KDE wikis such as Techbase or Userbase?
Within the Plasma team, developers put a fair amount of time and effort into writing tutorials, with some more taking shape on our Community wiki pages. We're about to start on content on Userbase, starting with documenting how Actitivies work from a user's point of view in the 4.5 release. Other teams within KDE are doing similarly.
While this is creating a very nice set of resources, the cost of making them is fairly high as we trade development (read: software quality improvement, feature) time for documentation time because it's the same people doing both sets of tasks. We regularly encourage people outside our core development group to contribute to this growing body of documentation, and occasionally they do. Usually .. they don't. Now, I'm used to the usual "talk to 10 people and one will actually do something" we all know and love from sales so I don't expect a very high success rate, but the success rate for documentation seems even lower than that.
Even when we seed a document with the essential information, people hesitate to add to it. When a new bit of information is discovered by someone using those tutorials, I have to urge them to add their findings to the page, and even then they often don't. I know we "all dislike writing documentation" (well, that overstates it a bit :), but I get the feeling we're doing something wrong here.
I could make guesses such as, "It isn't obvious that the wiki is something even me, as a casual third party developer, is encouraged to improve." Even then I'm not sure what would help fix that? A big "contribute, contribute!" header / footer on each page? The main landing page(s)?
So I'm looking for your feedback as to what would turn you into a contributing author. I look forward to your comments below. :)