►
From YouTube: Collaborative Literacy - New Zealand Presentation
Description
Latest thoughts on Collaborative Literacy. Overview of OSE goals and aligning thousands of collaborators to reinvent the economy.
https://wiki.opensourceecology.org/wiki/OSE_Collaboration_Protocol
See the collaborative literacy page - https://wiki.opensourceecology.org/wiki/Collaborative_Literacy
-----------------
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
So,
let's
start
recording
this
so
welcome
to
New
Zealand
yo
so
session
on
collaborative
literacy.
So,
first
of
all,
what
are
the
known
resources
that
we
have
on
the
wiki?
There's
there's
a
couple
of
pages.
What
I'll
do
is
because
collaborative
literacy
is
so
important.
I'll
do
like
literally
like
a
whole
manual
for
how
you
collaborate,
I
mean
it's
like
a
standard
procedures
for
what
we
do
right
now.
It's
found
on
a
couple
of
pages.
We
have
a
page
called
collaborative
literacy.
A
So
let
me
share
my
screen,
so
we're
recording
well
since
nobody
joined
us
here
yet,
but
I
can
still
not
just
cancel
that
since
nobody's
listening
besides
us
here,
a
couple
of
pages,
so
there's
a
page
called
on
a
wiki
once
again.
The
first
first
thing
is
like
okay:
what's
the
wiki
first,
it
was
a
public
collaborative
editable,
real-time
platform.
A
There's
so
in
the
under
collaborative
literacy,
you
see,
are
we
recording
here?
Yes,
we
are
so
under
collaborative
literacy.
We
have
a
couple
of
assets,
there's
there's
a
webinar.
You
might
want
to
take
a
look
at
because
this
is
like
look
as
I
say
about
this
in
a
steam
camp.
We
put
in
a
lot
of
knowledge
into
the
packet
into
a
short
time
period.
It's
only
like
the
first
expectations
to
say
that
hey,
it's
only
a
beginning,
it's
like
what
you
get
out
of
it.
This
is
really
know
someone.
Someone
join
us.
A
Oh
okay,
it's
really
like
do
you
have
a
clear
motivation
for
doing
this,
like
if
you're
gonna
work
want
to
create
a
business,
producing
3d
printers,
teach
people
or
start
a
micro
factory
for
yourself
or
go
deeper
with
it?
We
present
you
with
some
basics,
but
what
we
present
here
is
just
scratching
the
surface.
So
the
first
expectation
is
it's
really
like.
Do
you
have
something
that
you
want
to
get
out
of
it
because,
as
far
as
what
you
can
get
out
of
it,
it's
it's
a
lot.
A
It's
the
idea
that
we're
trying
to
get
a
lot
of
people
working
together
through
a
package
of
multiple
elements,
so
there's
the
Steenkamp
on
one
side,
which
is
like
basic
bootcamp
literacy
training
in
this
Steenkamp.
We
don't
have
the
five
project
days
where
we
apply
the
things
like
you're,
printing,
you're,
uploading
to
the
wiki
you're,
possibly
doing
circuits
that
you're
milling
plotting
like
plotting
search,
but
primarily
with
a
3d
printer.
A
You
can
do
a
lot
with
off-the-shelf
parts
and
the
printer
you
there's
a
lot
of
prototyping,
but
the
bigger
part
is
also
the
collaborative
aspect
where
you're
constantly
uploading
things
to
the
wiki,
putting
them
into
freecad
the
cool
thing
about
the
printer.
Is
that
say:
you're.
You
know
we
got
a
design
sprint
to
make
a
car
which,
which
is
what
we
see
like
in
the
future.
A
If
we
have
a
number
like
say
20
of
these
events,
at
the
same
time
with
like
20
people,
each
like
400
people,
you
can
in
principle
say
ok
and
during
the
steam
camp
we
can
prototype
a
lot
of
it,
but
maybe
like
after
the
steam
camp.
We
could
have
a
thing
where
we
all
get
together
into
one
location
to
actually
build
it
or
something
like
that
with
ideas.
It
is
about
much
larger
development
by
collaborative
effort
so
start
with
a
steam
camp.
A
The
incentive
challenges
as
the
grand
kind
of
grand
finale,
where
we
get
a
lot
of
people
collaborating
through
an
incentive.
That's
monetary
reward,
but
it's
more
about
like
the
the
way.
Those
things
work
is
that
people
spend
more
effort
than
you
give
the
prize
for
clear,
like
by
a
factor
of
ten
or
a
hundred.
People
will
spend
so
much
effort
to
compete
in
that.
A
But
for
us
we
skew
the
rules
to
collaboration
and
there's
a
very
interesting
point
about
that,
because
when
you
look
at
the
heroics
platform,
all
right
pretty
much
any
platform
out
there,
it's
a
competition.
We
have
a
bunch
of
teams
working
against
each
other,
but
what,
if
you
skew
the
rules
so
that
everyone
is
actually
working
together
and
uploading
constantly?
So
you
can
think
that
okay,
there
is
that
possibility.
But,
interestingly,
it
has
not
happened
like
if
you
look
at
dawn,
heroics
right
now,
there's
hundreds
of
projects.
A
You
will
not
find
a
single
one
where
they
collaborate.
Do
that
look
at
it.
In
fact,
you
look
at
the
rules.
You
say
that
they
say
you'll
be
disqualified
if
you
copy
from
others.
So,
okay!
Well,
that's
a
that's
a
shifting,
so
we're
talking
about
this
mindset
where
it's
not
a
dozen
or
a
couple
of
people
parked
it
and
collaborating
like
the
two
Pizza
team
at
Amazon
or
whatever.
No,
it's
mobile,
it's
thousands
of
people.
So
that's
the
case.
A
We
need
to
use
the
tools
that
allow
us
allow
us
to
do
that
effectively
and
things
like
wiki's
and
free
CAD
and
tory's
cloud
editable,
Google
Docs,
which
we
use
currently
like
Google
Docs,
for
example,
are
not
open-source,
but
there
is
no.
Currently,
there
is
no
really
good
Google
slides
alternative
that
we
can
use
very
effectively
with
a
lot
of
people.
So
so
there's
there's
that
idea
that
we're
talking
about
large
collaboration
there's
also
the
idea
of
university
chapters.
Where
think
about
that
we're
not
just
having
chapters
that
do.
One
thing.
B
A
A
typical-
maybe
you
know
if
you
might
have
engineers
Without
Borders,
okay,
one
team
goes
to
Ghana
another
one
goes
to
Costa
Rica
or
whatever,
no
we'll
all
collaborate
on
one
big
project
where
it's
gonna
be
something
grated
like.
Let's
solve
a
problem
like
okay,
let's
develop
a
hydrogen
car,
you
know,
let's
solve
the
afforestation
issue
or
the
housing
issue,
by
providing
low-cost
modular
housing
to
everybody
like
I
mean
there's
technical
solutions.
Of
course
it's
it's
much
deeper
than
that,
but
at
least
on
the
technical
level,
we're
saying:
okay.
A
We
start
by
first
it's
that
vision,
the
collaborative
literacy
which
to
me
is
the
like.
The
number
one
thing:
that's
missing
and
people,
because
people
are
just
net.
No.
Where
are
you
really
used
to
like
me?
For
example,
your
company,
you
guys,
are
not
going
to
share
your
your
stuff
with
others,
possibly
if
that
did
happen,
then
the
whole
industry
could
be
brought
up
in
terms
of
the
kind
of
products
they're
possible
to
happen
like,
for
example,
you
know
some
related
industry
might
might
be
making
straw
board
from
grass
or
biomass.
A
Like
imagine
that
technology
like
right
now
you
go
to
the
park
or
you
get.
You
know
we're
plywood
panels.
What,
if
that
technology
was
available,
that
anyone
like
anywhere
could
make
this
construction
material?
That's
really
good,
because
we
all
collaborate
on
it.
Things
like
that
just
solving
bigger
problems.
So
we
talk
about
scales
of
thousands
of
people,
potentially
there's
the
Aussie
University
chapters
which
we're
trying
to
get
spawned
up
like
a
lot
of
times.
The
discussion
comes
about
like
how
do
you
work
with
the
universities?
Definitely
that's.
A
That's
worth
doing
if
I
think
the
way
to
crack
that
nut
is
to
have
every,
because
it's
a
huge
coordination
question
right.
So
how
do
you
crack
that
nut
and
I
think
the
way
to
crack?
It
is
the
collaborative
literacy,
the
idea
that,
first
of
all,
you
can
work
on
a
bigger
project.
You
do
have
the
tools
and
then
selecting
bigger
projects
that
are
beyond
any
single
team.
A
That's
the
other
component
and
then
the
role
division,
just
like
in
software
Linux,
was
solved
by
the
ability
of
people
to
make
it
to
work
on
many
many
parts.
At
the
same
time,
and
using
repositories
like
high
modular
breakdown,
that's
the
key!
So
for
modular
breakdown,
you
can
break
the
technology
down
into
very
small
parts,
but
you
can
also
break
the
teams
down
into
very
small
parts
like
for
this
event.
You
know
we
can
start
drawing
up
a
list
of
like
a
hundred
people
that
can
contribute
meaningfully
like
another.
A
One
would
be
like
say
that
they
are
instructionals.
Where
you
take
a
picture
of
that
and
through
AI
it
will
tell
you
hey.
That
thing
is
actually
not
right
there.
You
know
things.
That's
like
an
advanced
level
of
information
architecture
that
you
can
have
in
this,
but
all
of
those
things
require
a
lot
of
effort.
So
there's
there's
that
even
that
AI
assist
there's
the
IKEA
style
fabrication
drawings.
There's
like
the
plain
manual
there's
video
instructionals,
there's
just
the
technology
refinement.
A
There's
Production
Engineering
everything
you
know
you
can
have
like
full.
There's,
there's
electronics
in
there
there's
mechanics
in
there's,
there's
thermal
thermal
dynamics
in
there
and
all
of
those
you
can
break
this
into
teams.
And
so
the
point
is,
you
can
create
collaboration
architecture.
A
lot
of
people
are
doing
the
development
and
then
taking
that
too.
A
Okay
can
we
be
actually
working
on
the
Steenkamp
itself?
Okay,
so
how
we?
How
do
we
develop
that
model
to
train
people
to
get
the
operations
on
that?
To
give
the
logistics
proper
to
get
all
the
details
that
go
into
running
bad
press
so
bottom
line?
You
can
turn
one
project
into
this
massive
effort
with
many
many
people
working
on
it
together
and
I
think
it
starts
with
taking
on
bigger
projects
and
bigger
problems
like
because,
because
if
you
have
a
big
hairy,
audacious
goal
in
mind,
this
is
kind
of
like
from
Peter.
A
A
Actually
I
got
that
from
the
book
being
bold,
the
guy
who
founded
the
XPrize
so
basically
like
global
we're
in
challenges,
big
issues
that
are
worth
working
on,
there's
plenty
of
them,
but
most
of
us
kind
of
reduce
ourselves
to
okay,
there's
like
more
mundane
things
that
we
have
to
to
make
a
living.
But
there's
certainly
a
lot
a
lot
of
good
work
to
be
done,
and
we
have
to
start
at
the
level
of
inspiring
people
to
work
on
such
such
issues
and
and
then
there's
the
tools,
the
actual
tools
that
you
can
use.
A
It's
called
Aussie
collaboration
protocol.
So
what
are
the
basics?
I
mean
the
basics
that
anyone
can
can
do
like.
For
this
event,
the
things
the
kind
of
things
we
want
to
do
is
people
documenting
stuff
on
a
wiki,
so
you
so
get
an
account.
So
we
know
that
wiki's,
like
Wikipedia,
are
highly
scalable.
You
can
have
thousands
of
people
on
it,
hundreds
of
thousands
of
people
collaborating
and
how
do
you?
How
do
you
keep
track
of
where
everything
is?
There's
two
things:
there's
people
that
are
involved
and
then
there's
the
actual
content.
A
That's
involved
for
people
same
you
got
this
team
like,
say
we're
working
on
a
full-time,
we're
developing
like
with
the
other
steam
camp
instructors.
Each
of
us
has
a
log
on
the
wiki,
like
a
log
where
you
just
keep
track
of
all
that
you
do
so
so
that
somebody
else
looks
at
your
log
and
they
can
go
like
that.
Okay,
this
person
did
this.
A
So
how
does
it
look
first
of
all
there's
an
effort
graph
where
we
see
how
many
hours
are
being
contributed
so
right
now
we're
at
about
250
or
so
maybe
so
I
go
to
March
and
log.
So
the
log,
the
the
nomenclature
there
is
okay,
so
the
page
name
is
Ian
log.
So
you
start
that
you
first
of
all
get
an
account
on
a
wiki
I,
just
embedded
this
overall
time
graph
each
person.
A
A
I've
got
tabs
I
got
that's
part
of
the
thing
make
it
easy
like
my
my
log,
but
how
do
you
parse
like
say
I
I,
do
all
that
I?
Do
you
can
completely
follow
everything
that
I've
done
in
a
day?
What
I
do
is
and
that's
important
if
you
have
a
large
team-
and
you
don't
want
to
like
parse
through
pages
of
logs.
The
cool
thing
to
do
is
put
a
date
on
it
and
then
put
a
link
to
it,
which
is
a
hyperlink
which
means
it's
double
brackets
as
far
as
the
syntax.
A
So
the
ideas
on
a
lock
don't
put
this
in
your
log,
the
link
to
it
in
your
log,
so
a
person
can
parse
it
immediately.
So
I've
done
that,
but
then
also
I
did
global
petroleum
revenue.
I
was
thinking
about
a
renewable
energy
and,
and
so
I
just
was
surfing
than
that,
and
that's
actually
an
important
figure,
like
all
units
is
still
going
way
up.
A
A
That
you
do
that's
related
to
the
overall
goals
like
how
like
in
the
future
like
I,
can
go
into
the
search
box
and
say
like
petroleum
revenue
and
I
would
find
that
page
and
I
could
look
it
up
immediately,
as
opposed
to
happen
to
look
on
the
web,
so
we're
trying
to
distill
like
all
the
time.
It's
about
distilling
information.
So
it's
more
relevant
for
this
specific
project.
A
I
can
just
control
F
on
my
lot
of
page
and
find
it
in
a
second
like
within
five
seconds,
like,
for
example,
so
I
was
working
on
a
3d
printer,
extruder
control,
F,
3d,
printer
extruder
and
I'll,
get
a
bunch
of
links
and
just
to
emphasize
put
don't
put
a
wall
of
your
work
here.
Just
put
the
links
to
other
pages.
That's
the
hyperlinking
part,
that's
a
very
powerful
concept.
A
Anything
that
I've
done
and
say
I
when
I
look
at
your
like
okay.
How
are
you
doing
on
a
video?
Well
I
would
expect
a
thing
like
say
the
d
3d
Universal
idea
diagrams
or
something
whatever
you
put
a
look
like.
If
I
don't
know
the
title.
I
just
go
on
your
log
and
if
I
know
you
you
committed
to
doing
that.
Like
next
Friday's
meeting
I'll
go
to
Friday
and
I'll
say:
hey
where's
wood
it
in
do.
Where
is
that
I
can
find
that
in
seconds
yeah?
A
So
it's
you
can
have
a
team
of
many
people.
I
would
say
that,
like
for
one
manager,
what's
the
limit
of
how
many
people
we
can
follow,
I
think
it's
like
Dunbar's
number.
You
know
that
number.
So
Dunbar's
number
is
the
size
of
a
village
or
the
size
of
people.
The
number
of
people
that
any
one
individual
can
know
face
to
face.
That's
about
between
100
and
200.
You
can
say
it's
like
12
by
12
144,
but
that's.
A
Size
of
a
village
and
it's
the
amount
of
people
we
can
actually
know
face
to
face
before
like
we
completely
are,
you
know
before
we
were
strangers,
but
I
think
that
applies
here
like
if
I
have
a
team
of
my
people,
you
know
I
think
I
can
handle
like
a
hundred
people.
I
can
know
exactly
what
they're
doing
and
then,
after
that,
you
would
need
more
like
dedicated
managers
who
maybe
know
like
what
a
bunch
of
projects
exist.
But
the
point
is
you
can
scale
that
kind
of
collaboration
through
this
very
simple
tool.
A
So
the
idea
on
the
wiki
is
that's
very
important,
like
just
document
all
this
stuff,
because-
and
don't
worry
like
oh
well,
word
put
it
where
am
I
gonna
find
just
just
put
it
up
there,
so
we
don't
lose
it
if
it's
important
information,
because
indexing
can
happen
afterwards,
like
save,
have
a
bunch
of
messy
pages.
That's
the
separation
between
content
and
its
presentation.
A
Yeah
the
wiki
is
a
database,
so
you
can
organize
it
and
as
exquisite
detail
as
you
as
you
like,
like,
like
all
the
assets
for
like,
for
example,
on
a
printer
like
they're.
All
scattered
all
over
the
place,
but
if
somebody
takes
HTML
CSS
to
it,
they
can
organize
it
into
something
that
looks.
Super
professional
and
wikipedia
has
got
a
bunch
of
templates
and
other
things.
We
have
some
templates
that
we
use,
but
you
can
completely
use
templates.
Html
CSS
like,
for
example,
to
show
you
an
example
of
a
template.
A
So
all
of
this
is
live.
Editable
information
completely
alive,
not
dead,
like
that's
the
beauty
of
it,
the
internet,
the
things
keep
living
and
you
can
put
links
to
make
this
very
easy
to
to
work
on
like,
for
example,
if
we
have
a
Google,
slides
presentation
embedded
underneath
that
you
want
to
click
it
put
put
on
an
edit
link
so
that
people
can
can
edit,
but
also
in
the
Google
Doc
itself,
open
it
up
to
open
editable
like
by
anybody
in
the
world.
We
do
that.
A
Most
of
the
time,
because,
if
you're
collaborating
it's
like
it'll,
be
a
pain
to
like
okay,
now,
I'm
gonna
share
it
with
you,
Sam
yeah
too
many
people
just
blank
it
open
it
and
cool
thing
about
Google,
Docs
and
wiki.
It
has
a
version.
History,
don't
worry
about,
vandalism
actually
never
had
vandalism.
Yet
over
the
decade
of
the
project
like
where
people
like
going
to
your
document
and
just
like
trash
it
yeah,
it
just
doesn't
happen.
A
A
A
For
example,
that
document,
if
I,
were
to
say
possibly
it
that
should
link
me
to
it.
It
went
to
this
editable
Doc,
but
actually
see
there.
I
wasn't
as
vigilant
about
I
have
certain
people,
since
that's
kind
of
like
a
high-level
document
like
some
documents
which
are
high-level,
like
you
just
want
to
close
up,
but
most
working
Docs,
at
least
the
working
docs.
You
go
there.
A
So
there's
the
share
button
and
in
it
you
always
want
to
go
to
like
advanced
anyone
like
change
the
main
permission
to
say
that
on
public
on
the
web,
anyone
can
edit
that
I'm
gonna
cancel
it
for
now.
But
but
that's
like
the
default.
If
you
got
a
working
back,
you're
working
things
out,
it's
like
people
are
collaborating
just
just
open
it
up,
don't
worry
about
it,
but
that's
a
cultural
thing
like
some
people
are
like.
A
Oh,
what's
somebody's
gonna
trash
it
I
can't
do
that
like
people
are
not
used
to
that,
but
you
gotta
get
used
to
the
idea
that
it's
okay
and
we're
all
here
to
collaborate
and
work
together,
because
the
idea
is
it's
like
the
good
old
fight
of
good
versus
evil.
There's
probably
gonna
be
more
good
guys
that,
like
say
somebody
sees
somebody
trash,
something
they'll
fix
it.
That
does
work.
The
idea
that
when
you
have
like
X
greater
than
Y
X,
is
the
good
guys.
Y
is
the
number
of
the
guys.
A
Typically
X
is
greater
than
Y.
That's
the
case.
The
things
will
go
up
in
quality,
not
reducing
quality
right.
So
that's
a
that's
another
principle
and
going
back
a
little
bit
to
the
court,
the
grand
coordination
of
how
you
work
together,
collaboration
protocol.
Well,
the
first
thing
that
we
actually
got
to
think
about
is
all
getting
aligned
to.
What
are
we
doing
here
so?
A
The
first
thing
we
got
to
start
with
is
OSC
is
working
on
a
global
village
Construction
Set
week,
that
least
50
machines
that
include
the
3d
printer
and
many
much
more
and
the
goals
there
are
2028
is
the
current.
We
have
a
critical
path
document
online
you
can.
You
can
see
that
the
point
is
that
by
2020
80
will
finish
all
the
machines
and
anything
that
I
say
to
anybody
is
revolves
around
that
and
like
the
people
who
join
a
team,
everyone
has
to
be
on
the
team
to
say
that.
A
Ok,
we're
doing
that
and
therefore,
if
you're,
one
of
the
hundreds
of
schools
that
universities
are
the
osc
classrooms
that
want
to
collaborate
start
with
that.
You
know
you
have
to
start
with
that
goal,
and
then
you
can
say:
ok
well
that
we've
got
these
50
projects
do
I'd
like
something
in
there.
Oh,
maybe
it's
the
electric
car
so
then
go
at
it.
Understanding
that
2028
were
seriously
aiming
to
finish
all
of
this
up
to
like.
What's
the
left
last
level
of
technology,
we
have
up
to
the
some
of
the
most
advanced
things.
A
Are
induction
furnace,
which
means
you
can
take
metal
and
get
virgin
steel
sections
to
build
anything,
any
heavy
machine,
our
cars
or
whatever
the
ability
to
melt
steel
and
then
roll
it
and
make
wire
and
make
sheet?
That's
part
of
the
set?
That's
in
there.
This
high
have
metal
processing
it's
in
there
and
then
there's
even
a
one,
even
more
funky
one,
which
is
still
doable
that's
extraction
of
aluminum
from
clay.
You
got
dirt
out
there.
You
can
make
aluminum
right
here.
A
You
can
make
these
printers
if
it
wouldn't
be
steel,
they'd
be
aluminum,
but
that's
the
limit.
If
you
have
system
energy,
which
that's
the
basic
principle,
you
have
ten
thousand
times
more
power
that
comes
from
the
Sun
that
we
use
today,
even
with
fossil
fuels
like
fossil
fuels,
which
are
stored
energy
over
a
long
history,
we've
got
plenty
of
power,
so
things
crazy
things
like
making
aluminum,
that's
just
a
bunch
of
processes.
It's
like
metal
vessels,
electricity,
gears
and
motors,
and
maybe
some
vacuum
pumps
here
and
there
and
there
you
go.
A
A
Let's
have
a
little
places
than
earth
like
the
Moon
and
Mars
I
could
actually
got
a
few
invitations
this
year
too,
like
space
conferences,
people
are
saying:
okay.
Well,
how
do
you
good
strap
civilization,
where
there's
no
resources?
Well,
you
gotta
make
them
from
the
rocks
and
twigs
whatever
you
got
there.
So
those
are
the
goals,
so
the
making
metal,
that's
advanced,
civilization
and
then
make
an
aluminum,
that's
also
advanced
civilization,
but
also
a
Nam.
A
So
those
are
the
formerly
the
machines,
but
with
all
the
different
machines
like
save
Gottman,
cnc
machining,
the
ability
to
make
anything
from
metal,
you
can
then
go
to
other
things
like
how
about
silicon
production
for
solar
cells
or
even
microchip
production
from
silicon
and
some
dopants,
like
that's
all
known
technology.
It's
been
around
for
decades,
we're
saying:
okay,
well,
let's
open
source
that
so
that,
like
doles
out
like,
for
example,
the
chip
making.
That's
like
some
of
the
most
concentrated
proprietary
stuff,
but
it's
also
very
important
because
kind
of
runs
our
world.
A
A
Where
you,
if
you
don't
know
the
chip
design,
you
don't
know
what
that
chip
is
doing
so
like
with
things
like
spying
and
security
issues.
Those
are
real
issues
for
a
lot
of
people
like
I'm,
not
worried
about
it
myself,
but
that's
my
my
feeling
on
it
because
I
think
there's
because
we
can
solve
that
readily.
If
we
open-source
the
design.
That's
that's
what
I
say:
it's
like
I'm,
not
gonna,
spend
time
worrying
about
it.
A
I'm,
just
gonna
get
busy
doing
the
open-source
version
of
that,
so
that
we
have
that
security,
which
is
gonna,
be
a
huge
value
once
that
does
come
out
like
everyone's
gonna
want
that,
because
you
want
security,
you
don't
want
people
spying
on
you
at
NSA,
spying
on
you
or
whatever.
So
that's
starting
with
a
big
vision.
Okay,
that's
that's
the
goals.
A
The
global
village
construction
set
finished
by
2020,
and
so
we've
got
like
eight
years
and
we're
at
a
time
where
we're
just
starting
to
get
some
of
the
enterprises
with
steam
camps
of
printer
production
by
this
summer,
we're
aiming
to
produce
cnc,
torch
tables
and
tractors
in
addition
to
the
larger
printers,
so
we're
just
moving
right
along
now,
so
you
say
you
have
the
GBCs
50.
The
other
important
thing
is
is
to
talk
about.
A
The
construction
set
approach
like
I
did
a
diagram
where,
where
I
showed
that
when
we
make
it
safer,
attract
or
let's
say
that
say
the
printer
here-
we
use
the
universal
access.
It's
a
construction
set
in
the
sense
that
you
can
build
a
different
version
of
that
or
you
can
scale
it
and
modify
it
to
make
other
machines
like
C&C,
torch
tables
or
even
heavy
duty
machines
when
the
rods
in
there
are
not
8
millimeters
but
like
3
inches
up
to
3
inches
using
similar
types
of
geometries.
A
So
scalability,
Construction,
Set
approach
means
that
you
build
building
basic
building
blocks
and
you
can
do
a
lot
with
it.
So
we
we
use
that
a
lot
with
the
construction
set
approach
comes
the
ability
to
produce
multiple
machines
from
a
small
core
set
like
Legos.
So
that
decreases
the
amount
of
information
or
skill
that
somebody
developing
with
it
needs
to
have,
because
you
can
work
with
the
existing
modules
to
make
like
a
novice,
could
pretty
much
take
this
basic
design
and,
for
example,
design
the
second
z-axis
to
make
it
really
good
for
milling.
A
You
know,
or
you
can
make
the
larger
deeper
you
crawl
with
it
or
larger,
like
up
to
like,
say
two
feet
with
this
kind
of
access.
It's
about,
like
you,
can
make
about
two
bike
to
put
print
beds
like
3/4
meter
or
something
like
that.
So
that's
the
construction
set
approach.
Now
the
engineers
could
actually
redesign
the
the
modules
themselves.
They
can
go
deeper
into
the
technology
to
make
better
modules
where,
as
novices,
can
completely
work
with
the
modules
like
Legos
to
use.
A
What's
already
there
as
the
novice
gets
better,
they
get
more
engineering
skill
to
do
the
deeper
level
of
redesign
using
all
open-source
tools.
So
there's
the
modularity
on
the
machines,
then
what
about
the
modularity
of
the
development
process?
So
we
have
the
50
machines,
we
break
modular
Lee,
we
break
each
one
into
like
a
dozen
modules.
Like
you
know,
you
can
go
okay,
you
have
the
axes.
You
got
the
control,
you
got
the
base,
you
got
the
extruder.
You
can
further
break
that
down
into
things
like
one
aspect
of
the
controller.
A
Let's
say
the
ramps
board
controller
board.
You
can
break
it
down
into
into
saying.
Oh
well,
that's
got
three
different
axes
and
you
can
develop
teach
access
to
optimize
it.
There's
a
bed
module
which
you
can
add
things
like
heat
to
it
or
whatever,
or
we
actually
have
an
insulated
heat
bed
and
ours
which,
like
the
only
printer
in
the
world
that
has
that
for
the
v3d
pro
as
we
want
to
save
30%
energy
I'm
using
that,
so
you
can
develop
into
module
level.
So
after
the
modules.
A
A
Machines
development
so
on
our
main
website,
chuckle,
oh,
but
how
how
this
development
process
looks
well.
First
of
all,
you've
got
instruction
sets,
so
we
break
this
down
into
like
tractor
construction
set
universal
rotor
construction
set,
wrote,
universal
rotors
could
be
things
like
augers
or
even
wheel,
drive
units
you
can
have
construction
sets
for
electronics
for
hydraulics
for
electric
motors
and
everything
so
break
it
into
a
generative
approach,
but
then
more
important
than
that.
That's
the
basic
philosophy
of
it,
but
and
more
important
than
that.
A
You
have
the
breakdown
of
machines,
so
you've
got
a
machine,
you
break
it
into
say
a
dozen
modules
and
then
for
the
dozen
modules
you
go
through
about
40
development
steps
or
20,
depending
on
like
how
advanced
you
want
to
get
so
at
for
each
machine.
You
got
say:
12
modules
say:
20
development
steps
12
times,
20,
it's
like
240
right
there
you
go
through
several
versions
of
each
machine,
so
there's
like
three
four
or
five
and
we're
up
to
like
seven
on
like
the
power
cube
and
other
things.
A
So
it's
like
a
thousand
items
already
for
one
machine
that
you
have
to
track.
If
you
got
50
machines,
you
got
50,000
items
right
there
and
you
can
multiply
that
even
further,
because
technology
is
one
aspect,
but
the
second
aspect
is
actually
the
the
enterprise
development.
So
there's
like
way
more
aspects,
but
this
gets
into
taxonomy.
So
what
are
all
the
development
steps
that
you
need
to
know?
While
this
comes
from
the
standard
product
development
process?
A
There's
standards
are
already
that
anyone
who
designs
products
already
knows
like
you're
gonna
come
up
with
requirements,
concept
and
technical
design.
Then
you
got
build
procedures.
You
got
data
collection
and
you
got
testing
there's
a
bunch
of
different
steps
that
are
well
known
and
we
just
simply
follow
those.
So
so
then,
how
do
you
find
something
on
it?
On
a
wiki?
We
followed
that
taxonomy.
So
we
say
3d,
printer
extruder,
there's
this
sub
mantra.
So
you'd
have
a
page
called
3d
printer,
extruder
fabrication,
diagram.
A
So
so
you
go
to
defeat
of
Universal
and
I
would
put
in
CAD
so
C
ad
and
the
way
it
works
is
off
so
enter
and
there's
no
page.
So
what
you
can
do
here
is
redirect
it
to
where
it
actually
is.
So
this
is
like
what
we
can
all
do,
but
if
you
don't
find,
if
you
get
a
result
like
this,
then
go
back
to
D,
3d
universal.
It
must
be
there
so
yeah
if
you
go
to
be
3d
Universal,
there's
a
CAD
right
there.
A
C
A
A
A
We
also
use
a
little
bit
of
project
management,
so
on
each
development
page
we
would
embed
like
a
scrum
board.
We
have
tasks
and
people
can
sign
up
to
that
different
tasks.
So
that's
we
were
using
scrum
II,
which
looks
like
see.
They
just
took
it
down
a
couple
of
months
ago.
So
we're
looking
for
another
scrummy
alternative,
some
very
lightweight
thing.
You
can
embed
in
a
website
that
you
don't
it's
like.
You,
don't
have
to
go
to
another
site
like
on
top
of
we
had
to
the
last
team.
A
A
A
A
Plus
value
proposition
like
what
are
you
trying
to
do
here,
you
know
like
with
a
printer,
we
want
to
say:
oh
we're
doing
a
printer.
That's
got
the
lowest
unique
part
count
in
the
world,
it's
scalable
and
modular,
so
you
can
add
any
different
tool
head
to
it,
like
that's
part
of
our
requirements
and-
and
it's
also
industrial
great
in
the
sense
that
you
can
bootstrap
it
up
to
more
industrial
machines.
A
That's
requirements
in
this
item
to
is
industry
standards
so
before
he
built
this,
we
we
study
what
people
have
done
so
for
this
industry
standards
would
be
RepRap
project.
So,
whatever
you
start,
you
better
believe.
There's
somebody
else.
That's
done
that
before
and
it's
worthwhile
to
document
who's
done
something
else
before
so.
That's
then
go
to
conceptual
design.
A
A
B
A
So
then,
okay
module
would
break
down.
So
that
means
you're,
allowing
many
more
people
to
collaborate.
You
got
3d
CAD,
it's
obvious
calculations
like
say:
you've
got
extruder
calculations
based
on
the
heat
input
to
the
extruder.
This
is
how
much
filament
we
should
be
able
to
make
melt
per
hour
and
it'll
get
you
insight
onto
extrusion
rates,
and
then
you
can
verify
that
in
data
collection
later
later
on,
but
you
want
to
start
with
like
okay.
A
This
is
that
working
like
oh,
that
may
be
extremely
too
slow
or
not
slowing,
like
you'd,
be
able
to
get
insights
from
making
calculations.
You
can
do
calculations
on
a
lot
of
things
like
including
cost
calculations,
weight,
calculations,
print
time,
calculations
based
on
from
your
cab.
You
can
do
all
that
electronics
design,
that's
the
circuitry
wiring
and
plumbing
so
like
there's
the
design
with
a
controller
board,
but
the
wiring
is
how
you
connect
everything
together
for
plumbing
they'll,
be
more
for
like
hydraulics
and
and
house
plumbing
systems,
software,
obviously
there's
software.
A
So
then
you
go
into
the
next
main
section
is
the
Bill
of
Materials.
So
we
have
a
B
om,
the
main
builders.
All
all
that
is
found,
for
example,
for
the
printer.
You
can
look
all
the
parts
there's
like
I,
think,
80
or
so
V
BOM.
We
do
a
visual
bill
materials
where
we
cut
and
paste
images
of
the
actual
things.
You
can
take
a
look
at
examples
each
by
the
way
you
can
click
on
each
one
of
these
and
it'll
show
you
examples,
cam
files,
so
computer-aided
manufacturing
files.
A
In
our
case,
that's
the
G
coder
files
which,
if
we
have
a
stable
version
of
this
exact
3d
printer.
Yes,
that
g-code
file
will
work
for
the
next
printer,
that's
identical,
but
in
case
you
have
different
printers.
You
need
the
STL
files
to
generate
the
manufacturing
files
from
because
you
have
different
geometries
and
stuff
cut
list.
So
cutlass
is
important.
If
we're
making
this
printer,
you
say
we
say:
ok
get
get
six
rods.
There
are
12
inches,
one
rod,
that's
six
inches!
The
board
is
cut
to
this
length
and
there's
wire
lance.
A
So
you
want
to
list
all
that
next
is
the
build,
build
instructions,
obviously
fabrication
drawings.
So
those
are
more
like
graphical
drawings
of
how
you
have
one
part.
Maybe
you
can
cut
that
out
of
CAD
and
show
how
you
have
these
two
parts.
They
go
make
this
part
and
you
can
do
to
do
like
a
tree
diagram
how
it
comes
together.
A
No,
actually,
there
was
fabrication
drawings.
So
that's
the
thing
you
can
get
out
of
cat
I
was
pretty
and
fabrication
drawings
explode
apart
diagrams,
so
so
clear
diagrams
like
that
Production
Engineering,
which
would
be
like.
How
do
you
actually
what
tools
you
use
and
how
do
you
build
it
like?
If
we
build
the
extruder
heater
block,
all
I
did
was
a
cut-off
saw
and
a
drill
press,
it
wasn't
CNC
and
high
quality
controlled.
A
So
that's
the
production
engine
we've
used
and
we
found
that
this
time
around,
like
there's
limits
to
that,
because
we
got
like
twenty
percent
failure
rate
like
one
of
the
five
was
not
working
well
on
the
other
ones.
We
have
to
kind
of
modify
buddy
I
like
see
and
see
that
we,
like
the
next
level
production
engineering,
where
you
say:
okay,
hey
just
put
this
on
a
CNC
mill,
and
this
is
how
you
do
it,
which
you
can
outsource
or
build
in-house
there's
data
collection,
so
build
pictures
and
videos.
You
know
for
this
build.
A
We
should
have
a
section
on
the
wiki
that
does
that
data
collection.
Ok,
the
data
collection
is
like
oK.
We've
got
these
getting
measured,
B's
and
he's
gonna,
say
okay,
but
on
this
one
millimeter
nozzle,
we
actually
got
walls
that
are
exactly
1.05,
millimeters
and
stuff.
Like
that,
a
lot
of
a
lot
of
data
you
can
collect
on
everything
like
what
the
issues
were
in
the
build
process
and
then
there's
future
work.
So
that's
the
twenty
basic
ones.
Now
you
can
expand
that
to
more
like
there's,
there's
them
actually
on
very
top.
A
There
is
the
full
development
template
which
has
got
40
items
and
you
can
get
more
specific
I'm,
just
getting
more
and
more
detail,
but
so
now
to
answer
your
question:
okay,
where's
an
example
of
that.
We
have
very
few
examples
which,
where
everything
is
complete,
because
you'll
see
that
this
requires
hundreds
of
people
so
yeah.
So
the
best
we
have
is,
let's
show
an
example.
What
let's
look
at
the
CB
print?
I
mean
C,
be
press
as
far
along
so,
for
example,
I
think
we
can
find
one
under.
A
A
Let
me
so,
let's
be
true
to
what
I
just
said,
so
CB
press
press
development
template,
so
that
should
be
a
page
and
if
it's
not,
this
is
once
again
I
can't
not
do
like
fifty
thousand
these
pages
myself
so
but
at
the
CB
press
development
template,
you
know
it's
only
one
of
fifty
I
should
have
probably
done
that
at
some
point,
no
power
cube
development
template.
So
this
is
where
people
can
fill
it
in
so
power
cube
is
another
one
of
our
machines
power,
cube
development,
template
nope.
A
A
A
Can't
find
a
good
one
like,
but
the
idea
is
you
have
versions,
and
so
let
me
go
to
versions
how
that
works.
Cuz,
that's
like
what
we
found
is
that
initially
we
had
documentation
and
in
the
wiki
kind
of
collapsed,
because
then
a
person
does
the
next
version,
and
then
you
don't
know
which
is
which,
because
versioning
it's
more
complex
than
github
the
official
way
to
version
it
is
that
you
fork
the
entire
project
and
you
start
afresh
and
that's
your
version
there,
but
yeah,
but
even
I'm,
giving
this
that's
limited.
Cuz.
A
A
So
select
from
that
3d
printer
genealogy,
they
look
at
all
the
versions.
We've
already
done.
That's
what
I'm
saying
each
one
of
these
would
have
your
full
development
template.
You
might
find
one
like.
Maybe
let's
see
1806
does
that
have
a
development
template
there.
It
is
and
that's
what
we
filled
out
in
that
one
and
we're
like
completely
done
with
the
requirements
like
study
of
industry
standards,
only
put
two
there.
Two
out
of
ten.
You
know
it's
not
really.
A
So
so
that's
how
it
works
and
we
even
have
like
we
have
a
thing
where
you
can
embed
it
burn
down.
So
that's
the
burn
down
for
this
actual
thing.
It
parses
this
thing
and
it
burns
it.
So
it's
like
we
stopped
at
like
45
percent,
and
then
we
carried
on
in
the
next
versions.
But
you
see
like
every
time
you
make
a
major
change.
You
we
create.
A
new
version
is
already
like
15
versions.
So
it's
like
so
I'm
saying
this.
This
requires
my
thinking.
Right
now
is
like
we
need
those
hundreds
of
chapters.
A
B
A
Get
an
idea
of
this:
let's,
let's
talk
about
some
of
the
critical
things
like
so
wiki,
taxonomy
I
described
how
you
can
find
any
page.
That's
you
know
it's.
You
have
to
study,
it's
there's
versioning,
where
there's
a
protocol
of
how
you
do
that,
so
you
gotta
kind
of
read
through
this.
But
there
is
a
like
there's
like
five
hundred
thousand
I
say:
250
thousand
pages
and
theory.
You
should
be
able
to
just
type
in
power,
cube
version.
Nineteen
point
which
is
October
of
2019
and
hydraulics.
A
That's
one
of
the
many
hydraulics
build
instructions
that
should
be
there.
Yep
there's
properly
done,
I
can
guarantee
you.
Most
of
this
is
not
done.
There's
a
lot
of
prominent
stuff
that
is
done
like
like
you
should
be
able
to
find
like
if
you
want
to
find
a
printer,
what
I
would
say,
Paige
look
at
the
last
printer
click
on
that
and
then
see
the
older
assets
there.
There
should
be
a
template
if
it's
not
start
one.
So
this
is
like
work.
A
If
everybody
has
that
understanding
by
reading
wiki
taxonomy
by
reading
the
collaboration
protocol,
then
you
should
pretty
much
be
able
to
do
that
and
that's
that
that's
basically
a
maintainer
somebody
who
understands
how
this
is
structured
and
all
that,
but
a
maintainer
has
to
be
involved
in
development,
because
otherwise
they're
not
going
to
know
like
enough
about
the
thing
like
what
the
modules
of
this
machine
are
like
the
maintainer
has
to
have
a
lot
of
info.
They
they
should
be
a
developer.
A
So
right
now
it's
like
the
ideas
there
needs
to
be
thousands
of
people
working
on
just
like
Linux
I
mean
this
is
Linux
times
100.
So
that's
why
it's
a
massive.
We
need
hundreds
times
more
people,
so
that's
kind
of,
but
do
take
a
look
at
the
collaboration
protocol.
That's
like
the
main
page
that
definitely
leads
you
to
so
there's
work
logs.
A
A
The
basic
format
is
you've
got
all
the
parts
listed
as
little
things.
You've
got
a
file
if
you
click
on
a
file,
the
free
CAD
file
for
the
frame.
You
should
see
a
version.
History
there's
only
one
frame
there,
but
you
will
see
like
say
for
this:
one
free
CAD
this
this
part
of
the
motor
piece.
You
know
we've
gone
through
many
iterations,
starting
in
2017
and
2019,
but
you
can
download
the
old
version.
You
can
now
upload
a
new
version
of
this,
so
this
has
got
a
built
in
version
history
to
it
as
well.
A
But
the
part
library
is
what
we
do
like
I
like
to
point
to
the
part.
So
that's
the
d30
universal,
the
part,
libraries.
What
you
see
there
each
part
has
got
a
freaking
file
and
an
STL
file
for
printing
for
the
printed
parts
above.
What
we
actually
do
is
this
kind
of
like
a
visual
history
where,
for
each
part
that
we
did
we
kind
of
like
put
a
snapshot,
so
you
can
kind
of
trace
how
the
the
machine
was
kind
of
designed
all
together.
A
So
it's
kind
of
helps
you
out
to
get
oriented
like
if
there's
like
a
hundred
people
developing
this
actively,
then
I
would
look
at
this
person's
and
observe
like
okay,
which
new
part
has
been
made.
If
I'm
an
active
development,
I
can
kind
of
see
quickly
as
opposed
to
having
a
wall
like
a
hundred
files
have
to
read
the
name,
and
you
don't
know
how
it
looks,
but
here
we're
trying
to
use
these
visual
histories
to
do
that.
But
that
concept
here
is
a
large
team.
A
So
so
right
here
on
this
one
module,
you
can
have
two
four
six,
eight
ten
twelve
people,
20
people,
30
people
developing
all
those
modules
uploading
downloading
each
each
one
can
have
a
few
people
on
it
and
that's
just
for
one
module
that
then
there's
the
other
modules
that
extruder
down
here.
There's
another
module.
So
already
here,
we've
got
like
a
hundred
thing.
Hundred
people
have
to
be
developing
activate
like,
for
example,
this
is
the
3d
printed
bushing.
So,
instead
of
the
bearings,
the
linear,
bushings
that
we're
using,
we
can
3d
print
them.
A
We've
done
that
we're
refining
them
we're
not
putting
that
into
the
final
version,
because
we
haven't
developed
them
enough,
but
you
can
be
developing
everything
I
here,
for
example,
Sam.
You
can
now
add
to
this
free
CAD
file,
like
you,
you
can
add
like,
for
example,
the
digital
like
instead
of
the
STL
files,
you
can
also
add,
like
the
the
milling
files
to
that.
C
A
Yeah,
you
have
to
look
at,
you
have
to
basically
yeah,
but
the
first
peer
review
is
the
fact
that
someone
was
from
outside
the
project.
They're.
Not
even
gonna
know
this
exists,
so
they're,
probably
already
on
boarded
as
a
developer,
and
then
they
probably
are
working
like
coordinating
like
say:
you've
got
your
team
here,
they're,
probably
coordinating
with
you
and
you're,
overseeing
that,
so
you
could
taken
there
free
to
upload
it,
but
if
you're
the
the
maintainer,
you
can
say
no
I,
don't
really
like
it.
A
Yeah
see
the
way
we
do
it
right
now.
Here,
like
you,
can
have
pages,
where
the
way
to
address
that
is,
you
can
have
like
the
official
versions
go
into
the
indexed
part
library.
The
the
major
part
library
thing
like
that.
The
this
one
worked,
which
has
the
major
projects
like
we
can,
for
example,
lock
this
down.
So
only
the
maintainer
x'
would
be
able
to
add
the
official
versions
and
you
can
have
other
working
progress
versions,
yeah.
A
So
one
way
to
address
that
is
the
person
who
does
that
they
put
a
link
on
that
to
their
log,
for
example,
and
then
the
maintainer
would
say:
okay
well
actually
like
this
I'm
gonna,
just
upload
it
to
the
main
version
there.
So
there's
different
ways
to
address
it
but
see
like
if
you
have
so
many
people
working
on
it.
A
The
best
way
to
do
it
is
the
way
we
found
works
really
well
like
they're,
like
nobody
controlled
who
put
it
up,
but
I
know
that,
for
example,
Michelle
and
Chris
were
working
on
a
part
and
I
trust
them.
They
they're
gonna
make
good
changes
like
they're,
gonna
print
them
out
and
test
them
and
give
stuff
on
their
log.
So
it's
like
it's
self
management,
but
for
dad
you
have
to
have
the
people
that
know
how
to
do
that,
and
that's
the
collaborative
literacy
for
how
we
get
thousand
the
people
working
on
that
yeah.
C
A
Yeah
definitely
like,
like
okay,
so,
for
example
like
if
you've
got
this
yeah,
that's
completely
doable
because,
like
okay,
so
you
take
this
part
here,
the
freakout
file
and
you
think,
like
oh,
maybe
like
I,
just
cleaned
up
something
in
that
part
tree
even
like
in
the
freakout
file,
feel
free
to
upload
it.
And
then
what
we
can
do
is
just
put
notes
here
and
say:
oh
well,
the
13th
June
version
it's
the
same
as
the
last
one,
but
it's
got
this
thing
cleaned
up.
A
If
you
want
the
former
one
for
another
purpose,
just
do
that,
but
typically
you
want
to
have
one
on
top.
Where
no
I
mean
it
could
be
anywhere
in
there,
because
then
the
thing
is,
you
can
index
like,
say,
say:
the
person
wants
to
print
out
the
entire
printer
with
the
updated
parts.
You
can
have
another
page
on
the
wiki
which
just
lists
links
directly
to
the
parts
that
you
need,
whereas
maybe
like
this
repo
here
it
has
everything
in
there.
So
there's
different
ways
to
go
about
it.
A
But
typically,
what
we
do
here
is
that
sometimes
I,
like
typically
I,
just
download
the
latest
file,
but
sometimes
to
see.
Oh,
that's
the
file
like
the
SDF
file,
which
has
like
four
of
them
nested
on
embed,
no
I
just
wanted
a
single
one,
because
I
just
want
to
print
one.
So
you
look
at
that
because
there's
descriptions
here
or
there's
notes
that
people
make
and
you
can
see,
okay,
which
is
which
so
I
mean
we're
trying
to
come
up
with
a
way.
A
A
Like
there's
a
few
elements
you
need
to
know,
and
then
you
can
just
go
at
it
and
then
it's
more
or
less
self
managing,
but
but
that
self
management
is
it's
expensive.
It's
it
takes
a
lot
of
effort
like
as
I
said,
Wikipedia
spends
30
million
dollars
a
year
to
manage
their
contributions.
That's
their
budget
right,
so
it's
not
like
high
high
coordination
is
not
cheap,
but
here
hopefully
we
have
a
like
a
unifying
vision.
A
Okay,
we're
gonna
do
in
this
kernel
this
new
operating
system
for
Earth,
which
is
you
know,
it's
not
a
small
task,
we're
saying.
Okay,
we've
got
these
this
redesign
of
society
for
doing
stuff
in
an
open-source
way
in
terms
of
its
technology
base,
we're
trying
to
do
the
best
to
teach
it,
but,
as
I
said,
the
biggest
block
is
the
collaborative
literacy.
A
The
mindset
of
people,
where
everyone
thinks
that
you
got
to
get
patents
and
not
collaborate
to
get
ahead,
which
is
one
way
to
do
it,
but
I,
don't
think
it's
as
effective
as
open-source
and
I
think.
People
will
see
that
over
time,
like
they've
seen
it
now,
and
software
very
clearly
and
the
same
isn't
just
coming
for
hardware.
It's
just
a
matter
of
time.
We're
not
there
yet.