Apprenticeship Onboarding: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
Line 6: Line 6:
*Learning how to ask good, important questions - as then out come good, important answers.
*Learning how to ask good, important questions - as then out come good, important answers.
*Understanding the meaning of ''working on stupid shit'' vs solving pressing world issues as a matter of consciousness expansion, not essential capacity expansion
*Understanding the meaning of ''working on stupid shit'' vs solving pressing world issues as a matter of consciousness expansion, not essential capacity expansion
=Collaborative Transcendence=
*Recommend new Fellows
*Propose Invited Guests to the Enterprise Sessions


=Tech Goals=
=Tech Goals=

Revision as of 22:29, 17 June 2021

Development

  • Critical start is Core Development Method
  • The second part is all participants reaching out to their top 3 potential contacts. Do this on Global Collaboration Days. The point is that everyone of us probably has someone willing to join because we joined - and make them an irresistable offer. Is this a faulty assumption?
  • How do we all collaboraton on Solving for People Showing Up
  • Learning how to ask good, important questions - as then out come good, important answers.
  • Understanding the meaning of working on stupid shit vs solving pressing world issues as a matter of consciousness expansion, not essential capacity expansion

Collaborative Transcendence

  • Recommend new Fellows
  • Propose Invited Guests to the Enterprise Sessions

Tech Goals

  • MMOG for SEH 2 build practice. HiFi, real parts make it useful. Collaborative aspect makes it more so.
  • FreeCAD Workbenches - guest presentation by G

OSE Design Principles

  • We follow and continuously evolve the OSE Design Principles. This is participatory and iterative - and builds on the OSE Specifications. Remember that the end goal of OSE is evolution and transformation via collaborative design, with specific tactics such as Extreme Manufacturing and Extreme Enterprise.
  • Always transcend by assuming unlimited potential for collaboration. For example, why Unreal AND Godot? Because if we collaborate, we can do both, and each has its place. It's inclusive to include better solutions while developign open source solutions.