OSE Chapters at Universities

From Open Source Ecology
Revision as of 19:16, 6 March 2020 by Marcin (talk | contribs)
Jump to navigation Jump to search

Video

Meeting - March 6, 2020 - discussing University Chapters

  • How to address community?
    • Collab - start by calling out a collaboration ecology of 12 discipled.

How to Start

  1. Founders - Start with 2 co-founders who get the ball rolling. These individuals must be interested in promoting the OSE Vision, and must have some familiarity with OSE's work based on participating in OSE development work, Extreme Builds, or other educational programs.
  2. Club Formation - Co-Founders approach their respective University student club office to register a club with the university. Club charter is filed, and officers are selected.
  3. OSE Charter - Founders work with OSE to develop a charter, which specifies a year-long critical path for the club. The focus is on creating a collaborative team across disciplines: design, architecture, engineering, enterprise, writing, videography, marketing, documentation, software development, art, publishing, and more. The critical path should revolve either around the particular year's Incentive Challenge - a public, collaborative contest where we develop meaningful products with intent of distributing production - or another project of particular interest to the Chapter. The incentive challenge for 2020 has the Professional Grade, 3D Printed Cordless Drill - intended for creating distributed production of cordless drills (see OSE Incentive Challenge)
  4. Chapter Launch - It would be useful to invite an OSE Ambassador or OSE Founder to the event to stimulate interest. A lecture followed by a 1-2 day collaborative design training course would be ideal.
  5. Resources and Funding - Chapter secures meeting space or working space at the Unviersity. Chapter applies for university student club funding to build up their productive infrastructure, such as a Desktop Microfactory with 3D printers and plastic recycling as a good entry level program for teaching collaborative design while cleaning up the environment.
  6. Operation - Chapter begins development. Typical activities include onboarding with 3 webinars - Intro to OSE and Collaborative Literacy; Intro to OSE's Collaborative Development Protocol; introduction to FreeCAD and part libraries. Chapters coordinate with other chapters for regular Design Sprints, and chapters coordinate a date for a real Extreme Build in a select location during a weekend or school break.
  7. Outcomes - Goal clarity means that we are developing real products collaboratively - whether it's an open source tool, household appliance, a food product, or even a house or car. We are clear that a transition to the open source economy means that we take common products - and rework them to fit a circular economy based on cities producing all that they need. The concept is simple, execution is hard, and implications are significant.

Operational Notes

  1. Willingness to work as a team - OSE Chapters, in order to coordinate on effective development, are designed to collaborate on development with other chapters around the world. This increases development velocity, and allows meaningful results to be obtained on short time periods
  2. Ideally, OSE Chapters meet for an extreme build or other hands-on build event to implement what they have been designing together. This solidifies team connections, and reifies the design work that has been carried out. The printciple here is that together, large-scale projects can be accomplished easily - such as building a microfactory or a school over spring break or over a vacation.