Education/EduCourse/BlueprintExample

This is an example of what an early-stage blueprint idea could look like. It makes use of the Blueprint Template, and provides a rough sketch of the original idea. This is where we'd like projects to be after week 1.

Assuming that this is the starting version that I will work on during the next six weeks of the course, it would change based on what I hear in the seminars and feedback from other participants. After six weeks, I'd like to have the basic technology set-up and ready for use, and some pretty solid ideas on who to involve in the seminars, and how to find participants for the course.

Basics

Short description: An online course for educators to learn about open licensing, open tech, open pedagogy and apply to own projects

Audience: Educators with some background in either of the three core areas of the course, and a concrete project idea.

Goals: Build skills, grow the community, connect Open Education with Mozilla and ccLearn, create a model course for future sessions and also for other Mozilla Education courses

General approach/ What does it look like: It's a mix of synchronous, hour-long web seminars, a discussion list for most of the interaction between participants, and group work on projects.

Technology

Describe the main tools and applications you use as part of the project

• Use one of the many options for synchronous seminars. Most of them are not entirely open. Necessary to investigate which ones are "most" open, and balance against other factors (features, stability, etc.). Webex seems like the most feature-rich and robust solution, but is not open - and expensive to use for others. Limits replication potential.
• Use an open source wiki for hosting of the core content. Hosted by Mozilla.
• Use a hosted mailing list that implements open standards (email, rss) to minimise the administration and tech support needs
• Social bookmarking with diigo (and del.icio.us). Must investigate how to integrate the two.

Content / Licensing

What types of content are you using or producing, and how are they licensed. Do you need to clear copyright for any of them? Are there institutional policies that affect what you can (or cannot) do?

• All materials produced by the course (seminars, wiki) will be CC licensed.
• Live seminars and audio interviews will be made available from the course wiki (or hosted somewhere else and linked to) and tagged with the appropriate licenses
• The basic course wiki uses a CC license.
• No copyright materials are used in a way that would require clearing. It's possible that participants will point each other to content that is available online and not licensed openly, but those materials will not be hosted by the course.
• In the context of Mozillla and ccLearn, the institutional requirements are maximum openness

Pedagogy

How do participants learn? What forms of assessment are you using?

• Live interaction
• Limited potential for apprenticeship / mentorship through exposure and discussion with some of the leading practitioners in the field
• Peer 2 Peer learning, participants review each others' work and comment / support each other
• Participants are encouraged to remix the course while it is happening
• Work in a small core group to create a sense of community and ensure that participants get to know each other

Sketches

This is a rough outline of the overall set-up. Participants engage with each other using a core set of technologies (wiki, bookmarking, etc.). They access resources that live anywhere on the web. There is a flexible line around the community of participants. Others (everyone) can look inside, and see all of the materials produced, but participation is limited for now to the core group.