►
From YouTube: Collaborative Literacy 2021
Description
-----------------
What you see here at Open Source Ecology is an ambitious open source project for the common good. Join our development team:
http://opensourceecology.org/wiki/OSE_Developers
We run One Day Extreme Build workshops in many locations. Please put yourself on our map if you'd like us to host a workshop near you:
https://microfactory.opensourceecology.org/request-a-workshop/
Take a minute to subscribe to our email newsletter (updates, workshops, etc): http://bit.ly/1LtcM44
A
We
could
actually
make
it
better,
better
and
better
build
upon
there's
that
collaborative
core
of
okay,
we're
trying
to
share
the
the
revenue
more
among
the
co-op
cooperative,
but
at
the
end
of
the
day,
it's
still
this
consortium,
a
proprietary
consortium
that
does
not
share
its
design
or
its
economic
know-how
to
exterior
players.
It's
still
the
same
kind
of
competitive
thing,
but
there's
definite
potential
in
it.
A
B
Even
but
I
think
that.
A
The
tools
are
needed
to
be
created
like
specific
efforts,
where
that's
kind
of
like
that
was
the
notion
of
this
summer
of
extreme
design,
build
and
apprenticeship
like
how
we
start
generating
various
assets
that
help
move
that,
along
whatever
structures,
whether
it's
like
taos
or
I
mean
modern
tools
of
modern
economics
or
collaborative
marketing
assets
or
whatever,
based
on
a
very
deliberate
effort
to
to
get
to
the
products.
Products
across
the
board
could
be
anything
specifically
towards
like
making
stuff
better
like.
Why
aren't
all
cars
like
running
on
hydrogen
with
water,
lubricated
engines?
A
That's
a
complete
techno,
technological
feasibility.
In
fact,
there's
a
modern
steam
engine
out
there
that
that
is
water,
lubricated,
high
performance,
state
of
art,
stuff,
and
it's
like,
oh
well,
that
doesn't
pollute,
doesn't
dribble
oil.
It
does.
I
mean
it
still
uses
traditional
fuels,
because
the
hydrogen
economy
is
not
not
here,
but
I
mean
we
could
be
really
knocking
out
problems
like
this
environmentalism
or
resource
depletion
and
stuff
like
that.
A
So
that's
the
higher
call
out,
but
it's
very
difficult
for
somebody
to
see
that
until
they
can
understand
the
raw
power
of
productivity
that
humans
have
developed
and
that
that
that's
that
should
be
made
like
the
central
focus
of
people's
energy
could
be
that
we're
actually
trying
to
share
that
make
it
go
forward
and
bring
everybody
up
across
the
board.
So
it's
a
mindset
issue,
it's
it's
that
would
lead
us
to
yes,
there
could
be
more
people
doing
this
and
creating
those
collaborative
tools.
A
A
So
that's
all
worth
developing
and
it's
a
sad
sad
lack
of
them,
but
I
think
you
know
things
are
coming
out.
Looks
like
things
are
coming
out.
B
A
Ridiculous
amount
of
money-
yeah
I
mean
there,
so
that's
like
fintech
this
that's
financial
innovation,
where
somehow
you're
able
to
incentivize
large
amounts
of
people
to
collaborate.
I
mean
that's
the
kind
of
theme
we've
been
talking
about
all
summer,
like
how
do
you
really
incentivize
a
whole
bunch
of
people?
How
do
you
reward
them?
I
mean
that's
some
real
heavy
thinking
and
an
experience
and
practice
that
has
to
go
into
it.
A
It's
not
somebody
on
wall
street
that
that's
going
to
do
it
you're
going
to
have
to
have
more
motivation
like
and
also
like
a
good
understanding
of
like
what's
possible
through
open
collaboration,
so
yeah
a
lot
of
potential
there
and
once
again,
it's
up
to
us
to
to
create
that.
B
So
I'll
say
just
with
regards
to
the
collaborative
literacy.
So
in
looking
at
the
resources
right.
A
B
So
if,
if
I'm
sitting
here
saying,
I
want
to
be
the
most
effective
osc
collaborator.
C
C
B
The
shop
last
night,
so
I
guess
the
big
question
would
be.
Is
there
a
crash
course?
That's
helpful!
What's
the
most,
what's
the
most
helpful
thing
in
the
next
hour
right
or
is
my
best
bet
to
just
spend
the
time
between
now
and
lunch,
going
through
information
getting
up
to
speed
on
this
and
then
the
afternoon
all
right.
A
A
Rapid
onboarding
of
people
do
collaborative
cad
like
collaborative
cad,
doesn't
really
exist.
The
way
typically
works
is
locking
down
files
we're
trying
to
do
something
different
through
our
workflow,
but
at
the
end
of
the
day,
it's
like
how
do
you
design
something?
So
that's
like
design
lessons,
there's
the
actual
tool
you
design
with
such
as
your
cad
tool.
A
There's?
Where
do
you
put
it?
How
do
you
find
it?
What
are
other
people
doing
in
the
mindset
of
what
we
do
with
osce?
It's
like
think
about
it.
Okay,
long-term
products
across
the
board
for
the
gbcs
still
the
goal
is
2028
is
my
personal
cutoff
for
all
the
gvcs,
like
whatever
technology
we
have
at
that
time.
It's
time
for
applications
like
much
more
focused
on
applications.
A
That
means
enterprise,
replication
or
the
things
that
sprout
from
it,
which
initially
was
what
you
would
call
intentional
communities,
but
I
mean
basically,
basically
an
entrepreneurial
way
to
build
to
rebuild
civilization,
whether
it's
like
it's
a
school
like
right
now.
The
model
for
me
that
I
think
could
work
is
the
the
campus
kind
of
concept
where
it's
like
a
university.
It's
a
mixture
of
and
there's
you
can
read
the
page
called
osce
campus
on
a.
I
think.
A
It's
a
hybrid
of
like
an
entrepreneurial
eco
park,
a
farm,
a
school,
a
business,
but
pretty
much
kind
of
like
what
we
do
here,
but
you
know
more
organized
which
focuses
around
skills,
gaining
skills
and
applying
that
to
enterprise
and
response
responsibility
that
we
take
I.e.
And
how
do
we
use
our
skills
and
economy
to
rebuild?
You
know
to
do
things
that
are
done
today,
but
just
without
hurting
others
and
killing
and
stealing
like
we
do
today
so,
which
is
a
big
call
out.
A
I
think
a
university
campus
like
thing
is
a
well
understood
thing
like
imagine
college,
but
add
to
that.
Like
a
working
farm,
you
got
r
d
that
actually
leads
to
real
products.
So
it's
like
a
slight
tweak
on
the
university
thing
which
that's
kind
of
what
they
do,
except
it
all
gets
privatized
and
to
individual.
C
A
B
That's
pretty
I've
kind
of
come
to
the
same
conclusion.
We're
like
hey.
If
I
was
at
a
university
that
had
and
a
tech
program-
and
I
was
doing
your
research
towards
open
source
development
and
semester
about
semester,
there
were
more.
That's
really
why
I
want
to
know
all
of
this,
because
I
think
in
a
semester's
time
I
can
take
a
new
cohort
of
open
source
collaborators.
A
Right
yeah,
I
mean
imagine
you
do
that
and
then
there's
another
person
like,
for
example,
joshua
pierce
right
now,
who's
in
canada.
Right
now,
he
he
set
up
his
whole
whole
program.
It's
focused.
It's
focused
on
open
development
where
he
now
you
can
get
a
phd
in
open
source
hardware.
A
I
mean
that's
for
you
right
now,
but
imagine
a
whole
bunch
of
people
like
that
who
are
collaborating
and
all
the
info
is
out
there
in
free
formats
like
like
free,
cads
and
open
scads,
and
all
that
they
do
a
lot
of
their
stuff
on
apropedia
and
yeah.
We
collaborate
with
them.
A
That's
who
actually
sent
us
the
pellets
that
we're
using
right
now
for
the
filament
maker,
but
imagine
that
where
yeah
you
do
get
a
cohort
of
people
and
as
long
as
you
can
understand,
okay,
this
is
how
we
document
and
he's
got
a
whole
bunch
of
stuff
on
how
they
do
that,
and
it's
similar
it's
like
wikis
and
open
files
that
you
share
and
builds
the
materials
and
build
instructions,
publishing
papers
that
kind
of
stuff
lots
and
lots
of
papers.
A
They're,
a
good
paper
mill,
yeah
they're
cranking
stuff
out,
and
they
just
applied
for
a
grant
to
get
a
bunch
of
equipment
from
us
like
actually
do
the
tractor,
so
they
could
actually
they.
I
apparently
got
some
experiment
land
for
experimentation
like
an
acre
few
acres
that
they're
actually
working
with
as
part
of
that
the
deal
he
struck
up
with
the
university
so
he's
you
know,
he's
moving
forward
with
the
open
source
hardware,
development
focus,
which
is
really
cool
yeah.
A
That's
the
idea
is
well
base
once
again
kind
of
going
back.
What's
the
operational
model,
what's
the
financial
model
for
that
to
actually
succeed
so
like
take
the
hbc,
you
might
have
okay,
there's
tuition
people,
actually,
students
are
paying
and
if
there's
that
kind
of
direction
that
come
in
and
there's
multiple
entities
that
do
that.
That
can
add
up
to
something
I
mean
the
promise
of
what
patents
used
to
promise,
which
was
oh,
we
can
actually
enhance
innovation
by
publishing
openly
well
patents.
A
Don't
they
give
you
the
concept,
but
a
concept
is
just
one
of
the
very
it's
not
adequate
to
actually
replicate
something,
but
that
was
actually
the
original
intent
that
you're
actually
giving
this
information
to
the
world
in
exchange
for
protection.
A
In
a
little
different
way,
like
you
gotta
somehow
tweak
that
to
say,
oh
we're
actually
sharing
the
enterprise
that
comes
out
of
it.
Well,
that's
distributed
enterprise
concepts,
not
very
popular
yet,
but
I
also
don't
see
that
how
if
problems
are
getting
more
complex,
we've
got
more
technology,
more
ability
to
learn
and
more
powerful,
flexible
fabrication
tools.
This
kind
of
open
collaboration
just
is
inevitable
because
people,
I
think
there
is
definitely
a
lot
of
talk
about
collaborative
development.
A
Maybe
not
people
don't
really
mean
the
same
thing
as
we
do
by
that.
I
even
they're
not
going
to
share
their
enterprise
info,
but
that
notion
is
certainly
well
accepted.
It's
just
pushing
that
to
say,
oh
well,
it
actually
does
mean
that
we
share
and
what
is
the
deepest
form
of
sharing.
It
would
be
well
sharing
in
the
economic
process,
which
is
very
unevenly
shared
today.
B
I
mean
they're
still
calling
it
like
smart
manufacturing
and
agility,
and
you
know
like
there's
a
lot
of
conversations
around
like
oh
cocaine,
supply
chain
instructions,
and
you
know
like
how
do
we
get
more
flexibility
and
resilience
and
agility
out
of
our
manufacturing
days
here
in
the
u.s?
You
know:
how
do
we
get
institution
measurement
in
manufacturing
processors
and
find
platforms
for
sharing
all
of
that
data?
So.
C
B
C
B
A
B
B
Things
they
take
a
long
time.
Everybody
recognizes
that
these
are
problems
and
the
main.
C
B
And
even
the
us
government
are
talking
about
it
and
trying
to
figure
out
how
to
fund
these
sorts
of
things,
but
they
don't
have
the
right
language
or
the
or
they
haven't.
The
people
who
are
involved
in
managing
these
things
have
not
been
exposed
to
the
alternatives
for
them
to
even
realize
that
there
are
other
options
out
there.
Besides
the
way
that
they're
used
to
innovation
taking
place.
So
that's
okay,.
A
Yeah-
and
that
goes
back
to
a
solid
revenue
model
that
we
can
develop,
which
I
right
now
think
is
still
the
cdca
home
and-
and
you
show
that
making
millions
and
say
hey,
we
actually
developed
this
all
collaboratively.
It's
completely
open.
You
can
start
an
enterprise
right
now
make
this
amount
of
money
like
once.
They
see
a
few
examples
like
that.
A
If
you
go
proprietary,
if
you're
collaborating
openly,
you
got
to
close
it
up
to
make
a
lot
of
money
or
like
prusa
printers
right
now,
which
is
awesome
and
open
source,
but
it's
like
they're,
not
they're,
not
trying
to
distribute
their
enterprise
model
or
anything
like
that,
in
fact,
more
towards
the
opposite,
like
away
from
the
open
ethic.
A
Just
like,
I
still
still
trying
to
figure
this
one
out
where
in
one
of
their
videos
they
they
showed
how
they
make
filament
for
their
high
precision
filament,
and
they
had
the
machines.
Actually
blanked
out
for
their
specs,
like
like
proprietary,
like,
oh
I'm,
not
going
to
show
you
like
what
parameters
I'm
using
or
what
machine
I'm
really
using
like
that
kind
of
stuff.
A
A
Okay,
we
gotta
do
this,
you
gotta
show
the
cash
flow
and
at
that
point
becomes
obvious
and-
and
you
have
a
cascade
of
further
development,
just
cascade
of
oh
cool
and
people
actually
see
that
see
the
numbers
and
see
the
data
coming
out
of
that
as
far
as
economic
output
and
and
that's
why
the
essence
here
is
like
industrial
product
of
on
a
small
scale,
the
meeting
or
exceeding
industry
standards.
That's
all
part
of
that
game,
but
we
just
needed
good
examples
and
that
cascade
can
happen.
A
It's
around
the
corner,
it's
it's
close,
but
just
nobody,
cracked
that
yet.
A
B
B
B
A
Right
and
there's
like
sbir
grants
and
things
like
that,
they
I
hear
the
department
of
energy
there's
the
department
of
defense.
B
B
Training
grant
programs
and
all
types
of
other
things
so
like
opportunities
to
say
we
train
people
in
advanced
manufacturing.
You
know
they
visit
oak
ridge,
national
lab
in
oak
ridge.
B
Manufacturing
demonstration
facility
to
mdf
right
and
I've
been
there,
and
you
know
they
got
a
bunch
of
big
full
metal,
3d
printers
doing
3d
printing.
None
of
this
open
hardware,
though.
A
Yeah
yeah
I
mean
I
should
definitely
be
interested
in
talking
there.
That's
there
might
be
some
people
that
are
like.
Oh
wow,
they're,
really,
click.
I
mean
completely
click
with
it.
I
mean
you
find
I
mean,
do
you
find
yourself
in
that
environment?
Some
people
that,
like
pretty
much
completely,
get
it
or
not,
really.
B
A
A
I
actually
find
the
documentation
aspect
to
be
more
important
these
days,
because
having
built
a
bunch
of
stuff,
what
I
noticed
this
is
how
you
evolve.
First,
you
go
out
in
the
workshop,
spend
all
your
time
in
a
workshop,
but
after
a
little
while
he's
saying
man,
if
I
planned
this
a
little
more,
I
didn't
have
wouldn't
have
to
do
that
again
and
then
you
say:
oh
well
now.
A
My
personal
evolution
has
been
now.
I
would
like
to
spend
like
either
10
to
or
100
to
1
ratio
of
design
to
build
that's
kind
of
what
we
implement
through
the
extreme
manufacturing
thing,
we're
going
to
say
we're
going
to
spend
100
days
preparing
for
a
one
day,
build
kind
of
a
thing
and
that's
the
reality.
Once
you
get
the
experience-
and
I
know
that
initially,
just
like
myself,
you
know
thinking
about
the
first.
I
remember
distinctly
the
old
workshop,
some
of
the
earliest
power
cubes.
A
A
Because
it's
it's
really
hard
work?
It's
it's
really
hard
work,
so
you
get
the
prototype,
but
a
prototype
is
a
prototype
and
you
need
to
go
through
dozens
of
them.
With
the
metaphor
to
software
being
that
I
mean
how
think
about
how
many
bugs
you
have
to
fix
in
software,
it's
literally
the
same
thing
in
hardware:
it's
like
you
make
this
improvement,
this
improvement,
but
all
that
costs
money
and
time,
and
then
you
start
thinking
about
okay.
A
How
do
you
design
for
disassembly
designed
for
modularity
designed
for
scalability,
so
you're,
not
just
designing
one
thing:
you're
designing
an
ecosystem
that
one
makes
your
effort
much
more
valuable.
So
for
me
that
came
out
of
necessity,
because
I
you
know
we
didn't
have
people
here.
So,
okay,
I'm!
I
said
if
I'm
gonna
design
this.
Let
me
design
it
in
a
way
that
can
be
the
most
robust
and
multi-purpose
just
as
a
way
to
save
time
and
then
at
that
time,
free
cap
didn't
really
exist.
A
So
we
were
like
trying
to
hardly
doing
design
work,
just
doing
simple,
simple
concept:
designs,
but
as
much
as
possible.
Like
say
you
look
at
life
track,
one
see
those
hydraulics
diagrams,
that's
all
that
was
all
really
prior
to
cad
and
then
there
was
there
was
sketchup
at
that
time.
But
it's
not
that
great.
A
But
then,
as
time
went
on
knowing
that,
okay
now
we
have
parts
part
libraries
techniques
that
we
know,
then
you
can
start
building
upon
all
that
and
so
over
time
you
start
noticing
that
man,
if
that
kind
of
knowledge,
could
be
built
up
for
more
people,
then
this
process
could
explode
and
that
kind
of
makes
it
very
clear
that
the
documentation
is
even
more
important
than
the
builds.
A
A
But
there's
I
mean
there's
a
standard
product
development
methodology
that
we're
not
inventing
anything.
There's
you
look
at
product
development,
google,
that
and
then
think
of
open.
So
then
google
open
source
product
development
and
then
you
actually,
you
know
you're
in
trouble
because
it
gets
us
to
our
wiki.
A
So
that
means
that
that
means
that
we're
like
ahead
of
the
game,
because
there's
no
other
stuff
talking
about
open
source
product
development
and
but
if
you
read
the
literature
and
it's
on
an
open
source
product
development,
page
read
some
of
those
seminal
papers
and
they
actually
talk
about
collaborative
open
is
the
next
phase
that
development
will
take
on,
but
they
still
use
the
same
kind
of
process.
You
got
to
go
through
all
the
due
diligence
steps
of
what
you
do
to
develop
and
that's
simply
captured
in
the
development
template.
A
A
Concept
there
being
yeah,
so
let's
I
think
that
should
turn
on.
Does
that
plug
in
yeah
the
important.
B
A
A
A
So
if
you
go
to
say,
osc
click
on
my
logs
so
once
again
logs
is
how
you
find
out
what
other
people
are
doing
and
you
can
look
at
work
log
on
the
wiki.
But
if
you
look
at
my
log,
say
osc
filament
maker
you'll
see
this
whole
thing.
That's
formatted
to
to
take
you
to
help
you
guide
guide
you
through
are.
A
Yeah
but
that's
template
dev,
so
that's
that's
the
actual
template,
but
let's
talk
about
it,
so
so
the
wiki
allows
you
to
easily
call
up
one
of
these
things.
If
you
know
this
thing
that
exists,
which
is
called
dev
plus,
it's
just
the
template
for
the
standard
development
that
we
do,
you
call
it
up
in
one
line.
It
takes
you
a
second,
so
it's
like
cloning,
a
project
on
github
forking
it
something
you
download
the
whole
the
whole
thing
from
what
you
start
building
on
it
here.
It's
a.
B
A
Different
because
it
sees
it,
but
it
sees
it
with
blank
pages
for
what
you've
got
working
on,
but
you
have
to
treat
it
as
a
fork
treat
every
build
as
a
fork
because
you're
going
to
do
things
differently.
So
we
encourage
that.
The
main
thing
is
we're.
Building
this
filament
maker.
Now
we
gotta
start
a
new
development
page.
Don't
try
to
put
anything
back
into
the
filament
maker
from
2018
or
whatever,
because
it's
going
to
start
jumbling
everything
up.
A
So
this
is
so.
How
do
you
document
everything
on
this?
So
this
is
the
development
plate
template
by
putting
in
a
single
word
into
the
wiki
edit,
so
so
go
to
the
wiki
say
test
test
page
right.
So
how
do
you
call
up
this?
I
just
started
page
called
test
page.
How
do
you
call
up?
How
do
you
start
development
say
you
want
to
work
on
whatever?
Whatever
you
got,
you
got,
you
want
to
develop
a
3d,
printable,
fitting
or
a
manual.
What
do
you
want
to
develop?
You
want
to
build.
A
A
Volume
is
zero
on
that,
so
this
is
what
I'm
doing
so.
I'm
editing
the
wiki
the
double
bracket
dev
plus,
that
plus,
is
a
template.
A
A
A
A
The
development
process
takes
you
through
the
standard
steps
of
development,
there's
design,
there's
which
starts
with
concept,
then
there's
actual
technical
design,
build
materials,
build
and
life
cycle
design,
which
is
more
like
data
collection,
future
work
kind
of
like
you
can
call
that,
like
data
collection
points,
but
this
is
nothing
new.
This
is
somewhat
of
a
standard
way
like
if
you
design
something
for
a
company
you're
going
to
start
with
requirements,
and
things
like
that,
oh
and
you
got
to
document
all
that
and
the
way
for
parallel
development.
A
What's,
I
think,
useful
to
note
here
that
a
lot
of
these
steps,
while
okay
there's
a
whole
bunch
of
them,
there's
a
lot
that
you
can
start
documenting
in
a
collaborative
way
because
well.
A
Because
a
lot
of
these
things
reinforce
one
another,
so,
for
example,
if
you
start
with
a
requirement,
I
actually
make
this
let's,
let's
start
with
a
limit
like
the
in
the
limit
of
infinity
statement,
which
says,
like
think
about,
I
like
to
do
things
such
as
thinking
about
the
extreme
case
of
something
to
get
inside
so
here,
to
give
you
an
example,
if
you
think
about
the
development
template,
it
should
be
such
that
any
one
of
the
elements
here
would
almost
be
like
in
its
fully
developed.
C
A
Yeah
so
that
you
just
set
it
like
yeah,
then
you
look
at
industry
standards
and
you
might
say,
oh
well,
there's
all
this
stuff
we're
already
building
on
so
all
together.
This
is
not
something
that
started
from
scratch.
You
can
be
building
upon
this
whole
vast
pool
of
knowledge,
and
this
is
the
time
binding
concept
that
we're
building
upon
all
the
stuff
that
already
exists.
So
when
you're
stuck
with
this
flat,
this
whole
empty
thing,
which
is
red,
means
empty
and
you're
like.
B
C
A
A
So
if
you
don't
know
what
something
is
called,
then
you
have
to
go.
Look
at
the
taxonomy
page
and
see
okay.
What
are
things
called
here?
How
do
we
develop
here?
So
we
would
go
to
taxonomy,
but
if
you
know
that
other
people
are
working
on
it,
then
you
can
look
at
their
logs
and
see
if
you
can
extract
that.
If
you
didn't
know
it
was
the
lyman,
you
might
go
back
to
see.
A
A
A
A
Yeah,
I
think
it
is
you
can
you
would
have
to
grade
this.
So
there's
a
bunch
of
stuff
here
that
this
is
by
no
way
no
means
complete,
but
there's
a
bunch
of
areas
like
50.
You
know
about
50
different
areas
like
fittings,
3d,
printing,
high
high-tech
materials,
ceramics,
pneumatics,
hydraulics.
A
It's
like,
if
you
think
about
like
50
gbcs
machines.
The
requirement
there
for
the
500
parts
would
be
that
the
50
you
can
take
the
500
and
make
any
other
50
with
it.
So
you
try
to
get
to
the
pattern
language
of
what
all
technology
is
made
of
and
then
you
have
to
say,
okay.
Well,
these
are
the
main
components
you
can
grade
them
and
you
can
say
these
are
the
most
common
elements
that
exist
like
a
ball,
bearing
would
definitely
be
in
there
or
a
hydraulic
motor.
Maybe
electric
motor
solenoid.
A
Yeah
and
you
can
go
infinitely
down
the
rabbit
hole,
so
you
have
to
stop
somewhere,
but
then
again
you
stop
that
number
slightly
over
100
with
all
the
elements
too.
You
know
there's
only
like
100
or
so
elements,
but
you
have
to
make
a
judgment
saying:
okay,
these
are
the
most
common
parts,
it's
very
useful
to
do
that
and
you
use
somewhat
of
a
visual
design
language
and
we
have
that
under
the
open
source
technology
pattern,
language,
yeah
yeah,
which
you
can
start
thinking
about.
A
How
do
you
synthesize
all
these
different
machines
that
things
that
look
completely
different?
But
once
you
start
looking
under
the
hood,
you
start
finding
that
hey,
there's
only
so
many
different
things
and
a
long
time
ago
I
drew
up
this
stuff
like
linear
motors
wheels,
rotors
frames
things
like
this,
but.
A
C
A
It
would
take
a
rigorous
set
of
phd
theses
to
try
to
define
what
that
would
really
mean,
but
it
would
be
quite
useful,
like
what's
a
good
example
of
where
we
see
it
works,
like
maybe
legos,
where
you've
got
these
lego
blocks,
that
build
all
these
kinds
of
things,
but
try
to
get
to
a
set
of
interchangeable
parts
and
that's
what
standards
try
to
do
like
iso
standards
or
standards
for
like
this
is
a
bolt.
This
is
how
the
threads
look.
A
There
could
be
a
lot
of
that
to
reduce
the
complexity
from
thousands
of
different
iterations,
which
a
lot
of
people
say.
Well,
that's
kind
of
I
want
that.
I
want
a
thousand
different
hubcaps,
but
you
might
say
well
altogether.
That
creates
a
lot
of
a
lot
of
effort
like
do
you
want
to
be
creating
gearhead
people
who
are
just
doing
that?
Or
do
you
want
to
spend
more
time
on
other
things,
so
I
think
there's
a
usefulness
call
out
knowing
that
right
now,
everybody's
not
provided
for.
A
Let's
try
to
make
an
easy
way
that
everyone
could
be
provided
for
with
abundance.
Therefore,
we
might
want
to
rethink
how
we
do
technology
to
make
it
more
appropriate
and
fixable
and
accessible.
But
what
would
those?
What
would
the
basic
it's
like
an
exercise
of
rebuilding
civilization
that
one
book
like?
What's
that
one
book
by
that
english
guy?
It's
called
whatever
the
great
reset
or
something?
A
No,
this
one
book
that
talks
about
well,
what
are
the
like,
the
most
basic
processes
in
in
technology
that
are
required
to
make
just
about
everything,
and
you
can
do
well
to
start
identifying
like
what
is
that,
like
a
steel
mill?
Well,
maybe
that's
just
like
electricity
arc
furnaces
or
a
flame
rock
burning
like
coal,
burning
and
and
melting.
C
A
And
and
so
on
and
so
on,
but
you
can
classify
things.
It
is
useful
to
classify
and
organize
things
so
that
you
can
actually
start
treating
it
as
a
building
block
construction
set
and
that's
kind
of
the
essence
of
the
global
village
construction
side.
Let's
try
to
identify
some
of
these
basic
things
that
can
be
used
for
many
things.
B
A
B
I'm
just
getting
to
the
if
I'm
a
random
contributor
who
says
oh
wow,
this
open
source
technology
project
looks
really
cool.
Oh,
they
have
a
wiki.
This
is
great,
and
then
I
come
to
the
wiki
and
I'm
on
the
home
page.
Looking
at
openswissocology.org
and
it's
like
oh
wow,
I
want
to
learn
how
to
navigate
this
thing.
On
the
left
hand
side
I
see
wiki
instructions,
so
I
click
on
wiki
instructions
and
there's
nothing
there
about
taxonomy
right.
B
C
A
Yeah-
and
this
gets
to
to
the
idea
of
well
like
yeah-
you
need
a
whole
management
team
to
to
develop
that
kind
of
collaboration
like
wikipedia
spends
30
million
dollars
to
do
that
per
year.
A
But
here
I
just
added
wiki
taxonomy
to
the
to
the
wiki
instruction
space,
but
the
thing
is
that
that
it's
like
part
of
the
collaborative
literacy
is
like
okay.
Well
we're
all.
This
is
just
a
wild
thing
that
lives
out
there.
You
can
feel
free
to
put
any
kind
of
indexical
environment
that
suits.
You
use
your
workload.
So
it's
it's
a
completely
wild
thing.
It's
that
it's
you
can
think
of
it
as
a
database
dump.
And
yes,
it
may
not
be
navigable,
but
that
that's
okay,
it
can.
A
That
can
come
with
time
too,
but
it
requires
once
again
that
there's
like
ongoing
continuous
effort
and
teams
and
stuff
like
that,
and
that
comes
from
once
again
the
revenue
models
and
people
being
supported
by
this
so
that
they
don't
just
pop
in
and
because
it
is
overwhelming
to
study
everything
you
have
to
be
engrossed
in
it
with
some
very
significant
motivation
like
making
a
living
or
something
like
that.
A
Yeah,
if
you,
if
I
log
out
and
that
would
go
request
account,
then
you
can
start
editing,
but
the
whole
thing,
like
the
first
thing
just
for
people
to
understand
what
a
wiki
is.
It's,
I
think,
a
lot
of
people
don't
even
understand
this
concept
that
oh,
you
can
actually
completely
just
log
in
and
start
editing
this
public
piece
of
work.
A
That's
that's
a
big
deal
too,
like
a
lot
of
people.
Don't
know
such
a
thing
as
even
an
animal.
It
exists.
How
many
people
know
that
actually
on
the
planet?
Right
now
I
mean
internet's
been
around
for
a
few
years,
but
a
lot
of
people
don't
know
it,
but
that
is
possible.
But
it's
part
of
the
learning
curve.
100
million
you'd
say
100
million
no.
A
Yeah
yeah
and
it's
a
different
way
of
thinking,
because
because
a
lot
of
people
come
to
me
like
like
treating
me
like
I'm
the
master
of
that,
you
know
I
kind
of
control
every
single
page,
but
I
don't
it's
like
I'm
one
of
the
editors,
how
many
current
editors
are
there?
Not
too
many?
But
let's
see,
let's.
A
A
Things
we
do
see
is
there's
11,
almost
12
000
pages
content
pages,
16
000
files,
there's
like
2
000
registered
users.
Active
users
are
15.,
that's
kind
of
it
well,.
C
What
about
visits
to
a
particular
page.
A
A
A
Yeah
there
is,
it
is
here
somewhere.
Let's
see,
where
is
that.
C
A
Yeah,
how
did
I
see
that
like,
for
example,
how
do
I
know
there's
a
page
called
cost
of
living
that
was
pretty
popular,
but
how
did
I
find
that
out?
A
Oh
yeah
page
information,
yeah,
I
mean
look
at
any
page
and
look
at
page
information.
Do
you
guys
see
that
or
is
that
an
admin
feature.
A
No,
it
doesn't
even
tell
you
stats
yeah.
We
should
be
tracking
all
this.
It's
like
it's
ph,
someone
who
knows
php
can
upgrade
this
wiki
we're
hoping
that
joshua
would
get
to
this
at
some
point,
but
he
disappeared,
went
awol.
A
What
what's
useful
is
things
like
what
links
here,
there's
a
bunch
of
useful
pages
and
under.
A
Special
pages,
but
what
the
way
to
navigate
this
is
look
at
recent
wiki
changes
and
then
you
know
kind
of
like
what's
happening.
So
someone
will
ask.
Is
anything
going
on
well
take
a
look
at
recent
changes
and
is
anything
happening?
Well.
Yeah,
you
know,
22
october
is
a
few
edits.
A
I
mean
the
year.
There
is
2021,
it's
not
like
2011
or
something
so
you
know
it's
active
and
you
can
look
at
all
the
all
the
recent
changes.
So
if
you
know
that
you're
working
on
a
team,
it's
useful
to
look
at,
let's
say
you're
collaborating
well.
One
thing
is
the
work
log
like
march
and
log
or
catalog,
or
something
and
if
you
know
who
the
team
is
like,
if
we
know
we've
got
the
team
here,
then
we'd
want
us.
A
If
someone
said
I
just
got
a
new
design
on
this
thing:
okay,
I'd
say:
okay.
That
means
I'll
look
at
your
log
and
look
at
the
cad
file.
Okay,
did
you
upload
a
free
cad
file?
Let
me
see
it
that's
kind
of
way
to
communicate
so
implicitly,
you
know
that
stuff
is
happening.
There's
part
libraries
on
the
wiki,
where,
like,
for
example,
for
the
cnc
torch
table,
there's
a
gallery
of
parts
we're
already
using.
A
A
So
if
you're
working
on
a
torch
table,
you're
trying
to
find
out
okay,
like
say
you
know,
we're
working
on
torch
table,
I
would
go.
The
first
thing
is
genealogy.
It
should
be
there.
It
should
be
the
21.08
because
you
might
think
well
what
do
we
name
it?
Well
we're
just
doing
a
simple
year,
ubuntu
style
like
year
and
month,
kind
of
a
thing
which
is
very
useful
because
there's
one
there's
so
many
projects
and
it
helps
you
identify
more
more
by
chronology
but
like
on
the
cat.
A
A
I
didn't
know
what
that
is,
so
that's
already
up
there
free
cut
files.
There.
A
Number
of
wiki
edits
like
on
your
work,
log,
finding
pre-cut
files-
I
mean
that's
like
the
ultimate
thing
like
talk
about
any
design
like
such
as
the
filament
maker
right
now,
the
bottom
line
is
okay.
Do
we
have
a
design
that
we're
digitizing
that's
the
free
cut
file
so
that
anyone
else
can
build
upon
it
or
10
years
from
now
we
make
a
you
know,
evolution
of
it
or
whatever,
or
somebody
across
the
world
can
actually
right
now
get
involved
in
it.
A
But
once
again,
the
issue
is
the
final
ability
like
getting
people
to
show
up.
A
As
I
always
say,
you
know
people
that
that
have
to
understand
the
idea
that
okay
collaboratively,
if
only
a
very
small
percentage
of
the
world's
population,
actually
did
work
on
this
I
mean
we
would
have
this
done
in
no
time,
but
that's
a
huge
organizational
challenge,
that's
very
costly,
and
you
have
to
be
really
good
to
be
able
to
execute
on
that,
because
how
do
you
get
so
many
people
to
collaborate
when
most
of
the
world
doesn't
even
know
that
there's
even
a
technical
capacity
to
collaborate
like
this
or
the
mindset
to
do
so
or
or
the
tools
and
processes
or
the
concept
of
here's
the
standard
product
development
methodology
yeah?
A
So
it's
it's
a
complex
package
and
I
think
companies
are
going
to
what
I
envision
in
the
future
is
definitely
companies
that
are
coming
to
a
common
pool
of
of
designs
and
collaborating
on
their
products.
I
do
think
that's
that's
gonna
happen
more
and
more
because
it's
efficient
like
at
the
end
of
the
day,
if
you
can
systematize
these
processes
end
of
the
day.
You
don't
want
to
it's
about
not
reinventing
the
wheel.
A
If
you
can
find
something,
that's
been
done
before
you're,
not
reinventing
the
wheel,
but
right
now,
unfortunately
reinventing
the
wheels.
This
is
the
standard,
it
happens
like
emmanuel.
You
mentioned
one
government,
company
or
one
company.
Does
this,
you
know
100.
Other
universities
are
working
on
the
same
thing.
Mine
doesn't
necessarily
know
it
yeah.
So.
C
B
C
A
Calculus
code,
aster,
open,
fem,
fml,
elmer
freecad
is
actually
borrowing
some
of
this.
I
think
it
uses
calculus
for
a
lot
of
stuff.
It
uses
open
phone,
there's
open
foam
foam
for
fluids,
okay,.
A
Yeah,
so
the
point
is
once
again:
it
goes
back
to
the
nature
of
the
open
source
tool
named
freecad,
which
is
that
all
these
additions
can
be
made
and
integrations
and
so
forth.
So
there's
expandability
there
is
really
powerful.
Like
imagine
there
was.
You
know
the
next,
a
thousand
phd
theses,
developing
all
these
modules
for
freecad,
and
now
you
have
the
best
software
analysis
tool
in
the
world.
A
So
I
mean
that's,
that's
the
potential
and-
and
I
think
it's,
if
you
look
at
how
freecad
is
growing,
I
mean
there's
indication
that
that's
that's
kind
of
happening
and
there's
I
mean
the
communities
the
projects
pretty
much
exploding
these
days
in
terms
of
a
number
of
people
using
it
market
share
is
almost
not
noticeable
but
like
when
I
was
ordering
parts
I
emailed
the
guys.
Hey
are
you
going
to
have?
A
A
Already
you
can
get
step
files
are
importable
into
precast,
so
like,
for
example,
mcmaster
car
any
part
there
pretty
much
has
as
cad
and
step
format.
We
just
import
into
freecad,
but
yeah
like
open
foam.
A
A
A
A
Can't
find
it
right
now,
but
there's
like
there's
all
kinds
of
stuff
coming
out
and
that
once
again,
that's
the
essence
of
the
open
source
nature
that
things
are
coming
out
that
are
made
accessible
to
all.
It
seems
that
if
you
think
about
it
that
kind
of
builds
kind
of
accretes
mass,
unlike
proprietary
packages,
where
I
mean
some
people
are
actively
saying
well,
we
can't
do
that
because
it
costs
so
much
to
get
the
license
here
if
you've
got
free
access,
potentially
there's
more
and
more
people
using
it.
A
I
think
that's
the
trend,
that's
that's
happening,
and
there's
critiques,
like
whatever
like
the
original
code
base
for
freecad,
may
not
be
sufficient.
I
mean
for
right
now,
whatever
we
do,
it's
sufficient
and
it
could
be
rewritten
completely
in
the
future
too.
So.
A
But
the
thing
is
on
a
wiki
to
start
uploading
like
the
the
real
like
the
badge
of
honor.
Here,
it's
like
okay,
really,
how
many
files
are
you
actually
contributing
that
other
people
can
use
build
upon
and
are
they
just
files?
Are
they
tested
files
things
that
you
actually
build,
because
if
you
build
it,
that
has
a
whole
level
of
merit.
A
A
So
if
you
want
to
contribute
like
in
the
long
term
to
the
project
that
the
ultimate
is,
how
many
files
of
things
that
are
buildable
or
have
been
built,
and
even
starting
with
the
files
because
a
file,
even
if
it's
not
buildable,
someone
who
knows
about
buildability,
can
improve
it
and
and
so
forth,
so
the
number
of
freecad
files
that
actually
are
downloadable
better
yet
organized
into
as
parts
of
other
part
libraries.
A
A
We
had
one
from
the
lyman
filament
maker,
yeah,
a
bunch
of
stuff
is
there
and
the
usefulness
of
part
libraries
here,
like
imagine,
you're
looking
for
parts
because
you're
trying
to
design
something
and
you're
trying
to
actually
find
the
real
part.
That's
the
real
thing
like
when
you
do
the
cad.
A
It's
one
thing
when
you
just
put
in
a
placeholder
versus
a
part,
that's
completely
geometrically,
correct,
and
even
if
approximately
but
like
it
has
the
critical
features,
so
it
doesn't
have
to
be
a
huge
file.
It
just
has
to
have
some
critical
features
that
now
he
can
really
work
with
it
and
analyze
things
like
oh
well.
Can
things
actually
be
put
together
how
much
space
it
takes?
A
I
want
to
do
that
filament
maker
where's,
the
file
of
the
heater
band
or
the
the
plug
that
goes
in
the
end
of
it
that
are
actual
real
parts
that
we
use.
That
can
help
us
do
the
real
design,
because
at
the
end
of
the
day
you
want
to
get
yourself
trained
to
the
point
of
when
you
see
something
like.
Is
it
a
real
design?
A
That's
buildable,
or
is
it
just
a
concept
because
sometimes
you
might
see
some
amazing
cad,
but
it's
not
super
buildable
in
fact,
actually
look
at
like
architecture
like
I
for
a
long
time.
I
didn't
know
what
architects
do
and
I
I
kind
of
still
don't,
but
no
but
architects,
actually
don't
design
houses.
They
design
house
concepts
like
they
don't
do
the
technical
stuff.
The
technical
stuff
is
implemented
by
the
people
who
actually
build
it,
but
they
do
draw
up
things
like
some
finished
detail
like
okay.
A
A
Because
if
you
can
do
the
actual
full
cad
to
down
to
like
buildability
and
ease
and
maintenance,
that's
a
whole
different
game
than
just
a
concept
and
in
terms
of
price
and
executability
and
part
of
the
reason
why
we
think
we
can
do
the
house
so
much
more
lower
cost
is
because
it's
not
a
concept
design.
It's
like
fully
technical
with
information
in
there
consideration
of
how
we're
actually
building
it.
A
So
we're
not
leaving
anything
to
chain
chance
rather
being
in
tight
control
the
product
you
can
actually
control
the
cost
and
and
what
the
business
model
comes
out
of
it,
and
that's
very
important
if
you're
going
to
take
this
to
the
level
of
here's
a
viable
economic
enterprise
to
make
it
happen.
So
you'll
find
a
lot
of
cad
out
there
and
grab
cat
like
grab
cat
is
really
good
for
like
a
lot
of
concept
stuff
but
like
buildability,
I
don't
know
it
takes
this
very
special
skill
set
to
design
something.
A
That's
it's
a
rare
skill
set.
I
don't
see
it
a
lot
at
all
where
you're
designing
something
that's
buildable
easy
to
build,
and
all
that,
because,
typically
different
people
do
those
different
steps
and
it's
a
disintegrated
process
which
implies
that
okay,
there's
these
huge
efficiencies
that
can
be
gained
because
you
can
consider
the
whole
chain
of
production.