Factor e Farm Blog - Revision history

Donovan: /* Introduction */

2012-12-01T00:21:39Z

Introduction

← Older revision		Revision as of 00:21, 1 December 2012
Line 1:		Line 1:
	=Introduction=		=Introduction=

	Factor e Farm (FeF) maintains a weblog at http://blog.opensourceecology.org. This blog is dedicated to documenting the progress and discussion on the [[Global Village Construction Set]] as it is being implemented at Factor e Farm. The blog is the main communication venue for updates on the work of the FeF experiment. The general flavor of the discussion promotes the [[Factor e Farm Position Statement]].		[[Factor e Farm]] (FeF) maintains a weblog at http://blog.opensourceecology.org. This blog is dedicated to documenting the progress and discussion on the [[Global Village Construction Set]] as it is being implemented at Factor e Farm. The blog is the main communication venue for updates on the work of the FeF experiment. The general flavor of the discussion promotes the [[Factor e Farm Position Statement]].

	Current, on-site members of Factor e Farm may author posts on the Factor e Farm blog. Special guests from off-site may also be invited to publish guest articles. Anyone may write comments on posts. We invite all constructive and insightful comments that uphold the [[Factor e Farm Position Statement]]. We value open, informed discussion highly, as we see it as the only route to an empowered society.		Current, on-site members of Factor e Farm may author posts on the Factor e Farm blog. Special guests from off-site may also be invited to publish guest articles. Anyone may write comments on posts. We invite all constructive and insightful comments that uphold the [[Factor e Farm Position Statement]]. We value open, informed discussion highly, as we see it as the only route to an empowered society.

Marcin: /* Technical Blogging Standards */

2012-05-12T21:02:37Z

Technical Blogging Standards

← Older revision		Revision as of 21:02, 12 May 2012
Line 31:		Line 31:
	#'''Field Testing Video''' - It is useful to cap off a blog post with actual usage video. See video at end of post.		#'''Field Testing Video''' - It is useful to cap off a blog post with actual usage video. See video at end of post.

	For other work product - such as construction or fabrication results - blog posts can be written with the corresponding 5 pieces of content.		For other work product - such as construction or fabrication results, or even organizational development - blog posts can be written with the corresponding 6 pieces of content that are closest to the actual item - such as a video demonstration of a web platform instead of the ''Field Testing Video.''
	[[Category:Documentation]]		[[Category:Documentation]]

Marcin: /* Technical Blogging Standards */

2012-05-12T21:00:43Z

Technical Blogging Standards

← Older revision		Revision as of 21:00, 12 May 2012
Line 27:		Line 27:
	#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. A tripod or camera stand should be used to capture action footage. ''Example: notice how the Pulverizer video walks the viewer dynamically through all the steps and actions in an effort to keep the viewer's attention, while covering the process from start to finish.''		#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. A tripod or camera stand should be used to capture action footage. ''Example: notice how the Pulverizer video walks the viewer dynamically through all the steps and actions in an effort to keep the viewer's attention, while covering the process from start to finish.''
	#'''Product CAD''' - Show CAD, models, animations, embed 3D manipulable files (STL, Sketchup, etc) into blog post, and link to the source files. ''Example: Note the CAD of the Pulverizer in qCAD with a direct link to the file repository.''		#'''Product CAD''' - Show CAD, models, animations, embed 3D manipulable files (STL, Sketchup, etc) into blog post, and link to the source files. ''Example: Note the CAD of the Pulverizer in qCAD with a direct link to the file repository.''
	#'''Product Specifications'''' - Shows specifications and performance data, focusing on [[OSE Specifications]]		#'''Product Specifications''' - Shows specifications and performance data, focusing on [[OSE Specifications]]. ''Example: see the table of specifications shown.''
			#'''Basic discussion of economic significance''' - discuss why the performance to cost ratio is high. ''Example: Note that the author points out a $200 dedicated parts cost for the soil pulverizer, or a fraction of what one would pay for a commercial counterpart.''
			#'''Field Testing Video''' - It is useful to cap off a blog post with actual usage video. See video at end of post.

			For other work product - such as construction or fabrication results - blog posts can be written with the corresponding 5 pieces of content.
	[[Category:Documentation]]		[[Category:Documentation]]

Marcin: /* Technical Blogging Standards */

2012-05-12T20:52:44Z

Technical Blogging Standards

← Older revision		Revision as of 20:52, 12 May 2012
Line 27:		Line 27:
	#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. A tripod or camera stand should be used to capture action footage. ''Example: notice how the Pulverizer video walks the viewer dynamically through all the steps and actions in an effort to keep the viewer's attention, while covering the process from start to finish.''		#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. A tripod or camera stand should be used to capture action footage. ''Example: notice how the Pulverizer video walks the viewer dynamically through all the steps and actions in an effort to keep the viewer's attention, while covering the process from start to finish.''
	#'''Product CAD''' - Show CAD, models, animations, embed 3D manipulable files (STL, Sketchup, etc) into blog post, and link to the source files. ''Example: Note the CAD of the Pulverizer in qCAD with a direct link to the file repository.''		#'''Product CAD''' - Show CAD, models, animations, embed 3D manipulable files (STL, Sketchup, etc) into blog post, and link to the source files. ''Example: Note the CAD of the Pulverizer in qCAD with a direct link to the file repository.''
			#'''Product Specifications'''' - Shows specifications and performance data, focusing on [[OSE Specifications]]

	[[Category:Documentation]]		[[Category:Documentation]]

Marcin: /* Technical Blogging Standards */

2012-05-12T20:51:41Z

Technical Blogging Standards

← Older revision		Revision as of 20:51, 12 May 2012
Line 22:		Line 22:
	=Technical Blogging Standards=		=Technical Blogging Standards=

	Every blog ~~post~~ by active project developers should include several features listed here. This applies to GVCS product development. A good sample blog post that contains these is the [[Soil Pulverizer Prototype II Blog Post]] - which is referenced in this list:		Every blog showing a finished build + test cycle by active project developers should include several features listed here. This applies to GVCS product development. A good sample blog post that contains these is the [[Soil Pulverizer Prototype II Blog Post]] - which is referenced in this list:

	#'''Status update and context regading its importance''': ''We have finished the second prototype of the open source soil pulverizer – an important labor-saving device for soil-handling in CEB construction. It is useful because it combines digging-pulverizing-loading the CEB press in one device...''		#'''Status update and context regading its importance''': ''We have finished the second prototype of the open source soil pulverizer – an important labor-saving device for soil-handling in CEB construction. It is useful because it combines digging-pulverizing-loading the CEB press in one device...''
	#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. Example: notice how the Pulverizer video walks the viewer dynamically through all the steps in an effort to keep the viewer's attention, while		#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. A tripod or camera stand should be used to capture action footage. ''Example: notice how the Pulverizer video walks the viewer dynamically through all the steps and actions in an effort to keep the viewer's attention, while covering the process from start to finish.''
			#'''Product CAD''' - Show CAD, models, animations, embed 3D manipulable files (STL, Sketchup, etc) into blog post, and link to the source files. ''Example: Note the CAD of the Pulverizer in qCAD with a direct link to the file repository.''


	[[Category:Documentation]]		[[Category:Documentation]]

Marcin: /* Blogging Technical Standards */

2012-05-12T20:47:18Z

Blogging Technical Standards

← Older revision		Revision as of 20:47, 12 May 2012
Line 20:		Line 20:
	In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.		In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.

	=Blogging ~~Technical~~ Standards=		=Technical Blogging Standards=

	Every blog post by active project developers should include several features listed here. This applies to GVCS product development. A good sample blog post that contains these is the [[Soil Pulverizer Prototype II Blog Post]]		Every blog post by active project developers should include several features listed here. This applies to GVCS product development. A good sample blog post that contains these is the [[Soil Pulverizer Prototype II Blog Post]] - which is referenced in this list:

	#Status update		#'''Status update and context regading its importance''': ''We have finished the second prototype of the open source soil pulverizer – an important labor-saving device for soil-handling in CEB construction. It is useful because it combines digging-pulverizing-loading the CEB press in one device...''
	#Fabrication video		#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. Example: notice how the Pulverizer video walks the viewer dynamically through all the steps in an effort to keep the viewer's attention, while

	[[Category:Documentation]]		[[Category:Documentation]]

Marcin at 20:40, 12 May 2012

2012-05-12T20:40:35Z

← Older revision		Revision as of 20:40, 12 May 2012
Line 19:		Line 19:

	In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.		In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.

			=Blogging Technical Standards=

			Every blog post by active project developers should include several features listed here. This applies to GVCS product development. A good sample blog post that contains these is the [[Soil Pulverizer Prototype II Blog Post]]

			#Status update
			#Fabrication video

	[[Category:Documentation]]		[[Category:Documentation]]

Marcin: /* Introduction */

2012-05-12T20:37:21Z

Introduction

← Older revision		Revision as of 20:37, 12 May 2012
Line 1:		Line 1:
	=Introduction=		=Introduction=

	Factor e Farm (FeF) maintains a weblog at http://~~openfarmtech~~.org~~/weblog/~~. This blog is dedicated to documenting the progress and discussion on the [[Global Village Construction Set]] as it is being implemented at Factor e Farm. The blog is the main communication venue for updates on the work of the FeF experiment. The general flavor of the discussion promotes the [[Factor e Farm Position Statement]].		Factor e Farm (FeF) maintains a weblog at http://blog.opensourceecology.org. This blog is dedicated to documenting the progress and discussion on the [[Global Village Construction Set]] as it is being implemented at Factor e Farm. The blog is the main communication venue for updates on the work of the FeF experiment. The general flavor of the discussion promotes the [[Factor e Farm Position Statement]].

	Current, on-site members of Factor e Farm may author posts on the Factor e Farm blog. Special guests from off-site may also be invited to publish guest articles. Anyone may write comments on posts. We invite all constructive and insightful comments that uphold the [[Factor e Farm Position Statement]]. We value open, informed discussion highly, as we see it as the only route to an empowered society.		Current, on-site members of Factor e Farm may author posts on the Factor e Farm blog. Special guests from off-site may also be invited to publish guest articles. Anyone may write comments on posts. We invite all constructive and insightful comments that uphold the [[Factor e Farm Position Statement]]. We value open, informed discussion highly, as we see it as the only route to an empowered society.

WikiSysop: /* Introduction */

2009-08-22T00:05:15Z

Introduction

← Older revision		Revision as of 00:05, 22 August 2009
Line 9:		Line 9:
	Certain basic standards should be followed by all blog writing. This includes:		Certain basic standards should be followed by all blog writing. This includes:

	#No profanity should be used.		#No excessive profanity should be used.
	#Content should be verifiable for its accuracy, and inaccurate or misleading information should be avoided.		#Content should be verifiable for its accuracy, and inaccurate or misleading information should be avoided.
	#Personal attacks and flame wars are forbidden.		#Personal attacks and flame wars are forbidden.
Line 16:		Line 16:
	#Negative or pessimistic comments, such as blanket statement that 'this will not work' - if missing any justification, reason, of proof - should be discussed in other venues. The FeF experiment is interested in solutions that frequently stretch the limits of one's imagination, so unsupported criticism does not contribute to our work. However, if one provides criticism with supporting information, and especially with direct implication of possible solutions - then we welcome such comments.		#Negative or pessimistic comments, such as blanket statement that 'this will not work' - if missing any justification, reason, of proof - should be discussed in other venues. The FeF experiment is interested in solutions that frequently stretch the limits of one's imagination, so unsupported criticism does not contribute to our work. However, if one provides criticism with supporting information, and especially with direct implication of possible solutions - then we welcome such comments.

	The moderator team reserves the right to determine the suitability of all comments. In the case of objectionable content, the commenting author shall be notified by email regarding this policy and specific points that were violated. The author will be given a chance to make corrections. Otherwise, the comment will ~~not~~ be ~~published~~. The moderation queue will be processed on a daily basis.		The moderator team reserves the right to determine the suitability of all comments. In the case of objectionable content, the commenting author shall be notified by email regarding this policy and specific points that were violated. The author will be given a chance to make corrections. Otherwise, the comment will be marked for deletion. The moderation queue will be processed on a daily basis.

	In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.		In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.

	[[Category:Documentation]]		[[Category:Documentation]]

WikiSysop: /* Introduction */

2009-08-21T23:59:38Z

Introduction

← Older revision		Revision as of 23:59, 21 August 2009
Line 9:		Line 9:
	Certain basic standards should be followed by all blog writing. This includes:		Certain basic standards should be followed by all blog writing. This includes:

	#No ~~excessive~~ profanity should be used.		#No profanity should be used.
	#Content should be verifiable for its accuracy, and inaccurate or misleading information should be avoided.		#Content should be verifiable for its accuracy, and inaccurate or misleading information should be avoided.
	#Personal attacks and flame wars are forbidden.		#Personal attacks and flame wars are forbidden.
Line 16:		Line 16:
	#Negative or pessimistic comments, such as blanket statement that 'this will not work' - if missing any justification, reason, of proof - should be discussed in other venues. The FeF experiment is interested in solutions that frequently stretch the limits of one's imagination, so unsupported criticism does not contribute to our work. However, if one provides criticism with supporting information, and especially with direct implication of possible solutions - then we welcome such comments.		#Negative or pessimistic comments, such as blanket statement that 'this will not work' - if missing any justification, reason, of proof - should be discussed in other venues. The FeF experiment is interested in solutions that frequently stretch the limits of one's imagination, so unsupported criticism does not contribute to our work. However, if one provides criticism with supporting information, and especially with direct implication of possible solutions - then we welcome such comments.

	The moderator team reserves the right to determine the suitability of all comments. In the case of objectionable content, the commenting author shall be notified by email regarding this policy and specific points that were violated. The author will be given a chance to make corrections. Otherwise, the comment will be ~~marked for deletion~~. The moderation queue will be processed on a daily basis.		The moderator team reserves the right to determine the suitability of all comments. In the case of objectionable content, the commenting author shall be notified by email regarding this policy and specific points that were violated. The author will be given a chance to make corrections. Otherwise, the comment will not be published. The moderation queue will be processed on a daily basis.

	In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.		In summary, the work of FeF is evolving and its contribution to post-scarcity via open source economic development is becoming increasingly significant. For this reason, and because of the blog's cultural-creative value - it is becoming increasingly important to keep high publishing standards. The intent of this blog policy is to assure such quality reporting and discussion.

	[[Category:Documentation]]		[[Category:Documentation]]