programmingops
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
programmingops [2009/09/05 19:18] – jer | programmingops [2017/01/14 14:24] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | //**THIS SHOULD BE UPDATED TO REFLECT THE CURRENT YEAR, IT HAS BEEN ARCHIVED**// | + | ====== Links to Prior Year Event Counts ====== |
+ | [[https://drive.google.com/ | ||
+ | [[https:// | ||
+ | [[https:// | ||
+ | [[https:// | ||
+ | |||
+ | ==== Areas for Improvement / 2015 Recommendations ==== | ||
+ | - Replace printed name tents with dry erase name tents (Example: http:// | ||
+ | - Have ProgramOps do room scheduling in advance of the convention rather than Programming. | ||
+ | - Standardize A/V available in each room. Ideal would be to have a projector and microphone in each room, but this is likely cost prohibitive. Have groups of rooms designated for panels (which typically don't need a projector), and group of rooms that are for individual speakers (which typically do need a projector). | ||
+ | - Work with Programming to get the programming data sent to ProgramOps to match the format listed below. | ||
+ | - Start date & time need to be combined into one field.\\ | ||
+ | - End date & time need to be combined into one field.\\ | ||
+ | - Tracks, A/V needs need separate fields if there is more than one listed per scheduled event, similar to how speakers should be.\\ | ||
+ | - Speakers need to be separated into separate fields where there is more than one. \\ | ||
+ | - Have microphones available for speakers to use when located next to a musical performance or other event likely to be loud.\\ | ||
+ | - Have a room available to move events to at the last minute if there is too much noise to be heard in their current room.\\ | ||
+ | - For all speakers, include the name their registration is listed under. | ||
+ | - Have Programming designate which presenters do or do not need name tents. | ||
+ | - Stop counting attendance at events. | ||
+ | - Create electronic counters for each room so as not to need people to visit each room to take attendance counts during each event.\\ | ||
+ | - Set up Google mail to forward a copy of all email sent to Programming or Track heads after the schedule is frozen to Program Ops. This is to ensure that Program Ops receives any notifications from presenters who need to cancel at the last minute.\\ | ||
+ | - Determine whether speaker packets need closer integration with pre-registration envelopes.\\ | ||
+ | - Provide ProgramOps a list of hours when the Makerspace is supposed to be open, if counting will continue.\\ | ||
+ | - Only have one Google calendar to update during the convention. | ||
+ | - Determine whether ProgramOps budget should be expanded to include swag, or whether that should fall under marketing.\\ | ||
+ | - Revisit speaker packets to see if they are still necessary, and if so, whether they are necessary for all types of speakers. | ||
+ | - Look into replacing name tents with reusable, dry-erase boards sized appropriately. | ||
+ | - Revisit warning system/ | ||
+ | |||
+ | ====== Program Ops Responsibilities | ||
+ | The Program Ops person is a staff member on the Operations (Ops) team who handles the direct operational running of the convention programming. Program Ops responsibilities include ensuring all convention events start & finish on time, providing real time updates to the schedule during the convention if event times or locations are changed, counting attendance at all scheduled events, and publishing the resulting data immediately after the convention. | ||
+ | |||
+ | ===== Required Skills & Availability ===== | ||
+ | - On-site availability during convention hours with scheduled events to make schedule modifications, | ||
+ | - Ability to understand event needs (space, A/V, etc.) and select a new time/ | ||
+ | - Ability to communicate changes to the schedule in a timely manner using all available technology.\\ | ||
+ | - Familiarity with technology used to publish changes to the schedule during the convention – Twitter, Google Calendar, etc.\\ | ||
+ | - Familiarity with database or other software with query & reporting capabilities that can be used to generate materials for participant packets.\\ | ||
+ | - Ability to coordinate planning activities prior to convention with other areas, particularly the heads of Programming & Operations.\\ | ||
+ | - Availability for the week prior to convention to generate & assemble packet materials, and make any last minute updates prior to the start of the convention.\\ | ||
+ | - Availability to attend feedback session (if there is one) and note recommendations for improving Program Ops.\\ | ||
+ | |||
+ | ===== Tools ===== | ||
+ | - Contact the designated Webmaster or the prior year’s Program Ops resource for the password to the ProgramOps at penguicon.org account, accessible via Google/ | ||
+ | - Samples of the following materials are available on Google drive when logged in to the Program Ops account:\\ | ||
+ | - GoH Welcome Letter\\ | ||
+ | | ||
+ | - Hourly Count Sheet | ||
+ | - Name tent | ||
+ | - Packet Labels | ||
+ | - Room Schedules | ||
+ | - Speaker Schedules | ||
+ | - Individualized Speaker Map | ||
+ | - Instructions for Ops Related to Program Ops | ||
+ | |||
+ | ===== Responsibilities ===== | ||
+ | Note that the timings below are recommended, | ||
+ | Key deadlines that Program Ops must clearly specify are the schedule freeze date and the date/time Program Ops provides completed participant packets for pickup.\\ | ||
+ | |||
+ | ==== Throughout the Year ==== | ||
+ | - Read and respond to email sent to Program [email protected] in a timely manner. | ||
+ | - Attend scheduled ConCom meetings to understand any decisions made that will impact the running of the convention.\\ | ||
+ | |||
+ | ==== 12 Weeks Prior ==== | ||
+ | - Notify volunteer coordinator (volunteers at penguicon.org) of hours when volunteers are needed. | ||
+ | - Friday, 4:00 PM - 11:00 PM, 1 (min.) - 2 volunteers needed at the start of each hour. (The last volunteers will finish at midnight)\\ | ||
+ | - Saturday, 10:00 AM - 11:00 PM, 1 (min.) - 2 volunteers needed at the start of each hour (The last volunteers will finish at midnight)\\ | ||
+ | - Sunday, 10:00 AM - 2:00 PM, 1 (min.) - 2 volunteers needed at the start of each hour (The last volunteers will finish at 3:00 PM)\\ | ||
+ | - Review sample materials. | ||
+ | |||
+ | ==== 8 Weeks Prior ==== | ||
+ | Request access to or an electronic copy of existing schedule information. | ||
+ | ^Attribute^Description^Required^Example Data^ | ||
+ | | Event Name |Name of the event | Y |Open Sketch and Draw| | ||
+ | | Event Start | Date & time at which the event starts| Y | 4/26/2013 16:00| | ||
+ | | Event End | Date & time at which the event ends| Y | 4/26/2013 16:50| | ||
+ | | Event Description| Text that will be used to describe the event in the program book. | Y | Need a quiet corner to draw and sketch and get your creative juices flowing to start off the convention? | ||
+ | | Event Track | Primary track or grouping (BOF, track, etc.) for the event. //Note//: All BOF sessions should be labeled as such consistently. | N | BOF| | ||
+ | | Venue | Location for the event. | ||
+ | | A/V Needs| Designates what A/V needs the event has, or " | ||
+ | |Speaker 1| Full name for the first presenter/ | ||
+ | | Speaker 2| Full name for the second presenter/ | ||
+ | | Speaker //n//| Full name for the //n//th presenter/ | ||
+ | |||
+ | - Confirm with the head of programming the approximate number of presenters. | ||
+ | - Request from the person creating the printed program book a copy of the map that will be provided to conference attendees.\\ | ||
+ | - Import the provided schedule information into the database/ | ||
+ | |||
+ | ==== Six Weeks Prior ==== | ||
+ | - Request green room information from the head of Hospitality for inclusion in GoH welcome letters.\\ | ||
+ | - Request a list of GoH liaisons from the appropriate department head.\\ | ||
+ | - Request a copy of the official map to be put in the scheduling book from the person responsible for the program book. Modify as needed to use for individual participant maps.\\ | ||
+ | - Update the welcome letters to reflect current green room & liaison information.\\ | ||
+ | - Generate samples of the information that will be provided in each packet and provide to the heads of Ops, Programming, | ||
+ | - Welcome letter\\ | ||
+ | - Speaker schedule\\ | ||
+ | - Speaker name tent\\ | ||
+ | - Speaker map\\ | ||
+ | - Determine pricing for & get approval from the head of Ops to order supplies for speaker packets. | ||
+ | - Envelope that holds an 8.5 x 11 sheet of paper\\ | ||
+ | - Label for each envelope, size of 10 per 8.5 x 11 sheet\\ | ||
+ | - Name tent, 4.25 x 11 inches folded\\ | ||
+ | - Paper to print schedule, typically white\\ | ||
+ | - Paper to print/copy welcome letter, typically white\\ | ||
+ | - Paper to print an 8.5 x 11 copy of the map\\ | ||
+ | |||
+ | ==== Four Weeks Prior ==== | ||
+ | - Confirm speaker count (to nearest 50, rounded up) with the head of Programming.\\ | ||
+ | - Order supplies for presenter packets.\\ | ||
+ | - Request an updated copy of the program schedule. | ||
+ | - Provide Registration a list of speakers, and the number of scheduled speaking hours for each.\\ | ||
+ | - Request a copy of room layouts, and room flip schedule. \\ | ||
+ | - Notify volunteer coordinator of any changes to volunteer needs based upon when programming is scheduled.\\ | ||
+ | - Verify which rooms will have which A/V capabilities, | ||
+ | |||
+ | ==== Two Weeks Prior ==== | ||
+ | - Confirm with the head of Programming the date upon which the schedule will be frozen. | ||
+ | - Request from the head of Ops ribbons to be included in presenter packets. | ||
+ | - Format a copy of the attendee map to fit on an 8.5 x 11 piece of paper. | ||
+ | - Request access to all accounts to be used during the convention for publicizing schedule changes (Twitter, Google Calendar, etc.)\\ | ||
+ | - Review with the head of Operations instructions to be provided to Ops staff/ | ||
+ | - Request GoH, participant, | ||
+ | - Provide Registration an updated list of speakers & hours by speaker, with differences from the prior version highlighted.\\ | ||
+ | |||
+ | ==== One Week Prior through the Day Prior to Convention ==== | ||
+ | Note: Typically plan for this process to take the better part of the weekend prior to the start of the convention, at a minimum, plus additional time up until the convention start to make any final changes.\\ | ||
+ | |||
+ | - Request a final copy of the schedule. | ||
+ | - Import and verify the schedule information. | ||
+ | - Generate printed materials for the presenter packets. \\ | ||
+ | - Welcome letter (GoHs and Featured Guests)\\ | ||
+ | - Participant schedule\\ | ||
+ | - Presenter name tent\\ | ||
+ | - Map (8.5 x 11 version)\\ | ||
+ | - Label\\ | ||
+ | - Assemble presenter packets. \\ | ||
+ | - Place a name label on the front of each envelope. | ||
+ | - Add the welcome letter, participant schedule, and name tent to each envelope. | ||
+ | - Add GoH ribbons to each GoH envelope.\\ | ||
+ | - Add presenter ribbons to each other envelope.\\ | ||
+ | - Add ribbons purchased on behalf of GoHs to their envelopes. | ||
+ | - Print out attendee count sheets and assemble into a three ring binder to be left at Ops. (Recommend 3 copies per hour.)\\ | ||
+ | - Print out room schedules, using a minimum 16 pt font. Print one copy to be posted by each door to the room.\\ | ||
+ | - Print out signs to hold up to provide presenters 5 & 10 minute warnings.\\ | ||
+ | - Assemble materials needed by volunteers – clip board with map, watch, writing implements, and warning signs.\\ | ||
+ | - If any changes are made to the schedule, update affected presenter schedules, room schedules, | ||
+ | - Provide Registration an updated list of speakers & hours by speaker, with differences from the prior version highlighted.\\ | ||
+ | ==== Convention – Set Up ==== | ||
+ | - Drop off packets at Registration as soon as Registration setup begins.\\ | ||
+ | - Place Program Ops binder & Program Ops materials in Ops in the area designated by the head of Operations.\\ | ||
+ | - Post room schedules outside each entrance to each room.\\ | ||
+ | |||
+ | ==== Convention - During ==== | ||
+ | - At the start of each hour when programming is scheduled (ending at midnight), go to Ops to meet with the volunteer(s).\\ | ||
+ | - Provide the volunteers instructions for counting & recording attendance at each panel and recording the same and for providing warnings when time is up.\\ | ||
+ | - Request volunteers communicate any issues they observe directly to Ops for resolution (Examples: A/V issues, no water for presenter, etc.)\\ | ||
+ | - If no volunteer is present, complete the activities normally assigned to the volunteer.\\ | ||
+ | - Respond to all texts/calls from Ops & address any schedule changes as outlined in the Schedule Changes section. \\ | ||
+ | - Periodically throughout the weekend, enter count of attendees at each event or in each scheduled space (gaming, DIY, etc.) into your tool of choice.\\ | ||
+ | - Attend the feedback session (if one is scheduled) and note any recommendations for improvement that could or should be completed by Program Ops.\\ | ||
+ | |||
+ | === Schedule Changes: Cancellations === | ||
+ | - Cross out the event on the room schedules.\\ | ||
+ | - Post a notice to Twitter indicating the event is cancelled.\\ | ||
+ | - Cross out the event on the schedules maintained by & any schedules posted in Ops.\\ | ||
+ | - Update Google Calendar and any other sources provided by Programming to indicate that the event is cancelled. | ||
+ | - Note the cancellation on the white board outside of Ops.\\ | ||
+ | - Confirm the change is entered on the schedule change sheet.\\ | ||
+ | |||
+ | === Schedule Changes: Changes / Additions === | ||
+ | - Based upon what is being requested (Larger room? Different time?, Different A/V Requirements? | ||
+ | - Update the schedule(s) posted outside the affected room(s).\\ | ||
+ | - Post a notice to Twitter with the schedule change.\\ | ||
+ | - Update Google Calendar and any other sources provided by Programming as needed.\\ | ||
+ | - Update the physical schedule maintained by & any schedules posted in Ops.\\ | ||
+ | - Updated the affected count sheets.\\ | ||
+ | - Note the change on the white board outside of Ops.\\ | ||
+ | - Confirm the change is entered on the schedule change sheet.\\ | ||
+ | |||
+ | ==== Following Convention ==== | ||
+ | - Retrieve any unclaimed packets from Registration. | ||
+ | - Complete the entering of attendance counts for each event.\\ | ||
+ | - Generate a CSV file with attendance counts. | ||
+ | - Verify information is accurate as possible and takes into account schedule changes.\\ | ||
+ | - Upload the CSV to Google Drive using the Program [email protected] account. | ||
+ | - Send an email to [email protected] & the ConCom distribution list ([email protected]. )with the CSV file as an attachment, or link to the same.\\ | ||
+ | - Update the wiki with a link to the attendance file.\\ | ||
+ | - Update the Areas for Improvement section on this wiki page with ideas for improving the functioning of Program Ops for the next convention.\\ | ||
+ | |||
+ | |||
+ | |||
+ | ====== Improvements Implemented for 2014 ====== | ||
+ | - Have Programming provide contact information for each presenter so they can be reached during the convention if they have not arrived for a panel. | ||
+ | - Send out an email prior to Penguicon telling all presenters/ | ||
+ | - Print out a schedule showing the A/V needs for each event, and the A/V available in each room.\\ | ||
+ | - Provide custom maps to each speaker that have their presentation locations highlighted.\\ | ||
+ | - For program blocks that are for setup, | ||
- | The Programming Ops person is a part of the programming team on the ConCom who handles the direct operational running of the schedule while at the convention. For instance, this person counts and records the number of attendees at each event, gives a signal to those running the event when they have five-minutes left in their time slot, and makes sure there is water to drink for the panelists during their presentations. | ||
- | ======Past Headcounts====== | ||
- | =====Penguicon 7.0 (2009)===== | ||
- | {{: | ||
- | ^Title^# Attended^ | ||
- | |Morning Coffee Ritual|Cancelled| | ||
- | |The Melancholy of Haruhi Suzimiya|?| | ||
- | |Wild About Harry|?| | ||
- | |Camp Unix|?| | ||
- | |Opening Ceremonies Preshow|?| | ||
- | |LN2 Ice Cream|?| | ||
- | |Beer Tasting|?| | ||
- | |Karaoke|?| | ||
- | |The Art and Zen of the Jello Shot|?| | ||
- | |Liar Liars!|?| | ||
- | |Gaohranger (live action)|?| | ||
- | |Never Click on a Link|?| | ||
- | |Hey! You've got RPG in my MMO!|?| | ||
- | |Talking About Drinking~ with Aegis|?| | ||
- | |SMOSCast|? | ||
- | |Minibridge|? | ||
- | |Keysigning I|?| | ||
- | |LN2 Ice Cream|?| | ||
- | |Keysigning II|?| | ||
- | |Illuminati|? | ||
- | |Brazillian Beef Serving|?| | ||
- | |Writer' | ||
- | |Charity Auction|?| | ||
- | |W.A.G.O.N. Webcomic Battle|?| | ||
- | |Intro to PHP|?| | ||
- | |Bacchus Banquet|?| | ||
- | |Exposition of Gear and Garb Masquerade Muster|?| | ||
- | |Masquerade Setup|?| | ||
- | |Dinner with Dawn and Greg|?| | ||
- | |Birds of a Feather|?| | ||
- | |FRAG|?| | ||
- | |LN2 Ice Cream|?| | ||
- | |The Dance|?| | ||
- | |Tournament|? | ||
- | |Stand by Wheaton... In Rock Band!|?| | ||
- | |SMOSCast|? | ||
- | |Yoga for the Insomniac|? | ||
- | |Casshern: Sins|?| | ||
- | |Luke Ski Hot Tub Singalong|? | ||
- | |LN2 Ice Cream|?| | ||
- | |Morning Coffee Ritual|?| | ||
- | |LN2 Ice Cream|?| | ||
- | |Webcomic Brunch|?| | ||
- | |Lie to Me!|?| | ||
- | |Anything But Ethernet|?| | ||
- | |Atari Competition|332| | ||
- | |Exhibition of Gears and Garb|230| | ||
- | |Opening Ceremonies|169| | ||
- | |Sex Toys with Shannon|135| | ||
- | |Upcoming Advancements in the Linux Desktop|100| | ||
- | |Knife Throwing|80| | ||
- | |Dr. Horrible' | ||
- | |Closing Ceremonies|60| | ||
- | |How DNS Works|54| | ||
- | |Open Hardware Overview|52| | ||
- | |Open Hardware with Arduino HOWTO|52| | ||
- | |The Chocolate Ritual|50| | ||
- | |Book Signing|50| | ||
- | |Introduction to Forensics|48| | ||
- | |BSP|45| | ||
- | |Tom Smith Concert|44| | ||
- | |SELinux: Modern Linux Security|43| | ||
- | |Where' | ||
- | |To Arms! Medieval Combat for Writers and Gamers|42| | ||
- | |Beginning Pygame Programming|41| | ||
- | |Luke Ski Concert|40| | ||
- | |Metalwork Demo and Discussion|40| | ||
- | |How To Kill A Character 2.0: No Bullets or Pointy Things|39| | ||
- | |Liquid Fluoride Thorium Reactor|38| | ||
- | |From Nosferatu to Body Glitter: What's Happened to Vampires? | ||
- | |Geeks With Guns|35| | ||
- | |Desktop Fabrication Panel|35| | ||
- | |Rob Balder Concert|34| | ||
- | |More~ Moore; Faster~ Faster: The Impact of Nanotechnology on Computers & Electronics|33| | ||
- | |Yep~ That's Steampunk|32| | ||
- | |The Good~ the Bad~ and the Ugly|32| | ||
- | |Can Hardware be Open Source?|32| | ||
- | |Linux in the Enterprise|32| | ||
- | |Self-Defense|32| | ||
- | |The Tom and Frank Show|32| | ||
- | |Lightning Talks|31| | ||
- | |Intro to Linux|31| | ||
- | |Dual Core Concert|30| | ||
- | |Can I Be Your Friend? Bringing Authors and Readers Together|30| | ||
- | |Trust Me~ It's Just Chemistry...with Professor X|30| | ||
- | |To See a Universe in a Grain of Sand|30| | ||
- | |What' | ||
- | |Polyamory|29| | ||
- | |Installing and Configuring MythTV|28| | ||
- | |Prop Weapons~ Nerf Modifications|26| | ||
- | |Building Community in a Free/Open Source Software Project|26| | ||
- | |Neural Networks for the Non-Technical: | ||
- | |Board Breaking|25| | ||
- | |We want the FuMP! Gotta have that FuMP!|25| | ||
- | |Most Anticipated Games of 2009/ | ||
- | |Life as a Math Post-doc: Theoretical Algebra on Parade|25| | ||
- | |Intro to RSS|24| | ||
- | |Best and Worst Games of 2008/ | ||
- | |PC VS Console Gaming|24| | ||
- | |Power Salad Concert|24| | ||
- | |FreeSpace Wrap-Up|24| | ||
- | |We Can't All Be Penny Arcade But That Doesn' | ||
- | |Sci-Fi /Fantasy - What Really Works?|23| | ||
- | |CSS Makeover|23| | ||
- | |Neural Networks for the Non-Technical: | ||
- | |Allergies|22| | ||
- | |Cooking With Aegis|22| | ||
- | |Paint and Take|21| | ||
- | |Sci-Fi/ | ||
- | |The King o' Drinks|21| | ||
- | |Social Networking Meet and Greet|20| | ||
- | |Current and Future Exploration of Mars|20| | ||
- | |Sustainable Computing|20| | ||
- | |Implications of Cutting Edge Microbiology|20| | ||
- | |How To Build A Universe That Doesn' | ||
- | |The Death of Retro Gaming|20| | ||
- | |PXE: It's Not Just for Servers Anymore!|20| | ||
- | |Junkpile Wars|20| | ||
- | |Finding Your Voice|20| | ||
- | |Introduction to OpenBSD|20| | ||
- | |Basic Class|20| | ||
- | |Webcomics~ It Takes a Village (Or Does It)?|20| | ||
- | |The New Who Review|19| | ||
- | |Frank Hayes in Concert|19| | ||
- | |Self-Publishing - How to Not Get Totally Screwed|19| | ||
- | |FreeSpace Launch|18| | ||
- | |Soggy Potato Chips Concert|18| | ||
- | |Tonks and the Aurors Concert|18| | ||
- | |So You Want to Quit Your Day Job?|18| | ||
- | |Costumer' | ||
- | |Faking the Pinup Girl Look|18| | ||
- | |Whose Con Is It Anyway?? | ||
- | |Making Fiction Work In Audio|17| | ||
- | |Build a New Language Compiler from Scratch on Parrot|17| | ||
- | |Johnny Can't Read and Nobody Thinks It's a Problem|17| | ||
- | |Henna Painting Workshop|17| | ||
- | |Copywhat? Copyrights! Open Source Licensing in Literature|17| | ||
- | |Multi-Threaded C++ Development|17| | ||
- | |Selling Your Soul - Marketing Your Work on a Limited Budget|17| | ||
- | |How I Learned To Stop Worrying And Love Rails|17| | ||
- | |Why Nuclear Needs to Be the Cool Thing to Do|16| | ||
- | |So a Robot~ a Martian and a Zombie Walk into a Bar|16| | ||
- | |Why is Free Software Like a Player Piano?|16| | ||
- | |Beltaine Ritual|15| | ||
- | |How AFS Changed & How You Can Use It Today|15| | ||
- | |Knife/Open Fighting|15| | ||
- | |Telling The Story One Page At A Time|15| | ||
- | |Collateral Damage|15| | ||
- | |Wallflower|15| | ||
- | |Holding Out for a Hiro - Sci-fi Goes Mainstream|15| | ||
- | |Gothic Belly Dance|15| | ||
- | |Monty Python Fluxx|15| | ||
- | |Who Wants To Do Something Stupid? Tactics In MMORPGs|15| | ||
- | |Flirting for Geeks|15| | ||
- | |Mixers and Shakers~ Cocktails 101|15| | ||
- | |Rhythm Game Madness!|15| | ||
- | |Fun Theory|14| | ||
- | |How NOT to Create a Webcomic|14| | ||
- | |Herbology 101|14| | ||
- | |Heuristics and Biases~ The New Science of Human Error|14| | ||
- | |Introduction to Massage~ Opening of Wellness Station|13| | ||
- | |Red Garden|13| | ||
- | |D. Gray-Man|13| | ||
- | |Intro to CSS|13| | ||
- | |Telling The Story In Three To Four Panels|13| | ||
- | |Rave Like A Sword Fighter|13| | ||
- | |Zombie Fluxx|13| | ||
- | |Taking Over the World with Penguins and Free Beer|13| | ||
- | |Coloring with Photoshop|13| | ||
- | |Maximizing Fun Per Pixel|13| | ||
- | |Maddog' | ||
- | |Crossplay - Cosplay Without Boundaries|12| | ||
- | |Basic Ubuntu Bug Triage|12| | ||
- | |Hack your World -> Who Needs An EV1 When You Can Build Your Own?|12| | ||
- | |Future Crash - What If We Lose the Knowledge? | ||
- | |Conjure Up a Costume|12| | ||
- | |Introduction to Open Soda|12| | ||
- | |L2P L4D|11| | ||
- | |Midnight Mind Merge|11| | ||
- | |Mental Health Crisis Intervention|11| | ||
- | |You Put My Bike Where??? | ||
- | |The Girl Who Leapt Through Time|11| | ||
- | |Fedora and Red Hat|11| | ||
- | |Paint and Take|11| | ||
- | |Q and A with Doug Houseman for All of Your Eco Needs|11| | ||
- | |sqlpython: SQL Is Fun Again|10| | ||
- | |Short Stories : What's the Story?|10| | ||
- | |Care of the Chronically Mentally Ill|10| | ||
- | |Beast King Go-Lion|10| | ||
- | |PHP and Open APIs|10| | ||
- | |Fully General Criticisms of Religion|10| | ||
- | |Perverted Poetry|10| | ||
- | |How to Give an Effective Reading|10| | ||
- | |High Performance PHP|10| | ||
- | |Designing Solutions from Business Workflows|10| | ||
- | |Demo of ConCentric: Open Source Con Scheduling|10| | ||
- | |Reaching for Immortality|10| | ||
- | |Ogre|9| | ||
- | |Introduction to Masquerade|9| | ||
- | |Sen-So|9| | ||
- | |The Brown Liquors|9| | ||
- | |Lojban Practice (rapcreze' | ||
- | |Lojban All Night la .lojban. cabna pi ro le nicte|8| | ||
- | |The Red Pill: the Truth about Self-Unemployment|8| | ||
- | |Sci-Fi/ | ||
- | |Goth Bunny Play Time|8| | ||
- | |You Are What You Eat|8| | ||
- | |Podcasting Gear|8| | ||
- | |Emma|8| | ||
- | |Savvy With Singers - HandMade Detroit|8| | ||
- | |Penguicon Tech Conference Panel|8| | ||
- | |501st Meet and Greet TBD|8| | ||
- | |Vampire: The Requiem|8| | ||
- | |Dancing with Wolves - And Vamps!|8| | ||
- | |Goth Bunny Play Time|8| | ||
- | |Book View Cafe|8| | ||
- | |Is Audio the New Print?|8| | ||
- | |Catan: Germany|8| | ||
- | |Computer History|8| | ||
- | |Costuming Feedback and 2010 Brainstorming|8| | ||
- | |Munchkin|7| | ||
- | |Settlers of Catan|7| | ||
- | |Gunbuster the Movie|7| | ||
- | |Writer' | ||
- | |Webcomics: Moving Beyond The Strip|7| | ||
- | |Composting 101|7| | ||
- | |Smithee Awards Ceremony|7| | ||
- | |Lojban~ the Logical Language la .lojban. no'u le logji bangu|7| | ||
- | |Writer' | ||
- | |Rule-Based Programming in Interactive Fiction|7| | ||
- | |Reducing Your Energy Bill While Greening the Environment (On the Cheap)|7| | ||
- | |Iron Age Comics VS The Care Bears|6| | ||
- | |What the he77 is Cosplay?|6| | ||
- | |Mystery Spatula Theater 11 Q&A Session|6| | ||
- | |How To Throw a Room Party|6| | ||
- | |Family Business|6| | ||
- | |Disparities in Mental Health Care|6| | ||
- | |Tytania|6| | ||
- | |Gangster|5| | ||
- | |Vampire: The Requiem|5| | ||
- | |Swag Swap|5| | ||
- | |Getting Your Break on the Embedded Screen|5| | ||
- | |Console Wars!|5| | ||
- | |Creating a Wikinomic Online Community|5| | ||
- | |Lojban All Night|5| | ||
- | |Bleach: Memories of Nobody|5| | ||
- | |We Didn't Playtest This At All|4| | ||
- | |Eco-what? | ||
- | |ComicPress|4| | ||
- | |Arkham Horror and Every Expansion|4| | ||
- | |Speed Dating|4| | ||
- | |Getting Paid for Complaining|4| | ||
- | |Iron Age Comics VS The Care Bears|4| | ||
- | |Legal Issues and Podcasting|4| | ||
- | |Glam Makeup Demo/ | ||
- | |Chronic Illness|4| | ||
- | |Keysigning III|3| | ||
- | |Lucky Star|3| | ||
- | |Watching the Watchmen - Comic Movies on the Silver Screen|3| | ||
- | |Paint and Take|3| | ||
- | |Water~ the Real Meaning of Life|3| | ||
- | |What Michigan Can Do (and You Too) to Create a Green Energy Manufacturing Economy|3| | ||
- | |Zero' | ||
- | |National Novel Writing Month|3| | ||
- | |Jenny Everywhere: The Open-Source Comic Character|3| | ||
- | |Rapidly-Scalable Nuclear-Wind Replacement System for Our Current Coal/Gas Generation|3| | ||
- | |SFOHA Open Board Meeting|3| | ||
- | |Beyond the Supernatural~ 2nd edition|2| | ||
- | |Costuming Making with Hot Glue and Sequins|2| | ||
- | |Gurren Lagann|2| | ||
- | |Desktop Fabricator Demos and Q&A|2| | ||
- | |Carrie Dahlby Concert|2| | ||
- | |Locavores Unite!|2| | ||
- | |Devil of a Belly Dance Workout|2| | ||
- | |What Is Lurking in Your House?|1| | ||
- | |Dreadfall Basics and Workshop|0| | ||
- | |Ouran High School Host Club|0| | ||
- | |Lord of the Fries|0| | ||
- | |Noir - Mutants and Masterminds - Save the Child|0| | ||
- | |Wellness Station - Relax~ Rejuvenate~ Refuel|| | ||
- | |Free Space|| | ||
- | |Introduction to LN2 Ice Cream|| | ||
- | |Schmoozing 101!|| | ||
- | |Sustainability: | ||
- | |Exploring Mind Matter Interactions: | ||
programmingops.1252178297.txt.gz · Last modified: 2017/01/14 14:24 (external edit)