Day 1 - Monday

• Overview, logistics, events
  • State of the School: http://creativecommons.org/weblog/entry/33041
• Setting individual and group goals for 10 days
  • set concrete benchmarks, eg. 6 courses by end of residency to be featured on SoO landing page: https://p2pu.org/en/schools/school-of-open/
  • prioritize what benefits having all of us in same space
  • individual focus areas: academia, open.michigan, open data - eg. core skills and competencies
• Skills map, eg. http://blog.okfn.org/2012/06/14/laying-foundations-for-the-school-of-data/
  • initial target sectors/areas/domains
  • secondary target areas
  • think about pipeline - learning about, applying, etc. 
• End of day blog post

Day 2 - Tuesday

• Review
• Skills map (cont'd)
• Align individual focus areas to skills map
• Draft description (aims for School of Open)
• End of day blog post

Day 3 - Wednesday

• Review
• Draft desc - send to initial partners & affiliates for feedback
• discuss and brainstorm community outreach
  • re digital sprint
  • individual interests (academia, open.michigan, cc)
  • affiliates
  • open sectors
  • overlap with other schools, eg. School of Data's open data track
• online media presence
  • social media: #schoolofopen, @schoolofopen taken
  • mailing lists
  • website/landing page, about info page (schools)
• Discuss and create (online) courses
  • use (current) challenges feature: https://p2pu.org/en/groups/make-a-course/, http://pad.p2pu.org/p/Open_Courses
    • meeting w/Vanessa
  • identify (and create) static resources that can be linked to/ integrated
  • open courses/anything brainstorm
    • low-hanging fruit
• End of day blog post

Day 4 - Thursday

• Review
• Create (online) courses (con'td)
• Write / Create -> About content / explanatory resources
  • info.p2pu.org about page
  • half-pager
  • slides
  • talking points
• End of day blog post

Day 5 - Friday

• Review
• Explanatory resources (cont'd)
• Create courses (cont'd)
• End of day blog post

Day 6 - Monday

• Review
• Digital sprint prep
• Feedback on other events
  • plan and run 26 july evening hackathon
  • saturday chloe event (school of open participates informally, maybe a 30 min group activity)
  • get feedback on agenda for open policy institute / school of open meeting
• Revisit skills map for badges/certification
  • survey existing badges, decide which to leverage: https://p2pu.org/en/badges/, map badges/certification to skills map
  • discuss who does assessment (validates learning)
    • badges for free / fee?
  • discuss/find partners/endorsers for badges and challenges - for example,  Open.Michigan holds a number of workshops and one-on-one sessions with  our community to help them learn to do these activities; we'd be happy   to endorse badges from the School of Open and display them on our site   when our community earns them
• End of day blog post

Day 7 - Tuesday

• Review
• Badges (cont'd)
• Digital sprint prep
• Open Challenges Virtual Sprint @2-5pm
• End of day blog post

Day 8 - Wednesday

• Review
• Head over cowork at Mozilla offices: http://www.josettihoefe.de/
• design and plan offline formats
  • create a workshop toolkit
    • include different formats
      • full workshops
      • lightweight group activities
  • testdrive workshop toolkit at 26 july event
• Individual focus areas
• End of day blog post

Day 9 - Thursday

• Review
• Individual focus areas
• Workshop prep
• Open Challenges Workshop @4-7pm: https://donate.mozilla.org/page/event/detail/hackjam/w5c
• End of day blog post

Day 10 - Friday LAST DAY

• Review
• Badges (cont'd)
• Explanatory resources (cont'd)
• Create courses (cont'd) / Individual focus areas
• Wrap-up and next steps!
• End of day blog post