Add information about time, some of which is by tabbot.

[wiki.git] / runninghackathons.mdwn

diff --git a/runninghackathons.mdwn b/runninghackathons.mdwn
index 0e923401ce4e34af41c12da1d7fc36e40e538bb8..779c3784e40fb935ce77da697414fce6cdbf2fdc 100644 (file)
--- a/runninghackathons.mdwn
+++ b/runninghackathons.mdwn
@@ -12,7 +12,7 @@ Announce the hackathon at the SIPB meetings coming up to it.
 
 Send out an email to sipb-announce@mit.edu, mentioning date, time,
 place, name, etc.  Sound excited and enthusiastic.  Add a "tl;dr" for
-lazy people.
+lazy people. They traditionally start 1pm and go until 11pm or so. Any earlier and people don't wake up early enough and the office is lonely. 
 
 Create a Facebook event.  You probably want to be an administrator of
 the SIPB Facebook group for this.
@@ -28,7 +28,8 @@ Send a reminder email the day before.
 Expenses:
 =========
 
-SIPB allocates $150 to a hackathon.  Most of this should be used on
+SIPB allocates $150 to a hackathon (assuming approval of the vice-chair).
+Most of this should be used on
 food (see below).  If you have extra money, you can be creative.  For
 Hackasaurus Rex and Velocihacker, we purchased prizes off of ThinkGeek
 and raffled them off on the hour.  It was reasonably popular.
@@ -123,7 +124,7 @@ Zephyr:
 -------
 
 Encourage discussion on zephyr, either on -c sipb or 
--c <HACKATHON_NAME>.
+-c $HACKATHON_NAME.
 
 
 Social stuff:
@@ -141,6 +142,8 @@ entertained.  It is very easy, especially near the end, for SIPB
 regulars to get into a niche and for new people to feel excluded.  Try
 to make sure that that doesn't happen.
 
+Someone should try to help people find projects they are interested in.
+One way to do this is to have enthusiastic happy person who knows whats going on at the door greeting people, asking what their interested are and routing them to the people leading those projects.
 
 Afterwards:
 ===========