Remote Prototyping

From Proposal_2008_Deployment_Strategy_For_OSE_Product_Cycle We are asking remote co-developers to take interest in the project, without enjoying the full benefit of seeing the integrated fruits of the effort - namely, the building of the facility itself. We address this point by motivating the development of each of the 16 key technologies for infrastructure building as products in their own right. We divide and conquer, and propose the development of the 16 technologies through the avenue of explicit products that utilize these technologies. As such, we can attract stakeholders interested in particular products, and develop the key generative technologies as part of that process.

The only way to meet the timeline goal is to proceed with parallel development of the technologies.

from FeF_Strategy_Statement Collaboration Potential – The essence of an open source development project is its openness to external contribution. FeF will engage in collaborative hardware projects (both hardware and other organizational projects) at any time that it can: (1), Identify significant, available, open source intellectual capital (open design, open expertise, etc.) that can be used in product replication at FeF or off-site; (2), Identify a person that could serve as project leader to implement those projects on-site at FeF via Dedicated Project Visits, or as a remote collaborator; (3), verify that the project is consistent with the GVCS and FeF Position Statement; and (4), proposed project does not divert resources from existing projects. When these four criteria are met, a solid foundation is created for project success, including fungibility via crowd funding or other methods. Non-hardware projects may include topics such as organizational or resource development, education, outreach, collaboration development, project replication, or many others.