We're a bit over a week away from the TOS symposium (unconference!) at SIGCSE

First: I know we have a lot more people coming than the list on http://teachingopensource.org/index.php/SIGCSE_2012/TOS_symposium#Who.27s_coming indicates -- if you're registering, either edit the page to add your name, or email me and I'll add it for you.

Second: the event is going to be unconference-style -- don't worry, we'll explain this at the start the event itself (it's much easier to explain in person). If you want a preview of what you'll be in for, see http://teachingopensource.org/index.php/SIGCSE_2012/TOS_symposium#Resources -- the general idea is that in most conferences, the "hallway track" has way more interesting conversations than the "sage on the stage" presentations do -- so why not try to facilitate a lot of hallway-track style interactions?

What this means in practice is that people come in with questions, thoughts, projects, materials, etc, and then we go around the room doing a rapid-fire pitch of our ideas at the start of the day, then take some time to group common interests into session slots (so 3 people interested in sharing various "FOSS for the humanities" ideas might share a session, and 2 people presenting on capstone classes may share a session -- and that is how the schedule's built). Think of a jazz jam session translated into conference format and you'll mostly have it.

Third: Because it is unconference style, it's good to start thinking about session topics you'd like to see now. Check out the current ideas on http://teachingopensource.org/index.php/SIGCSE_2012/TOS_symposium#Proposed_Sessions -- I know there are more things people are thinking of, so put them on the page, toss them out on this list, and let's see what we can do. ;-)

Questions? Holler here!

--
Mel Chua
[email protected]
PhD student, Open Source & Education focus
Purdue University, Dept. of Engineering Education
_______________________________________________
tos mailing list
[email protected]
http://lists.teachingopensource.org/mailman/listinfo/tos

Reply via email to