There seems to be a basic difficulty that we need to overcome. The recommended form for usability reports is to have each report be its own narrative story. But this site, as most wikis, is quickly organizing itself into narrow subject areas.
The following are the types of content it seems like we're getting:
- Bug encounters/reports
- Questions and answers, may be edited later to become documentation without the question part
- Documentation (as this is named Grokdoc)?
For the narrative usability studies, I believe we should have a page for each task we ask users to perform, but encourage reporters to add their comments inline, so that we get a running log of what issues users ran into at each step of the way. I'll cook up an example over lunch today.
I've been in and around several wikis. I'm here to provide edits and lobby for open policies that encourage maximal collaboration -- it's all too easy to accidentally constrict participation.
I'm with NIKA Consulting, a firm in suburban Chicago that supports Windows, but has also seen several of our customers switch to and enjoy Linux for their server platform. It's been frustrating not to be able to recommend Linux for the desktop, so we look forward to the fruits of our labor on Grokdoc.
-- Ryan Platte