Education/Projects/JetpackForLearning/DesignCamp/Agenda/FutureCommunity: Difference between revisions
< Education | Projects | JetpackForLearning | DesignCamp | Agenda
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
'''Group 2''': | '''Group 2''': | ||
- sense of community emerging; 3am hackathon, etc. shared purpose/vision & expertise. shame to lose it | |||
- look at browse as lens to social learning | |||
- what should we do with the course? run it again, become part of a bigger curriculum? what's the future? | |||
- ambassadors: spread the word, get people involved | |||
- connect this community with broader education world | |||
DISCUSSION 1: do you want to collaborate in a community of practice | |||
* yes | |||
* yes | |||
* only as advisor | |||
DISCUSSION 2 (10min): what do you need to get out of the collab to keep motivation above threshold? | |||
* access to expert advice feedback, access to macarthur people | |||
* keeping the list alive, giving feedback, geting coding help and ideas from the list | |||
DISCUSSION 3 (15min): 3 best ideas for collaboration moving fwd and on contest for next year | |||
* the "champion" of the group is the commandante, pilot, navigator | |||
* bring a learning scientist/educator/designer/potential users to the contest and have them give feedback to contestant teams early-on | |||
* connect CS education departments to the courses; make it a lab for a community. if associated with university, might outcast non-academics and older people | |||
* give people the code snippets to get started: now go crazy! twitter, quizlets, overlay, screenshots | |||
* each alumni gets a code and spreads it to get street-cred for others signing up with their code | |||
* pair a contest alumni with new contestant and give some sort acknowledgement | |||
* in the contest call, specify the learning toipcs: deconstruct x, y, z. language, science, math, etc. | |||
* "learning" vs "education" vs "hacking education" | |||
* give challenges about subversive learning topics | |||
* get paired up with a "geek big brother" that could be a former parole officer that cannot leave his laptop | |||
Revision as of 22:26, 12 March 2010
Thoughts on the Future of the Jetpack Community
Group 1:
Group 2: - sense of community emerging; 3am hackathon, etc. shared purpose/vision & expertise. shame to lose it - look at browse as lens to social learning - what should we do with the course? run it again, become part of a bigger curriculum? what's the future? - ambassadors: spread the word, get people involved - connect this community with broader education world
DISCUSSION 1: do you want to collaborate in a community of practice
- yes
- yes
- only as advisor
DISCUSSION 2 (10min): what do you need to get out of the collab to keep motivation above threshold?
- access to expert advice feedback, access to macarthur people
- keeping the list alive, giving feedback, geting coding help and ideas from the list
DISCUSSION 3 (15min): 3 best ideas for collaboration moving fwd and on contest for next year
- the "champion" of the group is the commandante, pilot, navigator
- bring a learning scientist/educator/designer/potential users to the contest and have them give feedback to contestant teams early-on
- connect CS education departments to the courses; make it a lab for a community. if associated with university, might outcast non-academics and older people
- give people the code snippets to get started: now go crazy! twitter, quizlets, overlay, screenshots
- each alumni gets a code and spreads it to get street-cred for others signing up with their code
- pair a contest alumni with new contestant and give some sort acknowledgement
- in the contest call, specify the learning toipcs: deconstruct x, y, z. language, science, math, etc.
- "learning" vs "education" vs "hacking education"
- give challenges about subversive learning topics
- get paired up with a "geek big brother" that could be a former parole officer that cannot leave his laptop
Group 3:
Group 4: