Open Source Comes to Campus/CCSF/Plan

Contact phase

 * Get local contacts' names (insist on two)
 * Get commitment from them

Logistics phase
(Begins 4 weeks pre-workshop)


 * Identify funding possibilities
 * Identify core staff
 * Asheesh TODO
 * Nail down date
 * Location: Only available until 3pm for now; that is bad news; Katherine is asking about that
 * Send a save-the-date email to CS department students
 * Done by Katherine... the spreadsheet where data goes is shared with Shauna and Asheesh
 * Commit to contacts that we want to do the workshop


 * Other Asheesh todo
 * Tell her installation should be fine
 * Tell her Android peeps are mega invited and we should try to tailor to them

Pre-event phase
(Begins 3 weeks pre-workshop)

otherwise appropriate for attendees enough and otherwise appropriate for attendees
 * Recruit more staff
 * Recruit career panelists
 * Make website with signup survey
 * Asheesh TODO by 5/23
 * (2.5 weeks before) Prepare list of hand-picked bugs for projects time
 * (2.5 weeks before) Do diversity-oriented publicity
 * Mills College computer science
 * Berkeley WiCS
 * SFSU WiCS -- does it exist?
 * (2 weeks before) Do general publicity
 * SFSU ACM
 * Choose attendees
 * Confirm with attendees
 * (9 days before) Review staff list and make sure it is large enough and
 * (5 days before) Review hand-picked bug list and make sure it is large

Event phase
(3ish days before)


 * Visit space pre-event
 * Order food
 * Ensure event is photographed

Post-event phase

 * Blog post on openhatch.org
 * Expense report
 * Send post-event survey to attendees
 * Send thank-you notes to campus orgs that helped

Notes from call

 * Staff ratio
 * we like to do 6:1
 * Reminder email
 * Make sure students are on a wifi list
 * Staffers should be on a wifi list, which we should send to IT by Thursday
 * Thursday... 7-9:30 vs. 7... for laptop setup
 * AL to find previous emails for this
 * AL can send laptop setup
 * AL can add tar mission to the laptop setup