On Mon, Aug 16, 2010 at 07:59:27PM -0400, Charles Profitt wrote: > Hello all: > > I recently got news that I have been approved for an eight hour hands-on > session > at NYSCATE. I will be 'introducing' FOSS to K-12 educators and though I have > a > rough draft of what I want to do I thought I would ask for ideas and > resources > from the community. This could be as simple as success stories about using an > application to specific lesson plans that utilize FOSS. > > As I get further along with planning I will look for feedback to adjust the > plan > and when the final product is done I will publish it under creative commons.
To thoughts jumped to mind: 1. Can we get them to learn abou teaching open source participation in that timeframe? 2. Mel said to me before we talked at OSCON, "When I have a room with people for a period of time, I like to put them to work!" (Paraphrased.) In other words, active learners probably learn more than passive, so if we get them doing _something_ it probably means more of them will get our theses. Speaking of theses, what are yours? I presume you want to go beyond teaching them _about_ open source and in to learning something while experiencing something about participation? Some ideas: * Live edit a wiki page in a way that is a real contribution, that draws on the experience and knowledge of those in the room. For example, give them an exercise, and when completed, edit a wiki page to input the content. If possible, make it Wikipedia; if not, use a teachingopensource.org page about the NYSCATE event (for example.) * Mel had a game she described once that I'll paraphrase as, "Use a bunch of cloth scraps and safety to construct smaller sections in small teams, then larger 'quilts' by connecting cloth scraps together. Teaches small group collaboration on choices (order v. chaos, sort by color or size, etc.), then participation with a larger group on merging the smaller changes to a greater whole. A reverse idea is to start with a big pattern in scraps and cut it up for "improvement". Returning a section untouched is legitimate (code or content review), but safety pins are there to "fix" the design and submit it back for review by the whole group (a table in the middle.) Etc." - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41
pgpxQO3BIjAPC.pgp
Description: PGP signature
_______________________________________________ tos mailing list [email protected] http://teachingopensource.org/mailman/listinfo/tos
