1 of 13

Agenda - 9 AM-5 PM Work Session

Strategy of OSE - Roadmap, Critical Path

Strategy Handbook - how do you do OS R&D
What is importance of user onboarding flow. Is a Workshop a place to build capacity?

Governance

OSE Governance
Decision making process - part of Holacracy

A way to distribute decision-making so decisions are made faster

Schedule

Decide and/or Schedule a public event

Documentation of last build
Onboarding Process

SMEs, Dev Team

Catarina’s Role

2 of 13

Strategy

Statement of Strategy:

“Create livelihoods to support full-time researchers even at the cost of not supporting those building OSE part-time.”

Information:

3 people doing 10 hrs / wk for OSE devs
Bc it takes too long to do too many things
Other attempts:

“Microtasks” -- failed. Too long to document
Jimmy Lin’s Rare Genomics Institute - medical cancer “selective recruitment” process (Ted Talk)

By setting boundaries high
You get better contributors
Has an HR team that interviews ppl

Design Challenges

Product Ecologies
Part-timer contributions
Alignment risk: OSE spec -- design principles that contradict current methodology folks

Product ecology -- use common parts. For simplicity. Etc. to simplify design pattern. Set must fit into 40 ft shipping container, compact & minimal.

Example: an OSE dev who didn’t want to use universal axis system for a new product.

Strategy considerations:

Family or village?

Village: makes sense bc best use of resources (find community first, that buys land next to each other, or we act as real estate developers, then sell it)
Family: deals with the way things are right now. (that way, deal with only 1 unit at a time): they would only get a homestead, but not necessarily extract aluminum from soil
Community-specific Revenue-generated Context:

Microfactory: 400 sqm^2
Desktop Microfactory

Minifactory --

OSE is an educational program. For sharing tools. The 3d printer workshop is just the beginning. Set in context of a larger module set. Which leads to CAD workshops or extended 3d printer workshops. There is a sequencing of workshops for ongoing revenue.
Selection of things you bild should only be $1billion dollar industries.

We train movement entrepreneurs. Physical hardware is the core of that. Contrast to corporate governance -- legalized murder, LLC -- the big elephant.

3 of 13

Learning from Software

Concurrent Development - social and technical at same time

Social infrastructure was lacking in immersion camp
There can be balanced development, to support folks, bc the technical will look way better when ppl feel good about it

Unfortunate: when there’s scarcity of resources, then ppl get turned around:

Kyle didn’t have bed sheets
Alex didn’t know about dryer

Just have an orientation or some other “basics”
Have a social system that people can use to organize
Flipping the structure: have fellows come first, and then the public folks come in next time.

Hablab User Manual

Transporting Model to India

Michigan Tech University Curriculum
Ask TED Fellow Friends, and folks
Design Constraints:

1 acre land. Land scarcity.

Benign Dictator for Life.

Linux got funded in 3-4 years bc there was a huge pain point. And it was modular. They had Leuitanants. They are “technical lead by merit.” But it’s just coding. Doesn’t have complexity of a design process.
“The success of open source” - book on the rise of Linux

1000 Campuses

“Don’t go to college. Go to OSE.”

Musts: OSE Spec, product ecology, and the goals.
People will not …?
Don’t start from scratch. A CNC torch table w/ a plasma torch. Not OSE spec.
Icluding integrated human training.

Future Talk

Marcin says that by 2028, he will become a full human.
Health, Self-esteem, Economics, Education,

4 of 13

Strategy

Other strategies:

Build a college campus to demonstrate “how it works”
Liberation is making it so that you don’t need jobs.
Strategy constraints:

Regulations of the city
Cost of land
Folks who do work
(land is $2000 / acre)

Vertical planters - Alex’s idea

Profit idea - but, requires significant R&D at this time
Selling 3D printers is an untested hypothesis
OSE sells tools
Vertical planters - here’s a community and a benefit

5 of 13

On Open Source + Product Strategy

Interest Returns Theory of Change

Make a quality 3d printer

Open Source Question

What if ppl steal our resources?

1. “I don’t care if ppl rip me off”
2. “We want ppl to rip me off” (this will change the world)
3. Our livelihood are fine -- we are one-step ahead.
4. Ppl respect creators:
5. brand appreciation
6. Education differs from Google: education vs. product -- not copyable
7. Ethical higher ground

Business model: constant innovation.

He puts out a product out every 6 weeks.
We are always ahead of the competition.
Intellectual property is artificial scarcity.

Trademark

Yes, it’s your name. Require your attribution.
OSE label or logo… icon is a sub
Fake from real:

Managing Kits

Charge folks for

Product Strategy

Current Strategies:

Extreme manufacturing workshop
2-day teacher training (for credit)

Upcoming Strategies

Simple Kits: sell on Amazon. Markup on manual. Tech support. Get a USB stick. Automate that. Printed version (amazon on demand).
Remote Workshop - good revenue stream, less $$ than regular workshop. Finish in “5 hours.” Ask them to pre-build, etc. “Guaranteed Results” w/ pre-tested. Require multiple ppl to work on it together.

Other Strategies:

Incentive Challenges -- fundraise from companies based on product challenges

6 of 13

On Supply Chain

Dixon’s suggestion

Concerns:

supply chain variability:

this needs to be nailed
same issue with kits
solution: supply chain is part of product.
stable build - backlog of parts
parts per workshop - nah
6 months worth of workshop
slice workshop timewise...
drop ship whoever is teaching the workshops…
OR form partnership with manufacturer... there can still be issues.
problem: upfront capital. sucks to have inventory.

Classic issue:

Open source hardware ALWAYS run into variability issues. Can’t get it domestically.

Technological Recursion:

Later, this will be developed by us, not outside.

BULK

Nooooo
They will jumble shitty parts into it.

Other things

Have a jig to test most expensive components
Marcin will do sourcing and drop shipping.

7 of 13

6 Layers of Documentation

Interface - how part relates to other parts
Functional Knowledge - inner interface, how it works itself ex bed - film + wires, + copper clad board
Instructional - how it works. Layered - so full details vs digest procedure.
Troubleshooting - Refinement of Instructions - longer than the 3rd section
Completed Checklist- how do you check that it's successfully built. Prevents frustration
Design Considerations - how could it be made differently. Give people the toolset to be a developer. Trade-offs and choices.

More:

Parts list, tool list
Decision making principles for how to build
Individual Hardware Handling Heuristics:

Don’t blame yourself
Find the right tool, even if you have to wait.
Measure twice, then cut.
Ask someone after working on XYZ for 5-10 minutes.
Pair building?

Workshop Orientation:

Emphasize that we will do your change next build, not this build

Building Principles:

Good, Cheap, Fast, Scalability

Psychology - ask for help, don’t blame yourself, right to fail

8 of 13

OSE Governance

See wiki on OSE Governance
BDFL - under direction of Marcin
The lower cost is achieved by open source (10x cost reduction), lifetime design (10x lower cost), and Modularity/Product Ecologies (10x).

Key Links for Governance

Fun talk

Start 8pm walks. To the lake. Dammed. Resorvior for town. Maysville. They switch to city water.

Buy it. Build developer community there.
Labs. Boat.
No building codes in this county. In Missouri. 30 counties: "pockets of freedom"
Seed Eco-home:
Cost: $2-3 million.

Side note:

Crypto folks miss the “material reality” for setting up “Life after Google”

Collaborators

Toolset?

Grinder, cordless drill, etc.

9 of 13

Holacracy

Schedule:

Week 2: document everything about the build

pull in the things from the wiki
#1 thing: portray what we have to do: words & pics
Nothing fancy
Do the 6 layer treatment of the manual
There’s 8-10 modules
Start with errors that we missed. (Get the confidence up) List all the things that went wrong. (They are finite! We can solve them!) [this document is available on Marcin’s Log: xyz quality control]
Use Instructional Template as a start
2-3 days of documentation, then prep parts of exisitng printers, do a build: bring computers. Do it at hab lab or here, then fill in gaps in the manual.
Overview: get printers up and running to producing parts such that printing parts for next 3d printers.
Troubleshooting is included in the manual.
After

Other Notes:

Shredder: precious plastic build.

Lyman-based extruder.

Regular training meetings: will orient folks re: research skills, rather than doing that right now.

Daily Schedule:

meet 9-5
Could ask dev team to help?
Host a remote design sprint, to clean up the sprint

Bhakti: i want to learn more from Marcin.

When does sourcing work occur? Who does it?

Logistics, organization, lesson plan, dealing with the public, folks being drunk, extreme design jams

1st 2 weeks:

Vet that they work w/ a production fluster.

Week 1, 2, 3…

After that… decide on things.

What’s the approach to documenting?

Alex:

1st build: (monday)

1 printer… 1 module at a time.
Everyone documents.
Pull together from what exists on the wiki.

Documentation lowers morale: it’s hard, boring (highest value).
Team A & Team B… divide into teams. Lay out the responsibilities. Review anything.
Get a morale boost from only following instructions in order to build it.
Copy and paste into the 6 layer format.
Divide by module interfaces. THEN do
We can skip steps 1 & 2 outside the build. We write the instructionals together. Do troubleshooting after the build.
6-8 modules:

10 of 13

Schedule

Week 3: Production Cluster

Producing parts.
2nd and 3rd printers are SINGLE DAY BUILDS.
Cluster: develop redundancy on printing parts for a workshop

Week 4: Filament Maker & Shredder & Circuit Mill & Laser:

Each takes 1-2 days to build.(8 days to build)
Ideally build 4 of these
? -- how much time spent on filament maker, shredder, laser cutter | vs | going out into public w/ marketing and stuff.

Week 5: Public or Private Workshop w/ Eval

1-2 days where 2 folks build theirs on 1 day, and 2 in other days, in-house or on-the-road

Priorities:

Run workshops successfully as revenue stream
Perfect ability to build filament maker

Make a list of priorities?

11 of 13

Holacracy + Schedule

Tactical Meeting

Metrics for whether something works

Governance Process -

Governance meeting - when we decide things

Governance

OSE Governance
Decision making process - part of Holacracy

A way to distribute decision-making so decisions are made faster

Governance Process:

* Vote: 5, 5, 5, 5, 5, 4, 4

* alex to put decision-making process into OSE wiki

12 of 13

Documentation - See Former Work and D3D

Instructionals Template - reuse this
Modules: (there should be docuentation layers (at least) 1, 2, 3, and probably 6 to help orient new folks.
Frame
Axis: X, Y, Z
Heated Bed
End-stops
Extruder
Electronics
Cable Routing
Final Assembly

9 AM

Rian - video

Agenda:

Schedule -- Wed at 9am Governance

Come to discussion ready for what they need. Especially independent collaborators.

Documentation Steps:

Marcin goes through modules. 4 folks document.

Documentation Process:

Brute Force Step 1: document together initial talk together
Picture Role: Upload onto FB, then pull from it, and label it on the doc. Also, create diagrams, concept drawings, and doing that in google docs.
Brute Force Step 2: after a break, synthesize the layers together and ask any extra questions. (by making a duplicate and trashing the doc)
Use a google Slide, File=>Custom=> 8.5x11in.
5,5,5,4,4,5

Template