CS382:Reviewers Notes

• ready for review: reviewers go in, make comments, add a custom reviewer tag, then when the time comes for them to make revisions, we can compare the latest reviewed version with the latest version
  • "Fuck all of that!"
• use copy and paste to insert comments, screw a numbering system
• whenever we make a review comment on a page, add "Reviewer" tag or whatever so that the wiki versioning does the work for us
• Charlie will take care of who is late etc
• reviewers will each take "some color"

GRADING

• completeness check
  • is each item addressed with more than a header?
• layout, does this show clear thinking about the presentation? will this develop
• read background reading, make sure they make sense and are relevant
  • is it reasonable
  • is there enough, too much
  • is it at the right level
  • FOR RELEASE 2
    • be specific about exactly which sections of material in what order should be read
    • background reading for teachers?
    • be specific about WHO is supposed to read this
      • two categories of reading?
      • three? teacher, student, reference?
      • ask them to break down the readings into this framework
• lecture notes: is what needs to be taught adequately outlined? at least so the teacher knows what needs to be covered?
• scheduling is the architects' jobs