►
From YouTube: Development Team Meeting - May 15, 2017
Description
Here we cover process for Language Agnostic Instructionals, and invite Documenters to join. We have a backlog of curriculum development to be done to help new people learn the development process faster.
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
And
I
will
share
my
screen
so
that
we
all
follow
this
and
every
time
it's
we
try
to
refine
a
process
here
we
make
the
road
by
walking
is
the
idea
and
it's
a
learning
environment,
essentially
where
I
would
say.
One
of
the
missing
pieces
of
the
whole
project
is
that
is
make
me
to
make
the
road
by
walking
we're
on
a
cutting
edge
of
collaborative
development
and
open
hardware,
and
as
such,
it's
up
to
all
of
us
to
teach
each
other,
and
it's
like
we're
forming
a
tribe
where
we
are
teaching
each
other.
A
All
the
different
different
skills
and
I
definitely
see
that's
a
weakness
in
the
sense
that
sometimes
there's
a
lot
of
confusion,
not
enough
process
and,
yes,
that's
a
recognized
thing
from
the
feedback
form.
So
let
me
go
back
to
the
document
and
Fallin
agenda,
so
here
we
go
first
of
all
welcome
to
so
we
start
the
meeting
of
kind
of
reviewing
where
we
are,
as
the
team
and
first
thing.
First
of
all,
is
we
kind
of
look
at
the
numbers
how
the
team
is
doing
in
terms
of
teen
population
team,
health.
A
So,
first
of
all
welcome
to
Kathy
and
Israel
two
new
players
on
the
team,
so
we're
up
to
about
actually
15
people
all
together.
Our
acceptance
rate
so
far
has
been
30
30%
about
so
you're
the
chosen.
It's
not
so
easy
to
pass
the
pre-cut.
That's
a
lot
of
people
have
given
up
on
that,
but
for
those
of
you
who
haven't
filled
out
the
time
sheet,
you
see
in
the
bottom
corner
here
you
see
the
big
dip
for
today's
date.
A
That
means
people
haven't
just
simply
haven't
logged
in
their
time.
Yet
please
do
that.
Let
me
just
capture
that
yeah
much
as
you
see
the
average
time
right
now
we're
at
about
like
15,
it's
15
there.
That
means
150
hours
per
week
of
contributions
from
the
dedicated
development
team,
moving
forward
on
the
official
development
process.
Once
again,
it's
working
on
the
global
village
construction
set,
which
is
not
just
a
bunch
of
individual
tools,
but
a
collection
and
an
operating
system
kind
of
a
kernel
for
hardware,
which
is
an
extremely
hard
proposition
because
we're.
A
How
do
you
draw
the
boundaries?
How
you
define
everything
clearly,
but
please
file
your
timesheet.
If
you
haven't
done
so,
and
as
far
as
the
process
of
the
team
is
so
here
just
just
summarizing
this
graph
here,
we're
tracking
the
number
of
contributors,
so
so
10
is
actually
even
though
we've
got
like
15
people
like
10
people
or
13,
or
so
people
10
people
are
actually
people
who
have
logged
their
time.
So
maybe
there's
a
person
or
two
that
maybe
had
a
bad
week
or
something
then
get
to
log.
A
But
the
fact
that
15
is
a
actual
number
of
hours
is
above
is
above
the
number
of
contributors.
That
means
that,
on
average,
if
the
red
is
above
the
blue,
that
means
we're
doing
more
than
10
hours
per
week
on
average,
which
is
good,
I
know
I,
certainly
am
I
mean
I.
Do
this
full-time,
so
I
put
in
about
50
hours
per
week.
That
kind
of
brings
up
the
average
a
little
bit
but
I
think
altogether.
It
seems
that
people
are
going
above
of
the
10
hour
per
week,
which
is
good.
That's
really
good.
A
Ok,
as
far
as
last
week,
I
posted
a
feedback
questionnaire.
Please
fill
it
out.
Only
three
people
have
filled
it
out
so
far.
Now
you
can
look
at
the
responses
here
on
page
3
and
just
click
on
that,
but
based
on
the
feedback
so
far
as
I
mentioned,
there's
definitely
a
gap
on
the
documentation
of
best
practices.
A
How
you
do
stuff
because
we're
we're
working
things
out
so
we're
currently
at
the
language,
agnostic,
instructional,
space,
meaning
really
clear,
super
clear
instructionals
and
how
to
how
to
build
stuff
working
on
a
3d
printer,
primarily
right
now
so
I
would
say.
The
way
we
can
address
that
is
I
am
trying
to
find
some
time
to
do
the
recruit
more
documentary
specifically
for
producing
curriculum.
So
it's
it's
still.
A
Developers
still
have
to
learn
free
CAD
because
we
use
freaked-out
of
the
central
part,
but
from
there
we
would
create
all
kinds
of
curriculum
so
that
person
who's
a
curriculum
creator.
The
educator
has
to
actually
end
up
understanding
the
tool
itself.
So
the
way
teaching
works
is
that
you
really
want
to
learn
something
the
best
ways
to
teach
it
because
then
you
certainly
have
to
understand
you
have
to
present
it.
So
it
takes.
It
takes
learning
something
to
a
whole
new
level.
A
It
would
actually
encourage
you
to
think
that
way
when
you
think
about
oh,
why
am
I
learning
this
well
I'm,
not
just
learning
it
for
myself,
I'm
going
to
teach
others
and
that's
a
big
part
of
this
collaborative
literacy.
We
talk
about
working
as
a
team,
but
this
week
so
last
weekend
this
week,
I'm
focusing
actually
a
lot
on
the
utilities
for
the
seed
eco-home,
which
we
built
last
year,
because
we
have
a
bill
coming
up
in
November
and
we
still
have
to
install
all
of
them.
A
So
I've
been
spending
a
bit
of
time
on
that
in
just
a
little
bit
of
time
on
the
3d
printer.
But
this
after
this
week,
I
I
really
aim
to
go
full
full-time
back
into
the
3d
printer
and
the
print
cluster
and
refining
the
print
quality.
Basically
getting
perfect
prints
out
of
our
3d
printer.
So
we
can
use
start
using
them
and
in
fact
the
goal
is
I'm
not
going
to
be
using
the
robot
mini,
which
I
used
last
time,
because
we
didn't
have
the
3d
printer
to
print
parts.
A
Now
I
want
to
use
the
the
printer
itself,
the
d
3d
to
print
parts
for
the
next
workshop,
so
that
means
a
print
cluster
and
perfected
prints
and
to
assist
with
that.
We're
also
working
on
a
filament
maker
to
make
3d
printing
filament.
But
that's
a
big
task
now
perfecting
our
design
to
the
point.
It's
got.
A
reliable
printing
capacity
and
I
want
to
set
up
a
cluster
of
about
four
to
six
of
those
printers,
which
is
what
we'll
need
to
print
out
parts
in
time.
A
If
we
aim
to
scale
up
the
workshop
to
24
participants.
So
that's
the
goal
that
we'd
like
to
have.
That
means
24
people
participating
at
a
fee.
That
means
the
robust
business
model
for
doing
that.
It
means
you
can
get
people
around,
get
people
to
show
up
and
pay
you
to
run
these
workshops
when
they,
when
they
get
a
3d
printer
to
take
home
after
a
single
day
of
build.
So
that's
the
extreme
manufacturing
in
practice
very
efficient
builds
for
which
we
need
good
documentation
which
is
coming
along.
A
We
did
excellent
on
the
exploded
part
animations.
Last
time
people
gave
us
a
standing
ovation
during
the
workshop
for
the
quality
of
those
and
that's
the
people
building
that
on
the
front
page.
But
the
next
step
is
the
language
agnostic
instructions
I'm
actually
quite
encouraged.
A
little
preview
here.
Look
at
this
Roberto's
going
at
it
with
these
excellent
instructions
like
this
here.
So
let
me
just
return
back
to
a
little
bit
of
the
agenda
here.
So
feedback
form.
Yes,
if
you
haven't
filled
it
out,
please
do
so
we're
a
learning
organization.
We
teach
each
other.
A
You
don't
provide
feedback,
we
don't
we
don't
know
what
we're
doing
right
or
wrong.
That's
important
to
do
so.
Only
three
people
have
done
that.
There's
like
10
people
that
need
to
fill
it
out
the
new
people.
You
have
to
worry
about
it
since
you
haven't
seen
enough
of
this
process
yet,
but
if
you're
inspired,
you
can
still
fill
out
the
feedback
form
if
you
have
any
pressing
issues.
Okay,
next
item
is:
how
do
we
do
this
process
of
documenting
and
developing
better?
A
So
we
have
the
scrum
stand
up
to
report
on
the
progress
from
last
week,
but
let's
try
something
different.
Actually
I
was
looking
at
so
first
of
all,
I
failed
to
post
this
document
in
time.
I
just
posted
this
agenda,
which
I
promised
I
would
do
last
Monday,
which
I
didn't
by
the
way
we
need
mean
we
need
someone
to
actually
do
that
as
a
process
manager
as
we
get
more
people
on,
but
what,
if
we
kind
of
go
back
to
the
lazy
way,
which
we
already
have
to
do,
which
is
our
logs?
A
Okay,
so
I,
don't
know
if
it's
possible,
but
we
wanted
to
do
this.
The
scrum
stand
up
here
so
that
people
can
go
through
their
stuff
pretty
rapidly,
but
it's
definitely
redundant
yeah.
So
if
you're
not
in
this
document,
so
let
me
just
paste
this
document
again
for
whoever's
not
watching
over
back
inside
the
document.
Please
go
into
the
document
and
this
document
should
be
openly
editable.
Actually,
let's
see
the
permissions,
we
do
everything
on
these
docs
open
permissions
for
edit
and
that's
because
the
Google
Docs
have
revision.
A
Okay,
I
need
to
go
to
advanced
and
make
it
that
everyone
can
edit.
This
can
view
can
edit.
This
is
our
industry
standard.
When
you
do
link
sharing
share
when
you
share
documents
save
as
anyone
can
edit
done
so
that
you
can
actually
contribute
to
the
document
throughout.
But
idea
is
if
someone
messes
up
something
in
a
document,
you
have
to
worry
about
it
because
there's
a
revision
history
and
we
can
go
back
to
a
former
version.
A
But
let's
try
this
on
a
team
progress
update.
So
we
have
the
scrum
typically
and
I
didn't
post
this
document,
but
I
know-
and
this
is
up
for
debate-
I
mean
we
can
definitely
try
this
document
again
next
week
for
the
quick
report
on
what
people
have
done.
But
the
other
way
is
to
go:
go
back
to
the
kind
of
the
rough
way,
opening
up
all
the
tasks
for
all
the
peoples
logs
and
going
through
that.
So
this
is
what
I
did
I
put
up
all
the
tabs
of
all
the
different
contributors.
A
So
if
you
want
to
find
out
who
all
the
contributors
are
go
to,
for
example,
d3d
log,
which
you
should
be
familiar
with
from
your
welcome
email,
the
d3d
log,
if
you
go
to
that,
it
has
a
link
to
everybody's
like
here.
For
this
is
I'm
on
the
d3d
log
page,
there's
a
link
to
everybody's
log,
so
you
can
quickly
review
what
everyone's
doing
now
I
guess
we
haven't
added,
Israel
or
Cassie
to
this.
A
A
So
I
would
say:
let's
just
try
this
like
just
hyper
length,
your
your
main
working
document
and
that
main
working
document
could
simply
be
say
your
log,
but
in
your
log,
try
to
make
it
transparent
like
embed
the
Google,
Docs
or
embed
pictures,
so
that
someone
can
see
and
I
guess.
Let
me
just
go
through
so
I'm
going
to
kind
of
breathe
through
these
eyes,
I'm
going
to
point
out
IO,
for
example,
what
he
did.
A
Let
me
see
if
we're
OK
look
at
this,
for
example,
so
this
is
IO,
so
this
is
what
he's
doing
on
Saturday
cyclic
at
what
he's
doing?
That's
really
cool
embedded
pictures
in
your
log
worked
really
well
he's
got
his
badge
and
links
to
all
the
other
logs
here.
So
that's
the
way
to
collaborate,
but
this
is
a
cool
thing,
so,
instead
of
say
like,
if
you
want
to
put
a
link
in
the
DVD,
the
the
dev
team
meeting
role
allocation,
that
would
be
one
effective
way
to
do
it.
A
Just
simply,
yeah
I
mean
let's
try.
This
just
try
to
link
to
your
key
number
one
product
within
the
role
allocation
slide,
because
before
we
had
an
individual
slide
for
every
single
person
and
that
works
I
think
it's
a
little
more
infrastructure
and
maybe
you
guys
can
provide
feedback
or
so
there's
a
there's,
a
page
within
the
working
document
here,
which
is
the
suggestions
and
questions
page
slide
7.
So
if
you
go
towards
the
end,
there's
a
suggestions
in
question:
question
K.
A
So
this
is
questions
and
suggestions,
so
these
were
all
from
last
week,
so
we
can
actually
erase
them
and
review
them
from
last
week's
document.
But
these
are
the
suggestions
from
today
and
the
FAQ
is
also
this
now
which
we
can
save
for.
We
can
review
some
of
these
questions
if
we
like,
but
feel
free
to
put
put
all
your
questions
in
there.
So
let's
try
it
if
this,
if
this
new
way
of
linking
work,
product
works,
but
for
now
I'm
just
going
to
go
through
people's
logs
part
of
is
because
I
didn't
really
prepare.
A
I
had
to
have
enough
time
to
walk,
because
we
didn't
have
this
working
duck
up
up
and
about
so.
Okay,
Richard
he's
doing
the
recruiting
work,
that's
good,
lash,
low
deliverables,
so
I'm
going
to
comment
on
last,
oh
here,
a
clear
date
format,
so
yeah
I
would
like
to
request
more
of
this
kind
of
clear
date
format.
So
people
can
see
like
like
here.
I
can
tell
you
right
now,
like
I,
don't
know
this
has
been
done.
A
You
know
yesterday
or
a
week
before
and
I
can
look
into
the
view,
history,
tab
and
probably
there's
going
to
the
view
history.
Tab
is
going
to
show
you
that
all
it
says,
May
13
was
the
last
edit,
but
I
can't
really
point
where
that
edit
was
that's.
Why
I
suggest
in
the
regular
log
now,
let's
see
like
this
is
who
this
is
Jean,
Baptiste
date
and
product,
so
that
it's
clear,
okay
that
date
I
did
that
like
here,
I
can't
really
say
like
is
this
one
week's
work?
Is
this
one
months
work?
A
Is
it
one
hours
work?
So
I
can't
it's
hard
for
me
to
trust
that
that's
the
suggestion
here
for
Laszlo
I
know
he
did
stuff,
but
it's
not
transparent
without
him
doing
the
stand
up
right
now
as
far
something
to
ask
you
to
do
the
stand
up
time,
I'm
just
going
to
go
through
everyone's
log
for
now
so
Jean
Baptiste,
he's
kind
of
disappeared,
I
think
he's
travelling
or
recovering
so
Wednesday.
The
26th
of
April
was
the
last.
So
okay,
we
look
at
that.
A
Roberta,
okay,
we
know
we
got
some
good
product
here.
Someday
may
14
X
s,
idler,
side,
language
of
mastic
instructions,
so
there's
a
definite
product,
awesome!
Okay,
it
goes
to
a
group
editable
Google
Doc,
which
is
actually
not
editable,
because
I
asked
for
permission
and
it
wasn't
so.
Please
share
that.
A
One
comment
on
this
doc:
these
are
going
to
be
printed
as
paper
papers,
pieces
of
paper
during
the
workshop
for
those
people
who
don't
have
a
computer,
for
example,
or
if
you
don't
have
a
computer
available
for
a
workshop,
because
you're
building
to
stay
in
a
workshop
or
by
yourself
or
somewhere
I'm,
going
to
comment
on
the
format
of
this.
This
long
extended
page
is
not
really
printable,
so
please
put
this
in
a
format
that
can
be
printed
with
a
printer,
regular
printer,
so
just
simply
reformatting
is,
but
this
is
awesome
stuff.
A
This
is
free
CAD
and
some
manipulation
using
using
Inkscape,
okay,
good
stuff
and
I'll.
Ask
you
for
a
little
more
tell
me
yeah,
let's,
since
we're
doing
going
through
everybody's
work.
Maybe
maybe
let
us
do
that.
Let
us,
as
we
continue
here
so
we
know,
have
to
go
back
lash
low,
would
you
mind
so
lash,
first
lash
low
and
then
Roberto?
A
Lastly,
would
you
mind
going
through
what
your
main
main
results
were
from
last
week,
cuz
I
know
you
did
some
good
stuff
there
and
possibly
like
in
this
slide
right
here
with
the
pace
that
try
to
in
this
slide
that
I'm
showing
paste
your
main
main
work
product.
If
there's
one
thing
that
is
made,
ok
we'll
go
ahead.
Please.
B
B
A
B
A
A
B
It
looks
have
and
I,
and
you
have
put
to
the
top
and
yes
I,
like
this
kind
of
formula
page,
because
that
is
one
aspect
that
you
would
like
to
keep
track
of
their
data
and
also
others
expect
a
special
and
somebody
joins
and
would
like
to
review
somebody's
growth.
Then
it's
very
difficult
to
clean
from
the
Badminton
yeah.
A
I'm
going
to
say,
we
can
easily
do
a
like
a
little
tent
wiki-based
template
for
top
of
for
top
of
a
person
log.
So
the
cool
thing
I,
don't
know
if
you
know
about
this,
but
the
wiki
allows
you
to
use
templates
where
you
can
put
any
kind
of
a
well
structured
thing
on
top
of
them.
On
top
of
a
log,
for
example,
or
anywhere
templates
can
be
very
powerful.
You
it's
a
template
that
gets
you
all
the
formatting
and
then
it's
easy
for
you
to
put
in
the
critical
item
of
information
there.
A
Maybe
it's
time
to
devise
that
put
in
our
backlog
of
tasks
which
we
for
that
we
need
somebody
who
knows
the
wiki
media
wiki
and
knows
how
to
do
templates,
but
I
would
see.
That's
a
that's
a
perfect
case
where
we
standardize
everybody's
lockers
right
now,
I'm,
looking
at
as
you
see,
everyone's
log
looks
kind
of
different,
but
maybe
we
could
come
up
with
a
standard
format
which
at
work,
which
has
like
the
critical
working
items
and
then
that
we
can
navigate
each
other's
work.
Better.
A
B
D
A
D
A
A
D
A
Okay,
so
so
here's
the
the
next
steps
here,
what
I'm
seeing
is
a
lot
of
good
experiences
coming
about
for
extract
I
mean
it
took
a
little
bit
of
time
for
us
to
learn
the
extraction
of
the
isometric
view
from
freecad,
using
the
drawing
the
mat
I
believe
we're
using
the
drawing
dimensioning
workbench.
Now
here's
the
deal.
What
I'm?
What
I
mentioned
in
the
beginning
of
this
is
we're
missing
standard
operating
procedures.
What
I'm
going
to
do
is
spend
today
on
pulling
together
all
the
knowledge,
so
we
have
lash
flow.
A
We've
got
a
Roberto
and
I
think
we've
got
some
Frank
experience
and,
let's
see
Michael
did
you
gain
any
experience.
Michael
is
Michael
here
or
now,
no
Michael's,
not
here,
so
those
are
the
people
that
have
shown
demonstrated
experience
on
doing
the
language
agnostic
instructional
process.
What
I'll
do
is
I'm
going
to
edit
a
tight
video
on
how
to
go
through.
All
of
that,
so.
A
C
Okay,
yeah,
looking
on
the
visual
build
materials
for
the
extruder
and
say
I
did
have
some
technical,
hard
or
difficult
this
week,
so
my
log
was
a
little
bit
sporadic
I
guess,
but
I
resolved
those
and
the
continuing
work
on
that
and
then
I
started
reviewing
the
the
Lyman
extruder
instructions
and
PDF
and
some
of
his
instructions
on
how
to
build
that
a
little
more
thoroughly
to
figure
out
some
of
the
specifications
on
the
arts
and
so
on.
There's
I
guess
things
that
could
be
changed
in
there.
C
Maybe
but
I
assume
that
we
want
to
build
what
works
first,
that'll
be
the
goal
and
when
we
prototype
it
differently
in
the
future,
but
I've
gotten
most
of
the
visual
bottom
on
just
the
extruder
done
and
I'm
moving
on
to
the
D
winder
this
week,
anything
so
and
I
think
of
getting
quite
a
few
links.
It's
arranged
a
little
better.
Now
the
photos
and
arrows
to
kind
of
diagram.
Our
certain
parts
are
in
the
images
he
is
pretty
good
documentation
from
his
PDF
from
Thingiverse,
but
some
some
parts
are
a
little
confusing.
C
C
A
C
There's
see
most
of
the
parts
can
just
be.
You
know
just
a
few
order,
or
just
simple
MDF
and
parts
that
are
cut
up
sheets
that
are
cut
up
scraps
of
stuff
you
might
even
have
around
and
on
the
shop
that's
old
you
could
cut
up.
So
it
is
a
fairly
cheap
for
all
machine,
I,
think
other
than
you
know.
Some
of
the
electronics,
the
modern
stuff
is.
C
I
mean
there's
no
Arduinos
or
software
or
anything
like
that.
It
kind
of
just
put
it
together
and
I
think
it'll
work,
which
is
kind
of
nice
I
mean
I,
could
see.
People
might
want
to
do
it
without
Arduino,
make
it
more
open,
but
a
PID.
You
know
just
drop
it
in
PID
and
the
SSR
makes
it
fairly
easy
to
build.
A
C
F
C
A
C
A
No,
that's
that's
good!
So
it's
we
know
that
the
thing
works
for
him,
because
that,
in
an
email
communication
with
him
he's
got
three
of
these
working
right
now
and
he's
just
cranking
out
printing
filament
from
abs.
He
just
bought
like
a
you
know,
like
500
pounds
of
of
ABS
pellets
and
he's
just
extruding
his
own
filament
he's
got
three
of
them
mounted
on
the
wall
and
just
going
happily
at
it.
It's
a
very
simple
system.
A
It
appears
that
it
has
no
control
outside
of
pretty
much
temperature
set
and
then
just
on
and
off
for
the
like,
I'm
curious,
like
the
winder,
you
know
we
have
to
have
a
good
quality
of
the
filament
and
he's
getting
plus
minus
0.05
millimeters.
That's
really
good,
and
he
just
does
that
with
what
he
has
shown
there.
So,
let's
try
it
I
mean
that's,
that's
our
first
step
and
then,
given
that
we
have
no
experience
in
it.
Yet
we're
going
to
have
to
see
like
does
his
work
for
us
or
not
so
we'll
see.
So.
C
A
Okay,
so
so
that's
a
manual
he's
in
the
background
doing
stuff,
Jose
Jose
here
Jose
is
working
on
the
website.
He
not
here
today.
Cedric
see
Cedric
is
not
here.
By
now,
Cedric
did
the
the
new
new
extruder
for
the
3d
printer,
which
we
want
to
build
the
more
advanced
version
of
so
basically
the
open-source
extruder
from
the
original
crew
sy3.
So
it's
good
yeah.
So
that's,
let's
see,
for
example,
on
Thursday
he's
got
combined
file
into
one
video,
let's
see
so
he
posts.
So
that's
good.
A
A
A
Okay,
an
I/o
now
IO
is
not
here
either,
but
the
idea
with
iowa's
he's
working
on
a
basically
drawing
up
the
simplified
frame
made
out
of
PVC
pipe,
because
you
can
do
that.
Also
a
manual
communicated
he's
going
to
do
a
frame
out
of
just
plywood.
The
advantage
of
plywood
is
it's
low-cost
cheap,
but
whenever
they
work
for
us
here
we
have
a
lot
of
humidity
and,
for
example,
my
Ulta
maker
here,
which
was
the
made
of
wood.
It
started
to
rot,
get
fungus
on
it.
A
So,
with
high
humidity
wood
is
going
to
have
issues.
The
original
Ultimaker
was
wooden,
so
it
kind
of
started
getting
corroded
after
some
time.
Pvc
pipe
is
actually
quite
safe
from
corrosion.
So
that's
a
decent
way
for
a
for
a
printer
in
mune
to
environmental
effects,
but
very
simple
ways
to
make
a
frame
are
possible
and
we
just
then
add
our
frames
at
our
motion
elements
to
that.
A
But
that's
what
he's
working
on
for
a
low-cost
3d
printer
version,
so
that's
IO
Israel,
so
Israel
is
joining
us
and
so
that's
it
for
the
as
far
as
the
logging.
So
now
I'm
going
to
go.
So
it's
1139.
Let's
look
at
where
we
are
on
the
20-30
work
assignments
and
progress
updates.
So
ok,
so
what
I'm
going
to
do
is
go
over
the
language.
What
do
we
know
about
language,
agnostic
instructionals?
So
last
week
we
went
over
a
little
bit
of
that
on
slide,
8,
so,
basically
doing
very
simple,
simple
drawings.
A
A
Did
here
what
you
see
or
you
extract
the
ISO,
which
is
a
really
good
way,
because
to
get
you
the
perfect
images,
an
idea
is
to
strip
all
the
noise
out
of
it
just
strip
everything
outside
of
the
needed
parts,
and
you
can
look
at
if
you,
google,
IKEA
diagrams,
we
can
see
what
we're
talking
about
and
I
think
that's
on
the
the
protocol
page
on
the
wiki
I
think
has
it
has
a
sample
it's
actually.
The
page
is
called
IKEA
style,
fabrication
diagram
and
we
show
this
but
the
links
yeah
there
you
go.
A
So
that's
some
work
here.
This
is
I,
believe
national
I
guess
this
is
just
a
general
protocol
page.
So
the
specific
page
for
the
D
3d
printer
should
be
in
a
separate
page,
because
this
is
just
the
protocol
page.
But
if
you
look
at
Google
ikea
style
fabrication,
ikea
diagrams
from
ikea
furniture,
you'll
see
what
this
is
about
and
basically
stripped
down
all
the
excess
and
fossil
read
through
this,
but
now
the
next
next
thing.
A
So
the
things
I'm
just
continuing
this
standard
operating
procedures,
so
one
follow
the
script,
lay
out
the
procedure
in
your
presentation
and
use
a
cover
page
so
use
the
instructional
cover
page
which
reviews
before.
So
when
you
start
a
document,
we
have
this
nice
attractive
cover
page,
so
you
can
use
that
and
then
hyperlink
to
your
log
or
at
the
role
allocation
page
slide,
which
is
the
slide
number
six
here
with
a
document
link.
A
So
if
you're
working
on
us
currently
like
I'm
slide
six
we're
going
through
what
everyone
is
working
on,
you
can
link
link
that
to
that
and
then
fit
as
much
information
per
page
without
overloading
a
page.
So
remember
that
this
is
going
to
be
printed
in
the
printed
document
so
make
it
format
such
they
can
be
printed
on.
A
A
3d
printer
then
put
a
link
to
your
working
script
in
your
document,
so
your
source,
the
working
script,
is
your
source
and
then
put
a
link
to
the
isometric
source
files
from
freecad
in
your
document
as
well.
So
that
someone
who
can
look
at
your
document
can
edit
it
by
looking
at
the
script
and
looking
at
your
your
free
cat
files,
and
they
can
just
extract
things
from
there
and
now
we're
hearing
that
the
other
piece
of
source
is
your
Inkscape
files,
also
upload
your
Inkscape
files
and
link
to
them.
A
Now
what
I'll
do
is,
and
as
we
see
it
as
a
missing
procedure
like
we
need
a
nice
tight
procedure
to
show
a
good
working
example
of
this,
so
it
can
get
some
really
nice
product
here,
and
this
is
this-
is
pretty
good
stuff
I
mean
there's
very
few
people
who
end
up
doing
the
language
agnostic
instructional
step,
but
for
us
it's
critical,
because
we
want
to
make
the
workshop
experience
totally
replicable
that
you
can
literally
have
a
whole
workshop
full
of
people.
The
goal
like
the
metric
of
success
is
really
killed
instructor.
A
If
the
instructor
disappears,
what
happens?
Can
the
people
actually
have
enough
information?
Is
the
documentation
good
enough
that
everyone
can
actually
go
through
the
complete
build?
Even
if
the
instructor
is
not
there?
That
to
me
would
be
the
single
most
profound
metric
of
success
of
how
well
we
did
the
documentation
so
think
about
that?
A
Okay,
so
that's
on
a
language,
agnostic
instructions
and,
as
I
said,
I'm
going
to
work
on
doing
an
instructor,
a
type
instructional
for
that
this
is
part
of
our
curriculum
development,
and
maybe
I
could
actually
get
get
inspired
to
put
out
a
video
calling
out
for
curriculum
developers,
because
this
is
really
curriculum
development
teaching
ourselves
how
to
do
the
language
of
math
the
constructions.
Okay
with
that
said,
let's
talk
about
the
next
priorities
and
where
we
are
for
role
allocations.
A
So
we're
number
of
people
working
on
language,
agnostic,
instructionals
Abe,
is
working
on
a
filament
maker
and
the
one
thing
that
we
want
to
start
on
is
the
CNC
torch
table.
I
know
Chaz's
is
working
on
it
on
the
electronics
Chaz.
Do
you
want
to
pipe
into
to
the
discussion
today,
where
you're
at
on
that,
or
is
that?
Okay,
so.
A
A
C
E
E
A
Further
arduino,
we
can
use
the
same
control
code
as
before,
so
basically
the
marlin
that
we're
using
on
a
3d
printer.
You
can
just
use
that
with
QR
up
the
control,
3d
printer
control
interface
and
you
can
make
hit
a
key
on
the
QR
platform
to
move
the
axes
back
and
forth
so
that
the
same
software
that
we're
using
you
can
use,
as
is
to
do
the
testing.
A
A
So,
for
example,
if
you
want
to
do
a
torch
table
which
is
I'll
get
the
next,
we
can
run
multiple
motors
like,
for
example,
if
you
want
to
put
a
two
motors
per
side
using
our
even
our
tiny
NEMA
17
motors,
we
can
do
two
per
side
and
it's
got
say
on
a
y-axis,
you
got
two
y-axis.
You
got
two
motors
per
sites.
We
got
four
motors.
A
That
means,
instead
of
running
one
motor
on
the
wire
or
two
motors
on
Y,
like
we
do
with
a
current
3d
printer,
we
can
run
four
or
more
or
however
many
we
need
to
give
extra
power
for
the
larger
machine.
So
that's
the
general
idea
of
being
able
to
run
much
higher
power,
stepper
motors
or
more
of
them,
using
the
same
controller
by
simply
adding
an
external
stepper
driver
to
the
identical
same
electronics.
So
that's
good
Chas.
A
E
A
A
So,
for
example,
so
I
can
tell
you
that
you
can
actually
pull
that
up
and
I'll
teach
you
how
right
now.
So
you
got
the
d3d
page
and
then
the
details.
So
that's
our
working
page.
So
it's
an
exercise
in
collaborative
literacy,
you'd
be
tweeting
page.
We
got
to
have
modules,
so
there's
modules
item
number
nine
and
then
we
go
to
hardware
and
controls,
and
then
there
is
the
d
3d
controller
and
d
3d
marlin.
Those
two
lengths
give
us
a
lot
of
insight,
pretty
much
complete
documentation.
A
What
we
have
so
far
on
using
marlin,
which
is
the
software
and
the
controller
which
is
the
wiring
and
stuff.
So
those
two
pages
chad's
start
with
that
and
see.
If
what
you
need
there
is
there,
so
you
can,
for
example,
on
a
DVD
Marlin
page
you
can
download
the
Marlin
as
is
right
there
and
upload
it
to
your
Arduino.
So
that's
good
there
and
then
on
a
controller
page.
A
The
other
page
we've
got,
let's
see
how
much
we
have
on
electronics,
but
there's
some
wiring
like
yeah
there's
a
decent
there's,
there's
a
bit
of
information
on
the
wiring
on
those
two
documents
see
what's
missing
and
maybe
fill
that
in,
but
that's
a
good
start
right
there.
So
here
we
talk
about
the
basically,
you
have
to
plug
up
wire
up
this
board
to
the
stepper
motors.
It's
essentially
this
control
board.
A
One
of
your
axes
only
trick
is
that
the
board,
as
is
it
it
needs
to
have
a
thermistor
like
it
needs
to
know
that
the
temperature
on
the
extruder
is
okay,
so
actually
the
only
trick
to
that
is
you
have
to
like
short-circuit
the
thermistor
connection,
which
is
right
there
I'm,
showing
it
it's
actually
like
that
white
white
thing
with
my
pointer
there,
that's
the
thermistor,
actually
I,
just
have
to
put
wires
in
between
that
to
show
that
that's
closed
anyway.
This
explains
it.
So
you
can
get
a
lot
of
that
info
from
the
wiring.
A
So
if
you
have
any
more
questions,
please
email
me,
but
that's
that's
where
it's
at
be
3d
and
then
the
3d
modules
and
then
the
controller,
so
there
that
is
okay,
so
talking
about
the
CNC
torch,
one
inch
axis
so
I
want
to
talk
about
scalability
and
then
let's
see
how
we
can
allocate
roles.
So
on
the
scalability
national.
You
asked
about
how
you
know:
how
do
you
scale
the
little
3d
printer
to
a
larger
machine?
Well,
here's
the
idea!
A
The
idea
is
that
the
electronics,
you
can
use
the
exact
same
electronics
controller
but
use
larger
stepper
motor
drivers
which
Chaz
is
working
on
and
that
new
stepper
drivers
$8.00
instead
of
like
two
dollars
or
something
per
axis.
So
that's
the
way
to
get
the
control.
Now
the
mechanical,
the
mechanical
means
you
can
still
use
the
same
motors,
which
are
the
tiny
NEMA
17s
and
that's
what
we're
going
to
do
for
now.
We
might
actually
go
to
NEMA
twenty
three,
which
are
slightly
larger,
but
we
can
do
either.
A
We
can
do
NEMA,
17
or
NEMA
23.
Those
are
size
of
stepper
motors
now
for
for
replicability
like
to
show
the
build.
You
know,
building
upon
prior
work
model,
we
can
use
the
very
tiny,
NEMA
17,
even
on
a
torch
table,
because
each
one
of
those
has
like
15
pounds
of
drive
force,
which
is
enough
like
if
you
put
four
of
them
on
that
X
and
the
y
axis.
A
You
got
like
like
16
times
4
like
60
pounds
of
drive
rosettes
in
the
way
more
than
enough
to
drive
a
non-contact
torch
head
for
the
CNC
torch
table.
So
that's
that
but
you're
going
to
need
bigger
rods.
You
can't
go
get
away
with
the
8
millimeter
/
5/16
inch
rods.
You
need
bigger
rods,
so
we
are
going
to
so.
The
next
step
in
the
game
is
to
go
to
the
bigger
machines.
We
need
to
make
the
larger
3d
printed
pieces,
which
were
you
actually
already
have.
A
We
did
that
last
year
and
we
can
sit
in
the
missing
pieces
from
that
also
use
the
larger
3d
printed
pieces
and
one
inch
threaded
Rock
one
inch.
Sorry
one
inch
the
thread:
one
inch
rod
the
smooth
rods
and
then
the
belt
could
actually
be
the
same.
You
can
still
use
the
same
belt.
That
belt
is
good
enough
for
how
much
force
we
need
for
the
torch
table
so
most
same
parts,
and
then
you
need
a
bigger
frame.
A
Now
you
need
to
mount
this
somewhere,
but
the
next
step
on
a
CNC
torch
is
actually
to
draw
up
the
universal
access
details
in
the
one-inch
form,
and
this
is
what
I'd
actually
like
to
talk
about,
maybe
Cassie
and
to
Israel.
Maybe
you
guys
can
pair
up
and
I
can
guide
you
through
where
those
files
are
for
the
one
inch
and
starting
to
do
the
universal
access
remake
in
one
inch,
so
we
haven't
done
any
of
them.
A
We
do
have
the
3d
printed
pieces,
the
CAD
for
that
from
last
year,
but
beyond
that
now
we're
going
to
assemble
the
whole
axis
assembly
using
the
one-inch,
much
larger
rod
size,
so
I'll
follow
up
with
you
on
that.
I
won't
talk
too
much
about
that
right
now,
I
can
go
offline
once
we
allocate
other
roles,
but
what
I'll
do
after
this
meeting
is
simply
email
you
with
what
the
problem
statement
is
so
basically
use
larger,
3d
printed
pieces.
A
A
Everything
else
is
just
about
the
same
and,
of
course,
larger
frame,
so
we'll
have
to
do
a
larger
frame,
but
one
way
to
do
a
larger
frame
is
to
take
four
of
the
16
inch
frames
and
use
those
as
corner
pieces
to
hang
the
much
larger
one-inch
axis.
So
actually,
this
is
not
a
larger
frame.
Just
use
four
of
the
16
inch
d3d
frames
to
mount
your
axis
upon,
so
that
that
you
have.
You
just
need
a
hanging
point
to
mount
the
axis
D
3d
printers,
now,
okay,
but
the
magnets.
A
Sorry,
we
can't
do
that
anymore.
The
magnets
are
good
for
the
3d
printer,
in
this
case,
we're
going
to
have
to
use
the
existing
bolt
holes
that
are
within
the
carriage
the
3d
printed
pieces
to
attach
them
more
firmly
to
the
frame.
So
so
no
magnets.
We
move
two
bolts
now,
but
that's
okay,
because
you
still
use
the
identical
parts
you're
just
using
bolts
to
go
through
the
frame.
That
means
the
frame
will
have
to
have
a
few
holes
in
it.
A
So
each
frame
piece
wherever
you
attach
an
axis,
would
have
to
two
bolt
holes
minimum
on
each
side,
so
like
four
bolt
holes
per
frame,
piece
which
are
not
currently
in
a
CAD,
so
we
might
actually
want
to
add
that
to
the
cab,
so
I
would
say.
Add
this
to
the
CAD
frame,
but
that's
kind
of
beyond
the
scope
work
on
the
larger
the
basic
Universal
axis
we're
talking
about
now,
five
by
ten
feet.
This
is
large,
much
larger
five
feet
by
ten
feet
about
two
by
three
meters
inside.
A
This
is
a
full-scale
machine
that
gets
us
parts
for
the
tractors.
Brick
presses
everything
else
and,
like
Abe
talked
about
some
of
the
parts
per
se
for
the
filament
extruder,
he
said
there
was
a
few
fabricated
parts.
I
saw
some
of
those
parts,
they
can
be
two
CNC
torch
cut,
so
CNC
torch
cutting
is
a
very
powerful
industrial
tool,
but
it
will
get
you
you
guys
on
that.
A
But
that's
the
basic
problem
statement
reformulate
the
current
universal
axis
into
the
one
inch
rod
form
so
and
make
you
know:
let's
do
the
x-axis
first,
which
is
five
feet.
The
y-axis
is
going
to
be
ten
feet
and
then
there's
going
to
be
a
z-axis,
which
is
only
a
few
inches
that
you
just
need
to
move
the
torch
up
and
down
just
a
little
bit.
So
that's
that's
what
that
is,
and
also
there's
a
in
the
background.
We
also
have
another
project
going
DVD
Circuit
mill
that
Shane
is
working
about.
A
I
won't
talk
about
that,
but
the
only
thing
to
say
about
that
is
using
the
same
frame,
the
metal
frame
from
the
d3d
16
inch
version,
3d
printer
6,
16
inch
version.
We
can
use
that
same
frame
and
put
a
spindle
on
that
to
make
a
small
circuit
mill.
So
that's
some
really
good
work.
That's
going
to
get
it
happen,
June
18,
when,
when,
when
Shane
is
going
to
come
for
a
little
dedicated
project
visit
of
two
weeks
to
factory
farm
here,
to
work
on
that,
ok,
but
now
I'm
going
to
go.
A
So
that's
that's
a
bit
of
an
answer
to
Laszlo's
question:
how
do
we
go
to
the
larger
scale?
Things
and
you
have
to
kind
of
go
through
the
whole
design
say:
okay!
Well,
can
I
use
the
identical
thing
wherever
possible?
Yes,
use
that
use
the
same
belts,
use
the
same
motors
use
the
same
controller
use
the
same
same
16,
inch
frame,
feet,
frame
idea
so
basically
along
the
construction
set
approach.
Okay!
A
Achmed
he's
kind
of
disappeared,
Abe,
Abe,
you've
got
plenty
of
work
appears
on
the
filament
extruder
IO
will
have
to
follow
up
with
him
Jose
we
have
to
follow
up
Chas,
it
looks
like
he's
going.
Michael
will
have
to
follow
up
with
them.
Frank
will
have
to
cédric
Roberto
and
lash
loads
and
Baptiste.
A
And
did
I
miss
anyone
else
from
the
meeting
today.
Cassie
and
and
Israel
will
get
you
going
so
we
can
follow
up
on
that
and
we'll
communicate
on
a
3d
printer.
So
look
at
this
you
in
a
welcome
email.
You
have
the
link
to
the
deep,
the
open
source
ecology
network,
which
is
the
technical
discussions.
Go
there
put
communicate
publicly
there.
A
So
what
I'll
do
is
I
actually
write
the
email
but
I'll
post
it
on
the
network
and
just
let
you
know
that
I
posted
on
a
network,
so
everyone
can
see
the
discussion
so
put
all
the
discussion.
Don't
email
me,
the
netiquette
is
upload
files
to
the
wiki
and
send
links
to
them
and
send
links
to
don't
send
email
send
links
to
what
you
posted
on
the
public
development
page.
That's
the
way
we
want
to
roll
okay,
so
lash
flow.
Oh,
this
file
joined
us.
A
A
A
Okay,
that's
the
hangout,
let's
see
so
with
Laszlo
and
Roberto
I
think
you
guys
are
working,
but
let's
see
what's
a
good
thing,
you
can
work
on.
Definitely
you
can
continue
on
what
you're
doing
you've
got
the
scripts
lash
load.
Do
you
have
next
steps
that
you're
working
on
or
do
you
need
more
direction?
I.
A
A
A
And
let's
see
what
else
so
and
as
far
as
the
meeting
agenda
goes,
we
just
got
the
pretty
much
on
a
teamwork
assignments.
Let's
continue
all
the
questions
and
discussions
on
the
development
network
and
I'll
send
out
a
follow-up
email
so
that
everybody
has
each
other's
email
where
I'm,
including
Israel
and
Cassie,
on
to
the
email
thread,
because
there
is
that
email
thread
we're
also
keeping,
but
for
now
let's
go
through
the
questions
and
suggestions
page
so
does
anyone
have
any
questions
and
any
suggestions?
A
Okay,
what
else
to
talk
about
to
review
I'll
just
sum
up
here
we're
at
at
noon
time.
So
just
about
end
time
for
our
meeting
people
I,
would
say
yeah.
This
is
going
pretty
good,
I
mean
as
normal,
just
as
far
as
the
overall
review,
so
so
make
sure
you
do
the
feedback
questionnaire,
but
the
overall
reviews
I
mean
it's
pretty
good.
A
Where
my
response
to
this
is
that
yeah,
it's
a
wild
hairy
process
were
making
the
road
by
walking
and
definitely
missing
the
aspect
of
curriculum
or
protocols
or
instructions
on
how
to
do
the
stuff
that
we
do
so
standard
operating
procedures.
How
do
we
do
one
step
or
another?
So
that's
a
big
call-out
for
producing
curriculum,
getting
people
on
the
team
that
can
focus
on
documentary
role,
documenting
the
processes
and
I'm
going
to
step
in
to
do
the
instructional
on
the
language
agnostic
instructions
which
I
think
is
a
very
important
piece
of
the
puzzle.
A
Just
like
we
pretty
much
cracked,
the
the
exploded
part
animations,
but
for
a
new
person
doing
the
explode
apart
animations,
for
example,
we
don't
really
have
a
great
video
summarizing
that
whole
process
we've
got
excellent
product,
but
that
kind
of
a
project
would
lend
itself
to
somebody
joining
the
curriculum
development.
Looking
at
what
all
the
people
have
done,
asking
questions
to
how
everyone
did
everything
and
what
were
the
things
that
worked
and
tricky
things
and
and
easy
things.
A
So
we
can
do
a
nice
tight,
edited
video
on
the
exploded,
part
animations
and
now
on
the
language,
agnostic,
instructional,
so
I
think
we're
going
forward.
It's
pretty
good,
but
for
me
just
the
general
feedback
is
yeah.
We
were
definitely
short
on
it
as
we
get
more
and
more
people,
it's
harder
to
Train
everybody
up.
As
you
know,
every
week
maybe
a
new
person
comes
in
that
person
is
to
get
up
to
speed
as
soon
as
possible.
A
I
understand
that's
a
challenge
and
we
got
to
work
that
out,
but
that's
just
more
documentation,
more
standard
procedures
to
be
documented,
with
good,
good
videos,
and
that's
all
I
can
say
about
that
and
I
wish.
The
recruiting
function
would
provide
more
of
those
people,
it's
kind
of
slow
on
the
recruiting
thing.
A
I
think
we're
really
kind
of
like
the
guinea
pigs
here,
and
sometimes
it
might
get,
might
get
depressing
that
you
know,
are
we
making
progress
but
then
and
then
again
we
come
up
with
you
know
stuff,
like
Roberto
I,
get
a
little
depressed
and
then
I
see
that
kind
of
stuff
and
say:
oh,
this
is
great,
just
beautiful
we're
making
progress
so
keeping
the
morale
high,
because
where
we
are
doing
some
very
good
work
with
respect
to
this
all
being
open-source
workflows,
that
is
a
beautiful
part.
That
means
a
lot.
A
A
lot
of
people
can
join
this
process
and
in
retrospect,
so
I
did
the
TED
talk
in
2011.
It's
been
five
years
since
then,
I
wish
I
started
the
teams.
At
that
time
we
did,
and
we
basically
had
all
this
ad-hoc
development,
where
people
just
pop
popped
up,
and
they
said
yeah
yeah
I'm
so
excited
to
help.
But
the
thing
that
was
missing
there
was
the
idea
that
we
didn't
have
a
team
like
a
team
structure.
So
now
we're
definitely
working
on
that.
A
But
I
wish-
and
you
know
in
retrospect
of
course,
heyn
heyn
is
too
high.
Site
is
20/20,
as
they
say
definitely
should
have
started
on
the
very
dedicated
team
a
long
time
ago,
but
it
took
a
lot
of
learning
to
understand
that
that's
even
possible
the
first
breakthrough
right
there
was
learning
just
about
a
year
ago.
It
was
like
one
or
two
years
ago
now
that
that
is
even
possible,
that
people
will
work
in
a
dedicated
way
on
a
dedicated
team.
As
volunteers
like
when
you
think
about
that,
how
do
you
do
that?
A
How
do
you
motivate
people
to
do
it?
Well,
it's
possible,
so
we
know
it's
possible
and
we're
doing
that.
So
we've
cracked
that
barrier
and
now
the
question
is:
how
do
we
actually
scale
the
entrepreneurial
activity
where
people
are
getting
livelihoods
from
this
be
or
developing
products
to
a
good-enough
state
that
they're
sold
as
products
as
workshop
offerings
to
the
point
of
an
open
source
micro
factory?
A
That
could
be
a
standard
product
to
the
point
that
the
seed
eco-home
can
be
a
standard
product
that
can
roll
out
in
a
workshop,
you
know:
have
a
bunch
of
people
show
up
in
five
days
you
build
a
house
or
have
a
bunch
of
people
show
up
and
one
day
you
build
a
3d
printer
or
a
tractor
I
mean
that's
it's
a
very
attractive
enterprise
model.
I
think.
Definitely,
as
people
get
more
skilled
and
automation,
robotics
and
all
this
comes
in
information
access
is
unbridled.
A
The
possibility
of
people
making
their
own
stuff
is
an
absolute
inevitable
reality
and
I
think
we're
treading
the
foreground.
I
mean
basically
paving
the
way
on
that.
So
this
is
exciting.
Keep
doing
the
good
work
and
the
real
real
deal
for
this
starting
to
really
really
scale
is
a
few
few
projects
that
really
take
off.
A
Like
you
know
the
3d
printer,
whatever
it
is,
the
house,
the
open
source
micro
factory,
maybe
the
torch
table,
or
just
going
that
with
the
simplest
lowest
hanging
fruit
right
now,
which
is
the
3d
printer,
because
it's
a
well
understood
very
popular
device
as
a
way
to
get
everybody
involved,
as
opposed
to
making
the
much
larger
machines
like
the
tractors,
which
are
much
larger
entry
barriers,
so
we're
making
the
road
by
walking
anyway
keep
going
people.
We
were
working
on
the
the
3d
printer,
the
torch
table,
the
the
extruder
progress
is
happening.
So
thank
you.
A
F
F
F
A
F
You
keep
itself
from
basicity,
give
me
about
creating
my
power
utility
patent
leather,
that
we
natural,
open
question
is
when
you
have
found
lots
of
open
source,
so
could
the
alligator
you
want
to
be
inside
the
pipe
after
another
period,
the
size
that
I
want
to
insulate
the
tunnel
prisoner
compression?
If
every
time
you
do
that
has
been
bad
like
heavy
because
of
the
practical
work
in
a
process
by
dilemma.
Document
not
know
how
to
format
power.
F
A
A
Okay,
oh
good
point,
so
that
kind
of
gets
us
to
the
point
that
there's
three
main
instructions
we
need
to
do
like
there's
a
the
thing
we
haven't
done
right
now
is
to
perfect
the
library,
4d
3d
3d
printer.
What
that
means
that
there's
several
different
levels
of
manipulating
those
files,
one
is
the
absolute
complete
detailed
files.
Others
could
be
less
detailed,
much
lighter
files,
but
altogether
we
have
to
organize
around
several
levels.
One
is
the
part
files.
A
One
is
the
module
files
and
overall
assembly
files
which
the
workflow
can
be
greatly
optimized,
and
one
of
the
other
things
we
haven't
checked
for
is
actual
validation
of
how
each
of
those
parts
were
made.
So
we
have
to
actually
go
back
there
and
clean
up
and
literally
go
through
each
file
and
the
sequence
of
how
each
part
was
made
to
make
sure
that
the
the
parts
are
created
according
to
best
practice,
including
things
like
setting
proper
constraints
or
having
a
certain
kind
of
a
procedural
workflow.
A
Where
there's
a
pattern
of
how
you
actually
create
an
object
using
best
practices
because
I
know
people,
you
can
design
an
object
in
many
different
pathways
like
you
can
go
to
create
one
object
that
many
many
different
ways
can
get
you
there.
You
can
do
one
part
first
than
another,
that
order
could
be
changed
upside-down.
So
we
need
to
have
this
really
kind
of
makes
me
go
back
to
the
document
or
oh.
A
We
need
somebody
to,
and
that
takes
time
that
will
take
time
to
actually
go
through
how
every
one
of
the
files
that
we
already
have
has
been
made
to
approve
it
to
actually
say.
Okay.
This
is
according
to
best
practice,
so
it
won't
crash
it'll,
be
fast
and
smooth
as
anything
and
I
think.
The
ultimate
test
of
that
would
be
that
any
novice
can
take
say,
there's
a
folder
of
part
files
and
within,
like
an
hour
or
half
an
hour,
an
entire
d
3d
printer.
A
A
But
designed
properly
and
at
the
proper
level
of
detail,
you
can
pull
down
like
say
the
entire
axis
and
create
a
complete
perfected
file
that
won't
crash
that
you
can
get
the
explore
part
animations
out
of
it
without
crashing
or
the
language
agnostic
instructionals
without
problem.
That
has
to
be
standardized
and
I.
Think
since
you're
expecting
a
better,
better,
better
deal
from
from
freak
at
I/o
yeah,
we
can
work
on
that
to
make
sure
that
everyone's
following
the
best
practices,
because
it
is
workable,
but
it
needs
more
teaching
of
people
how
to
do
that.
A
So
I'm
observing
that
the
overall
part
library,
4d
3d,
needs
a
major
instructional.
How
do
you
actually
create
all
those
files?
And
how
do
you
work
with
them
effectively
so
that
the
newcomers
right
now
like
like
Cassie
and
Israel?
You
can
totally
just
jump
right
in
and
without
spending
a
lot
of
time
be
very
effective
and
then
the
second
thing
is
a
instruction
on
the
other
language,
agnostic,
instructional
and
the
instructional
on
the
exporter.
A
Part
animations,
which
are
some
of
the
major
milestones
we're
achieving
so
far
so
man,
the
real
question
is
here:
we
need
to
spend
some
time
documenting
and
try
to
find
more
people
for
the
team
to
do
that.
In
the
meantime,
what
I'll
do
is
I'll
I'll
work
on
the
language,
agnostic,
instructional
documentation
and
yeah,
we're
absolutely
missing
stuff
on
them
on
the
cleaning
up
all
the
the
free
cat,
4d
3d
that
we
already
have
that's
like
that's
a
kind
of
like
a
bigger
project
that
the
new
people
shouldn't
really
have
to
go
through.
A
So
I
apologize
for
that
in
advance
here,
but
we
just
need
that
to
be
documented.
More
and
maybe
you
know,
maybe
what
I
could
do
is
the
people
who
the
other
people
haven't
shown
up
to
this
meeting,
maybe
try
to
get
them
on
doing
some
of
that
documentation,
work
and
creating
standards
by
which
we
say.
Okay.
A
So
we
have
to
go
through
that
process,
so
we
have
to
kind
of
go
back
to
that
and
now,
as
new
people
are
coming
on
yeah,
we
kind
of
owe
you
that,
for
that
all
to
be
ready,
so
we're
kind
of
getting
backlogged
on
a
documentation
not
really
allowing
the
new
people
to
come
in
and
learn
as
fast
as
they
could
so
kind
of
bear
with
us.
As
we
get
this
worked
out
or
possibly
maybe
get
involved
in
it.
Maybe
I
don't
know,
maybe
I.
Oh,
maybe
you
can.
A
We
can
get
you
going
on
that
if
that's
interesting
to
you
to
actually
look
at
the
files
how
they
were
made
and
to
clean
them
up,
because
I
think
we
can
define
a
very
clear
procedure
where
we
might
actually
have
to
start
every
part
from
scratch
because
they
weren't
made
according
to
the
specific
procedures.
But
the
good
part
is
that
once
you
have
a
single
you
know
a
pot,
there's
40
items
all
together,
so
it's
only
40
items.
That's
really
good
from
that.
A
You
can
create
everything
else,
but
we
got
to
make
sure
that
at
the
very
beginning
those
40
parts
have
been
constructed
perfectly.
That's
start,
so
maybe
what
we
should
do
well.
Definitely
we
need
to
do
that
is
approve
every
single
part
that
it's
according
to
best
practice
and
therefore
the
best
practice
has
to
be
written
up
and
there's
some
documentation
of
best
practices
from
free
cat
and
for
OSC
we
may
have
some
other
additional
best
practices,
so
there's
a
bit
of
work
to
do
on
documentation.
A
A
Now
that
we're
scaling
to
more
and
more
people,
we
might
have
to
do
a
little
bit
more
work
on
it,
and
maybe
you
know
it's
actually
a
perhaps
a
good
case
for
Cassie
and
Israel,
because
you
kind
of
have
that
little
bit
of
a
learning
curve
to
go
on.
Maybe
the
new
people
you
know
good
idea
would
be
to
actually
get
you
all
on
doing
some
of
the
documentation
work
at
least
getting
familiar
with
with
that.
So
maybe,
as
you
yeah
I
mean
we
still
want
to
do.
A
The
CNC
torch
table
one
introversion,
but
maybe
we
start
that
process
process
by
saying,
okay,
we
start
with
this
cleaned
up
file,
and
then
we
move
on
to
the
1-inch
version
like
by
scaling
it
up
or
using
the
files
that
we
already
have
using
those.
So
so,
let's
add
that
discussion
of
cleaning
up
documentation
to
the
new
people's
workflow
yeah
yeah.
A
Yeah
thanks
Cassie,
yeah,
I
think
yeah.
We
really
need
to
go
back
yeah
now
that
we've
got
new.
People
were
really
because
because
the
the
idea
here
is
on
the
scalable
3d
printer
construction
set,
you
have
one
set
of
files.
You
can
build
any
kind
of
machine
now
we
haven't
shown
it.
We
haven't
shown
a
case
where
somebody
in
like
half
an
hour
designs,
a
complete
printer
that
we
haven't
done.
Yet
that
means
our
files
are
not
good
enough.
It
may
be
too
messy
too
heavy.
A
They
might
not
have
the
right
level
of
abstraction.
What
do
I
mean
by
level
of
abstraction?
That
means
that,
once
you
go
to
a
complete
machine,
you
need
to
not
use
the
fully
detailed
files
like,
for
example,
screws
and
use
the
threads
on
all
the
screws.
That
would
make
the
machine
into
like
a
gig
gigabyte
of
memory.
If
you
included
all
the
threads
and
the
hundreds
hundreds
screws
right,
the
threads
weigh
a
lot.
A
They
take
a
lot
of
memory,
so
we
have
to
have
the
correct
level
of
abstraction
everywhere
and
I
think
that
the
metric
would
be
okay.
Anyone
can
now
take
download
the
files
that
we
have
for
the
existing
3d
printer
and
literally,
we
should
be
able
to
teach
a
novice
in
like
an
hour
of
dedicated
instructional
time
or
a
couple
of
hours
how
to
design
their
own
3d
printer
if
they
know
how
the
parts
go
together.
So
so
just
a
manipulation
part
like
for
us
that
we
have
done
it.
A
We
should
be
able
to
put
an
entire
printer
together
really
fast
and
we're
not
variant.
That
means
we
still
have
to
do
the
work
on
optimizing,
the
actual
design
process,
design
procedures,
so
one
product
that
comes
out
of
that
is
the
guide,
the
the
guide,
the
3d
printer
construction
set
manual.
How
do
you
actually
design
the
printer
and
how
these
freecad
to
effectively
work
with
the
files
that
we
have
and
which
files
do
you
want
to
use
where?
So?
That's
like
a
whole
course
there,
but
yeah
definitely
lots
of
documentation.
I'll
get
out.
A
So
I'll
talk
more
about
that
to
the
new
people
we'll
get
going
on
that,
so
we
can
actually
start
cleaning
up
the
old
files
and
it's
going
to
be
easier
for
everybody
because,
like
for
example,
at
I/o,
you
mentioned
I
think
what
you
mentioned
is
a
totally
tractable
problem.
You're
saying
that
freecad
is
just
hard
it's
hard
to
work
with
in
a
professional
way.
A
Well,
the
thing
is:
we
have
to
learn
a
different
way
to
approach
it
a
little
bit
but
I
believe
that
from
what
I've
seen
a
free
cat
so
far,
there
is
not
a
disadvantage
to
it
like.
If
you
use
it
properly,
you
can
get
really
fast
and
really
good
at
it
and
I
think
actually,
emmanuel
is
quote
right
now,
quite
good
and
fast
that
he
just
cranks
out
things
in
minutes
right
now,
but
that's
the
level
we
we
all
want
to
all
get
to
as
the
team
and
I
think
it's
quite
possible.
A
So
the
encouragement
is
there
yeah,
it
should
be
doable
as
long
as
you,
you
kind
of
invest
a
little
bit
of
time
to
know
what
to
do
with
in
free
CAD
and
that
we
can
document
the
certain
ways
to
operate
within
free
cab
that
prevents
crashes.
That
is
super
fast,
that's,
reliable
and
just
100%,
foolproof
and
I
think
we
can
get
there
and
for
the
things
that
are
not
there.
A
That's
where
we
go
to
then
the
programmers
and
say:
okay,
there's
this
known
bug
that
does
this
and
join
the
the
Freak,
a
developer
developer
team
to
actually
clean
that
up
within
the
free
CAD
source
code.
So
that's
a
call-out
for
for
developers
who
are
programmers
and
we
can
start
recruiting
for
those
kinds
of
people.
So
that's
that's
what
we
want
to
do
here,
but
for
now
I
think
I'll
quit
at
this.
We
ran
a
little
bit
over
time,
but
welcome
to
the
new
people.
A
Let's
continue
the
discussion
on
on
the
network
and
what
I'll
do
is
I'll
start
cleaning
up
the
I'm
going
to
go
start
looking
at
all
the
files
we
have
so
far
for
the
d3d,
because,
as
we
need
to
go
to
the
one-inch
version,
we
need
to
make
sure
that
that's
all
clean
and
the
ways
of
how
we
design
it
is
at
least
a
basic
clear-cut
instructional,
or
how
to
take
all
the
files
and
work
with
them,
because
right
now
it's
kind
of
scattered
over
the
wiki.
So
it's
a
great
case
for
documentation.
A
A
A
Next
page
next
page
processor,
boom
review,
general,
immediate
timeline
and
meeting,
so
everyone
knows
priorities.
We
can
identify
what
might
be
taking
too
long.
So
we
can
reprioritize
as
me.
The
priority
details,
help
focus
and
prevent
time
wasted
and
minor
issues,
and
then
we
can
move
towards
doing
the
burndown.
Eventually,
who
said
that
that's
pretty
good.
A
That's
good,
so
the
a
maybe
that's
good,
so
in
so
in
a
team
agenda,
I'm
going
to
try
to
be
better
and
pull
as
soon
as
this
meeting
is
done,
I'm
going
to
make
a
copy
of
this
team
agenda
for
the
I'm.
Sorry,
that's
may
15
there
for
the
May
22nd
meeting
and
then
please
review
the
agenda
before
the
meeting
and
keep
me
to
task
I'm,
not
sticking
to
the
agenda,
so
there'll
be
one
way
to
do
that.
A
What
else
that's
good
besides,
that
I
think
that's
about
it
for
now,
we'll
follow
up
over
the
over
the
internet
on
a
discussion
group.
Thank
you
for
participating
and
we'll
continue
from
there
closing
the
discussion
here.
Please
continue
all
the
discussions
on
the
network
and
email.
So
thank
you
and
great
job.
Everyone
I
think
this
is
moving
forward.
It's
a
little
tricky
but
yeah.
We
really
see
the
big
case
for
documentation
is
better
documentation
as
we
keep
building
the
team
because
that's
going
to
be
critical.