<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.opensourceecology.org/index.php?action=history&amp;feed=atom&amp;title=Documentation_Standards_Old</id>
	<title>Documentation Standards Old - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.opensourceecology.org/index.php?action=history&amp;feed=atom&amp;title=Documentation_Standards_Old"/>
	<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Documentation_Standards_Old&amp;action=history"/>
	<updated>2026-04-30T01:44:16Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.13</generator>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Documentation_Standards_Old&amp;diff=82254&amp;oldid=prev</id>
		<title>Marcin: Created page with &quot;=Introduction=  June 2011 marks a point of shifting the focus to professional documentation standard development at Factor e Farm. We are at the stage that such documentation...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Documentation_Standards_Old&amp;diff=82254&amp;oldid=prev"/>
		<updated>2012-12-01T23:27:27Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;=Introduction=  June 2011 marks a point of shifting the focus to professional documentation standard development at &lt;a href=&quot;/wiki/Factor_e_Farm&quot; title=&quot;Factor e Farm&quot;&gt;Factor e Farm&lt;/a&gt;. We are at the stage that such documentation...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
June 2011 marks a point of shifting the focus to professional documentation standard development at [[Factor e Farm]]. We are at the stage that such documentation is not only indispensable for production runs at Factor e Farm, but also for replication in other places worldwide. Check our [[Fabrication Procedure Standards]].&lt;br /&gt;
&lt;br /&gt;
A proposal for a GVCS documentation template is given in [[Mark J Norton/GVCS Template]].&lt;br /&gt;
&lt;br /&gt;
=Video Documentation Toolchain=&lt;br /&gt;
&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Cinelerra&amp;#039;&amp;#039;&amp;#039; as a free open-source cross-platform video editing software&lt;br /&gt;
&lt;br /&gt;
[http://cinelerra.org/ Cinelerra Home Page]&lt;br /&gt;
&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Audacity&amp;#039;&amp;#039;&amp;#039; as a free open-source cross-platform audio editing software&lt;br /&gt;
&lt;br /&gt;
[http://audacity.sourceforge.net/ Audacity Home Page]&lt;br /&gt;
&lt;br /&gt;
=Documentation Standards=&lt;br /&gt;
&lt;br /&gt;
We propose the following procedure for developing documentation based on prototyping work at Factor e Farm. &lt;br /&gt;
&lt;br /&gt;
#Upload all media to GitHub repository [https://github.com/organizations/OSE]&lt;br /&gt;
#Publish detailed fabrication procedure on wiki&lt;br /&gt;
#Fill in with pictures, jpg of CAD files, and links to actual CAD and CAM files in file repository&lt;br /&gt;
#Develop an instructional video based on wiki fabrication procedure and any additional material from media FTP repository&lt;br /&gt;
&lt;br /&gt;
=GVCS Documentation=&lt;br /&gt;
&lt;br /&gt;
Each GVCS tool should have OSE wiki pages with sections that deal with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Home&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Overview&lt;br /&gt;
* Detailed Description and Features&lt;br /&gt;
* Components&lt;br /&gt;
* Product Ecology&lt;br /&gt;
** Uses&lt;br /&gt;
** Creates&lt;br /&gt;
* Solution Statement&lt;br /&gt;
* Specifications&lt;br /&gt;
* Status&lt;br /&gt;
* See Also&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Research &amp;amp; Development&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Overview&lt;br /&gt;
* Research&lt;br /&gt;
** Goals&lt;br /&gt;
** General Design Goals&lt;br /&gt;
** Features&lt;br /&gt;
* Advantages&lt;br /&gt;
* Design&lt;br /&gt;
* Funding&lt;br /&gt;
* Peer Reviews&lt;br /&gt;
* Experiments and Prototypes&lt;br /&gt;
* Experimental Results&lt;br /&gt;
* Prototype Notes, Observation, Etc.&lt;br /&gt;
* Failure Mode Analysis&lt;br /&gt;
* Testing Results&lt;br /&gt;
* Recommendations for Improvement&lt;br /&gt;
* See Also&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Bill of Materials&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Google Docs&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Manufacturing Instructions&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Prepare&lt;br /&gt;
** Safety&lt;br /&gt;
** Workspace&lt;br /&gt;
** Tools&lt;br /&gt;
** Raw Materials&lt;br /&gt;
* Component Fabrication&lt;br /&gt;
** Cut&lt;br /&gt;
** Drill&lt;br /&gt;
** Misc&lt;br /&gt;
* Assembly&lt;br /&gt;
* Programming (if any)&lt;br /&gt;
* Finish&lt;br /&gt;
** Paint&lt;br /&gt;
** Test&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;User&amp;#039;s Manual&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Overview&lt;br /&gt;
* Safety Procedures and Considerations&lt;br /&gt;
* Operation Procedure&lt;br /&gt;
* Maintenance&lt;br /&gt;
* Breakdowns and Repair&lt;br /&gt;
* Assembly&lt;br /&gt;
* Disassembly&lt;br /&gt;
&lt;br /&gt;
=Documentation at Other Locations=&lt;br /&gt;
&lt;br /&gt;
As other locations come online, similar procedures should be implemented to facilitate contributions to the overall project.&lt;br /&gt;
&lt;br /&gt;
=Design Designations and Document Identifiers=&lt;br /&gt;
&lt;br /&gt;
As GVCS and other OSE tools mature, it will become difficult to keep documentation organized.  For identification purposes, a standard design iteration naming convention is proposed.  Each GVCS tool should be assigned a standard set of initials, LT for LifeTrac as an example.  Product iterations (models) can be either identified as P1, P2, etc. or given a descriptive name such as Rear Mounted Engine.  Thus, the current LifeTrac-2 would be referred to as a LT-P2 for documentation identification purposes.  It is quite possible that several design iterations are needed within a product model, thus the third design of the LifeTrac-2 would be referred to as LT-P2-D3.  The first design of the rear mounted engine could be known as LT-REM-D1.&lt;br /&gt;
&lt;br /&gt;
The main point of this identifications scheme is to create a name space that allows all documentation to be grouped together for a single design iteration.  Thus, the video that shows how to fabricate the back right wheel mount panel can be called &amp;quot;LT-REM-D1-Back-Rear-Wheel-Mount-Panel.wmv&amp;quot; and the related 3D CAD render could be called &amp;quot;LT-REM-D1-Back-Rear-Wheel-Mount-Panel=CAD-v2.png&amp;quot;.  Note that this is version 3 of the render.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Fabrication Procedure Standards]]&lt;br /&gt;
*[[Development]]&lt;br /&gt;
&lt;br /&gt;
=Video Documentation=&lt;br /&gt;
See [[Documentation/Video]]&lt;br /&gt;
&lt;br /&gt;
[[Video Documentation Best Practices]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Documentation]]&lt;/div&gt;</summary>
		<author><name>Marcin</name></author>
	</entry>
</feed>