Open Source Ecology - User contributions [en]

File:Subversivmesseday1.JPG

2009-05-14T14:10:19Z

SamRose: Day one of Subversiv Messe Linz, Austria

Day one of Subversiv Messe Linz, Austria

Talk:Open Source Fab Lab

2009-02-16T00:19:48Z

SamRose:

Let's talk about a learning curriculum for BRL-CAD.

It would be great to get several people proficient in BRL-CAD usage

A parallel project could be to develop easier to use interfaces for BRL-CAD.

We can develop this curriculum while we learn, right here in the wiki.

I will start placing notes at [[BRLCAD_learning_notes]]

Let's also seriously explore [[Open Cascade]] http://www.opencascade.org/

[[User:Jeremy|Jeremy]] 20:57, 14 February 2009 (PST)
OpenCascade sounds pretty cool, if it has a better UI with dragging and stuff and not just typing in coordinates like I guess BRLCAD does.

OpenCascade apparently has some kind of CAE and CAM functions or they said it integrates them somehow? We should definitely look into that if so. I'm trying to install OpenCascade but haven't figured it out yet. What do you suggest is the best way to install it with everything I need and then start it? Some tutorials have all the command lines needed to install and start a program. Maybe you can document it faster than I can find it, Sam. Take care!

Jeremy, what operating system are you working with, exactly?--[[User:SamRose|SamRose]] 16:19, 15 February 2009 (PST)

Talk:Open Source Fab Lab

2009-02-16T00:19:32Z

SamRose: Jeremy, what operating system are you working with, exactly?

Talk:Open Source Fab Lab

2009-02-14T21:55:32Z

SamRose:

Talk:Open Source Fab Lab

2009-02-14T21:53:00Z

SamRose: Let's talk about a learning curriculum for BRL-CAD.

Category:Collaborators

2009-02-11T16:23:29Z

SamRose:

The people who collaborate here...

List yourself by placing "<nowiki>[[Category:Collaborators]]</nowiki>" on a page with you name on it.

Category:Collaborators

2009-02-11T16:22:50Z

SamRose: New page: The people who collaborate here... List yourself by placin <nowiki>Category:Collaborators</nowiki> on a page with you name on it.

The people who collaborate here...

List yourself by placin <nowiki>[[Category:Collaborators]]</nowiki> on a page with you name on it.

User:SamRose

2009-02-11T16:21:54Z

SamRose:

I'm Sam Rose

http://socialsynergyweb.org/network is the place where I park my own work.

I figure out how to make things happen.

I am working on bringing http://socialsynergyweb.net/cgi-bin/wiki/FrontPage here (Open Business Models).

=== Notes ===

To investigate:

http://www.hpfem.jku.at/netgen/

http://pdb.finkproject.org/pdb/package.php/netgen

http://www.opencascade.org/getocc/require/

http://www.opencascade.org/occ/areas/cadcamproducts/

http://blenderartists.org/forum/showthread?t=54673

http://www.editthis.info/opencam/Main_Page

[[Category:Collaborators]]

User:SamRose

2009-02-11T16:18:59Z

SamRose:

I'm Sam Rose

http://socialsynergyweb.org/network is the place where I park my own work.

I figure out how to make things happen.

=== Notes ===

To investigate:

http://www.hpfem.jku.at/netgen/

http://pdb.finkproject.org/pdb/package.php/netgen

http://www.opencascade.org/getocc/require/

http://www.opencascade.org/occ/areas/cadcamproducts/

http://blenderartists.org/forum/showthread?t=54673

http://www.editthis.info/opencam/Main_Page

[[Category:Collaborators]]

User:SamRose

2009-02-11T16:18:37Z

SamRose:

User:SamRose

2009-02-11T16:17:23Z

SamRose:

Talk:Wiki Documentation Standards

2009-02-10T19:43:06Z

SamRose: we can discuss here if you want

We can discuss here if you want...

Wiki Documentation Standards

2009-02-10T15:56:23Z

SamRose: /* On OSE Wiki */

=Introduction=

As the number of contributors to the OSE Wiki is growing, it is time to begin defining standards for content. Wikipedia is a good example of clear formatting and standards. Our standards are by nature more demanding, since we are not only re-presenting knowledge as Wikipedia does, but also developing/inegrating designs at the same time. A collaborative multimedia strategy for accomplishing this task successfully is yet to be defined and perfected. Our aim is to start this process, and make significant contibutions thereto.

=On OSE Wiki=

Todo items for wiki development:

* We need some kind of template flag to place at the top of each page, to show where it lives in [[Development Work Template]] process. (a couple of days work).

* We need to install semantic media wiki extensions, and refactor pages to include semantic links, which will help us bridge our work with the work of others in an open way(and allow a bridge between OSE Drupal and OSE Media Wiki, and other projects. (probably a 1 to 2 month project, if 4-5 people help). Also, within the wiki, this would allow us to flag dependencies in logical ways. We would need to analyze and create a realistic workflow for this. We can also help other wikis participate in [http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData LinkingOpenData] in this way (like appropedia). Then, we can start to build open source web applications that can let you logically combine data from multiple locations, and output a unique collection as pdf, a repository, a new wiki, etc.

* We may need to create templates for steps in the [[Development Work Template]] process.

* Invite some volunteers to help with the above.

==Using Category==

Media wiki offers an affordance that allows exporting whole collections of pages by category. Pages in media wiki may have multiple categories. So, we should use category both in the way that it is being used now, plus

==Workflow==

One mistake that Wikipedia makes is to make ambiguous rules that people then use as a foundation for different agendas.

Therefore, we need a *fair*, objective criteria for quality of articles:

1: No deletion (unless page is total spam). Space on OSE wiki is cheap. It is better to keep a page, and edit it, than to delete. Category system can be used to map pages that are considered to be part of specific collections (like actual projects in progress vs an idea).

2: We should use a system of flags at the top of pages that let people know what needs to be done.

Criteria could be:

* There is a clear statement of purpose
* There are verifiable references to any claims made
* Templates are used where applicable
* pages maintain higher quality when they have maintainers. So, a page should list declared maintainer(s). These are the people who are responsible for creating, and upkeep of the page.

* please list anything I may be missing here...

=Exporting from wiki=

[[Category:Documentation]]

(draft in progress...not complete)

Structure your work stages according to [[Development Work Template]].

For each stage, first document text on wiki, as described above. This will allow others to work with you on text as project develops.

Click on Printable Version in left sidebar, right cick on page and save as "pagename.html" where pagename = the name of the wiki page.

Download Python http://www.python.org/download/releases/2.5/

Download Mercurial http://www.selenic.com/mercurial/wiki/

Place all of your files into a folder

navigate to that folder in your terminal (or Putty terminal in windows).

type "hg init"

This is will initiate the files into a repostiory of their own

Type "hg add", which will add your files to the repository.

Type "hg ci -m 'you notes and messages here'

Also usable: http://www.selenic.com/mercurial/wiki/index.cgi/OtherTools GUI clients for mercurial.

..more to come

Wiki Documentation Standards

2009-02-10T15:18:42Z

SamRose: /* On OSE Wiki */

Wiki Documentation Standards

2009-02-10T15:17:00Z

SamRose: /* Exporting from wiki */

Wiki Documentation Standards

2009-02-10T15:14:29Z

SamRose:

Wiki Documentation Standards

2009-02-09T20:01:56Z

SamRose: /* Basics */

Wiki Documentation Standards

2009-02-09T19:58:12Z

SamRose: /* Basics */

Wiki Documentation Standards

2009-02-06T15:46:27Z

SamRose: /* Basics */

Test Embed

2009-01-21T23:09:40Z

SamRose: A test embed with new settings

Open Source Fab Lab

2008-09-13T15:39:42Z

SamRose: /* Software */

=What is an Open Source Fab Lab=

The Open Source Fab Lab is a robust flexible and digital fabrication facility. When the enabling information is available, a skilled worked may replicate the Fab Lab at the cost of materials. The tooling package that we are considered is based loosely around the [[MIT Fab Lab item list]].

=OSE Open Source Fab Lab=

For the particular purposes of OSE's [http://openfarmtech.org/index.php?title=UM_Presentation Global Village Construction Set], here is a tool set that we need. It relies on proven techniques - no new inventions are needed - and immediate applications are the focus. The following list is Phase 1 technologies - primarily the equipment used in flexible and digital fabrication. See also [[Fab Lab Phase 2]], [[Fab Lab Phase 3]], [[Fab Lab Phase 4]], and [[Fab Lab Phase 5]].

#'''XYZ Acetylene Torch, Plasma Cutter, and Router table''' - CNC controlled, $1200 in parts. Three different cutting heads are interchangeable. This is for heavy duty metal, wood, and other material cutting with applications to tractor parts, CEB parts, sheet metal cutting, etc. Preparation of structure for many electromechanical devices.

#'''Multimachine''' - $700 in parts, $1500 with CNC control. This is for general purpose lathing, milling, drilling, and other rotary cutting/abrading/tooling applications. It is relevant to the preparation of rotors, shafts, bolting holes and patterns, milling metal shapes, fabricating cutting tools, and other cutting, abrading, and subtractive machining operations.

#'''Circuit Fabrication''' - $600 in parts - high precision version of XYZ table for fabricating electronic circuits and other very precise objects.

#'''RepRap''' - $500 in parts - a 3D printer for additive fabrication. We are interested especially in fittings for custom plumbing applications (water systems, chemical engineering processes, etc) and small parts for many applications. This printer can be used to make molds for casting plastics and metals

#'''Laser Cutter''' - $3000 in parts - extremely precise cutting of metals and other substances, requiring no finishing of edges. Useful for making precise rotor disks (solar turbine) and many other parts.

#'''Casting and Extrusion''' - plastics, metals, glass, and ceramics. This is for casting engine blocks and other metal parts; for sheet extrusion of plastics (glazing applications); making glass windows or glass blocks; making insulators. Also for making extruded metals and plastics - wire, tubes, rods; as well as insulated wires. Alloys and composites may be mixed with this equipment.

=Existing Work=

#http://reprap.org/bin/view/Main/WebHome - a well-developed 3D printer project - already achieved self-replication
#http://opensourcemachine.org/node/2 - project implementations built by developer - I don't know if anyone replicated this yet; documentation needs development; Factor e Farm engagement - parts list and drawings being developed (6.08) and implementation scheduled for July, 08
#http://openfarmtech.org/index.php?title=Torch_Table - Factor e Farm progress - all materials sourced, torch table ready for assembly and connection to LinuxCNC - need a volunteer to visit us here to build this
#http://www.appropedia.org/Callooh - circuit fabrication router - project on paper; code work in progress
#http://www.instructables.com/id/CO2-laser-that-cuts-sheet-metal/ - CNC laser cutter for metal. There is evidence that by using laser engraver tubes ($200 each), say 10 of them, an industrial power laser can be put together at reasonable cost. The challenge is to work out the optics for paralleling the beams

=Software=

Message from Sam:

Marcin, I am in transit right now. But, a quick reply:

Although it is extremely difficult to learn to use, http://www.brlcad.org/ is the most robust that I have tried this far.

http://www.qcad.org/qcad.html is also really nice for 2D CAD work.

http://www.linuxcnc.org/ looks awesome, but is only an "Enhanced Machine Controller", and doesn't provide CAD drawing, nor CAM toolpaths (G-code drawing). What it does is interpret g-code toolpaths to move the actual XYZ table, or whatever machine you are controlling.

So, linuxcnc is essential, but as I have no machines to run yet, i have not had much of a way to test it out.

Also, for non-commercial use http://fab.cba.mit.edu/about/fab/ (cam.py and cad.py) those are some simple but useful software programs both cad drawing and cam toolpath generation (but are not fully open source, as we discussed earlier)

I am still searching for other software, but you can really do a lot with brl-cad and q-cad.

I still want to try http://www-rocq.inria.fr/OpenFEM/ and http://avocado-cad.sourceforge.net/ and http://www.cademia.org/frontend/index.php?sub=29 and http://www.opencascade.org/ don't know anything about those yet.

== BRL-CAD ==

If you plan on trying to use BRL-CAD, the PDF's on this page are essential reading http://www.brlcad.org/wiki/Documentation

==BRL-CAD Industry Diagram==
[[Image:BRL CAD.jpg]]

== Other Software Sam Rose is evaluating ==

* [Fandango http://www.soffernet.com/jaime/fandango/kfandango-doc.html] a C++ 3D CAD package with Python extensions.

* http://www.pythoncad.org/ (2D CAD a dead project but workable software QCAD probably a better choice here)

* GIT DARCS or Mercurial as a repository for DFX or other formats

also will be copying to this tag http://delicious.com/srose/opensourceecology

Open Source Fab Lab

2008-06-12T14:00:29Z

SamRose: /* Software */ http://www.brlcad.org/wiki/Documentation

=What is an Open Source Fab Lab+

=Existing Work=

http://www.appropedia.org/Callooh

=Software=

Message from Sam:

Marcin, I am in transit right now. But, a quick reply:

Although it is extremely difficult to learn to use, http://www.brlcad.org/ is the most robust that I have tried this far.

http://www.qcad.org/qcad.html is also really nice for 2D CAD work.

http://www.linuxcnc.org/ looks awesome, but is only an "Enhanced Machine Controller", and doesn't provide CAD drawing, nor CAM toolpaths (G-code drawing). What it does is interpret g-code toolpaths to move the actual XYZ table, or whatever machine you are controlling.

So, linuxcnc is essential, but as I have no machines to run yet, i have not had much of a way to test it out.

Also, for non-commercial use http://fab.cba.mit.edu/about/fab/ (cam.py and cad.py) those are some simple but useful software programs both cad drawing and cam toolpath generation (but are not fully open source, as we discussed earlier)

I am still searching for other software, but you can really do a lot with brl-cad and q-cad.

I still want to try http://www-rocq.inria.fr/OpenFEM/ and http://avocado-cad.sourceforge.net/ and http://www.cademia.org/frontend/index.php?sub=29 and http://www.opencascade.org/ don't know anything about those yet.

== BRL-CAD ==

If you plan on trying to use BRL-CAD, the PDF's on this page are essential reading http://www.brlcad.org/wiki/Documentation

==BRL-CAD Industry Diagram==
[[Image:BRL CAD.jpg]]

Multimachine & Flex Fab

2008-03-08T18:00:52Z

SamRose: /* Flex Fab - Current Work */

{{Site header}}

----
Multimachine & Flex Fab- www.multimachine.net/ shows it - a general purpose metal fabrication tool including lathe, mill, and drill press. This could be the central tool piece of a flexible workshop - and this item is already open source! I have not assessed this more fully, but it appears to be a promising candidate to address tooling needs for a community- at absolutely rock bottom cost - eliminating thousands of dollars of expenditure requirement for similar abilities. The capacities and practicality of this lower tech 'personal fabber' need to be assessed fully. The multimachine could be the centerpieces enabling the fabrication of electric motor, CEB, sawmill, OSCar, microcombine and all other items that require processes from milling to drilling to lathing. Crucial.

=Collaboration=
==Review of Project Status==

We are currently assembling and evaluating the components that would make a robust flexible fabrication facility. To date, our list of proposed tooling is:

Machining:

===Multimachine Development (Zerohour template)===

#'''The Theory:''' ''The underlying theory in a nutshell.'' The Theory must be presented as a working hypothesis that is being explored and tested. There must be an experimental procedure to test the theory- the theory must be testable. The Theory question must be well-posed: an answer must exist. If any of these criteria are missing then the project will not move forward effectively.
# '''Existing problems''' in the real world that relate to this theory, a brief description.
# '''Proposed way''' to apply the theory to those existing problems, the context or pre-requisites for this solution (solution in this case is application of the theory)
# '''Related existing work''' that verifies feasability with context summary of links to those references
# '''Related existing data''' or facts that support theory
# '''Existing constraints''' and barriers to deploying
# '''Related existing work that argues against''' theory (or summary and link to a place where this already exists)
# '''facts and data''' that support arguments against theory
# '''A brief summary''' about how this is related to Open Source Ecology (Relevance to OSE) core values
# '''Links''' to partner site references

===Multimachine Parts list, Materials list, dimensions specs, assembly file===

This will be a first draft of a spec file for multimachine

#Multimachine - http://opensourcemachine.org/ , and documentation: http://opensourcemachine.org/book
##Add CNC numerical control to its xyz motion to automate milling and lathing operations
##Include long lathe bed for CNC milling of roundwood for [http://sustainablescience.org/ LPSA] structures ''(would a larger than spec multimachine be needed to accomplish this large lathing? it seems to be the case)''

#Torch table - similar to the [http://torchmate.com/overview/index2.htm Torchmate]
##Commercial kits start at $4k from Torchmate
##Open source CNC version could cost $1k
##Torch attachment is the basic tool

Materials
#Plastic extruder - see Extruder_doc.pdf at [http://www.fastonline.org/CD3WD_40/CD3WD/INDEX.HTM this library]
##Ok, but who can translate that publication to English?
#Metal casting - what is the best low-cost, robust solution available here?

Electronics:
#Circuit fabrication - solution etching or a PCB mill?
##[http://www.elektor.com/extra/profiler-milling-machine-from-a-kit.91274.lynkx PCB mill kit] available for about $2500
#PC oscilloscope

The above minimal toolset includes major machining, metal cutting, metal casting, plastic extrusion, and electronics capabilities. We are talking of cars, solar turbines, motor controls, CEB machines, agricultural combines, and so forth from this set. Plastic and metal forming, and subractive machining of all types, is covered. Thus, we are talking of producing advanced technology '''at the cost of materials''', and in particular, at the cost of waste stream materials, if, for example, scrap aluminum is melted and cast into motor housings and other useful parts.

===Multi machine Bill of materials 2 Block version===

(taken from http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf)

====Engine blocks suggested specs ====

http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf calls for a 3 7/8" Bore inline 6 cylinder engine (not a sleeve bore engine block).

====Engine blocks meeting criteria====

* http://en.wikipedia.org/wiki/AMC_Straight-6_engine#4.0 (Stock Bore size 3.88" in)

* http://en.wikipedia.org/wiki/Ford_Straight-6_engine#Fourth_generation (Stock bore size 3.5" in. Could possibly be bored over to 3.88. A call to a machine shop can confirm)

* Cummins 6BT 5.9 L B5.9 4.01"in bore (this engine is an option for Dodge Ram, and was agricultural engine in 1980's) Can be machined to close to 5 inch bore. ***Needs to be machined with Boring bar, or accurate boring machinery.*** '''Probably best candidate for largest Spindle Bore'''

====Three bearing spindle and chuck assembly====

====Other Parts (this list will be cleaned up)====

* You will need a smaller cast iron block for the vertical slide. Well, not exactly at this stage but you will need it when assembly first begins and it is easier to search for it while you are searching for the “big” block. What ever you choose, it needs to be as short and heavy as possible. An iron V6 will probably work fine or look for a very common small Dodge D50 truck four cylinder block. I've used everything from a Model A Ford to a Volvo turbo block. (2) 4' of 4" OD "round" (if possible, most is not truly round) pipe for the over arm. Remember that the overarm may not be needed for some machines but is critical for others. At the very least, make the #1 cylinder bore able to be retro-fitted to an available size of pipe without having to take the entire machine apart to have it re-bored later.

(3) A 20?" long piece of extra-extra heavy wall 2 1/2" xxhw pipe or a similar sized hollow bar to use for the spindle. The length of course depends on the size of the engine block that you use. Try to leave at least three extra inches of spindle outboard of the pulley. Different kinds of tooling like a traveling head boring bar may need this space. Try not to settle for less than a 1 3/4" spindle bore on a short bed lathe that is to be used for a wide range of projects. (4) 2 roller bearings and a flange or home cast thrust bearing The roller bearings could be anywhere from about 2 1/8" to 2 3⁄4" ID (assuming 2 1/2" xxhw pipe) and between 3 7/8" and 4 1/8" OD. The flange bearing (third spindle bearing) bore could be a little smaller than the roller bearing IDs and the pulley bored slightly smaller still. Think seriously about using those Metric 100 mm spindle bearings. (5) A threaded chuck or back plate to test the spindle thread if you are going to use a threaded spindle. (6) A 1 1/2”" slice of 3-1/2" steel shaft or a similar sized ZA-12 casting that can be bored to fit the spindle. It will be needed for the bearing adjuster. Get at least 6 extra two inch "slices" for horizontal mill arbors, boring heads, fly cutters, thrust bearings etc. (7) A 2" washer for the floating part of the adjuster. (8) A 1 or 2 groove 12" OD pulley that can be adapted to fit the end of the spindle. (9) An approx. 6" long piece of 3 1/2" pipe to make into a separator for the roller bearings. Important, length is bore length less the width of the bearings. This spacer "floats in the cylinder so it should be just a few thousandth of an inch smaller than the bore, use shim stock and Locktite to make a snug fit because a loose fit can be the source of strange noises. Ends must be accurately machined or the bearings will slightly "cock" and cause great trouble! The spindle can be slightly undercut in the area underneath this spacer to make it easier to press on the front bearing. . (10) Used head gaskets for both blocks. (an easy way to mark holes but not absolutely necessary)

==Flex Fab - Current Work==

The main point for the Multimachine is to start documenting the toolpath generator (Smari McCarthy) -> controller -> motor -> hardware (Multimachine) system knowhow integration. Massive cost reduction, F10 or better - is possible. If we're lucky, we could get the Multimachine to the accuracy of electronic circuit fab.

**(Sam's temporary note: probably a simpler smaller design will be more appropriate for electronic circuit fab. something closer to "RepRap" construction would work just fine. Parts could be made for it on multi machine, in part...)**

Toolpath generation:

Controller integration:

Motors:

=Development Work Template=
#[[Flex Fab - Product Definition]]
##[[Flex Fab - General]]
##[[Flex Fab - General Scope]]
##[[Flex Fab - Product Ecology]]
###[[Flex Fab - Localization]]
###[[Flex Fab - Scaleability]]
###[[Flex Fab - Analysis of Scale]]
###[[Flex Fab - Lifecycle Analysis]]
##[[Flex Fab - Enterprise Options]]
##[[Flex Fab - Development Approach]]
###[[Flex Fab - Timeline]]
###[[Flex Fab - Development Budget]]
####[[Flex Fab - Value Spent]]
####[[Flex Fab - Value available]]
####[[Flex Fab - Value needed]]
##[[Flex Fab - Deliverables and Product Specifications]]
##[[Flex Fab - Industry Standards]]
##[[Flex Fab - Market and Market Segmentation]]
##[[Flex Fab - Salient Features and Keys to Success]]
#[[Flex Fab - Technical Design]]
##[[Flex Fab - Product System Design]]
###[[Flex Fab - Diagrams and Conceptual Drawings]]
####[[Flex Fab - Pattern Language Icons]]
####[[Flex Fab - Structural Diagram]]
####[[Flex Fab - Funcional or Process Diagram]]
####[[Flex Fab - Workflow]]
###[[Flex Fab - Technical Issues]]
###[[Flex Fab - Deployment Strategy]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Calculations]]
####[[Flex Fab - Design Calculations]]
####[[Flex Fab - Yields]]
####[[Flex Fab - Rates]]
####[[Flex Fab - Structural Calculations]]
####[[Flex Fab - Power Requirements]]
####[[Flex Fab - Ergonomics of Production]]
####[[Flex Fab -Time Requirements]]
####[[Flex Fab - Economic Breakeven Analysis]]
####[[Flex Fab - Scaleability Calculations]]
####[[Flex Fab - Growth Calculations]]
###[[Flex Fab - Technical Drawings and CAD]]
###[[Flex Fab - CAM Files]]
##[[Flex Fab - Component Design]]
###[[Flex Fab - Diagrams]]
###[[Flex Fab - Conceptual drawings]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Performance calculations]]
###[[Flex Fab - Technical drawings and CAD]]
###[[Flex Fab - CAM files whenever available]]
##[[Flex Fab - Subcomponents]]
#[[Flex Fab - Deployment and Results]]
##[[Flex Fab - Production steps]]
##[[Flex Fab - Flexible Fabrication or Production]]
##[[Flex Fab - Bill of materials]]
##[[Flex Fab - Pictures and Video]]
##[[Flex Fab - Data]]
#[[Flex Fab - Documentation and Education]]
##[[Flex Fab - Documentation]]
##[[Flex Fab - Enterprise Plans]]
#[[Flex Fab - Resource Development]]
##[[Flex Fab - Identifying Stakeholders]]
###[[Flex Fab - Information Collaboration]]
####[[Flex Fab - Wiki Markup]]
####[[Flex Fab - Addition of Supporting References]]
####[[Flex Fab - Production of diagrams, flowcharts, 3D computer models, and other qualitative information architecture]]
####[[Flex Fab - Technical Calculations, Drawings, CAD, CAM, other]]
###[[Flex Fab - Prototyping]]
###[[Flex Fab - Funding]]
###[[Flex Fab - Preordering working products]]
###[[Flex Fab - Grantwriting]]
###[[Flex Fab - Publicity]]
###[[Flex Fab - User/Fabricator Training and Accreditation]]
###[[Flex Fab - Standards and Certification Developmen]]
###[[Flex Fab - Other]]
##[[Flex Fab - Grantwriting]]
###[[Flex Fab - Volunteer grantwriters]]
###[[Flex Fab - Professional, Outcome-Based Grantwriters]]
##[[Flex Fab - Collaborative Stakeholder Funding]]
##[[Flex Fab - Tool and Material Donations]]
##[[Flex Fab - Charitable Contributions]]

=Component References=
*Oscilloscopes
**[http://www.easysync-ltd.com/index.html?lang=en-uk&target=d16.html PC Oscilloscope]

[[Category:Zero Hour]]

Multimachine & Flex Fab

2008-03-08T17:57:53Z

SamRose: /* Three bearing spindle and chuck assembly */

{{Site header}}

----
Multimachine & Flex Fab- www.multimachine.net/ shows it - a general purpose metal fabrication tool including lathe, mill, and drill press. This could be the central tool piece of a flexible workshop - and this item is already open source! I have not assessed this more fully, but it appears to be a promising candidate to address tooling needs for a community- at absolutely rock bottom cost - eliminating thousands of dollars of expenditure requirement for similar abilities. The capacities and practicality of this lower tech 'personal fabber' need to be assessed fully. The multimachine could be the centerpieces enabling the fabrication of electric motor, CEB, sawmill, OSCar, microcombine and all other items that require processes from milling to drilling to lathing. Crucial.

=Collaboration=
==Review of Project Status==

We are currently assembling and evaluating the components that would make a robust flexible fabrication facility. To date, our list of proposed tooling is:

Machining:

===Multimachine Development (Zerohour template)===

#'''The Theory:''' ''The underlying theory in a nutshell.'' The Theory must be presented as a working hypothesis that is being explored and tested. There must be an experimental procedure to test the theory- the theory must be testable. The Theory question must be well-posed: an answer must exist. If any of these criteria are missing then the project will not move forward effectively.
# '''Existing problems''' in the real world that relate to this theory, a brief description.
# '''Proposed way''' to apply the theory to those existing problems, the context or pre-requisites for this solution (solution in this case is application of the theory)
# '''Related existing work''' that verifies feasability with context summary of links to those references
# '''Related existing data''' or facts that support theory
# '''Existing constraints''' and barriers to deploying
# '''Related existing work that argues against''' theory (or summary and link to a place where this already exists)
# '''facts and data''' that support arguments against theory
# '''A brief summary''' about how this is related to Open Source Ecology (Relevance to OSE) core values
# '''Links''' to partner site references

===Multimachine Parts list, Materials list, dimensions specs, assembly file===

This will be a first draft of a spec file for multimachine

#Multimachine - http://opensourcemachine.org/ , and documentation: http://opensourcemachine.org/book
##Add CNC numerical control to its xyz motion to automate milling and lathing operations
##Include long lathe bed for CNC milling of roundwood for [http://sustainablescience.org/ LPSA] structures ''(would a larger than spec multimachine be needed to accomplish this large lathing? it seems to be the case)''

#Torch table - similar to the [http://torchmate.com/overview/index2.htm Torchmate]
##Commercial kits start at $4k from Torchmate
##Open source CNC version could cost $1k
##Torch attachment is the basic tool

Materials
#Plastic extruder - see Extruder_doc.pdf at [http://www.fastonline.org/CD3WD_40/CD3WD/INDEX.HTM this library]
##Ok, but who can translate that publication to English?
#Metal casting - what is the best low-cost, robust solution available here?

Electronics:
#Circuit fabrication - solution etching or a PCB mill?
##[http://www.elektor.com/extra/profiler-milling-machine-from-a-kit.91274.lynkx PCB mill kit] available for about $2500
#PC oscilloscope

The above minimal toolset includes major machining, metal cutting, metal casting, plastic extrusion, and electronics capabilities. We are talking of cars, solar turbines, motor controls, CEB machines, agricultural combines, and so forth from this set. Plastic and metal forming, and subractive machining of all types, is covered. Thus, we are talking of producing advanced technology '''at the cost of materials''', and in particular, at the cost of waste stream materials, if, for example, scrap aluminum is melted and cast into motor housings and other useful parts.

===Multi machine Bill of materials 2 Block version===

(taken from http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf)

====Engine blocks suggested specs ====

http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf calls for a 3 7/8" Bore inline 6 cylinder engine (not a sleeve bore engine block).

====Engine blocks meeting criteria====

* http://en.wikipedia.org/wiki/AMC_Straight-6_engine#4.0 (Stock Bore size 3.88" in)

* http://en.wikipedia.org/wiki/Ford_Straight-6_engine#Fourth_generation (Stock bore size 3.5" in. Could possibly be bored over to 3.88. A call to a machine shop can confirm)

* Cummins 6BT 5.9 L B5.9 4.01"in bore (this engine is an option for Dodge Ram, and was agricultural engine in 1980's) Can be machined to close to 5 inch bore. ***Needs to be machined with Boring bar, or accurate boring machinery.*** '''Probably best candidate for largest Spindle Bore'''

====Three bearing spindle and chuck assembly====

====Other Parts (this list will be cleaned up)====

* You will need a smaller cast iron block for the vertical slide. Well, not exactly at this stage but you will need it when assembly first begins and it is easier to search for it while you are searching for the “big” block. What ever you choose, it needs to be as short and heavy as possible. An iron V6 will probably work fine or look for a very common small Dodge D50 truck four cylinder block. I've used everything from a Model A Ford to a Volvo turbo block. (2) 4' of 4" OD "round" (if possible, most is not truly round) pipe for the over arm. Remember that the overarm may not be needed for some machines but is critical for others. At the very least, make the #1 cylinder bore able to be retro-fitted to an available size of pipe without having to take the entire machine apart to have it re-bored later.

(3) A 20?" long piece of extra-extra heavy wall 2 1/2" xxhw pipe or a similar sized hollow bar to use for the spindle. The length of course depends on the size of the engine block that you use. Try to leave at least three extra inches of spindle outboard of the pulley. Different kinds of tooling like a traveling head boring bar may need this space. Try not to settle for less than a 1 3/4" spindle bore on a short bed lathe that is to be used for a wide range of projects. (4) 2 roller bearings and a flange or home cast thrust bearing The roller bearings could be anywhere from about 2 1/8" to 2 3⁄4" ID (assuming 2 1/2" xxhw pipe) and between 3 7/8" and 4 1/8" OD. The flange bearing (third spindle bearing) bore could be a little smaller than the roller bearing IDs and the pulley bored slightly smaller still. Think seriously about using those Metric 100 mm spindle bearings. (5) A threaded chuck or back plate to test the spindle thread if you are going to use a threaded spindle. (6) A 1 1/2”" slice of 3-1/2" steel shaft or a similar sized ZA-12 casting that can be bored to fit the spindle. It will be needed for the bearing adjuster. Get at least 6 extra two inch "slices" for horizontal mill arbors, boring heads, fly cutters, thrust bearings etc. (7) A 2" washer for the floating part of the adjuster. (8) A 1 or 2 groove 12" OD pulley that can be adapted to fit the end of the spindle. (9) An approx. 6" long piece of 3 1/2" pipe to make into a separator for the roller bearings. Important, length is bore length less the width of the bearings. This spacer "floats in the cylinder so it should be just a few thousandth of an inch smaller than the bore, use shim stock and Locktite to make a snug fit because a loose fit can be the source of strange noises. Ends must be accurately machined or the bearings will slightly "cock" and cause great trouble! The spindle can be slightly undercut in the area underneath this spacer to make it easier to press on the front bearing. . (10) Used head gaskets for both blocks. (an easy way to mark holes but not absolutely necessary)

==Flex Fab - Current Work==

The main point for the Multimachine is to start documenting the toolpath generator (Smari McCarthy) -> controller -> motor -> hardware (Multimachine) system knowhow integration. Massive cost reduction, F10 or better - is possible. If we're lucky, we could get the Multimachine to the accuracy of electronic circuit fab.

Toolpath generation:

Controller integration:

Motors:

=Development Work Template=
#[[Flex Fab - Product Definition]]
##[[Flex Fab - General]]
##[[Flex Fab - General Scope]]
##[[Flex Fab - Product Ecology]]
###[[Flex Fab - Localization]]
###[[Flex Fab - Scaleability]]
###[[Flex Fab - Analysis of Scale]]
###[[Flex Fab - Lifecycle Analysis]]
##[[Flex Fab - Enterprise Options]]
##[[Flex Fab - Development Approach]]
###[[Flex Fab - Timeline]]
###[[Flex Fab - Development Budget]]
####[[Flex Fab - Value Spent]]
####[[Flex Fab - Value available]]
####[[Flex Fab - Value needed]]
##[[Flex Fab - Deliverables and Product Specifications]]
##[[Flex Fab - Industry Standards]]
##[[Flex Fab - Market and Market Segmentation]]
##[[Flex Fab - Salient Features and Keys to Success]]
#[[Flex Fab - Technical Design]]
##[[Flex Fab - Product System Design]]
###[[Flex Fab - Diagrams and Conceptual Drawings]]
####[[Flex Fab - Pattern Language Icons]]
####[[Flex Fab - Structural Diagram]]
####[[Flex Fab - Funcional or Process Diagram]]
####[[Flex Fab - Workflow]]
###[[Flex Fab - Technical Issues]]
###[[Flex Fab - Deployment Strategy]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Calculations]]
####[[Flex Fab - Design Calculations]]
####[[Flex Fab - Yields]]
####[[Flex Fab - Rates]]
####[[Flex Fab - Structural Calculations]]
####[[Flex Fab - Power Requirements]]
####[[Flex Fab - Ergonomics of Production]]
####[[Flex Fab -Time Requirements]]
####[[Flex Fab - Economic Breakeven Analysis]]
####[[Flex Fab - Scaleability Calculations]]
####[[Flex Fab - Growth Calculations]]
###[[Flex Fab - Technical Drawings and CAD]]
###[[Flex Fab - CAM Files]]
##[[Flex Fab - Component Design]]
###[[Flex Fab - Diagrams]]
###[[Flex Fab - Conceptual drawings]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Performance calculations]]
###[[Flex Fab - Technical drawings and CAD]]
###[[Flex Fab - CAM files whenever available]]
##[[Flex Fab - Subcomponents]]
#[[Flex Fab - Deployment and Results]]
##[[Flex Fab - Production steps]]
##[[Flex Fab - Flexible Fabrication or Production]]
##[[Flex Fab - Bill of materials]]
##[[Flex Fab - Pictures and Video]]
##[[Flex Fab - Data]]
#[[Flex Fab - Documentation and Education]]
##[[Flex Fab - Documentation]]
##[[Flex Fab - Enterprise Plans]]
#[[Flex Fab - Resource Development]]
##[[Flex Fab - Identifying Stakeholders]]
###[[Flex Fab - Information Collaboration]]
####[[Flex Fab - Wiki Markup]]
####[[Flex Fab - Addition of Supporting References]]
####[[Flex Fab - Production of diagrams, flowcharts, 3D computer models, and other qualitative information architecture]]
####[[Flex Fab - Technical Calculations, Drawings, CAD, CAM, other]]
###[[Flex Fab - Prototyping]]
###[[Flex Fab - Funding]]
###[[Flex Fab - Preordering working products]]
###[[Flex Fab - Grantwriting]]
###[[Flex Fab - Publicity]]
###[[Flex Fab - User/Fabricator Training and Accreditation]]
###[[Flex Fab - Standards and Certification Developmen]]
###[[Flex Fab - Other]]
##[[Flex Fab - Grantwriting]]
###[[Flex Fab - Volunteer grantwriters]]
###[[Flex Fab - Professional, Outcome-Based Grantwriters]]
##[[Flex Fab - Collaborative Stakeholder Funding]]
##[[Flex Fab - Tool and Material Donations]]
##[[Flex Fab - Charitable Contributions]]

=Component References=
*Oscilloscopes
**[http://www.easysync-ltd.com/index.html?lang=en-uk&target=d16.html PC Oscilloscope]

[[Category:Zero Hour]]

Multimachine & Flex Fab

2008-03-08T17:53:37Z

SamRose: /* Engine blocks meeting criteria */

{{Site header}}

----
Multimachine & Flex Fab- www.multimachine.net/ shows it - a general purpose metal fabrication tool including lathe, mill, and drill press. This could be the central tool piece of a flexible workshop - and this item is already open source! I have not assessed this more fully, but it appears to be a promising candidate to address tooling needs for a community- at absolutely rock bottom cost - eliminating thousands of dollars of expenditure requirement for similar abilities. The capacities and practicality of this lower tech 'personal fabber' need to be assessed fully. The multimachine could be the centerpieces enabling the fabrication of electric motor, CEB, sawmill, OSCar, microcombine and all other items that require processes from milling to drilling to lathing. Crucial.

=Collaboration=
==Review of Project Status==

We are currently assembling and evaluating the components that would make a robust flexible fabrication facility. To date, our list of proposed tooling is:

Machining:

===Multimachine Development (Zerohour template)===

#'''The Theory:''' ''The underlying theory in a nutshell.'' The Theory must be presented as a working hypothesis that is being explored and tested. There must be an experimental procedure to test the theory- the theory must be testable. The Theory question must be well-posed: an answer must exist. If any of these criteria are missing then the project will not move forward effectively.
# '''Existing problems''' in the real world that relate to this theory, a brief description.
# '''Proposed way''' to apply the theory to those existing problems, the context or pre-requisites for this solution (solution in this case is application of the theory)
# '''Related existing work''' that verifies feasability with context summary of links to those references
# '''Related existing data''' or facts that support theory
# '''Existing constraints''' and barriers to deploying
# '''Related existing work that argues against''' theory (or summary and link to a place where this already exists)
# '''facts and data''' that support arguments against theory
# '''A brief summary''' about how this is related to Open Source Ecology (Relevance to OSE) core values
# '''Links''' to partner site references

===Multimachine Parts list, Materials list, dimensions specs, assembly file===

This will be a first draft of a spec file for multimachine

#Multimachine - http://opensourcemachine.org/ , and documentation: http://opensourcemachine.org/book
##Add CNC numerical control to its xyz motion to automate milling and lathing operations
##Include long lathe bed for CNC milling of roundwood for [http://sustainablescience.org/ LPSA] structures ''(would a larger than spec multimachine be needed to accomplish this large lathing? it seems to be the case)''

#Torch table - similar to the [http://torchmate.com/overview/index2.htm Torchmate]
##Commercial kits start at $4k from Torchmate
##Open source CNC version could cost $1k
##Torch attachment is the basic tool

Materials
#Plastic extruder - see Extruder_doc.pdf at [http://www.fastonline.org/CD3WD_40/CD3WD/INDEX.HTM this library]
##Ok, but who can translate that publication to English?
#Metal casting - what is the best low-cost, robust solution available here?

Electronics:
#Circuit fabrication - solution etching or a PCB mill?
##[http://www.elektor.com/extra/profiler-milling-machine-from-a-kit.91274.lynkx PCB mill kit] available for about $2500
#PC oscilloscope

The above minimal toolset includes major machining, metal cutting, metal casting, plastic extrusion, and electronics capabilities. We are talking of cars, solar turbines, motor controls, CEB machines, agricultural combines, and so forth from this set. Plastic and metal forming, and subractive machining of all types, is covered. Thus, we are talking of producing advanced technology '''at the cost of materials''', and in particular, at the cost of waste stream materials, if, for example, scrap aluminum is melted and cast into motor housings and other useful parts.

===Multi machine Bill of materials 2 Block version===

(taken from http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf)

====Engine blocks suggested specs ====

http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf calls for a 3 7/8" Bore inline 6 cylinder engine (not a sleeve bore engine block).

====Engine blocks meeting criteria====

* http://en.wikipedia.org/wiki/AMC_Straight-6_engine#4.0 (Stock Bore size 3.88" in)

* http://en.wikipedia.org/wiki/Ford_Straight-6_engine#Fourth_generation (Stock bore size 3.5" in. Could possibly be bored over to 3.88. A call to a machine shop can confirm)

* Cummins 6BT 5.9 L B5.9 4.01"in bore (this engine is an option for Dodge Ram, and was agricultural engine in 1980's) Can be machined to close to 5 inch bore. ***Needs to be machined with Boring bar, or accurate boring machinery.*** '''Probably best candidate for largest Spindle Bore'''

====Three bearing spindle and chuck assembly====

==Flex Fab - Current Work==

The main point for the Multimachine is to start documenting the toolpath generator (Smari McCarthy) -> controller -> motor -> hardware (Multimachine) system knowhow integration. Massive cost reduction, F10 or better - is possible. If we're lucky, we could get the Multimachine to the accuracy of electronic circuit fab.

Toolpath generation:

Controller integration:

Motors:

=Development Work Template=
#[[Flex Fab - Product Definition]]
##[[Flex Fab - General]]
##[[Flex Fab - General Scope]]
##[[Flex Fab - Product Ecology]]
###[[Flex Fab - Localization]]
###[[Flex Fab - Scaleability]]
###[[Flex Fab - Analysis of Scale]]
###[[Flex Fab - Lifecycle Analysis]]
##[[Flex Fab - Enterprise Options]]
##[[Flex Fab - Development Approach]]
###[[Flex Fab - Timeline]]
###[[Flex Fab - Development Budget]]
####[[Flex Fab - Value Spent]]
####[[Flex Fab - Value available]]
####[[Flex Fab - Value needed]]
##[[Flex Fab - Deliverables and Product Specifications]]
##[[Flex Fab - Industry Standards]]
##[[Flex Fab - Market and Market Segmentation]]
##[[Flex Fab - Salient Features and Keys to Success]]
#[[Flex Fab - Technical Design]]
##[[Flex Fab - Product System Design]]
###[[Flex Fab - Diagrams and Conceptual Drawings]]
####[[Flex Fab - Pattern Language Icons]]
####[[Flex Fab - Structural Diagram]]
####[[Flex Fab - Funcional or Process Diagram]]
####[[Flex Fab - Workflow]]
###[[Flex Fab - Technical Issues]]
###[[Flex Fab - Deployment Strategy]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Calculations]]
####[[Flex Fab - Design Calculations]]
####[[Flex Fab - Yields]]
####[[Flex Fab - Rates]]
####[[Flex Fab - Structural Calculations]]
####[[Flex Fab - Power Requirements]]
####[[Flex Fab - Ergonomics of Production]]
####[[Flex Fab -Time Requirements]]
####[[Flex Fab - Economic Breakeven Analysis]]
####[[Flex Fab - Scaleability Calculations]]
####[[Flex Fab - Growth Calculations]]
###[[Flex Fab - Technical Drawings and CAD]]
###[[Flex Fab - CAM Files]]
##[[Flex Fab - Component Design]]
###[[Flex Fab - Diagrams]]
###[[Flex Fab - Conceptual drawings]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Performance calculations]]
###[[Flex Fab - Technical drawings and CAD]]
###[[Flex Fab - CAM files whenever available]]
##[[Flex Fab - Subcomponents]]
#[[Flex Fab - Deployment and Results]]
##[[Flex Fab - Production steps]]
##[[Flex Fab - Flexible Fabrication or Production]]
##[[Flex Fab - Bill of materials]]
##[[Flex Fab - Pictures and Video]]
##[[Flex Fab - Data]]
#[[Flex Fab - Documentation and Education]]
##[[Flex Fab - Documentation]]
##[[Flex Fab - Enterprise Plans]]
#[[Flex Fab - Resource Development]]
##[[Flex Fab - Identifying Stakeholders]]
###[[Flex Fab - Information Collaboration]]
####[[Flex Fab - Wiki Markup]]
####[[Flex Fab - Addition of Supporting References]]
####[[Flex Fab - Production of diagrams, flowcharts, 3D computer models, and other qualitative information architecture]]
####[[Flex Fab - Technical Calculations, Drawings, CAD, CAM, other]]
###[[Flex Fab - Prototyping]]
###[[Flex Fab - Funding]]
###[[Flex Fab - Preordering working products]]
###[[Flex Fab - Grantwriting]]
###[[Flex Fab - Publicity]]
###[[Flex Fab - User/Fabricator Training and Accreditation]]
###[[Flex Fab - Standards and Certification Developmen]]
###[[Flex Fab - Other]]
##[[Flex Fab - Grantwriting]]
###[[Flex Fab - Volunteer grantwriters]]
###[[Flex Fab - Professional, Outcome-Based Grantwriters]]
##[[Flex Fab - Collaborative Stakeholder Funding]]
##[[Flex Fab - Tool and Material Donations]]
##[[Flex Fab - Charitable Contributions]]

=Component References=
*Oscilloscopes
**[http://www.easysync-ltd.com/index.html?lang=en-uk&target=d16.html PC Oscilloscope]

[[Category:Zero Hour]]

Multimachine & Flex Fab

2008-03-08T17:41:04Z

SamRose: /* Multimachine Parts list, Materials list, dimensions specs, assembly file */

{{Site header}}

----
Multimachine & Flex Fab- www.multimachine.net/ shows it - a general purpose metal fabrication tool including lathe, mill, and drill press. This could be the central tool piece of a flexible workshop - and this item is already open source! I have not assessed this more fully, but it appears to be a promising candidate to address tooling needs for a community- at absolutely rock bottom cost - eliminating thousands of dollars of expenditure requirement for similar abilities. The capacities and practicality of this lower tech 'personal fabber' need to be assessed fully. The multimachine could be the centerpieces enabling the fabrication of electric motor, CEB, sawmill, OSCar, microcombine and all other items that require processes from milling to drilling to lathing. Crucial.

=Collaboration=
==Review of Project Status==

We are currently assembling and evaluating the components that would make a robust flexible fabrication facility. To date, our list of proposed tooling is:

Machining:

===Multimachine Development (Zerohour template)===

#'''The Theory:''' ''The underlying theory in a nutshell.'' The Theory must be presented as a working hypothesis that is being explored and tested. There must be an experimental procedure to test the theory- the theory must be testable. The Theory question must be well-posed: an answer must exist. If any of these criteria are missing then the project will not move forward effectively.
# '''Existing problems''' in the real world that relate to this theory, a brief description.
# '''Proposed way''' to apply the theory to those existing problems, the context or pre-requisites for this solution (solution in this case is application of the theory)
# '''Related existing work''' that verifies feasability with context summary of links to those references
# '''Related existing data''' or facts that support theory
# '''Existing constraints''' and barriers to deploying
# '''Related existing work that argues against''' theory (or summary and link to a place where this already exists)
# '''facts and data''' that support arguments against theory
# '''A brief summary''' about how this is related to Open Source Ecology (Relevance to OSE) core values
# '''Links''' to partner site references

===Multimachine Parts list, Materials list, dimensions specs, assembly file===

This will be a first draft of a spec file for multimachine

#Multimachine - http://opensourcemachine.org/ , and documentation: http://opensourcemachine.org/book
##Add CNC numerical control to its xyz motion to automate milling and lathing operations
##Include long lathe bed for CNC milling of roundwood for [http://sustainablescience.org/ LPSA] structures ''(would a larger than spec multimachine be needed to accomplish this large lathing? it seems to be the case)''

#Torch table - similar to the [http://torchmate.com/overview/index2.htm Torchmate]
##Commercial kits start at $4k from Torchmate
##Open source CNC version could cost $1k
##Torch attachment is the basic tool

Materials
#Plastic extruder - see Extruder_doc.pdf at [http://www.fastonline.org/CD3WD_40/CD3WD/INDEX.HTM this library]
##Ok, but who can translate that publication to English?
#Metal casting - what is the best low-cost, robust solution available here?

Electronics:
#Circuit fabrication - solution etching or a PCB mill?
##[http://www.elektor.com/extra/profiler-milling-machine-from-a-kit.91274.lynkx PCB mill kit] available for about $2500
#PC oscilloscope

The above minimal toolset includes major machining, metal cutting, metal casting, plastic extrusion, and electronics capabilities. We are talking of cars, solar turbines, motor controls, CEB machines, agricultural combines, and so forth from this set. Plastic and metal forming, and subractive machining of all types, is covered. Thus, we are talking of producing advanced technology '''at the cost of materials''', and in particular, at the cost of waste stream materials, if, for example, scrap aluminum is melted and cast into motor housings and other useful parts.

===Multi machine Bill of materials 2 Block version===

(taken from http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf)

====Engine blocks suggested specs ====

http://opensourcemachine.org/files/How_to_build_a_multimachine.pdf calls for a 3 7/8" Bore inline 6 cylinder engine (not a sleeve bore engine block).

====Engine blocks meeting criteria====

* http://en.wikipedia.org/wiki/AMC_Straight-6_engine#4.0 (Stock Bore size 3.88" in)

* http://en.wikipedia.org/wiki/Ford_Straight-6_engine#Fourth_generation (Stock bore size 3.5" in. Could possibly be bored over to 3.88. A call to a machine shop can confirm)

* Cummins 6BT 5.9 L B5.9 4.01"in bore (this engine is an option for Dodge Ram, and was agricultural engine in 1980's) **NOT YET SURE WHETHER THIS IS SLEEVED ENGINE OR NOT**

====Three bearing spindle and chuck assembly====

==Flex Fab - Current Work==

The main point for the Multimachine is to start documenting the toolpath generator (Smari McCarthy) -> controller -> motor -> hardware (Multimachine) system knowhow integration. Massive cost reduction, F10 or better - is possible. If we're lucky, we could get the Multimachine to the accuracy of electronic circuit fab.

Toolpath generation:

Controller integration:

Motors:

=Development Work Template=
#[[Flex Fab - Product Definition]]
##[[Flex Fab - General]]
##[[Flex Fab - General Scope]]
##[[Flex Fab - Product Ecology]]
###[[Flex Fab - Localization]]
###[[Flex Fab - Scaleability]]
###[[Flex Fab - Analysis of Scale]]
###[[Flex Fab - Lifecycle Analysis]]
##[[Flex Fab - Enterprise Options]]
##[[Flex Fab - Development Approach]]
###[[Flex Fab - Timeline]]
###[[Flex Fab - Development Budget]]
####[[Flex Fab - Value Spent]]
####[[Flex Fab - Value available]]
####[[Flex Fab - Value needed]]
##[[Flex Fab - Deliverables and Product Specifications]]
##[[Flex Fab - Industry Standards]]
##[[Flex Fab - Market and Market Segmentation]]
##[[Flex Fab - Salient Features and Keys to Success]]
#[[Flex Fab - Technical Design]]
##[[Flex Fab - Product System Design]]
###[[Flex Fab - Diagrams and Conceptual Drawings]]
####[[Flex Fab - Pattern Language Icons]]
####[[Flex Fab - Structural Diagram]]
####[[Flex Fab - Funcional or Process Diagram]]
####[[Flex Fab - Workflow]]
###[[Flex Fab - Technical Issues]]
###[[Flex Fab - Deployment Strategy]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Calculations]]
####[[Flex Fab - Design Calculations]]
####[[Flex Fab - Yields]]
####[[Flex Fab - Rates]]
####[[Flex Fab - Structural Calculations]]
####[[Flex Fab - Power Requirements]]
####[[Flex Fab - Ergonomics of Production]]
####[[Flex Fab -Time Requirements]]
####[[Flex Fab - Economic Breakeven Analysis]]
####[[Flex Fab - Scaleability Calculations]]
####[[Flex Fab - Growth Calculations]]
###[[Flex Fab - Technical Drawings and CAD]]
###[[Flex Fab - CAM Files]]
##[[Flex Fab - Component Design]]
###[[Flex Fab - Diagrams]]
###[[Flex Fab - Conceptual drawings]]
###[[Flex Fab - Performance specifications]]
###[[Flex Fab - Performance calculations]]
###[[Flex Fab - Technical drawings and CAD]]
###[[Flex Fab - CAM files whenever available]]
##[[Flex Fab - Subcomponents]]
#[[Flex Fab - Deployment and Results]]
##[[Flex Fab - Production steps]]
##[[Flex Fab - Flexible Fabrication or Production]]
##[[Flex Fab - Bill of materials]]
##[[Flex Fab - Pictures and Video]]
##[[Flex Fab - Data]]
#[[Flex Fab - Documentation and Education]]
##[[Flex Fab - Documentation]]
##[[Flex Fab - Enterprise Plans]]
#[[Flex Fab - Resource Development]]
##[[Flex Fab - Identifying Stakeholders]]
###[[Flex Fab - Information Collaboration]]
####[[Flex Fab - Wiki Markup]]
####[[Flex Fab - Addition of Supporting References]]
####[[Flex Fab - Production of diagrams, flowcharts, 3D computer models, and other qualitative information architecture]]
####[[Flex Fab - Technical Calculations, Drawings, CAD, CAM, other]]
###[[Flex Fab - Prototyping]]
###[[Flex Fab - Funding]]
###[[Flex Fab - Preordering working products]]
###[[Flex Fab - Grantwriting]]
###[[Flex Fab - Publicity]]
###[[Flex Fab - User/Fabricator Training and Accreditation]]
###[[Flex Fab - Standards and Certification Developmen]]
###[[Flex Fab - Other]]
##[[Flex Fab - Grantwriting]]
###[[Flex Fab - Volunteer grantwriters]]
###[[Flex Fab - Professional, Outcome-Based Grantwriters]]
##[[Flex Fab - Collaborative Stakeholder Funding]]
##[[Flex Fab - Tool and Material Donations]]
##[[Flex Fab - Charitable Contributions]]

=Component References=
*Oscilloscopes
**[http://www.easysync-ltd.com/index.html?lang=en-uk&target=d16.html PC Oscilloscope]

[[Category:Zero Hour]]

Project Story

2008-03-08T17:02:02Z

SamRose: draft in progress

{{Template:Draft}}

Going to use this page to create a "story" about processes for projects, and how they will work on this wiki site, and on the http://socialsyenrgweb.org/opensourceecology project staging site we are creating.

===Proposed Process: Embryonic Stage===

Projects start life on this (http://openfarmtech.org/index.php?) wiki as ideas or proposed partnerships.

# We apply "Zero Hour" template to project, to try and map it into existing knowledge, existing problems, existing forces, barriers, etc
# We need at least one person to commit to mapping an embryonic project idea out into the Cycles and steps that we follow for any product/project development. That mapping happens on this wiki. (more detail needed on this mapping)
# We need at least 2 existing Open Source Ecology participants to vote to have Open Source Ecology support the project beyond it's embryonic stage

===Project Mapping===

====Cycles====

====Stages per cycle====

===Development Stage===

# If at least 2 people agree project should be supported, and if project is mapped correctly (see criteria above) then a project page is created on http://socialsyenrgweb.org/opensourceecology
#

Media-wiki talk:Copyright

2008-03-08T16:45:20Z

SamRose:

Both of these licenses are incompatible with the GNU GPL.

Could we include the GNU GPL as one more of the licenses - as a tri-license, or just use the GNU GPL alone?

I don't see why we can't tri-license. Will come back later.

Patrick, are you talking about GNU GPL for written content here, or GNU GPL for actual designs. Written content is different than designs. We should probably specify a copylefted license for hardware design, such as http://www.tapr.org/ohl.html or an appropriate license that addresses hardware design, for hardware designs themselves.

There is also the matter of code that will be generated, which is easy (GNU GPL)

But for license of written content here, we can tri license if you'd like. Maybe you can help me understand why GNU Freedoc and creative commons are incompatible with GNU GPL, and why GNU GPL must be included (I don't have a problem with it at all, just want to understand) --[[User:SamRose|SamRose]] 08:45, 8 March 2008 (PST)

Media-wiki talk:Copyright

2008-03-08T02:00:28Z

SamRose:

Media-wiki:Copyright

2008-03-06T16:25:35Z

SamRose: New page: All content is Dual Licensed: [http://creativecommons.org/licenses/by-sa/3.0/us/ Creative Commons License ]<br />This work is licensed under a [http://creativecommons.o...

All content is Dual Licensed:

[http://creativecommons.org/licenses/by-sa/3.0/us/ [[Image:cc.png|Creative Commons License]] ]<br />This work is licensed under a [http://creativecommons.org/licenses/by-sa/3.0/us/ Creative Commons Attribution-Share Alike 3.0 United States License].

[#TOC1 GNU Free Documentation License]

Version 1.2, November 2002

Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

'''0. PREAMBLE'''

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

'''1. APPLICABILITY AND DEFINITIONS'''

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

'''2. VERBATIM COPYING'''

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

'''3. COPYING IN QUANTITY'''

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

'''4. MODIFICATIONS'''

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

* '''A.''' Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
* '''B.''' List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
* '''C.''' State on the Title page the name of the publisher of the Modified Version, as the publisher.
* '''D.''' Preserve all the copyright notices of the Document.
* '''E.''' Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
* '''F.''' Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
* '''G.''' Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
* '''H.''' Include an unaltered copy of this License.
* '''I.''' Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
* '''J.''' Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
* '''K.''' For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
* '''L.''' Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
* '''M.''' Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
* '''N.''' Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
* '''O.''' Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

'''5. COMBINING DOCUMENTS'''

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements."

'''6. COLLECTIONS OF DOCUMENTS'''

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

'''7. AGGREGATION WITH INDEPENDENT WORKS'''

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

'''8. TRANSLATION'''

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

'''9. TERMINATION'''

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

'''10. FUTURE REVISIONS OF THIS LICENSE'''

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

===[#TOC4 How to use this License for your documents]===

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled "GNU
Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.

Media-wiki:General disclaimer

2008-03-06T16:20:20Z

SamRose: adapated from http://www.mediawiki.org/wiki/Project:General_disclaimer feel free to edit

Please note that all textual contents of Open Source Ecology Wiki, unless they're not exclusively marked as [http://en.wikipedia.org/wiki/Public_domain public domain], are released under the [http://www.gnu.org/copyleft/fdl.html GNU_Free_Documentation_License GNU Free Documentation License] (GFDL). See [[Copyright]] for more information.

'''Open Source Ecology Wiki''' at http://openfarmtech.org/ is the online home of and the first access point for information about the Open Source Ecology. The community working here is a voluntary association of individuals and groups who are developing an open-content common resource of different media and human technical knowledge. The structure of this site, which is a [http://en.wikipedia.org/wiki/Wiki wiki], allows anyone with an Internet connection and World Wide Web browser to alter the content found here. Therefore, please be advised that nothing found here has necessarily been reviewed by professionals with the expertise necessary to provide you with complete, accurate or reliable information.

That is not to say that you will not find valuable and accurate information on Open Source Ecology Wiki; much of the time you will. However, Open Source Ecology Wiki cannot guarantee the validity of the information found here. The content of any given information may recently have been changed, vandalized or altered by someone whose opinion does not correspond with the state of knowledge in the relevant fields.

===No formal peer review===

We are working on ways to select and highlight reliable versions of information articles. Our active community of editors uses tools such as the [[Special:Recentchanges]] and [[Special:Newpages]] feeds to monitor new and changing content. However, Open Source Ecology Wiki is not uniformly peer reviewed; while readers may correct errors or engage in casual review, they have no legal duty to do so and thus all information read here is without any implied warranty of fitness for any purpose or use whatsoever. Even articles that have been vetted by informal review may later have been edited inappropriately, just before you view them.

: :: ''None of the authors, contributors, sponsors, administrators, sysops, or anyone else connected with Open Source Ecology Wiki in any way whatsoever can be responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these web pages.''

===No contract; limited license===

Please make sure that you understand that the information provided here is being provided freely, and that no kind of agreement or contract is created between you and the owners or users of this site, the owners of the servers upon which it is housed, the individual Open Source Ecology Wiki contributors, any project administrators, sysops or anyone else who is in any way connected with this project or sister projects subject to your claims against them directly. You are being granted a limited license to copy anything from this site; it does not create or imply any contractual or extracontractual liability on the part of MediaWiki or any of its agents, members, organizers or other users.

There is no agreement or understanding between you and Open Source Ecology Wiki regarding your use or modification of this information beyond the [/wiki/GNU_Free_Documentation_License GNU Free Documentation License] (GFDL); neither is anyone at Open Source Ecology Wiki responsible should someone change, edit, modify or remove any information that you may post on Open Source Ecology Wiki or any of its associated projects.

===Trademarks===

Any of the trademarks, service marks, collective marks, design rights, personality rights or similar rights that are mentioned, used or cited in the articles of Open Source Ecology Wiki are the property of their respective owners. Their use here does not imply that you may use them for any other purpose other than for the same or a similar informational use as contemplated by the original authors of these Open Source Ecology Wiki articles under the GFDL licensing scheme. Unless otherwise stated Open Source Ecology Wiki sites are neither endorsed nor affiliated with any of the holders of any such rights and as such Open Source Ecology Wiki can not grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk.

===Jurisdiction and legality of content===

Publication of information found on Open Source Ecology Wiki may be in violation of the laws of the country or jurisdiction from where you are viewing this information. The MediaWiki database is stored on a server in the e [http://en.wikipedia.org/wiki/United_States_of_America United States of America], and is maintained in reference to the protections afforded under local and federal law. Laws in your country or jurisdiction may not protect or allow the same kinds of speech or distribution. Open Source Ecology Wiki does not encourage the violation of any laws; and cannot be responsible for any violations of such laws, should you link to this domain or use, reproduce, or republish the information contained herein.

Thank you for spending the time to read this page, and please enjoy your experience at Open Source Ecology Wiki.

User talk:SamRose

2008-03-06T15:54:00Z

SamRose:

Hey Sam,

Saw your research links and wondered if the following would be useful for your goals:

http://BRLCAD.org >>The BRL-CAD package is a powerful Constructive Solid Geometry (CSG) solid modeling system with over 20 years development and production use by the U.S. military. BRL-CAD includes an interactive geometry editor, parallel ray-tracing support for rendering and geometric analysis, path-tracing for realistic image synthesis, network distributed framebuffer support, image-processing and signal-processing tools.

Thanks! Will check this out. Getting memory module fixed on my Debian machine. Once that is done, I will have a good platform to try this out.

I am trying to figure out which will be the best for [[MultiMachine]] mapping into a set of files.

User:SamRose

2008-03-06T00:11:27Z

SamRose: New page: I'm Sam Rose === Notes === To investigate: http://www.hpfem.jku.at/netgen/ http://pdb.finkproject.org/pdb/package.php/netgen http://www.opencascade.org/getocc/require/ http://www....

I'm Sam Rose

=== Notes ===

To investigate:

http://www.hpfem.jku.at/netgen/

http://pdb.finkproject.org/pdb/package.php/netgen

http://www.opencascade.org/getocc/require/

http://www.opencascade.org/occ/areas/cadcamproducts/

http://blenderartists.org/forum/showthread?t=54673

http://www.editthis.info/opencam/Main_Page

Talk:Friendly Organizations

2008-03-05T20:26:16Z

SamRose: we will get unlocked

I don't understand why this page is locked, but the entry for "Personal Sovereignty '''Foundation'''" is mislabeled as "Personal Sovereignty '''Society'''". Please repair. -- [[User:AGNUcius|AGNUcius]] 09:06, 5 March 2008 (PST)

I'll login as admin and unlock the pages. Some pages around here are still locked from when we were implementing anti-spam measures. Sorry about that --[[User:SamRose|SamRose]] 12:26, 5 March 2008 (PST)

Agile Project Management

2008-03-05T18:30:45Z

SamRose: /* Applying to our processes */

=Introduction=

This is a proposal for the future course of design of the http://socialsynergyweb.org/opensourceecology development

==Reference Material==

http://www.ccpace.com/Resources/documents/AgileProjectManagement.pdf

http://www.rheingold.com/cooperation/decisionmaking.pdf

http://necsi.org/research/multiscale/Civilization.html

http://www.edgeperspectives.com/index3.shtml

==Summary Overview==

===Traditional Project Management===

Traditional Project Management, and Product Development seeks to manage, control, organize and coordinate projects, to create order via:

* Hierarchical Organization

* Increasing Control

* Rigid procedures

* People as "resources"

* Reductionist problem solving

* Up-front planning to manage risks, and to enhance predictability

(adapted from pg.3 http://www.ccpace.com/Resources/documents/AgileProjectManagement.pdf)

===Complex Adaptive ("Agile") Project Management Framework===

"Agile" project management borrows from [http://en.wikipedia.org/wiki/Complex_adaptive_system Complex Adaptive System] principles.

(see page 8 table 1 http://www.ccpace.com/Resources/documents/AgileProjectManagement.pdf )

===Framework Outline===

====Guiding Vision====

"Guiding Vision" has an immediate effect on influence of behavior of people involved

====Teamwork and Collaboration====

People are treated as autonomous, intelligent indviduals. Whenever possible, decision making power is handed over to the participants, to allow them to guide in collaborative ways

====Simple Rules====

Rather than micro-managed control, we all agree to a set of simple rules that guide complex distributed development

====Open Information====

This site, and all sites, and all communications are open, and constitute open information. Our processes are open and transparent.

====Light Touch====

Rather than trying to force the direction of evolution, we scale back imposed order, in favor of emergent order. We are flexible, and allow many directions to emerge from any given point. '''Our goal is to support and enable emergent order.'''

====Agile Vigilance====

Leaders, coordinators, people with responsibility pay attention to what is going on, and adapt to the emergent order, rather than trying to force what is evolving and emerging. Instead, they rely on the simple rules, the Guiding vision, open information, and Light Touch to help them adapt to what is emerging

===Applying to our processes===

All of us Propose a Guiding Vision, and all of us are then responsible for working towards emergent order over imposed order.

[[Open Product Development]] is a proposed Guiding Vision, that we are trying to implement. All of the projects evolving at [http://openfarmtech.org/index.php?title=Category:Zero_Hour Zero Hour] are proposed guiding visions, that try to connect with real-world solutions.

Ideas, proposals, projects are born on the (openfarmtech) wiki. When at least 1 person committs to them, we ask them to post it as a project (using content-type "project") on the Drupal site, with details there, and links back to wiki pages. If at least 2 people committ to the project, then we create a group/core team portal for the project or product. This can be a mirror of existing external workspaces if this is a parternship. At minimum, we at least update status on core team portal group pages for each project or product.

This expands OSE product development platform to projects that are not actual product development.

Constraining rules are proposed, but can be adjusted. So that every project does not ultimately need to follow a rigid set of cycles, but cycles that are most useful to it's own development.

[[Category:Zero Hour]]

Agile Project Management

2008-03-05T18:27:20Z

SamRose: /* Applying to our processes */

Agile Project Management

2008-03-05T18:11:55Z

SamRose: /* Applying to our processes */

Agile Project Management

2008-03-05T18:10:00Z

SamRose: New page: =Introduction= This is a proposal for the future course of design of the http://socialsynergyweb.org/opensourceecology development ==Reference Material== http://www.ccpace.com/Resourc...

=Introduction=

This is a proposal for the future course of design of the http://socialsynergyweb.org/opensourceecology development

==Reference Material==

http://www.ccpace.com/Resources/documents/AgileProjectManagement.pdf

http://www.rheingold.com/cooperation/decisionmaking.pdf

http://necsi.org/research/multiscale/Civilization.html

http://www.edgeperspectives.com/index3.shtml

==Summary Overview==

===Traditional Project Management===

Traditional Project Management, and Product Development seeks to manage, control, organize and coordinate projects, to create order via:

* Hierarchical Organization

* Increasing Control

* Rigid procedures

* People as "resources"

* Reductionist problem solving

* Up-front planning to manage risks, and to enhance predictability

(adapted from pg.3 http://www.ccpace.com/Resources/documents/AgileProjectManagement.pdf)

===Complex Adaptive ("Agile") Project Management Framework===

"Agile" project management borrows from [http://en.wikipedia.org/wiki/Complex_adaptive_system Complex Adaptive System] principles.

(see page 8 table 1 http://www.ccpace.com/Resources/documents/AgileProjectManagement.pdf )

===Framework Outline===

====Guiding Vision====

"Guiding Vision" has an immediate effect on influence of behavior of people involved

====Teamwork and Collaboration====

People are treated as autonomous, intelligent indviduals. Whenever possible, decision making power is handed over to the participants, to allow them to guide in collaborative ways

====Simple Rules====

Rather than micro-managed control, we all agree to a set of simple rules that guide complex distributed development

====Open Information====

This site, and all sites, and all communications are open, and constitute open information. Our processes are open and transparent.

====Light Touch====

Rather than trying to force the direction of evolution, we scale back imposed order, in favor of emergent order. We are flexible, and allow many directions to emerge from any given point. '''Our goal is to support and enable emergent order.'''

====Agile Vigilance====

Leaders, coordinators, people with responsibility pay attention to what is going on, and adapt to the emergent order, rather than trying to force what is evolving and emerging. Instead, they rely on the simple rules, the Guiding vision, open information, and Light Touch to help them adapt to what is emerging

===Applying to our processes===

All of us Propose a Guiding Vision, and all of us are then responsible for working towards emergent order over imposed order.

[[Open Product Development]] is a proposed Guiding Vision, that we are trying to implement. All of the projects evolving at [[Category:Zero Hour]] are proposed guiding visions, that try to connect with real-world solutions.

In the News

2008-03-05T14:58:20Z

SamRose: Factor E Farm Field Trip

Here are various news stories, features, blogs, and other articles about Open Source Ecology's work from other sources:

*12.07.07- [http://blog.onevillage.tv/wp/?p=491 Factor E Farm Field Trip]
*1.22.08 - [http://blog.p2pfoundation.net/marcin-jakubowskis-open-farm-the-most-important-social-experiment-in-the-world/2008/01/22 P2P Foundation calls us ''the most importand social experiment in the world'']
*2.9.08 - [http://blogs.salon.com/0002007/2008/02/09.html#a2096 How to Save the World blog on our brick machine]
*2.9.08 - [http://www.newmediaexplorer.org/steve_bosserman/2008/02/09/giving_it_away_making_money.htm Steve Bosserman on OSE economic model]
*2.19.08 - [http://blog.p2pfoundation.net/steve-bosserman-on-economic-sustainability-in-a-world-of-open-design/2008/02/19 P2P Foundation on OSE economic model]
*2.25.08 - [http://www.boingboing.net/2008/02/25/open-source-compress.html BoingBoing: A Directory of Wonderful Things]
*2.25.08 - [http://blog.wired.com/sterling/2008/02/the-liberator-a.html Wired Magazine blog, by Bruce Sterling]
*2.26.08 - [http://www.thingsaregood.com/2008/02/26/open-source-ecology/ Things Are Good]

Video Bridge

2008-03-05T14:36:01Z

SamRose: /* '''Links''' */

maintained by [[User:Globalvillagesinfo]]

SEE ALSO: http://www.dorfwiki.org/wiki.cgi?VideoBridge/Beschreibung

='''The Theory'''=

The term "videobridge" as opposed to "videoconferencing" signifies that there is something happening at local scale, which we are simply enhancing (or enabling) by a "bridge".(while a videoconference is primarily an event in virtual space. Television in two generations life has shaped methods of transmitting content and atmosphere of events that can be applied by skilled people at local level to share and connect learning communities. That could be a lecture at a university or at a conference, or a special meeting on a special subject, or simply a come-together of a local group. At the other end of the line there are complementary activities. Thus a videobridge is simply the enhancment of the possibilities of a local (mostly educational) place by tying in happenings from elsewhere or sharing local events with those elsewhere

='''Existing Problems'''=

While Videobridges can dramatically expand the learning opportunities in any given place, there are some obstacles:

* availability of broadband connection in rural areas
* price of hardware involved
* ability of local institutions to serve manifold educational needs
* incentive to produce quality content

='''Proposed Way'''=

There are two common things that we wish to avoid:

* expensive technology TV Cameras, Director, professional cutting place
* dull technology Videoconferencing as usual with one camera with remote control

We want to examine in particular, how the (cheaper) digital medium with its features (relatively small and flexible produser input devices, mixing of data and video streams, and many other things) can be used to transmit "feeling" and content of an event in the best possible way.

There are many preconditions, some met, like having a good video beamer and a sound system, but we need to experiment with diverse input devices (scaler, mixer, webcams, DV-cams) to achieve optimal input output relations (and especially the necessary compression/transmission speed to have truly interactive events.)

For the receiving and showing of a quality videostreams besides the computer a beamer and sound system is necessary

For production and live interaction there is a need for a streaming encoder and a mixer etc.

We are targeting the goal of an "Open Virtual University of the Villages", coordinated and open content in a large community of local educational institutions.

='''Related Existing Work'''=

This will take some time to document, but there is a lot.

='''Related Existing Data'''=
''- or facts that support theory''

='''Existing constraints'''=
''- and barriers to deploying''

='''Related Existing Work that Argues Against'''=
''- theory (or summary and link to a place where this already exists)''

='''Facts and Data'''=
''- that support arguments against theory''

='''Brief Summary'''=
''- about how this is related to Open Source Ecology (Relevance to OSE) core values''

='''Links'''=
''- to partner site references''

* [http://www.usemod.com/cgi-bin/mb.pl?VideoBridge Meatballwiki:VideoBridge]

[[Category:Zero Hour]]

Multimachine & Flex Fab

2008-03-03T20:44:16Z

SamRose: /* Multimachine Development (Zerohour template) */

Multimachine & Flex Fab

2008-03-03T20:35:54Z

SamRose: +zerohour template

Multimachine & Flex Fab

2008-03-03T20:20:35Z

SamRose:

Nine Principles for Designing Living Machines

2008-03-01T20:08:42Z

SamRose:

==Nine Principles for The Design of Living Machine==

Adapted from ''From Eco-cities to Living Machnes: Principles of Ecological Design Nancy Jack Todd and John Todd<ref>page 169 Table 1</ref>''

# Microbial Communities
# Photosynthetic Communities
# Linked Ecosystems and the Law of the Minimum
# Pulsed Exchanges
# Nutrient and Micronutrient Reseviors
# Geological Diversity and Mineral Complexity
# Steep Gradients
# Phylogenetic Diversity
# The Microcosm as Tiny Mirror image of the Macrocosm

===See also===

* [[Living machines]]

[[Category:Zero Hour]]

Nine Principles for Designing Living Machines

2008-03-01T20:08:20Z

SamRose: /* Nine Principles for The Design of Living Machine */

Nine Principles for Designing Living Machines

2008-03-01T20:07:36Z

SamRose: work in progress

==Nine Principles for The Design of Living Machine==

Adapted from ''From Eco-cities to Living Machnes: Principles of Ecological Design Nancy Jack Todd and John Todd<ref>page 169 Table 1</ref>''

# Microbial Communities

# Photosynthetic Communities

# Linked Ecosystems and the Law of the Minimum

# Pulsed Exchanges

# Nutrient and Micronutrient Reseviors

# Geological Diversity and Mineral Complexity

# Steep Gradients

# Phylogenetic Diversity

# The Microcosm as Tiny Mirror image of the Macrocosm

===See also===

* [[Living machines]]

[[Category:Zero hour]]

Talk:Core Team

2008-03-01T15:20:38Z

SamRose: /* Mentoring? */ YES!

== Mentoring? ==

One thing that's missing from this article - where the next generation of open source engineers will be coming from. What kind of provision do you have on these teams for young people who might not have as much practical experience or degrees, but have done some hacking on their own and want to contribute to a real project with other engineers? Where do they fit in? [[User:Mchua|Mchua]] 17:02, 29 February 2008 (PST)

== Yes! ==

This is exactly what I had in mind, when I began http://socialsynergyweb.org/educommons/, which is intended to be an open license distance learning platform. Meaning, the content there is released under an open license. In this case, we will use a dual-license (creative commons, Gnufreedoc)

So, over time, we are going to create a certification system, and a way for people to mentor and be mentored at all levels of expertise. In some cases, we will also deliver these courses for a very low cost in person, but the material will always be online as well.

And, in advanced stages, we would have a system set up that proves that you can design and/or fabricate withing specified tolerances and quality, in order to attain higher OSE certification. That is the general plan. For the short term, if you are interested in helping, but don't have practical experience, we want to help you get involved in a real project somehow, in ways that are satisfactory for your. Please discuss right here, and we will also have an email list soon. --[[User:SamRose|SamRose]] 07:20, 1 March 2008 (PST)

Fractional Ownership Trade Agreement

2008-02-29T20:30:22Z

SamRose:

Tenative proposal for a "Contract" or some kind of "Terms of Operation" for a business, organization, or even applied between just two property owners:

== DEFINITIONS:==

* The term 'Physical Sources' denotes Capital or Land such as living organisms, tools, real estate.
* The term 'Object' denotes a tangible or ephemeral product, output or purpose of a Source such as the harvest from a farm, a ride in a car, the shade of a tree.
* Ther term 'Type' denotes the class or variety of some thing with infinite potential such as the genetics of an organism, a computer program, video or audio data, the design of a tool.
* The term 'Instance' denotes a single copy of any Type of thing such as a living organism, a CD containing a computer program or video/audio data, a physical tool.
* The term 'Recipient' denotes an entity which receives a good or service.

== TERMS ==
As owner, you may use this Object Instance for any purpose.
If you trade, sell, give, lease, rent or otherwise make this Object available to a Receipient you must:
1. Accompany that Object Instance with a paper or digital copy of this agreement.
2. Invest the difference between selling price and production costs in more Physical Sources.
3. The investment made in #2 shall vest to the Recipient as fractional ownership after ??? (time or condition)?

----
Some resouces to determine how "Common Law" usually effects these arrangements:

http://en.wikipedia.org/wiki/Fractional_Ownership ''In business, fractional ownership is a percentage share of an expensive asset. Shares are sold to individual owners. A fractional owner enjoys priorities and privileges, such as reduced rates, priority access on holidays and income sharing. Typically, a company manages the asset on behalf of the owners, who pay monthly/annual fees for the management plus variable (e.g. per-hour, per-day) use fees. For rapidly-depreciating assets, the management company may sell the asset and distribute the proceeds back to the owners, who can then claim a capital loss and optionally purchase a fraction of a new asset.''

http://1st-of-Pryor.com/co-ownership%20contract.htm ''This agreement is provided to our pilot friends at no cost and for no consideration. You are welcome to utilize it for whatever purpose you choose. Please modify this agreement to suit your particular situation. However, the First Pryority Bank of Pryor cannot and will not provide any assurance that the agreement is suitable for your situation and we will not provide any warranty or guaranty as to it accuracy, or legal validity. You are electing to use the agreement by assuming any risk as to its legal correctness, validity, or consequences.''

http://AndySirkin.com ''Vacation home co-ownership (sometimes also known as fractional ownership)''

http://en.wikipedia.org/wiki/Concurrent_estate
''A concurrent estate or co-tenancy is a concept in property law, particularly derived from the common law of real property, which describes the various ways in which property can be owned by more than one person at a given time. The parties who own property jointly are referred to as co-tenants or joint tenants. Most common-law jurisdictions recognize three kinds of concurrent estate: tenancy in common, joint tenancy with right of survivorship, and tenancy by the entirety. Many jurisdictions simply refer to a joint tenancy with right of survivorship as a joint tenancy, but a few U.S. States treat the phrase joint tenancy as synonymous with a tenancy in common.''

Co-tenants, irrespective of the type of tenancy, share certain rights relative to each other and to the property, except to the extent they have modified these rights through an agreement among themselves:

1. Each tenant has an unrestricted right of access to the property. Where one co-tenant wrongfully excludes another from making use of the property, the excluded co-tenant can bring a cause of action for ouster,', and may receive the fair rental value of the property for the time that he was dispossessed.
2. Each tenant has a right to an accounting of profits made from the property. If the property generates income such as rent, each tenant is entitled to a pro-rata share of that income.
3. Each tenant has a right of contribution for the costs of owning the property. Co-tenants can be forced to contribute to the payment of expenses such as property taxes and mortgages on the entire property.

Co-tenants do not have any obligation to contribute to any costs of repairing or improving the property. If one co-tenant adds a feature that enhances the value of the property, that co-tenant has no right to demand that any others share the cost of adding that feature - even if other co-tenants reap greater profits from the property because of it. However, at partition, a co-tenant is entitled to recover the value added by his or her improvements of the property. Conversely, if the co-tenant's "improvements" decrease the value of the property, the co-tenant is responsible for those decreases as well.

Furthermore, each co-tenant can independently encumber the co-tenant's own share in the property by taking out a mortgage on that share (although this may effectively convert a joint tenancy to a tenancy in common, as described below); other co-tenants have no obligation to help pay a mortgage that only runs to another tenant's share of the property, and the mortgagee can only foreclose on that mortgagor's share. Bank loans secured by mortgages on individual shares of co-owned property is one of the most rapidly expanding areas in the mortgage lending industry.

Finally, co-tenants owe one another a duty of fair dealing. Because of this, any co-tenant who acquires a mortgage claim against the property must give his co-tenants a reasonable opportunity to purchase proportionate shares in that claim.

[edit] Tenancy in common

Tenancy in common is the default form of concurrent estate, in which each owner, referred to as a tenant in common, is regarded by the law as each owning separate and distinct shares which may differ in size. This form of ownership is common where the co-owners are not married or have contributed different amounts to the acquisition of the property. Also, if joint owners had attempted to use another form of joint ownership such as a joint tenancy with right of survivorship or a tenancy by the entirety, and the effort was for some reason invalid, the joint owners would then be tenants in common. If conclusive evidence is not available of the desire to create a tenancy with rights of survivorship or a tenancy by the entirety, courts will determine that a tenancy in common has in fact been created.

Tenants in common have no right of survivorship, meaning that if one owner dies, that owner's interest in the property will pass by inheritance to that owner's devisees or heirs, either by will, or by intestate succession.

[edit] Destruction of a tenancy in common

Where any party to a tenancy in common wishes to destroy the joint interest, he or she can do so through a partition of the property - a division of the land into distinctly owned plots if such division is legally permitted based upon zoning and other local land use restrictions or, where such division is not permitted, a forced sale of the property followed by a division of proceeds.

If the parties are unable to agree to a partition, any or all of them may seek the ruling of a court to determine how the land should be divided up, physically divide it between the joint owners (partition in kind), leaving each with ownership of a portion of the property representing their share. Courts may also order a partition by sale in which the property is sold and the proceeds are distributed to the owners. Where local law does not permit physical division, the court must order a partition by sale.

Each co-owner is entitled to partition as a matter of right, meaning that the court will order a partition at the request of any of the co-owners. The only exception to this general rule is where the co-owners have agreed, either expressly or impliedly, to waive the right of partition. The right may be waived either permanently, for a specific period of time, or under certain conditions.
''

http://en.wikipedia.org/wiki/Timeshare

[[Category:Zero Hour]]

Legal Reform

2008-02-28T18:32:25Z

SamRose:

(pasting this in for reference to flesh out this page)

1. The Theory: The underlying theory in a nutshell in this case for User Owner
2. Existing problems in the real world that relate to this theory, a brief description.
3. Proposed way to apply the theory to those existing problems, the context or pre-requisites for this solution (solution in this case is application of the theory)
4. Related existing work that verifies feasability with context summary of links to those references
5. Related existing data or facts that support theory
6. Existing constraints and barriers to deploying user owner
7. Related existing work that argues against User owner (or summary and link to a place where this already exists)
8. facts and data that support arguments against
9. A brief summary about how this is related to Open Source Ecology (Relevance to OSE) core values
10. Links to partner site references
11. Seperate headings for descriptions of all active businesses, which will be supported by OSE infrastructure. We will provide you with resources you need, and help in growing this into an actual pilot project, help in connecting with other people, etc. We will help you grow this into a tangible real world project, the same way that we are growing open designs into real world products right now. When ventures are made, partnered open source software, open knowledge resources, and open design projects will receive a share of revenue

=Facts=
*[http://www.iamlawsuitabuse.org/facts/ Tort claims in the USA] are $880/citizen

[[Category:Zero Hour]]

Category:Zero Hour

2008-02-28T18:25:22Z

SamRose: /* Founding Question */

==Introduction==

When Open Source Ecology comes across people who are releasing under some form of open/reusable license, ideas or theories that we collectively think are useful, we will start an active project to immediately apply those ideas.

==Founding Question==

'''How can we work together apply some or all of your ideas in real world situations, right now, today?'''

==Origin==

''"This network, this human construct of technology and intellect, has been opened to us like a great beautiful playground. A total frontier. We, the nocturnal innocent throng through the gates and begin to explore, and we begin to build. We can build great landscapes in this blank slate paradise, works of great beauty and deep meaning. But it must be claimed for beauty and not for cash. It must be claimed for truth and progress, for learning and exploration. For glory through achievement, and not power through greed. Let now be the zero hour." (from the now defunct http://web.archive.org/web/20010208150333/http://zerohour.net/ site)''

We add:

We must also work together to accelerate ideas into action. A tradition borrowed from http://www.communitywiki.org/en/ThinkTalkAct

We want to help focus ideas into '''usable, replicable solutions''', both in the realm of physical products, and in the realms of all other human systems. Let now ''also'' be the zero hour for us to help you start a project to apply your ideas into the real world as soon as possible, in an open and transparent way.