The Wikipedia Adventure: Difference between revisions
From CommunityData
| Line 10: | Line 10: | ||
* read & discuss new draft sections (Aaron) | * read & discuss new draft sections (Aaron) | ||
* plan next revision (Sneha & Aaron) | * plan next revision (Sneha & Aaron) | ||
* upload to sharelatex (Sneha) | |||
===Friday, May 6th=== | ===Friday, May 6th=== | ||
| Line 19: | Line 20: | ||
*** large-scale user survey and invitation-based field experiment under realistic conditions provide more useful evidence (than hallway testing or small-scale usability studies). | *** large-scale user survey and invitation-based field experiment under realistic conditions provide more useful evidence (than hallway testing or small-scale usability studies). | ||
* revise the discussion (make sure Jake's concerns are addressed). | * revise the discussion (make sure Jake's concerns are addressed). | ||
* | * share completed draft with collaborators | ||
===Friday, May 13th=== | ===Friday, May 13th=== | ||
Revision as of 20:09, 29 April 2016
Project page for The Wikipedia Adventure
Timeline for CSCW submission
Friday, April 29
- draft methods from survey study (Sneha)
- draft results from survey study (Sneha)
- draft restructuring of section headers (Sneha)
- recover old pieces of design rationale and add to system design section (Sneha)
- read & discuss new draft sections (Aaron)
- plan next revision (Sneha & Aaron)
- upload to sharelatex (Sneha)
Friday, May 6th
- revise subsections for study 1 to keep refining structure (see Aaron's comments in the document)
- revise introduction and framing.
- add justification for 2-study design
- incorporate the argument that large-scale field testing is important.
- challenges of deploying new systems in a massive community with passionate, experienced members
- large-scale user survey and invitation-based field experiment under realistic conditions provide more useful evidence (than hallway testing or small-scale usability studies).
- revise the discussion (make sure Jake's concerns are addressed).
- share completed draft with collaborators
Friday, May 13th
- incorporate feedback from collaborators (double check with Jake)
Friday, May 20th
- read it a hundred times, make sure the title works
Friday, May 27th
- submit final version! (though earlier is better)
