You are expected to understand this. CS 111 Operating Systems Principles, Spring 2006
You are here: CS111: [[2006spring:scribeguidelines]]
 
 
 

Scribe notes guidelines

Everyone will participate at least once in creating a set of scribe notes for a lecture. Three scribes will be assigned at the beginning of each lecture. Over the following week, they will cooperate to produce a single set of notes. The notes will be posted on the Web for everyone's reference.

Scribe notes are posted on this wiki. To access a particular set of notes, see schedule. Notes that have been written, or are in the process of being written, appear as green links. Notes that don't exist yet are in red. Scribes should create their notes by logging in to the wiki, jumping to their scribe notes link from the schedule, and clicking "Edit" to edit that page. Only the scribes for lecture N can edit the page named [[notes:lecN]]. However, anyone in the class can create or edit any other page named [[notes:WHATEVER]]. Scribes can use this ability to create sub-pages of their main notes page.

For more information on syntax for the wiki, see syntax. You can include images in your notes, too; the image attach button on the Wiki's edit page, which looks like this , will let you upload the relevant .gif, .jpg, or .png files along with your notes.

The professor will provide each scribe note group with write access to the corresponding page. Scribes should complete the first draft of their notes approximately a week after the lecture. Let me know when they are complete.

Style

Your audience in these notes is essentially yourselves -- this class -- in about 4 weeks' time, when you have forgotten what the lecture was about. Your notes should be clear enough to get a sense of the important topics in class without having been to class (or after forgetting the class). I prefer full sentences to bullet points. Do not forget the motivation for the topics we discuss -- the reasons why an interface is good, for example. Motivation makes the topics easier to remember.

In the past, the most successful notes have consisted mostly of text and pseudocode, with a handful of diagrams. Consider your diagrams carefully: does the picture really help?

Here's some notes that would earn an A+: http://www.cs.ucla.edu/~kohler/class/05s-osp/notes/notes4.html

Last quarter's notes are available here; the quarter before's are here. Please feel free to use them as a starting point. Your notes should improve on those of your predecessors. And the lectures will change for this quarter, so the previous notes may not apply exactly. If you do use prior notes, make sure to cite them properly.

Make sure you sign your notes (put your names on them).

Grading

Notes will receive letter grades. The average grade for a set of notes will be in the low B range. To earn an A, I will expect you to produce clear notes, in grammatical English (a minimum of bullet points), that cover the topics in class, with motivation, and with a sense of the hypothetical examples I often use to move the class along. To earn an A+ you will need to go above and beyond the call of duty. Feel free to produce notes that are in your own words, or that present the lecture in a new way, or that link to external references.

Again, here's some notes that would earn an A+: http://www.cs.ucla.edu/~kohler/class/05s-osp/notes/notes4.html

 
2006spring/scribeguidelines.txt · Last modified: 2006/04/17 10:44 (external edit)
 
Recent changes RSS feed Driven by DokuWiki