CS382:Reviewers Notes - Revision history

Mclauia: /* Third Pass Notes */

2009-04-21T14:51:54Z

Third Pass Notes

← Older revision		Revision as of 14:51, 21 April 2009
Line 3:		Line 3:
	* Protected namespace for reviewers called "Grading"		* Protected namespace for reviewers called "Grading"
	* Grading page will be a matrix with the left column being the unit template outline, followed by an integer value from 0-3 for each unit for each item on the template		* Grading page will be a matrix with the left column being the unit template outline, followed by an integer value from 0-3 for each unit for each item on the template
			** 0: Nothing?
			** 1: Minimal effort
			** 2: It's coming along...
			** 3: Good stuff
	* If the value is less than 3 for any part of a unit, comments will be written below for that section/subsection for that unit		* If the value is less than 3 for any part of a unit, comments will be written below for that section/subsection for that unit
	* Calendar test: Ian		* Calendar test: Ian
Line 11:		Line 15:
	* Lab requirements should (theoretically) be in each unit.		* Lab requirements should (theoretically) be in each unit.
	* Catalog description: [https://wiki.cs.earlham.edu/index.php/CS382:Structure-deliverables already written]?		* Catalog description: [https://wiki.cs.earlham.edu/index.php/CS382:Structure-deliverables already written]?
	*

	== Second Pass Notes ==		== Second Pass Notes ==

Mclauia: /* Third Pass Notes */

2009-04-21T14:48:54Z

Third Pass Notes

← Older revision		Revision as of 14:48, 21 April 2009
Line 1:		Line 1:
	== Third Pass Notes ==		== Third Pass Notes ==
			For Reviewers:
	* Protected namespace for reviewers called "Grading"		* Protected namespace for reviewers called "Grading"
	* Grading page will be a matrix with the left column being the unit template outline, followed by an integer value from 0-3 for each unit for each item on the template		* Grading page will be a matrix with the left column being the unit template outline, followed by an integer value from 0-3 for each unit for each item on the template
Line 8:		Line 9:
	* TA tasks: pending labs' completion		* TA tasks: pending labs' completion
	* (Realistic deadline: end of May)		* (Realistic deadline: end of May)
			* Lab requirements should (theoretically) be in each unit.
			* Catalog description: [https://wiki.cs.earlham.edu/index.php/CS382:Structure-deliverables already written]?
			*

	== Second Pass Notes ==		== Second Pass Notes ==

Mclauia at 14:44, 21 April 2009

2009-04-21T14:44:33Z

← Older revision		Revision as of 14:44, 21 April 2009
Line 1:		Line 1:
			== Third Pass Notes ==
			* Protected namespace for reviewers called "Grading"
			* Grading page will be a matrix with the left column being the unit template outline, followed by an integer value from 0-3 for each unit for each item on the template
			* If the value is less than 3 for any part of a unit, comments will be written below for that section/subsection for that unit
			* Calendar test: Ian
			* Syllabus: Charlie
			** Copy-editing: Kay and Ian
			* TA tasks: pending labs' completion
			* (Realistic deadline: end of May)

	== Second Pass Notes ==		== Second Pass Notes ==
	* Each of the reviewers (Ian, Kay, Charlie) will review 6 units; Kay starts with What's a Model, Ian with Visualization, and Charlie Agent Based.		* Each of the reviewers (Ian, Kay, Charlie) will review 6 units; Kay starts with What's a Model, Ian with Visualization, and Charlie Agent Based.

Mclauia: /* First Pass Notes */

2009-03-30T14:37:44Z

First Pass Notes

← Older revision		Revision as of 14:37, 30 March 2009
Line 21:		Line 21:
	* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.		* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.
	* Charlie will take care of tracking when things are turned-in and deducting points as need be.		* Charlie will take care of tracking when things are turned-in and deducting points as need be.
	* Reviewer colors - Ian = darkmagenta, Charlie = red, Kay = blue, Dylan = green		* Reviewer colors - <font color=darkmagenta>Ian = darkmagenta</font>, <font color=red>Charlie = red</font>, <font color=blue>Kay = blue</font>, Dylan = green

	Review checklist for the first draft review:		Review checklist for the first draft review:

Mclauia: /* First Pass Notes */

2009-03-30T14:36:31Z

First Pass Notes

← Older revision		Revision as of 14:36, 30 March 2009
Line 21:		Line 21:
	* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.		* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.
	* Charlie will take care of tracking when things are turned-in and deducting points as need be.		* Charlie will take care of tracking when things are turned-in and deducting points as need be.
	* Reviewer colors - Ian = ~~slategray~~, Charlie = red, Kay = blue, Dylan = green		* Reviewer colors - Ian = darkmagenta, Charlie = red, Kay = blue, Dylan = green

	Review checklist for the first draft review:		Review checklist for the first draft review:

Charliep at 10:59, 10 March 2009

2009-03-10T10:59:13Z

@@ Line 1: / Line 1: @@
 For everyone (mostly):
 * Make sure you have an abstract, and overview of the unit's intent and purpose
@@ Line 18: / Line 31: @@
 **is there enough, too much
 **is it at the right level

Mclauia at 15:38, 25 February 2009

2009-02-25T15:38:30Z

← Older revision		Revision as of 15:38, 25 February 2009
Line 1:		Line 1:
			For everyone (mostly):
			* Make sure you have an abstract, and overview of the unit's intent and purpose
			* Draw up estimates of the cost of your unit for the worst case scenario (80 students)
			* Questions? Silly? Too hard?

	General process for the first draft review:		General process for the first draft review:
	* Use copy and paste to insert comments into each unit.		* Use copy and paste to insert comments into each unit.

Kay at 15:28, 25 February 2009

2009-02-25T15:28:33Z

← Older revision		Revision as of 15:28, 25 February 2009
Line 3:		Line 3:
	* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.		* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.
	* Charlie will take care of tracking when things are turned-in and deducting points as need be.		* Charlie will take care of tracking when things are turned-in and deducting points as need be.
	* Reviewer colors - Ian = slategray, Charlie = red, Kay = ?		* Reviewer colors - Ian = slategray, Charlie = red, Kay = blue, Dylan = green

	Review checklist for the first draft review:		Review checklist for the first draft review:

Charliep at 13:50, 25 February 2009

2009-02-25T13:50:46Z

← Older revision		Revision as of 13:50, 25 February 2009
Line 1:		Line 1:
	*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~~		General process for the first draft review:
	**"Fuck all of that!"		* Use copy and paste to insert comments into each unit.
	*use copy and paste to insert comments~~, screw a numbering system~~		* Whenever we make a review comment on a page, add the "Reviewer" tag so that the wiki can track comments for us.
	*~~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 tracking when things are turned-in and deducting points as need be.
	*Charlie will take care of ~~who is late etc~~		* Reviewer colors - Ian = slategray, Charlie = red, Kay = ?
	*~~reviewers will each take "some color"~~

	~~GRADING~~		Review checklist for the first draft review:
	*completeness check		* completeness check WRT the assignment page
	**is each item addressed with more than a header?		**is each item addressed with more than a header?
	*layout, does this show clear thinking about the presentation? will this develop		*layout, does this show clear thinking about the presentation? will this develop
Line 14:		Line 13:
	**is there enough, too much		**is there enough, too much
	**is it at the right level		**is it at the right level
	**FOR RELEASE 2
			Review checklist for the second draft review:
			* completeness check WRT the assignment page
	***be specific about exactly which sections of material in what order should be read		***be specific about exactly which sections of material in what order should be read
	***background reading for teachers?		***background reading for teachers?

Mclauia at 17:59, 18 February 2009

2009-02-18T17:59:05Z

← Older revision		Revision as of 17:59, 18 February 2009
Line 4:		Line 4:
	*whenever we make a review comment on a page, add "Reviewer" tag or whatever so that the wiki versioning does the work for us		*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		*Charlie will take care of who is late etc
			*reviewers will each take "some color"

	GRADING		GRADING