# Format for P1 "Proposals"

You may use the "long form" of TextWeb::/699/proposals.txt but that
might be overkill. Those questions are good food for thought.

What you __must__ do:

1. Give a general idea of the problem you are trying to solve.

2. Give a specific goal of what you expect to achieve in the short
   term (that is by March 3 when this milestone is due). Try to
   describe things in a way that will allow us to evaluate what you do
   achieve. 

   Its probably best to describe what you are going to implement, what
   you expect it will look like, and what pieces you will build it
   from. 

3. Give a suggestion of the bigger picture: where would this go if you
   were successful and continued it for another 4-8 weeks.

4. Give a rough idea of your plan of attack. Give details on the first
   steps (if the first steps of the project aren't clear, then there
   might be an issue).

5. What do you intend to read for this project. As part of your
   "final" report, you will need to provide summaries for at least 4
   (if you are working alone) or 6 (if your are working as a team)
   papers. 

   You may not know all of the things you will read, so list the ones
   you do know, and give some ideas as to what else you might read. 

   Note: a web hunting expedition CAN count for one of your
   papers. This is especially valuable if you are looking for things
   on game programming.

The exact form isn't critical - what is important is that you give a
clear explanation of where you expect to get to by March 3, and that
you've thought through how to start.

Please place a text file in the directory:
<pre>/p/course/cs777-gleicher/public/Summaries/P1-Proposals</pre>
For my scripts to work, it has to have a ".txt" extension.

If you want things to display nicely, you can put your file into
markdown http://daringfireball.net/projects/markdown/ format.

Also beware that my text->html translator tries to automagically
convert html links to clickable links, and to do some other text->html
conversions.