More polishing.

Just need the FAQ.

website/docs/format.md

@@ -1,38 +1,38 @@
 Lectures will be loosely organized around four modules: differential privacy,
 cryptography, language-based security, and adversarial machine learning. The
 instructor will give most of the lectures for the first module, on differential
-privacy. For each of the remaining modules, the instructor will give the first
-lecture introducing the topic and background material. Then, each student will
-lead one lecture, presenting a paper and guiding the discussion.  
+privacy. For each of the remaining modules, I will give the first lecture
+introducing the topic and background material. Then, each student will lead one
+lecture, presenting a paper and guiding the discussion.  
 
 The topics we will be reading and thinking about are from the recent research
 literature---polished enough to be peer-reviewed and published, but not always
 completely refined. Given that this is a graduate course, not all lectures are
-set in stone and there is some flexibility in the choice of topics. Students
-with interested in specific topics not covered in the syllabus should feel free
-to contact the instructor.  
+set in stone and there is considerable flexibility in the topics. If you are
+interested in something not covered in the syllabus, please let me know.
 
 ## Readings and Homework
 
-Paper discussions are a core component of this course.  Students are expected to
+Paper discussions are a core component of this course. You are expected to
 read papers before lecture, attend lectures, and participate in discussions.
 Before every lecture presenting a paper, students are expected to read the paper
 closely and understand its significance, including (a) the problem addressed by
 the paper, (b) the main contributions of the paper, and (c) how the authors
 solve the problem in some technical detail.  
 
-The instructor will also send out 2-3 questions before every paper presentation.
-Students will submit brief answers---no more than 1-2 paragraphs per
-question---before the lecture. These questions are meant to make sure you have
-understood the paper at a high level and prepare for the discussion in class,
-they are not meant to be very difficult or time-consuming.
+I will also send out 2-3 questions at least 24 hours before every paper
+presentation. You should send me brief answers---no more than a few sentences
+per question---before the lecture.  These questions are meant to help you
+prepare for the discussion in class, they are not meant to be very difficult or
+time-consuming and they will not be graded very thoroughly.
 
 ## Course Project
 
-Students will work individually or in pairs on a topic of their choice,
-producing a conference-style write-up and presenting their project at the end of
-the semester. This project should have the potential to turn into a research
-paper or survey. Details can be found [here](projects/details.md).
+The other main component is the course project. You will work individually or in
+pairs on a topic of their choice, producing a conference-style write-up and
+presenting their project at the end of the semester. This project should have
+the potential to turn into a research paper or survey. Details can be found
+[here](projects/details.md).
 
 ## Grading and Evaluation
 
@@ -44,6 +44,6 @@ Grades will be assigned as follows:
 
 ## Academic Integrity
 
-Pre-lecture questions should be done individually. The final project may be done
-individually or in groups of two students. Collaboration projects with people
-outside the class may be allowed, but must be approved by the instructor.
+The final project may be done individually or in groups of two students.
+Collaborative projects with people outside the class may be allowed, but please
+check with me beforehand.

website/docs/index.md

@@ -16,7 +16,7 @@ complete a final project.
 
 Please use the mailing list if you want to contact the whole course:  
 
-- [compsci839-1-f18@lists.wisc.edu](compsci839-1-f18@lists.wisc.edu).
+- [compsci839-1-f18@lists.wisc.edu](compsci839-1-f18@lists.wisc.edu)
 
 All registered students should be on this list. If you are not registered but
 would like to follow along, please let me know and I will try to add you.
@@ -27,9 +27,9 @@ right place, please start the subject with **CS839**.
 ## Course Staff
 
 - **Instructor**: Justin Hsu
-    - **Email**: email@justinh.su
-    - **Location**: TBD
-    - **Office hours**: TBD
+- **Email**: email@justinh.su
+- **Location**: TBD
+- **Office hours**: TBD
 
 ## FAQ
 

website/docs/projects/details.md

@@ -1,6 +1,9 @@
+# Project Details
+
 This course covers a wide range of topics in security and privacy. The goal of
 the course project is to dive more deeply into a particular topic individually
-or in groups of two. This project could take different forms:
+or in groups of two.  A good project could potentially lead to a publishable
+result.  This project could take different forms:
 
 - **Theoretical**: Extend a technique, explore a new application, or develop
   some other kind of conceptual contribution.
@@ -11,27 +14,33 @@ or in groups of two. This project could take different forms:
   research area. Summarize the significance, then compare and contrast.
 - **Other**: Feel free to propose other kinds of projects.
 
-A good project will be the start of a potentially publishable result.
+If at any point you have trouble finding a project, run into difficulties, or
+just want some advice, **please come talk to me** and I will try to help you get
+unstuck.
 
 ## Deliverables
 
-In order to keep projects on track, each group will turn in two short (**1-2
-pages**) milestone reports along the way. At one-third of the way through, you
+In order to keep projects on track, each group will turn in two milestone
+reports along the way, **1-2 pages each**. At one-third of the way through, you
 should have settled on a project goal and made some exploratory steps.
 
 - **Milestone 1**. Describe the project goal concretely, summarize what
   preliminary things have been tried, and plan out which directions to explore
-  next.
+  next. [Heilmeier's
+  Catechism](https://en.wikipedia.org/wiki/George_H._Heilmeier#Heilmeier%27s_Catechism)
+  is a good series of questions to keep in mind.
 
 At two-thirds of the way through, the project should be progressing and it
 should be clear what remains to be done.
 
-- **Milestone 2**. Clarify the project goal if it has changed, summarize current
-  progress, and plan out how to finish remaining items.
+- **Milestone 2**. Clarify the project goal, summarize current progress, and
+  plan out how to finish remaining items. Describe what you think can definitely
+  be done, along with further reach goals that might be possible.
 
 Besides the milestones, the main deliverable of the project will be a final
 report, around **15-20 pages** in length. Reports should be written in a
-research paper style, covering the following broad areas in some order:
+research paper style, covering the following broad areas in some reasonable
+order:
 
 - **Introduce** the problem and the motivation. 
 - **Review** background and preliminary material.
@@ -39,12 +48,9 @@ research paper style, covering the following broad areas in some order:
 - **Survey** related work.
 - **Summarize** and evaluate the results.
 
-At the end of the course, each group will present their project in class.
+At the end of the course, each group will give a brief project presentation in
+class.
 
 ## Deadlines
 
-The most immediate task is to form groups (if desired) and select a preliminary
-project topic. Discuss with the instructor or send an email with the project
-topic and group members (less ideal) by **???**.
-
-Deadlines for the deliverables are [here](../schedule/deadlines.md).
+See [here](../schedule/deadlines.md).

website/docs/resources/software.md

@@ -10,5 +10,3 @@
 ## Language-Based Security
 - [Jif](https://www.cs.cornell.edu/jif/)
 - [FlowCaml](https://opam.ocaml.org/packages/flowcaml/flowcaml.1.07/)
-
-## Adversarial Machine Learning

website/docs/schedule/deadlines.md

@@ -1,12 +1,11 @@
-Before class on the dates indicated.
+The first key date is **September 19**. Before this date, you should:
 
-## Course Deadlines
-- **Check in with instructor**: TBD
-- **Sign up to present paper**: TBD
-- **Check-up questions**: Before each paper presentation.
+- **Check in** with me briefly.
+- **Sign up** to present a paper.
+- **Choose** a project topic and form groups. This is not a firm commitment, but
+  you should have an initial direction.
 
 ## Project Deadlines
-- **Choose topic**: TBD
-- **Milestone 1**: TBD
-- **Milestone 2**: TBD
-- **Final writeup**: TBD
+- Milestone 1: **October 15**
+- Milestone 2: **November 14**
+- Final writeup and presentation: TBD