From 0ea1002d7de99e33302ef697185ad519f7bdf995 Mon Sep 17 00:00:00 2001
From: Edgar Bering <ebering@caffeine.csclub.uwaterloo.ca>
Date: Mon, 23 Nov 2009 13:23:20 -0500
Subject: [PATCH] adding code party

---
 events.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/events.xml b/events.xml
index 8cd005e..fd777c9 100644
--- a/events.xml
+++ b/events.xml
@@ -4,6 +4,21 @@
 <eventdefs>
 
 <!-- Fall 2009 -->
+<eventitem date="2009-11-27" time="7:00 PM" room="Comfy Lounge" title="Code Party!!11!!">
+  
+    <short><p>A fevered night of code, friends, fun, energy drinks, and the CSC. Facebook will be around to bring some food and hang out.
+</p></short>
+  
+  
+    <abstract><p>Come join us for a night of coding. Get in touch with more experianced coders,
+advertize for/bug squash on your favourite open source project, write that personal
+project you were planning to do for a while but haven't found the time. Don't
+have any ideas but want to sit and hack? Try your hand at the Facebook puzzles,
+write a new app, or just chill and watch scifi.
+</p></abstract>
+  
+</eventitem>
+
 <eventitem date="2009-11-05" time="4:30 PM" room="MC2065" title="In the Beginning">
 
     <short><p>To most CS students an OS kernel is pretty low level. But there is something even lower, the instructions that must be executed to get the CPU ready to accept a kernel.  That is, if you look at any processor's reference manual there is a page or two describing the state of the CPU when it powered on.  This talk describes what needs to happen next, up to the point where the first kernel instruction executes.