Open Source Product Development Pipeline - Revision history

Syk0 saje at 16:49, 29 April 2011

2011-04-29T16:49:27Z

← Older revision		Revision as of 16:49, 29 April 2011
Line 93:		Line 93:
	This starts with defining product [[Specifications]].		This starts with defining product [[Specifications]].

	~~[[Category:OSPDP]]~~
	[[Category:Open Engineering]]		[[Category:Open Engineering]]
	[[Category:Collaboration]]		[[Category:Collaboration]]

WikiSysop: /* Rubber Hits the Road */

2009-03-16T17:01:37Z

Rubber Hits the Road

← Older revision		Revision as of 17:01, 16 March 2009
Line 94:		Line 94:

	[[Category:OSPDP]]		[[Category:OSPDP]]
			[[Category:Open Engineering]]
			[[Category:Collaboration]]

WikiSysop: /* Rubber Hits the Road */

2009-03-06T18:34:37Z

Rubber Hits the Road

← Older revision		Revision as of 18:34, 6 March 2009
Line 91:		Line 91:
	=Rubber Hits the Road=		=Rubber Hits the Road=

	~~Yes. Let's do it~~.		This starts with defining product [[Specifications]].

	[[Category:OSPDP]]		[[Category:OSPDP]]

WikiSysop: /* Design */

2009-03-01T20:10:28Z

Design

← Older revision		Revision as of 20:10, 1 March 2009
Line 71:		Line 71:
	*Technical drawings		*Technical drawings
	*Calculations and Computer Aided Engineering, if applicable		*Calculations and Computer Aided Engineering, if applicable

			See the [[Product Specifications]] for the 40 technologies of interest.

	==Review and Bidding==		==Review and Bidding==

Mathew: /* Problem Statement */

2009-03-01T19:13:43Z

Problem Statement

← Older revision		Revision as of 19:13, 1 March 2009
Line 11:		Line 11:
	The main barriers to rapid development that we have faced so far at Factor e Farm is the lack of integrated information that helps one deploy all the technologies for the GVCS. It is our experience that while the internet contains lots of information, it is largely disorganized, low quality content. It is especially difficult to find '''economically-significant information''' - ie, that information which would help people become effective producers. So, while there's tons of crappy, incomplete, disintegrated, and biased information exists - rational information that can help one assess technological design, and therefore gain technological literacy towards the goals of effective production - is missing.		The main barriers to rapid development that we have faced so far at Factor e Farm is the lack of integrated information that helps one deploy all the technologies for the GVCS. It is our experience that while the internet contains lots of information, it is largely disorganized, low quality content. It is especially difficult to find '''economically-significant information''' - ie, that information which would help people become effective producers. So, while there's tons of crappy, incomplete, disintegrated, and biased information exists - rational information that can help one assess technological design, and therefore gain technological literacy towards the goals of effective production - is missing.

	~~This means that~~ in ~~practice~~, ~~ecologically-integrated product~~ and ~~production~~ systems, ~~such as~~ we~~'re proposing with~~ the ~~GVCS~~, ~~are literally nonexistent~~. ~~On top~~ of ~~this~~, ~~there is much vanity production - stuff that is built not to satisfy essential needs but rather~~ individual ~~egos~~. ~~"Look how cool I am because I built this." This~~ is ~~essentially the Maker community. Another maker~~ community, ~~Instructables~~, ~~is full of inferior~~ design, and is ~~largely non-replicable because it's lacking in meaning~~.		Sites like Instructables encourage individuals to develop and share but do not provide the structures necessary to refine designs into economically competitive projects. The Maker community is still in it's infancy, and the focus is largely on the very important step of empowering people to make things. But we are intent on developing products that replace primary economic goods (food and shelter systems) rather than hobby products. We need more than design sharing, we need a robust system that socializes the design process at every step, making the most of every volunteer's time and expertise. The current model of Making is individual design, community discussion, derivative individual design. Our goal is community design, life-cycle analysis, derivative community design. This ecologically-integrated product and production development system is literally nonexistent.

	To summarize, we have to date been unable to spawn a massive, open source product development process. The missing link is ~~lack of ready access to~~ expertise and useful information, ~~for reasons stated above~~. ~~Because~~ of a ~~lack of resources, we are~~ to ~~date unable~~ to ~~attract~~ the ~~team (30 people) who could organize the effective deployment~~ of ~~the GVCS. While~~ we ~~are recruiting people slowly but surely, an accelerated process of development is needed that would assure delivery of~~ the entire GVCS ~~in 2 years~~. The level of support will determine the quality of the 40 product package.
			To summarize, we have to date been unable to spawn a massive, open source product development process. The missing link is a online collaborative infrastructure that can not only collect expertise and useful information, but organize it into coherent design proposals. This lack of a community support structure leaves developers on the ground at Factor E Farm to develop in isolation. We need support online and around the world to make accelerate on-site development and to make our site an attractive destination for the kind of talent we need to build the entire GVCS. The level of support will determine the quality of the 40 product package and the speed with which we can deliver it. We think we can prototype the package in 2 years time, but it will take a global village.

	=The Solution=		=The Solution=

WikiSysop: /* Deployment */

2009-02-27T18:37:04Z

Deployment

← Older revision		Revision as of 18:37, 27 February 2009
Line 86:		Line 86:
	*If the above is not possible, a member of Factor e Farm must travel to the fabricator's location.		*If the above is not possible, a member of Factor e Farm must travel to the fabricator's location.

			=Rubber Hits the Road=

			Yes. Let's do it.

	[[Category:OSPDP]]		[[Category:OSPDP]]

WikiSysop at 18:27, 27 February 2009

2009-02-27T18:27:29Z

@@ Line 32: / Line 32: @@
 In practice, the 2 points of The Solution above may be implemented as follows.
-To address the first point, we need to involve outside expertise early on in each project. To date, the entire package has been defined in [[Distillation 2]].
+To address the first point, we need to involve outside expertise early on in each project. To date, the entire package has been defined in [[Distillation 2]] - so this is the springboard for further action. Basic product descriptions can be collated readily from these, with performance and cost specifications. This should be then taken to experts for peer review.
 =Overall Product Development Technique=
 [[Category:OSPDP]]

WikiSysop at 17:53, 27 February 2009

2009-02-27T17:53:23Z

← Older revision		Revision as of 17:53, 27 February 2009
Line 28:		Line 28:
	One possible deployment scenario is that outside expertise is funded to develop technical details of implementation, and [[Dream Team 30]] will serve largely in an integrative and testing capacity. It takes a village to build a village.		One possible deployment scenario is that outside expertise is funded to develop technical details of implementation, and [[Dream Team 30]] will serve largely in an integrative and testing capacity. It takes a village to build a village.

	=Tactical Approach=		=Proposed Tactical Approach=

	~~#Lack~~ of ~~technical review~~ to ~~validate~~		In practice, the 2 points of The Solution above may be implemented as follows.

			To address the first point, we need to involve outside expertise early on in each project. To date, the entire package has been defined in [[Distillation 2]].

			=Overall Product Development Technique=


	~~The basic working assumption of this process is that large external support can be generated bey~~
	[[Category:OSPDP]]		[[Category:OSPDP]]

WikiSysop: /* The Solution */

2009-02-27T17:50:33Z

The Solution

← Older revision		Revision as of 17:50, 27 February 2009
Line 25:		Line 25:

	These two development points also assume the presence of a physical laboratory - Factor e Farm - for carrying out the building of the world's first, replicable, open source, global village. Moreover, we have under our command the building techniques, utilizing both standard and CEB construction methods - for housing any collaborators on-demand.		These two development points also assume the presence of a physical laboratory - Factor e Farm - for carrying out the building of the world's first, replicable, open source, global village. Moreover, we have under our command the building techniques, utilizing both standard and CEB construction methods - for housing any collaborators on-demand.

			One possible deployment scenario is that outside expertise is funded to develop technical details of implementation, and [[Dream Team 30]] will serve largely in an integrative and testing capacity. It takes a village to build a village.

	=Tactical Approach=		=Tactical Approach=

WikiSysop: /* Problem Statement */

2009-02-27T17:48:35Z

Problem Statement

← Older revision		Revision as of 17:48, 27 February 2009
Line 13:		Line 13:
	This means that in practice, ecologically-integrated product and production systems, such as we're proposing with the GVCS, are literally nonexistent. On top of this, there is much vanity production - stuff that is built not to satisfy essential needs but rather individual egos. "Look how cool I am because I built this." This is essentially the Maker community. Another maker community, Instructables, is full of inferior design, and is largely non-replicable because it's lacking in meaning.		This means that in practice, ecologically-integrated product and production systems, such as we're proposing with the GVCS, are literally nonexistent. On top of this, there is much vanity production - stuff that is built not to satisfy essential needs but rather individual egos. "Look how cool I am because I built this." This is essentially the Maker community. Another maker community, Instructables, is full of inferior design, and is largely non-replicable because it's lacking in meaning.

	To summarize, we have to date been unable to spawn a massive, open source product development process. The missing link is lack of ready access to expertise and useful information, for reasons stated above. Because of a lack of resources, we are to date unable to attract the team (30 people) who could organize the effective deployment of the GVCS.		To summarize, we have to date been unable to spawn a massive, open source product development process. The missing link is lack of ready access to expertise and useful information, for reasons stated above. Because of a lack of resources, we are to date unable to attract the team (30 people) who could organize the effective deployment of the GVCS. While we are recruiting people slowly but surely, an accelerated process of development is needed that would assure delivery of the entire GVCS in 2 years. The level of support will determine the quality of the 40 product package.

	=The Solution=		=The Solution=