Teaching Module Requirements for STEAM Camps

From Open Source Ecology
Jump to: navigation, search


The goal of 12x12 is to create - specifically - an open source product development methodology - in addition to the skills building and hardware access of participants.

STEAM Camp curriculum can be broken into small modules for MOOCs.

Curriculum can also be integrated with the Open Source Everything Store (OSES) - which means that the kit involved in the curriculum can be a viable product, or the actaul MOOC can be a product in the Open Source Everything Store.

OSES can be templated with a beautiful template on the OSE wiki.

Critical elements to think about when designing curriculum/MOOCs: Modular, scalable, product ecology, lean.

  1. Modular - Means manageable, and high quality. Think of creating *the goto lesson* on any topic - branded as Rapid Learning for Rapid Learners. That is elitist, but ok. There are other courses for slower learners. Thus, we are filtering high performers into the organization. Small bites, allow a person to contribute 4 hours to create a 1 minute course. This can be a basic requirement for a microcontribution.
  2. Scalable - means easy derivation of applications to industrial productivity on a small scale - meaning distributed, open source, efficient production. So, for example a minimalist arduino that can be put on a 3D printed circuit board made of plastic with holes - that can be wired together for a real application of pressing bricks in the brack press. The minimalist arduino (rather than building a full one) made this possible: direct application to industrial productivity on a small scale. But another aspect of 'scalable' is transformation, by not concentrating wealth
  3. Product Ecology - part of the greater OSE Context. Open Source Everything Store. Also using other OSE tools, such as Kdenlive and FreeCAD and OSE Linux. Product Ecology also refers to the Enterprise Construction Set Approach - we develop building blocks for free, and users/devs can use these to make Mass Creation of Right Livelihood feasible. For example, MOOC modules are free. But someone can create an online STEAM Camp from these free elements, where elements such as the kit sourcing is facilitated. So we don't have to worry about how to divide up revenue: each agent can do their own enterprise if they like for max economic freedom, or they can cooperate with others. The revenue model of OSE revolves around creating further access to the building blocks of enterprise of any kind.
  4. Lean - enterprise is self-managing. It is Automated - so does not require staff such as accounting.

As such we are hinting at economic significance of the MOOC product - and of the kit involved - and of the industrial application of what we are doing.

Question: how do we motivate 10-100 of people to collaborate on open source content for the STEAM Camp?

Braindump of STEAM Camp Teaching Module Elements - for a Wiki Template

  1. Lesson - formal 1 hour lesson. Detailed schedule. Learning objectives - esp application to industrial productivity on a small scale. Standards met - what school, high school, or other standards this content meets, so this could be used to construct a degree/certification.
  2. Hardware BOM - BOM of parts required for the experiment. See How to Make a BOM
  3. Pre-requisites - List of lessons needed to have been completed before this lesson.
  4. Hardware picture
  5. Hardware - embeddable 3D view that can be rotated
  6. Maybe keep it to 2 minutes. Make video modules if longer lesson is required. Maybe do an intro video that explains perspective, such as why we are building this, and how it relates to IPOSS (Industrial Productivity On a Small Scale)
  7. Product specification and requirements - crystal clear explanation of scope and what this is supposed to do
  8. Diagram of How It Works - embedded Google Slides
  9. Kit.com or other - 1-click order of parts
  10. PayPal for buying lesson. DIY lesson - one that you do by yourself. Prerecorded. DIT - the webinar version - which has actual live participation and Q&A possibility.
  11. PDF - full downloadable version if someone wants to print it out.
  12. Part Library - all components for that lesson in FreeCAD format
  13. Blender - assembly animation
  14. 3D Print files - for components that one can produce oneself for the build
  15. Scalability experiment - instructions for how to scale the experiment in an interesting way for industrial applications. A homework assignment for doing this for real, or a throught experiment.
  16. Modularity Experiment - practical or thought exercise on how to make this work with other modules
  17. Grading / test - get evaluated on your understanding, towards a badge, certification, or degree. This may be self executing, automated, or manually done by others, or mutually-done with other course students.
  18. Discussion - can be Discourse or Hackernews platform - for discussion
  19. Cheatsheet - a single page that can be followed by a teacher when teaching this class, to make this easy for the teacher.
  20. Language-Agnostic Instructional - inter-language communication of the experiment. Instructions for the experiment without using words, just pictures
  21. Badge - a skills badge that you can post on your work log. Includes Badge source code for editability.
  22. Review - how many starts this lesson gets, evaluated by people who do the lesson.
  23. Webinar product - a variation of the lesson, that can be ordered for pay at a given time and date
  24. Integration with OSES - same product, put into format of OSES.
  25. Product Page on main website - at Productssite.png
  26. Post on OSE Workshops FB Page and OSE Social Media for people to take the course.
  27. Wiki template - for uniformity of OSE lessons
  28. Infobox template for the OSE lesson - for further uniformity of lessons pages
  29. Background reading - background information, videos, etc - to prapare for the lesson
  30. Industrial significance - an explanation that we are true to our brand of applications to solving pressing world issues through ethical entrerpreneurship. Thus, describe clearly how does this project apply to OSPD, OSES, Microfactories in every town.
  31. KiCad file source
  32. Design Workbench in FreeCAD - buttons in FreeCAD where you drag and drop parts automatically into a working doc - for redesign - and more FreeCAD practice.
  33. Technical drawing - extracted from FreeCAD
  34. Where this product fits in all of human technology - a map of all technologies, and what this technology includes
  35. Open Source Technology Pattern Language - an iconic representation of the product's main building blocks.
  36. Incentive Challenge - a reward for making an interesting application of the product.