►
From YouTube: Incentive Challenges and Development Template Details
Description
What you see here at Open Source Ecology is an ambitious program based on a volunteer effort. To help us reach the goals - please consider joining as an OSE Developer in 2017-
http://opensourceecology.org/wiki/OSE_Developers
Take a minute to subscribe to our email newsletter (updates, workshops, etc): http://bit.ly/1LtcM44
A
Yeah
we're
going
okay,
so
I
wanted
to
talk
about
just
just
in
terms
of
a
global
collaborative
development.
What
kind
of
understanding
is
required
between
the
different
people
that
engage
in
it
so
that
people
can
collaborate?
And,
of
course,
you
have
to
have
a
in
order
for
that
to
happen.
People
have
to
be
familiar
with
the
process
and
then
to
begin
with
the
idea
that
public
development
is
possible,
a
lot
of
people
are
used
to
simply
working
working
in
secluded
ways,
not
really
large
collaborative
teams.
A
So
I
talk
how
how
the
mindset
of
collaborative
development
well
as
long
as
the
number
of
people
share
that,
then
it
can
happen.
Well,
the
main
challenges
for
hard
open
hardware
is
that
not
a
lot
of
people
do
know
about
this
kind
of
work.
It's
not
part
of
familiar
culture.
So
it's
a
challenge
of
incidence
and
the
way
you
get
over.
That
is
that
there's
enough
people
that
actually
do
it.
A
So,
for
example,
in
20
2012
we
did
the
open
source
hardware
documentation
jam
where
we
defined
a
basic
taxonomy
for
what
documentation
should
include
should
include
things
like
the
project
name,
the
version,
the
repository,
the
history
of
the
project,
things
like
that,
there's
there's
certain
things
you
have
to
document
for
a
project
for
new
projects
to
build
upon
it.
But
you
know
no
matter
what
we
do
on
that.
You
know
we
can
have
an
advanced
excellent
development,
template
or
procedures
within
the
wiki,
but
but
the
other
missing
requirement
is
people.
A
We
need
to
have
people
to
do
that
without
that,
whatever
you
do,
it's
like
writing
an
academic
paper
or
whatever.
Unless
people
read
it
or
unless
people
know
about
it,
you
don't
get
buy-in
so
so
the
second
challenge
is
is
getting
people
a
number
of
people
that
do
engage
in
open,
open
economic
development
is
so
small
that
effectively
in
the
economy
that
doesn't
exist.
So
what
do
we
do
about
it?
A
The
techniques
that
we're
developing
here
are
based
on
the
wiki
cloud,
collaborative
collaborative
Doc's,
common
tools,
as
I
mentioned,
and
we
used
some
other
other
things
like
the
design
jams
that
we
will
be
developing,
which
I
talked
a
little
bit
about
before,
and
the
incentive
challenges
which
are
a
way
to
get
of
that
awareness
into
a
much
greater
public.
So
platforms
like
the
XPrize
foundation,
I
mean
those
are
well-known
things
that
that
get
many
people
involved
in
the
deep
way.
A
So
so,
when
you
throw
up
a
prize
like,
for
example
like
say
the
automotive
x
prize,
I,
don't
know
what
it
was
like
that
think
they,
they
threw
a
carrot
on
a
stick
of
like
a
million
dollars
for
the
winning
entry
right
now.
I
believe
some
of
that
is
continuing
as
startups
that
are
trying
to
still
kick
that
off,
but
that
basically
a
lot
of
people
excited
about
it.
People
worked
on
it
and
the
teams
that
didn't
work
on
it
put
in
millions
of
dollars
of
development
for
a
million-dollar
prize.
Well,
how
does
that
happen?
A
It's
just
part
of
the
psychology,
it's
an
incentive
challenge
that
does
work.
So
we
do
know
that
if
we
follow
other
projects
that
have
done
that
successfully
life
like
the
XPrize
foundation,
we
know
that
incentive
challenges,
work
so
and
that
is
now
quite
accessible
to
many
people
well
to
anyone.
Actually,
anyone
who
who
cares
to
do
it
there's
a
book
called
bold
by
Peter
Diamandis.
A
Those
are
the
guys
behind
the
XPrize,
but
that
talks
about
all
the
methods
of
crowdfunding
and
crowdsourcing
for
the
reward
itself.
So
the
one
platform
we
are
to
use
as
part
of
the
emergency
program
and
something
that
we
want
to
go
forward
with
this
hero.
X
I
mentioned
that
this
board,
but
you
can
crowdfund
the
price
and
you
you
crowd,
you're,
basically
crowdsource
the
development
effort.
So
there's
two,
you
know
two
elements,
the
funding
or
the
prize
and
the
actual
work
that
people
doing
in
order
to
to
win
that
comes
in
from
from
the
crowds.
A
So
it's
an
effective
way
to
do
it
and
therefore,
how
do
we
do
it?
Well,
we
we
will
prepare.
So
the
two
projects
that
we
did
want
to
do
is,
as
I
mentioned,
the
cordless
drill.
We
are
gonna
try
to
do
that
session,
where
we
we
actually
3d
print.
Some
parts
get
a
motor
battery
pack.
Do
some
freak
out
on
that.
We
are
aiming
to
do
the
four
hour
session
on
that
to
see
how
far
we
get
on
that
project,
but
that
could
be
the
seed
of
the
heroics
challenge.
A
Where
that
we
document
what
we
have,
but
the
biggest
thing
is
designing
the
specification
and
then
this
is
designing
the
the
rules,
the
so-called
rules,
which
are
how
do
you
you
know
what
is
a
winning
entry
mean?
What
how
do
you
encourage
people
to
participate?
What
do
they
do?
What
are
the
rules
that
either
encourage
or
discourage
collaboration?
Our
challenge
is
going
to
be
to
write.
A
The
rule
is
such
that
it
maximizes
collaboration
and
kind
of
enforce
that
people
keep
uploading
stuff
to
the
wiki
use
common
formats
like
like
prefab
or
Park
libraries
that
we
already
use
within
the
global
village
construction
set,
so
that
when
someone
comes
into
that,
they
can
pick
up
on
that
and
build
upon
another
another
person's
work.
So
the
heroics
platform
is
something
we
will
be
doing
and
I'd
like
to
do
that
also
for
for
the
phone,
a
phone
which
is
a
tool
that
every
single
person
on
this
planet
uses.
A
So
both
a
cordless
drill
on
a
phone
cordless
drill
is
a
good
example
of
a
3d
printable
item.
The
phone
is
a
great
example
of
something
can
be
done
largely
with
a
CNC
circuit
mill.
Then
you
can
do
the
the
case
and
other
wrapper
wrapper
around
that
using
3d
printing.
But
right
now
we
have
access
to
all
the
mean
all
the
chipsets,
for
a
phone
like
your
GSM
module,
your
you
know
your
your
CPU,
your
screen,
like
touch-tone
screens,
those
things
all
cost
like
10
$20
these
days,
all
that
is
accessible.
A
A
Definitely
want
to
try
simply
because
everybody
has
one
and
I
do
believe.
There
is
a
enough
of
a
population
in
the
world
that
wants
to
hack
and
hack
their
products
are
environmentally
conscious
enough
to
say,
hey,
don't
be,
throwing
out
my
phone
every
couple
of
years
or
something
like
that.
I
know
that
my
phone's
right
here
I
mean
I'm
borrowing,
Katarina's
phone
I,
hope
I,
don't
crack
it
by
the
end
of
the
workshop.
I
mean
I.
A
Do
a
lot
of
I
do
a
lot
of
video
all
over
the
place
and
my
phone's
go
in
about
three
to
six
months.
So
for
me
it
would
be
a
very
direct.
You
know
direct
environmental
benefit
if
I
can
build
my
own
phone
and
then
then
be
able
to
replace
the
parts
about
truly
module
away,
yeah
yeah
and
exactly
that.
So
so,
let's
take
a
look
at
it.
A
There's
several
open
source
foam
foam
projects
that
are
already
so
called
doing
this,
like
yeah,
the
whatever
that
is
it's
actually
by
the
guy
that
did
precious
plastic
foam
blocks,
is
an
example
of
one
Google
took
over
that
some
other
groups
took
over
that.
Never
Tennant
enough
to
be
a
product.
I
think
that
failed,
there's
some
couple
other
ones.
That
also
did
that.
But
the
idea
there
was
I
mean
they
were
trying
to
go
for
a
full-blown
out.
Commercial
mainstream
will
kind
of
a
deal,
whereas
for
us
we
can
be
no
less
less
precise.
A
We
can
be
more
DIY
user
centric
and
make
it
happen
because
those
pieces
do
all
exist,
I
mean
in
the
worst
case.
We
wouldn't
have
a
phone,
that's
you
know
tight
and
as
much
as
palpable
as
this.
It
might
be
bigger,
more
bulky,
but
still
I
mean
if,
if
it's
that
basic
function,
I
I,
certainly
would
you
if
it's
something
like
the
size
of
an
iPod
or
something
still
I
would
still
want
to
use.
It
I
think
there's
many
people.
That
would
also
want
to
do
that.
A
So
our
current
plan
right
now
is
to
is
to
fundraise,
so
the
fundraising
or
the
incentive
challenge
one
you
can
do
crowdfunding
within
the
hero
acts
itself.
So
you
can.
You
can
spawn
a
crowdfunding
campaign
just
like
Kickstarter.
It
goes
concurrently
with
with
the
project
or
then
before
that
you
can
organize
your
effort
and
fundraise
from
the
corporations,
and
things
like
that.
If
I
talked
to
people
like
our
favorite
company,
lulzbot
I
talked
to
Jeff
Moe
he's
willing
to
throw
in
10k
on
this
I
was
actually
aiming
to
generate
like
100k.
A
We
do
like
50k
on
the
cordless,
the
cordless
drill,
Construction
Set
and
like
50k,
on
the
phone
foam
project,
but
basically
I
think
we
can
motivate
it.
You
know
the
idea
is:
do
you
get
buy-in
for
this
kind
of
stuff?
Well,
it's!
If
it's
public,
true
public
interest
development,
everyone
benefits,
yeah,
you
can
get
by.
That's
that's
the
difference
here
that
you
can
motivate
people
because
of
the
public
public
interest
nature
nature
of
that
an
incentive
challenge.
If
it's
a
it's
a
monetary
prize
that
definitely
gets
a
lot
of
people
involved.
A
So
we
want
to
try
that
and
make
it
work
once
again
the
the
biggest
deal
to
that
is
getting
very
specific.
Okay,
so
getting
our
heads
around
okay,
what
exactly
you
know
direct
it
as
much
as
possible
versus
it
being
super
loose
in
terms
of
its
definition.
If
you
define
it
and
specify
it
as
explicitly
to
drive
towards
what
you
want,
you
can
do
it,
but
that's
that's
the
hard
part,
because,
as
I
talked
about
in
the
concept
of
degeneracy,
two
groups
should
should
aim
towards
a
similar
solution.
A
A
Maybe
maybe
there's
a
few
million
printers
out
there,
largely
by
know
a
lot
of
it
is
by
DIY
people,
just
individuals
who
who
may
be
interested
in
this.
So
focusing
the
the
cordless
drill,
final
challenge
around
the
3d
printing
aspect.
It
would
be
a
great
way
to
do
it
and
you
can
push
things
further
by
saying:
hey,
you
actually
have
to
start
from
scratch:
plastic
and
extrude,
your
filament
them
do
that
I
mean
we
can
make
those
rules,
I
mean
that
would
definitely
cut
out
many
people
that
that
would
participate.
A
But
what,
if
you
said,
the
rules
such
as
okay,
you
get
points
for
whichever
aspect
you
do.
If
you
contribute
to
the
extruder
part,
you
get
so
many
points.
If
someone
builds
upon
it
and
actually
uses
your
design
to
do
the
final
product,
you
might
you
might
score
and
so
either
you
know
it's
not
necessarily
that
if
we
expanded
the
scope
and
difficulty
that
you
get
less
participation,
I
think
it
could
design
it
in
the
correct
way.
You
can
get
even
more
participation
to
make
it
make
it
an
even
better
project
so,
but
at
all.
A
Also
in
this
we
do
for
best
results.
We
would
you
know
the
people
who
do
participate.
We
would
have
to
produce
some
kind
of
training
materials
for
them
in
order
for
for
them
to
to
work
more
along
the
route
of
what
we
do,
because
right
now,
for
example,
things
like
like
free
cab,
I
mean
hardly
anyone
uses
it.
So
maybe
a
really
good
documentation
on
free
CAD
would
help
a
lot
of
people
cuz.
A
Everyone
just
uses
the
proprietary
packages
like
the
free
like
fusion,
360
or
whatever,
which
are
free
online
things,
but
are
not
open
source,
so
you
know
don't
really
fit,
but
with
our
game.
So
you
know
we'll
see
how
we
can
make
those
encourage
people
to
use
open
tools
throughout
it,
but
we
can.
We
can
make
those
rules
happen
and
maybe
maybe
we
get
less
people
participating,
but
maybe
we
get
even
more
if
we
do
it
right.
A
Just
do
it
just
a
little
bit
on
a
development
template,
but
for
for
a
lot
of
people
to
collaborate
effectively
on
the
work
that
we
do.
I'm
open
product
development
party
taxonomy
that
has
to
be
understood,
is
all
the
development
steps
that
do
go
into
any
kind
of
a
hardware
project.
So
let
me
just
go
through
through
them
briefly,
because
that's
something
that
you
know
in
the
fellowship
program
or
any
collaborators
that
want
to
collaborate
with
us
for
longer.
A
If
you
read
some
of
the
later
latest
papers,
there
is
indication
that
open
modular
design
is
the
way
that
more
design
will
be
shifting
towards
in
the
future
modular,
because
it's
them
can
become
more
interoperable
and
open
source
because,
as
things
get
more
complicated,
there's
a
higher
incentive,
as
you
move
forward,
to
build
upon
priority
in
an
effective
way
because,
as
technology
gets
part,
you
know
more
more
and
more
advanced
or
sophisticated.
There's
more
knowledge
that
goes
into
any
product
and
therefore
there's
a
natural
tendency
for
more
open
source.
A
Rather
than
less
just
like
when
I
went
to
the
Linux
Linux
Leadership
Summit
I
found
that
all
the
googles
and
Facebooks
are
shifting
towards
open
development
on
every
just
about
everything
that
they
do
and
they
monetize
on
top
of
that.
But
the
core
underneath
just
like
with
the
telephony
companies
they're
they're,
making
more
open,
will
open
open
source
as
the
as
the
process,
and
probably
part
of
that
is
like
a
I
for
for
modern
software,
AI
or
computer
vision.
I
mean
so
complicated
that
you
couldn't
do
it
without
open
sourcing
modules
that
you
build
upon.
A
So
there's
definitely
a
tendency
for
open
and
the
product
development
literature.
If
you
read
the
papers
on
that,
I've
got
a
page
on
the
wiki
called
open
source
product
development.
It
lists
some
of
the
the
latest
papers,
which
was
very
encouraging
when
I
read
it
because
the
people
are,
you
know
the
forward.
Thinkers
are
saying
open,
source
and
modular
will
be
the
way
products
are
designed
in
the
future.
That's
not
how
it
happens
today,
the
most
open
source
or
modular.
How
people
have
their
own
thing?
A
Don't
don't
interoperate
in
many
fields,
but
that
is
so
the
good
news
that
the
writing
on
the
wall
is
is
far
more
open
in
the
future.
So,
let's
just
just
want
to
cover
a
little
bit
of
the
development
template.
We
did
go
through
once
again,
because
I
mean
we'll
be
beating
this
over
and
over
through
the
immersion
program.
A
A
It's
mostly
about
the
technical
development
for
watching
able
to
build
upon,
including
some
documentation
but
kind
of
briefly
going
through
this.
You
always
want
to
start
with
requirements.
You
define
those
two
to
define
what
you're
trying
to
solve
so
that
there's
no
ambiguity
of
what
the
goals
are.
The
requirements
can
can
also
include
what
functionality
or
after
some
performance
performance
specifications
you
can
get
as
detailed
as
possible
in
requirements.
I
mean,
then
you
can
go.
Take
that
to
a
very
very
very
far,
but
typically
you
want
to
define
your
requirements.
Then
you
develop
some.
A
You
find
more
info
in
our
normal
iterative
process.
You
go
back
to
the
requirements.
You
might
modify
them
to
make
it
more
precise,
like
tune
them
in
and
if
you
can
tune
the
requirements
into
two
extremely
specific.
Nothing
I
mean
you're
on
your
way
to
get
a
lot
of
people
producing
meaningful
content.
We
have
a
thing
like
an
infographic.
A
Module
breakdown
is
the
absolute
critical
part
that
I
mentioned
for
modular
design.
Where
we're
breaking
hearts
down
breaking
machines
down
into
modules.
You
can
break
the
modules
down
into
parts
and
further
modules
sub
modules,
a
critical
part
for
a
parallel
development
interface
design
is
the
thing
that
must
follow
the
modules,
because
you
need
to
know
how
they
fit
together.
A
Oh
hello,
hello,
then
you
go
into
so
we're
out.
Okay,
so
we're
on
to
the
page.
I
can
actually
share
that
for
the
Dixon
okay.
So
we're
sharing
sharing
the
screen
here.
Interface
design
goes
with
module
breakdown.
All
the
time
you
have
to
go
out,
fit
things
back
together.
Now
part
libraries,
you
can
get
specific
like
if
you
want
to
get
somebody
a
head
start
on
how
to
design
something,
for
example,
for
the
3d
printer.
Of
course
you
put
your
axis
system,
you
put
your
critical
components.
A
You
already
used
into
that
system,
so
you
can
use
them
as
they
are,
and
then
people
can
build
a
comment
or
modify
them.
You
start
with
them
can
three-dimensional
language
that
anybody
can
use
if
we
got
access
to
open
software.
Part
libraries
important
so
3d
CAD
now
becomes
the
integration
of
part
libraries
into
working
sub
modules
modules.
You
want
to
say
here,
3d
CAD,
at
the
at
the
park
level,
module
level
machine
levels
so
that
you
can
start
developing
where
whoever
is
most
appropriate.
A
3D
CAD
parts
I
forget
what
that
is:
3d
print
substitutions
for
a
lot
of
different
devices.
There
might
be
places
where
it's
very
convenient
to
to
produce
something
that
sweetie
print
instead
of
an
off-the-shelf
part
like,
for
example,
the
grinder.
It
was
very
convenient
to
print
the
the
bearing
holder,
as
opposed
to
getting
like
a
50
or
100
dollar,
a
hex
bearing
or
actually
ones
that,
when
I
couldn't
find
I
couldn't
find
any
ones
that
had
a
bearing
on
them.
They
had
these
weird
mounts.
A
So
three
parts
up
print
substitution
is
where
you
just
analyze
the
whole
whole
machine
and
say
okay,
which
of
these
things
should
I
be
3d
printing,
if
that's
part
of
the
normal
dr.
that
I
have
calculations
that
gets
into
benjamine
weather.
That's
that's
computer-aided
engineering,
simple
back-of-the-envelope
calculations,
basics
that
you
various
calculators
on
the
internet
that
you
can
apply
readily
like
beam
deflection
for
knowing
how
much
your
axis
is
gonna
bend
when
it's
so
long.
A
Things
like
that
strength,
compressive
strength
such
as
how
much
how
tall
can
you
can
you
build
your
building
before
the
bricks
actually
start
collapsing
upon
one
another
things
like
that
hydraulics
diagrams.
We
work
with
a
lot
I
draw
it.
Hydraulics
can
also
apply
to
house
like
like
house
plumbing
systems,
but
hydraulics
and
tractors
and
high
power
hydraulics.
You
have
hydraulics
diagrams
to
define
how
your
power
is
distributed,
for
example,
in
the
micro
tractor,
functional
diagrams
are
useful
for
defining
an
abstraction
of
the
functions
of
a
given
machine.
A
So
there's
a
lot
of
diagramming
that
can
be
done.
Electronic
schematics
so
now
getting
into
electronics.
For
for
what
the
circuits
actually
are,
then
getting
into
electronics
layouts,
which
are
the
actual
middle
files
that
you
can
get
yet
from
the
schematics,
which
are
the
schematics
ER,
is
the
abstraction
of
what
what
marks
exist
there,
without
necessarily
considering
the
routing
of
how
everything
is
connected.
A
Wiring
diagrams
and
maybe
some
simple,
simpler
things
like,
for
example,
the
graphical
wiring
diagram
of
the
3d
printer
on
a
DVD
controller
page,
where
you
show
diagrams
of
how
things
are
plugged
in
software.
That's
a
big
big
kind
of
things
which
would
be
firmware
or
software
or
anything.
That's
that's
code,
Bills
of
materials.
Well,
naturally,
you
need.
A
That's
that's
a
very
important
thing
with
something
that
some
of
the
most
important
things
are
your
CAD,
your
bill,
materials,
fabrication
procedures
so
be
OMS
ranks
very,
very
top,
because
that
tells
you
what
you're
actually
doing
that's
the
secret
sauce
when,
when
you
want
to
reverse
engineering,
some
machine
like
first,
you
have
to
know:
where
are
you
gonna
get
it
like?
What
you're
gonna
do?
What
are
you
gonna
build
with?
Where
are
you
gonna
get
it?
A
Those
two
things
must
be
embodied
enough
and
the
build
materials
we'd
like
to
do
visual
Bills
of
materials
where
we
specify
well,
we
we
do
things
like
weather
little
cat
clips,
clippings
or
actual
clippings,
just
copy
and
paste
from
Amazon,
which
shows
how
the
actual
parts
look,
and
you
can
show
short
diagram,
arrows
pointing
to
the
different
parts
that
you
represent
visually.
So
he
can
understand
it
in
a
better
way.
A
Cam
files
are
computer,
aided
manufacturing
files,
so,
for
example,
STL
files
are
cam
files
or
DXF
files,
which
show
like
the
cutouts
for
flat
steel,
computer-aided
manufacturing
anything
that
the
computer
CNC
machine
takes
in
order
to
produce
with
it
cut
lists
like,
for
example,
we
have
cut
lists
like
make
make
38
inch
wires.
37
inch
wires,
39
inch
wires,
make
30
wires
of
3
feet
for
an
extender
for
such-and-such,
make
the
rods.
You
know
whatever
28
inches
32
inches
in
sulfur.
A
That
has
to
be
defined
in
the
numbers
and
numbers
so
that
when
you
get
into
the
workshop,
we
first
typically
operate
an
ability
typically
operate
in
the
cup
list.
So
you
get
all
your
parts
cut
and
then
that's
ready
to
go
to
like,
for
example,
when
we
prepare
the
boxes,
as
we
I
think
this
time
around.
We're
wasting
a
lot
a
lot
of
time
on
just
trying
to
get
parts
and
once
again
the
Box
to
the
ready
box
with
all
the
parts
it
would.
That
would
be
an
implementation
of
the
cut
list.
A
You
put
all
the
parts
in
there
and
save
that
kind
of
confusion
from
within
build
like
yeah,
like
that,
test-driven
prototypes
is,
as
you
go
along.
You
want
to
test
things
as
soon
as
possible,
either
either
as
steel
models
or
anything
a
paper
model.
It
could
be
a
calculation.
It
could
be
anything
that
simulates
short
of
doing
the
real
thing
or
it
could
be
just
one
thing
that
you
test
in
isolation,
so
that'd
be
a
test
driven
design.
A
Have
you
isolate
one
part?
Then
you
copy
and
paste,
then
you
say:
okay,
this
part,
plus
this
part
they
go
into
this
next
part
and
so
forth.
So
you
can
kind
of
diagram
out
a
whole
a
whole
build
on
in
a
graphical
way
and
that
helps
people
see
see
how
all
the
parts
come
together
down
to
the
final
machine.
A
So
at
the
very
end,
the
tree
is
branched
out
to
many
many
multiple
parts
and
then
goes
down
to
to
the
final
product,
and
you
can
do
that
for
every
module,
because
the
whole
machine
would
get
doesn't
leave
gonna
be
a
lot
of
parts
at
the
top,
so
you
might
want
to
break
it
down
and
to
to
communicate
that
effectively.
That's
that
takes
some
skill
and
communication
explored
part.
A
Diagrams
are,
like
you
see
a
lot
in
typical
manuals
where,
where
you
have
a
diagram
like
in
black
and
white
and
just
everything
has
exploded
along
an
axis
or
multiple
axes
that
separates
out
the
parts,
so
you
see,
parts
are,
as
opposed
to
the
whole
assembly
explode
part
animation.
So
you
can
add
a
little
bit
more
aesthetics
to
that
through
animations,
like
a
free
cat,
does
explore
part
animations,
which
also
allow
you
to
separate
something
in
a
short
video.
So
you
can
see
the
progression
of
how
something
goes
together.
A
I'm,
actually
playing
an
exploded
part
animation
in
Reverse
will
then
get
you
somewhat
of
a
build
procedure,
language
that
are
asked
to
domestic
instructionals.
That's
that's!
Actually,
we
classify
that
a
separate
thing
beyond
the
build
instructions,
because
the
build
instructions
can
be
as
simple
as
just
playing
words,
but
she
didn't
be
one
of
the
pictures,
but
the
language
agnostic
instructions
are
no
all
pictures,
parallel
production
engineering,
so
you
have
to
think
about
okay,
what
are
all
the
steps
that
can
be
done
done
together
and
based
on
a
number
of
people?
A
You
have
for
the
build
you
you
want
to
allocate
roles
accordingly,
so
ideally
we
would
have
had
that
all
planned
out
for
for
this
event.
But
then
again
you
can't
plan
out
too
much
of
that,
because
some
people
might
tend
to
like
other
things.
Maybe
they
have
special
skills,
so
you
kinda
have
to
play
by
ear
and
Carroll
production
engineering.
A
So
then
you
go
to
do
that
a
collection
after
the
build
parts,
so
that
collection
is
critical,
so
you
can
build
upon
and
then
person
that
builds
it
next
doesn't
fall
into
the
same
mistakes
that
you
have.
Unfortunately,
you've
had
like
when
people
replicated
several
times
like
both
of
the
tractors.
Three
of
the
tractors
I
mean
they
made
several
mistakes
that
we
could
have
told
them
if
they
spoke
to
us
before
the
build,
and
we
do
have
that
communicated
on
wiki
and
various
locations,
but
the
most
direct
sources
communicate
with
the
author.
A
Then
the
first
thing,
if
you
want
to
you,
want
to
build
upon
another
person's
work.
Number
one
thing
is
contact
the
author
find
out
what
the
latest
thing
is,
because
the
documentation
always
lags
behind
the
behind
the
real
reality.
That's
that's
always
the
case
I
mean
cross.
You
see
that
clearly
there
too,
so.
A
Build
upon
people's
work
by
documenting
everything,
so
it's
built
video,
so
that's
useful
things
like
time.
Lapses
are
great
we're
capturing
some
video
also
build
data
collections
so
sitting
with
a
notebook
and
saying
okay,
this
step
took
salt,
so
long,
etc.
So
you
can,
you
can
learn
for
the
next
time
or
just
trouble
spots
of
which
we
ran
into
many.
That
needs
to
be
documented,
making
sure
that
for
the
next
time
we
don't
run
into
those
same
issues
and
then
a
lot
of
times.
A
You
find
out
that
okay,
you
correct
one
thing
and
once
you've
fixed
everything
and
you're
perfect,
you
think
and
some
new
issues
might
resurface.
So
it's
always
about
revisiting
to
the
point
that
okay,
it
is
solid
and
stable.
That's
the
ideal
performance
data
collection.
So,
on
top
of
just
build
data,
you
wanted
to
gather
performance
data
like
for
exam
laughter
on
the
3d
printer.
Did
it
print
on
the
first
try?
What
was
the
issue?
How
fast
can
I
bring
news
and
crank
it
up
to
a
hundred
fifty
percent,
two
hundred
percent
or
five
hundred
percent?
A
A
Experts
for
review
is
one
of
the
other
aspects
we
can
be
developing
throughout
this
project
so
that
we
get
external
feedback,
not
just
our
small
group,
but
anyone
from
from
anywhere
someone
who
might
have
just
a
very
little
time
but
is
but
as
an
expert
in
something
they
might
be
able
to
provide
excellent
feedback,
especially
people
who
are
more
the
practitioners,
the
guys
who
are
using
something
like
you
have
designed
or
have
experience
with
it.
That's
that's
what
a
feedback
is
valuable,
of
course,
as
opposed
to
armchair
theorists
who
are
speculating
on
things.
A
So
you
want
to
go
find
that
people
have
a
lot
of
experience
in
something
future
work.
Is
you
want
to
define,
based
on
the
data
that
you've
collected,
you
will
find
things
okay.
Now
we
need
to
solve
this
document
that
has
future
work
bugtracker
we
will
list,
it
will
list
all
the
things
that
are
wrong,
that
you
need
to
work
on.
A
Maybe
it
could
be
minor
or
major
that
can
be
a
product
release
with
bugs
there,
for
example,
as
long
as
you,
there
might
be
basic
functionality,
that's
available,
but
if
you're
releasing
something,
that's
def
bug,
so
you
make
that
clear.
Okay,
the
bump
bug
bug
report
or
your
documentation
and
the
bug
trackers.
You
should
show
oK,
we've
got
everything
working,
but
I
don't
know
whatever.
A
Whatever
was
wrong,
be
aware
of
the
shortcoming
of
that,
so
that
your
expectations
are
met
when
using
the
thing
like
with
the
filament
maker,
we
know
that
that
thing
works
for
ABS,
but
the
disclaimer
already
that
we
know
is
also
well
from
PLA.
We
don't
have
to
formulate
yeah.
We
got
it
tuned
in
to
what
what
it
has
to
be
so
write
that
down.
You
know
whatever
as
much
as
you
can
write
down.
A
A
Oh
that's
just
another
pretty
printer,
but
then
we
can
say,
oh
well,
we
actually
got
these
certain
features
that
you'd
really
be
interested
in,
and
this
is
why
and
so
forth,
so
background
actually
put
background
research
I'd
be
very
young
because
I
start
with
development,
but
before
you
do
any
development,
you
want
to
do
a
lot
of
background
research
like
if
you're
developing
a
machine
for
the
global
village
construction
site.
You
want
to
take
a
look
at
the
product,
ecology.
A
What
is
what
else
is
in
the
set
that
that
makes
it
thick
if
you're
designing
the
CNC
certain
mill?
You
want
to
understand
that
it's
got
the
universal
axis
and
the
ramp
sport
or
other
parts
that
already
exist
in
other
parts
of
the
system
and
may
be
manufactured
with
other
tools
within
a
set
like
a
CNC
torch
table
for
the
frame
or
other
things.
What
else
do
we
have
in
a
system
like
eventually
we'll
be
down
to
the
induction
furnace,
where
you
can
take
scrap
steel
and
build
it?
A
But
you
want
to
be
aware
of
what
what
else
fits
with
that
particular
item
so
that
when
you're
designing
that's
a
consideration
in
your
specifications,
which
means
that
you're
going
to
be
designing
a
particular
way,
not
just
some
far-out
way.
That's
like
okay,
so
just
not
relevant,
because
that's
not
how
we're
designing
it.
You
have
to
look
at
product
ecology
as
the
first
thing
so
that
it
fits
because
we're
not
designing
one
thing
out
of
time.
We're
designing
50
things
at
a
time.
A
So
you
can
click
on
one
each
these
means
but
OSE
specifications.
That's
a
lengthy
page.
It's
got
about
5200,
it's
about
a
hundred
or
so
what
point
items
that
define
the
certain
values
that
we,
though
we
go
for
main
main
ones,
being
scalability
modularity
public
design,
open
source.
Those
are
some
of
the
main
ones,
but
then
we
get
more
refined
into
what
are
all
the
other
values.
A
So
if
you
follow
all
these
specifications
and
the
design
requirements,
that's
what
I'm
saying
you
should
the
generate
to
a
very
similar
solution
set
when
you
do
a
certain
development,
how
it
works.
How
it
works
is
the
kind
of
questions
Alex
was
asking.
He
was
asking
basic
questions
of
okay.
Well,
how
does
this
3d
printer
work?
You
want
to
explore
that
and
clarify
that,
for
anyone
who
does
not
have
any
familiarity
with
it,
so
they
can
also
become
familiar
tech-tree
of
choices
so
for
any
technology.
You
have
multiple
ways
of
doing
things
for
the
axis.
A
We
have
a
choice
of
elite
using
like
lead
screws,
which
are
super
precise,
very
strong,
accurate,
also,
ten
times
more
expensive.
So
we
choose
belts.
So
so
you
have
to
understand
your
tech
tree
of
choice
together
this
choice,
you
have
another,
you
have
you
have
many,
and
you
pick
a
one
that
that
fits
your
requirement,
background
readings.
So
for
any
project.
You
should
have
a
background
reading
list
that
shows
some
of
the
most
seminal
work.
I
mean
okay.
A
First,
the
seminal
work
like
what
is
it,
for
example,
the
first
3d
printer
that
was
built
in
the
world.
What
is
that?
What
is
the
ones
that
now
the
current
good
literature
or
whatever
paper
or
a
publication
that
explains
speedy
printing?
It
you
have
that
available
for
people,
so
you
can
catch
up
the
speed
really
quickly,
as
opposed
to
looking
for
a
bunch
of
things
that
are
not
really
essential
or
low
quality.
You
want
to
start
refining
throughout.
A
This
whole
process
is
about
refining,
getting
people
up
to
speed
faster
for
quick
learning,
background
research
and
patent
search.
So
before
you
do
anything,
patents
are
still
very
useful,
so
you
can
look
at
the
US
Patent
Office
and
you
can
just
google
patents
on
Google
search
and
3d
printing
patent
that
patent
or
a
patent
for
heated
bed
just
start.
Looking
at
the
keywords
that
you
already
know
from
all
the
other
parts
here
and
you
can
start
bleeding
great
inside
my
pants,
they
seem
like
complicated
but
they're.
A
Actually
not
if
you
start
looking
at
patents,
they're
gonna
show
you
like
diagrams
they're,
going
to
be
conceptual
because
they'll
never
tell
you
how
you
really
do
it,
because
patents
are
not
supposed
to
tell
you
how
to
really
do
it.
They're
not.
Patents
are
not
like
open
source.
It's
far
from
it.
It
doesn't
have
any
Bills
of
materials
and
you
kind
of
build
procedures.
Just
tell
you
the
concepts
of
what's
protected,
but
still
that
information
that
focuses
on
design
rationale,
which
is
quite
valuable
for
what
we
do.
A
You
you
find
out
how
they
do
it
and
why
they
do
it,
and
then
you
can
apply
that
to
the
way
we
want
to
do
things
so
don't
throw
the
patents
out
there
definitely
good,
even
though
they're
protected.
If
it's
19
years
old,
then
it
you
can
use
it.
Unless
someone
renewed
the
patent,
most
people
don't
care
about
patents
more
than
19
years
old,
they're
moving
on
to
new
technology.
But
we
talk
about
sufficiency.
What
technology
level
is
sufficient
for
for
us
to
be
able
to
work
with
it
and
solve
many
problems?
A
Many
issues
address
many
needs
without
necessarily
being
the
latest
and
greatest,
because
that's
not
always
necessary,
there's
a
sufficiency
criterion
for
what
you
want
to
do.
If
you
want
to
build
an
integrated
system,
you
don't
go
to
the
necessarily
to
the
peak
technology.
You
go
to
the
technology,
that's
the
peak
technology
for
the
system,
for
the
interactions
that
it
has
so
just
because
it
works
peak
performance
on
one
item.
A
What,
if
you
consider
two
three
or
ten
items
like
we
consider
well
that
may
be
thrown
out
because
it
doesn't
have
that
integrated
efficiency
on
multiple
fronts?
That's
why,
for
us,
a
lot
on
a
patent
search
could
be
very
useful
for
what
we
want
to
do
background
research.
So
you
start
just
googling.
Industry
standards
are
things
that
are
built.
A
Currently,
that's
looking
for
a
catalog
of
you
know
like
looking
at
what
John
Deere
does
or
whoever
industry
standards
you
start
exploring
what
everyone
else
is
doing
to
see
how
how
you
can
learn
from
that
technology
technology
assessment.
So
whenever
we
see
some
technology,
we
want
to
pass
it
and
start
passing
it
through
some
filters.
How
does
that
affect
rules?
These
specifications
and
maybe
like
make
notes
and
assessments.
Oh
okay,
this
is
a
great
concept,
but
just
doesn't
scale
it
doesn't.
A
You
know
it
doesn't
fit
well
on
us,
so
so
maybe
document
some
of
those
notes
of
how,
when
you,
when
you
study
something
document
that
so
the
next
person
you
can
read
about
that,
if
they,
if
they're
willing
to
to
spend
the
time
doing
that,
and
if
you
refine
the
technology
assessment,
you
know
people
build
upon
you.
You
write
some
basic
comments.
The
next
person
on
a
wiki
maybe
does
more.
You
can
get
to
some
very
high
quality
assessment,
so
select
on
forums.
A
Forums
are
very
low
on
technology
assessment,
like
people
start
blabbing
about
things,
a
lot
of
people
that
don't
know
anything
about
the
topic.
It's
a
lot
of
speculation
that
wouldn't
be
technology
assessment.
It's
like
it's!
It's
technology
assessments,
basically
the
the
forum
plus
rigorous
building
upon
all
those
comments
and
like
maybe
refactoring
them
to
do
like
imagine,
like
a
forum
had
okay,
now,
here's
all
the
discussion
and
then
some
the
master
that
forum
would
be
okay.
So,
given
all
that
we
learn
plus
these
other
things.
Here's
like
what
what
the
real
story
is.
A
A
Document
thing,
the
value
proposition
is
important,
so
to
be
very
clear
about
what
exactly
it
is
that
we're
offering
and
for
us
it's
scalable
modular.
Those
are
the
two
scalar
scalable
modular
distributive
distributive
azan.
We
are
helping
others
to
replicate
we're
open
about
others.
Producing
things
so
be
clear
about
what
the
particular
value
proposition
is
for
what
you
have
that
might
differentiate
from
having
to
differentiate
from
everybody
else.
A
No
one
in
the
world
has
a
scalable,
3d
printer
I,
don't
really
know
modular
ones
where
you
can
do,
interchange
like
we
can
and
certainly
nobody's
distributive
about
it.
The
closest
I
mean
closely
I
would
say
to
distribute,
it
would
be
lols
about.
That's
why
I
like
them,
they
publish
everything
up
to
even
their
operations
manuals
and
documents
that
define
how
they
do
their
IT
and
things
that
so
you
can
alert
them
and
I
actually
pick
that
up
and
it's
all
on
their
server.
You
can
download
it
on
our
development
server.
A
You
can
actually
learn
from
it.
They
use
the
Oh
Duke
Community
Edition,
that's
the
open,
ERP
used
to
be
well.
They
use
that.
So
you
can
learn
how
how
to
work
with
that
and
you
can
contact
them
to
for
technical
assistance
and
them,
and
that's
that's
so
close
to
that
ideal
state
where
another
company
actually
allowed
Foster's
helps
you
to
just
to
learn
rapidly
about
what
you're
trying
to
do
an
open
source.
A
So,
ideally,
all
that
stuff
is
documented
available
by
others
floor
any
other
type
in
the
steps,
and
then
you
can
stand
on
a
shorter
of
giants.
So
ok,
so
that's
about
it!
That's
a
quick
walk
through
of
the
basic
development
template.
What
all
goes
in
there.
But
this
is
the
kind
of
understanding
we
all
have
to
have
to
see.
What's
what's
involved
in
that
process,
any
questions
on
this
all
together
or
perfectly.
A
We
don't
we
use,
we
just
use
Google
Docs
and
what
we
typically
do
is.
We
have
cut
and
paste
like
the
standard
components
like
the
valve
like
the
fittings,
the
hoses
we
just
copy
and
paste
them.
So
it's
kind
of
its
kind
of
like
a
little
bit
of
a
construction
set.
We
have
a
page
page
of
a
cons
that
we
use
for
that.
So
those
are
the
kinds
of
things
that
are
very
important
to
the
document
that
have
in
one
place
that
we
should
have
one
hydraulics
for
plumbing,
maybe
for
3d
printers.
A
So
we
can
like
in
the
easiest
instance,
you
can
actually
take
something
as
simple
as
a
Google
Doc
and
if
it
has
all
the
all
the
images
and
that
you
can
attach
a
hyperlink
to
an
image,
so
it
correct
to
be
a
sourcing
link
as
well.
You
just
copy
and
paste
into
another
document
that
you
can
start
designing
the
conceptual
framework
for
the
next
version,
or
something
like
that.
That's
that
is
very
useful,
but
we
don't
have
any
specific
software.
We
use
right
now,
but
I'm
sure,
there's
things
we
could
do
better.
A
A
Yeah
yeah,
actually
so
about
that,
we
were
thinking
that
we
can
sell
kits
or
produce
kits
or
make
it
available.
It's
be
modeling
kits
for
the
funeral
home
parts,
because
that's
something
there's
actually
kid
out
there
to
get
the
name
of
it,
but
basic
basic
shapes
that
are
the
basic
modules
and
you
can
make
all
the
different
configurations
of
the
see
to
go
home.
Just
like
you
can
build
it
in
CAD.
A
You
can
also
cut
it
out
from
from
thin
sheet
and
make
it
kind
of
snap
together
it,
and
that
is
actually
a
very
useful
thing.
We
would
want
to
probably
we'll
get
to
it
once
we
get
to
the
C
needle
part,
where
we're
actually
creating
the
scale
models,
because
those
would
allow
customers,
for
example,
to
say:
okay,
sorry,
we
can
design
for
it.
A
A
A
A
Yeah,
no,
that's
that's
actually
quite
good
I
do
like
that,
and
you
know
if
we
have
the
energy
for
that
as
soon
as
we
have
the
energy
or
the
focus
on
that,
that's
something
to
do.
Definitely
it
would
take
some
good
effort,
but
I
think
the
core
design
that
we
have
already.
What
differentiates
us
I
mentioned
the
other
kit
project.
Well,
their
kit
is
just
something
that
you
designed
as
a
kid,
but
it's
not
connected
to
any
real
modules.
For
us
that's
different.