User Tools

Site Tools


Sidebar

projects

  • cci0 (due 20170607)
  • sof0 (due 20170614)
  • dow0 (due 20170621)
  • mbe0 (due 20170628)
  • pnc0 (due 20170705)
  • pnc1 (due 20170712)
  • mbe1 (due 20170719) iOR
  • pnc2 (due 20170719) (or do both, 1 as bonus)
  • fcc0 (due 20170726)
  • sfa0 (due 20170802)
  • oop0 (due 20170809)
  • EoCE – bottom of your journal (due 20170819)
haas:summer2017:cprog:projects:notes

Class Notes Project

Learning is not some passive experience- it is a crafted combination of observation, understanding, and practice.

This on-going project is an attempt to keep everyone engaged with course content, and to present it in a way that will be valuable to both the original producers as well as the entire class (and perhaps beyond…).

Premise

I would like to commence the organized recording of class notes on the Course Notes wiki page.

  • For each class, 3 roles are going to be assigned:
    • author - provides content (from the notes they took)
    • designer - provides stylistic tweaks (using wiki syntax, images/diagrams- although they may obtain source material from the author)
    • reviewer - provides recommendations on content and style (helps fill in blanks, suggests improvements)
  • There will be unique credit awarded to each role, according to the following criteria:
    • author: content (1), deadline (1). Basically: has the author produced complete and valid content by the deadline?
    • designer: appearance (1), deadline (1). Has the designer adequately styled the available content by the deadline?
    • reviewer: helpfulness (1), deadline (1). Has the reviewer actually been proactive and helping ensure the successful production of class notes by the deadline?
  • Should the author be delinquent in their duties, responsibility falls to the designer, and then to the reviewer should the designer fall through. Such extra credit will be applied to the appropriate party.
  • Should the designer be delinquent in their duties, responsibility falls to the reviewer, and then to the author should the reviewer fall through. Such extra credit will be applied to the appropriate party.
  • Should the reviewer be delinquent in their duties, responsibility falls to the author, and then to the designer should the reviewer fall through. Such extra credit will be applied to the appropriate party.
  • Should nothing be produced (universal delinquency), no credit is assigned for all chosen individuals.
  • Should class be canceled or end up being a work day, such responsibilities (if selected) are null and void.

Time Table

Class Author's Deadline Designer's Deadline Final Deadline
10/07/2014 10/09/2014 10/20/2014 10/22/2014
10/09/2014 10/20/2014 10/22/2014 10/24/2014
10/21/2014 10/23/2014 10/25/2014 10/27/2014
10/23/2014 10/25/2014 10/27/2014 10/29/2014
10/28/2014 10/30/2014 11/01/2014 11/03/2014
10/30/2014 11/01/2014 11/03/2014 11/05/2014
11/04/2014 11/06/2014 11/08/2014 11/10/2014
11/06/2014 11/08/2014 11/10/2014 11/12/2014
11/11/2014 11/13/2014 11/15/2014 11/17/2014
11/13/2014 11/15/2014 11/17/2014 11/19/2014
11/18/2014 11/20/2014 12/01/2014 12/03/2014
11/20/2014 12/01/2014 12/03/2014 12/05/2014
12/02/2014 12/04/2014 12/06/2014 12/08/2014
12/04/2014 12/06/2014 12/08/2014 12/10/2014
haas/summer2017/cprog/projects/notes.txt · Last modified: 2014/10/20 14:18 by 127.0.0.1