This is the News page – or a list of announcements that seem important. Please also check out the BasicInfo page for basic course information.
I think that each group has something worth showing to the world, so I am making the handin directory be web accessible. If you don’t want the world to see it, you can restrict access to the directory.
A handin directory has been created on afs at:
Each person in class should have write permission in this directory. You can see this directory on the web at:
For each group: please make a subdirectory in this directory, and put all your stuff in it. Please make sure there is a README file.
If there is a web document, please make it be the “index.htm” document, so that people visiting the directory via the web see it. Ideally, there will be an index page explaining to whoever visits what they can find.
If you don’t want people to see your work (other than me), you can add a “.htaccess” file that limits access to the directory:
means only authenticated CS users can see stuff.
We will do final project demos/presentations from 9:45am – noon (ish – we might not really finish on time) on Wednesday, May 11th. We’ll be in room 4310 CS (one floor above 3310 where we normally meet).
We’ll start at 9:45. Each group will get 10 minutes to talk/show off stuff. 5 minutes for questions and group switching. If everything goes according to plan, its 2 hours – add in 15 minutes of break in the middle, and we’re done at noon. In practice, we might shorten the break, and go a little longer since people may not really finish in 10 minutes.
I will give specific details of other expectations to each group by email later today.
Before Friday 5/6 (that means on Thursday, or at least before I check my email Friday morning), each group must send me an email with a “status update.” You should describe what the current state of your project is, where you expect to get to by the final deadline (Weds 5/11), and what kinds of things you think you’ll want to “hand-in.”
On Friday 5/6, I will reply to each group with the hand-in requirements. Unlike the previous project (and most projects I’ve ever given), the requirements will vary from group to group, based on the project type, the number of people in the project, and the content.
You should expect that your handin will include: a document, some visual representation of the results (probably a video), a reading list, and whatever you built. Some groups I might ask for other documents. I will also ask for a self-evaluation (not as extensive as last time).