Development Infrastructure: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(New page: {{draft}} =Notes on Wiki Infrastructure for Open Engineering= We need: a Platform for Open Engineering Marcin's personal attempt: openfarmtech.org - under Development Template. Marcin...)
 
Line 3: Line 3:
=Notes on Wiki Infrastructure for Open Engineering=
=Notes on Wiki Infrastructure for Open Engineering=


We need: a Platform for Open Engineering
Marcin's personal attempt: openfarmtech.org - under Development Template.
Marcin's summary: unless someone can show me a better development platform, the Development Template is good enough for now.
Once a better infrastructure for projects exists at Appropedia, then we could consider using it.
----
Mel's Comment:
Mel's Comment:


Line 39: Line 28:
-Mel
-Mel


OSE Brand Identity is what Vinay proposes, but I think it is as simple as 2 things.
----
 
Marcin's comments:
 
*We need: a Platform for Open Engineering
*Marcin's personal attempt: openfarmtech.org - under Development Template.
**However, this has a particular spec for its open engineering - it it open engineering + OSE Specifications (see Main Page)
*Once a better infrastructure for projects exists at Appropedia, then we could consider using it for some technical developments.
*Summary: unless someone can show me a better development platform, the Development Template is good enough for now. It embodies OSE Spec.
 
'''Critical additional comment''':
*OSE adds value in that (1) attempts open engineering, (2) does so according to a very unique goal - replicable villages with particular attributes as described on the Main Page
*It is the addition of value according to a unique goal that adds value to the open engineering itself. It is what drives the specifications for open engineering.
*I don't think one would come up with an option for creating OSE's replicable village if one just took a number of technologies and put them together. The OSE Specification (look on Main Page) is a glue for the type of engineering that goes on. Without that glue, you'd never arrive at the type of engineering proposed.
 
Comments?
----

Revision as of 19:50, 29 August 2007

This page was tagged as a candidate for deletion. If this page does not meet our criteria for deletion, please remove this notice.

(Explanation: deprecated, use Template: Under construction instead)

This page is a draft.
There may be relevant discussion on the talk page

Notes on Wiki Infrastructure for Open Engineering

Mel's Comment:

Marcin and I just spoke about this on the phone - Marcin, reminderping to coordinate a discussion w/ Chris (cc'd) & Vinay on the wiki-merge issue.

The way I see it, Appropedia can become a Sourceforge for open engineering. (Sure, it could use a better infrastructure for projects, but... we can work on that.)* It's a place where individual open engineering projects related to appropriate technology can have project websites, host files, etc. Development work, instructions on how to build a hexayurt, etc. would all be here.

OSE can then go and say things like "Look at all these different pieces of the puzzle that exist - full-fledged technologies being developed independently on places like Appropedia. Here's how you could combine them all into a working village - for housing, you could build hexayurts like this <link to hexayurt-building instruction pages on Appropedia> which would mean X, Y, and Z for the economics/dynamics/environmental impact of the village."

But that's just my $0.02, and I'll leave the discussion to Marcin, Vinay, and Chris.

-Mel


Marcin's comments:

  • We need: a Platform for Open Engineering
  • Marcin's personal attempt: openfarmtech.org - under Development Template.
    • However, this has a particular spec for its open engineering - it it open engineering + OSE Specifications (see Main Page)
  • Once a better infrastructure for projects exists at Appropedia, then we could consider using it for some technical developments.
  • Summary: unless someone can show me a better development platform, the Development Template is good enough for now. It embodies OSE Spec.

Critical additional comment:

  • OSE adds value in that (1) attempts open engineering, (2) does so according to a very unique goal - replicable villages with particular attributes as described on the Main Page
  • It is the addition of value according to a unique goal that adds value to the open engineering itself. It is what drives the specifications for open engineering.
  • I don't think one would come up with an option for creating OSE's replicable village if one just took a number of technologies and put them together. The OSE Specification (look on Main Page) is a glue for the type of engineering that goes on. Without that glue, you'd never arrive at the type of engineering proposed.

Comments?