On 08/16/2011 01:03 PM, Sebastian Dziallas wrote:
On Tue, Aug 16, 2011 at 5:20 AM, Heidi Ellis<heidijcel...@gmail.com>  wrote:
Hi Folks,

I've updated the Significance and Relevance of topic. We could use a few
more TOS folks to sign up to talk about their experiences and to demonstrate
that we have a vibrant community! Add yourself to the Discussion Leaders
section.

I've added Karl and Steve to the "Proposers" section and added in positions into "Discussion Leaders" -- if the list grows super-long, we can put the roster on a wiki page, say "X faculty, Y open source community members, Z students <see full list here"> and figure out how much we need to cut the list of proposers to get it to fit on one page.

I tried to do some light text editing to incorporate Steve's suggestions to the abstract, and have *probably* made it too long. It's easier to cut afterwards, anyhow. :)

Regarding students -- most "student" events I've been to involve a lot of talking *at* students, and I'm curious whether that dynamic could be reversed. So, counterproposal: Steve, what would it take to get a 3-4 hour block (an entire morning or an entire afternoon) in a room or block of rooms large enough to fit 4-6 small group discussions at a time? I'm thinking of a barcamp format. Depending on how broad we need to be to capture a sufficient audience, it can either be students-only or student-focus, open source focused or not (but we'd try to get people to put in sessions about FOSS/TOS/etc).

(For those who've never seen a barcamp before, the Wikipedia page is useful, though writing can never truly capture the flavor of it; basically, you start the event with a blank schedule grid, and the first 30 minutes or thereabouts is filled with audience members pitching session ideas and filling in the grid together with topics they want to discuss -- and everyone's expected to help/participate somehow.)

--Mel
_______________________________________________
tos mailing list
tos@teachingopensource.org
http://lists.teachingopensource.org/mailman/listinfo/tos

Reply via email to