Difference between revisions of "About"

From Organic Design wiki
m
m
 
(85 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<table class=document-code><tr><td>
+
The [[Organic Design peer group]] is a small [[trust group]] whose members work well together as a team on various projects involving common interests. The team members all share common values, covered in our [[manifesto]] but include, amongst other things, [http://www.fsf.org free software], [[w:Peer-to-peer (meme)|decentralised solutions]] and the general idea of maximising re-usability of these solutions and actively sharing them with others.
Starting some notes about the org to evolve into discussed useful documents (this is just at the stage of internal notes requiring a lot of shared context). The wiki has been main programming-development focussed and so the documentation of our core concepts at the project-scale have not progressed. In fact there's many notions that have been developed over the years of our part in the project which have not been "wikified" yet, much of this could be extracted from the so-called "Trinity" printed a few years back.
 
</table>
 
  
 +
Since all the members work together as a functional unit, each can confidently take on jobs that they otherwise wouldn't have the expertise to complete alone, and since all the members are associated with many potential clients, the availability of good projects to work on is also improved.
  
==== Organic Design Limited ====
+
The peer group has been working on a long-term project that involves defining a standard system we call the [[Platform specification]]. This is a [[system]] allows organisations to operate in accord with the principles outlined in the manifesto. We've been working on this in the background for over ten years as a long-term research project, and even though we've done a lot of development, it's all been in the context of research and prototyping.
An organisation set up by me (Aran) to support the development of the project and so be a legal trading entity that could be paid for performing services in the field. This didn't quite work out since my bankruptcy has had more lasting effects than expected, and also development work has been far more intense than expected.
 
;Platforms & Sanctuaries
 
The business OD will be carrying out is organisational functions and seminars and would be set up as a system including cafe, accomodation, education etc. The busniess plan would be a platform-template to allow other orgs to set up in the same way with more or less focus on the carious service aspects. For example a modified version was under construction called ''sanctuary'' which was desgined to be more remote and handle longer-term accomodation and education programs.
 
  
 +
We're now at the stage where we have a clear idea of the software and content we'd like to see in a packaged-up and releasable form. The peer group's role in this phase will be that of project architects. The input we'll have in terms of the software development will be focussed high-level technical direction. Our hands-on work will be mainly focussed on the ontology, which includes documentation, procedures, educational material and other system-oriented aspects.
  
==== The Project ====
+
Our aim is to minimise the amount of software development required, by using our current [[wiki organisation]] framework as a unified interface that effectively glues together a number of other applications into a mashup.
The big-picture project of which the Yi is an instance of an attempted solution, ie supplying tools to the common people allowing them to grow organisation in accord with the fundamental patterns. Organic Design is an org that is set up like a "branch office" to carry out work on behalf of the project in this region covered by its nodes.
 
  
 
+
[[Category:Organic Design]][[Category:No files or comments‎]]
==== Peer ====
 
Most of the development strands are focussed on the peer. This is the full p2p network operating system built on [[The Nodal Model]]. It is designed to be widely available using any OS/interface environments, but to be capable of working completely independently as well using its own Linux destribution called [[Peerix]]. This is an interface designed for non-IT-specialists to design and maintain any kind organisations in an extremely efficient and sustainable manor while inherently increasing co-operation, re-use and growth.
 
 
 
 
 
==== XmlWiki ====
 
This is a collaborative development environment built on top of the freely available wiki software called [[Wikipedia:MediaWiki|MediaWiki]] which was designed for the [[Wikipedia:Wikipedia|Wikipedia]] online encyclopedia. We have found that existing solutions like [http://www.sf.net Source Forge] are excellent for raw programming, but are too complex and rigid for conceptual development or other use by non-developers. With XmlWiki, we've combined the programming features we needed into the more adaptable wiki environment allowing us to evolve the environment to our needs as we go.
 
 
 
The purpose of XmlWiki has always been to be a temporary stepping stone into the new environment. We were unable to progress on the peer-environment effectively without an existing, but adjustable environment to work togther in.
 
 
 
The peer and XmlWiki enviornments are closely linked as far as content goes, but most actual programming development is wasted going into XmlWiki and should instead be put into peer-based solutions. Although many features are still being specifically added to XmlWiki every week because its a powerful enough environment to add a lot of functionality with little effort.
 

Latest revision as of 18:47, 6 July 2015

The Organic Design peer group is a small trust group whose members work well together as a team on various projects involving common interests. The team members all share common values, covered in our manifesto but include, amongst other things, free software, decentralised solutions and the general idea of maximising re-usability of these solutions and actively sharing them with others.

Since all the members work together as a functional unit, each can confidently take on jobs that they otherwise wouldn't have the expertise to complete alone, and since all the members are associated with many potential clients, the availability of good projects to work on is also improved.

The peer group has been working on a long-term project that involves defining a standard system we call the Platform specification. This is a system allows organisations to operate in accord with the principles outlined in the manifesto. We've been working on this in the background for over ten years as a long-term research project, and even though we've done a lot of development, it's all been in the context of research and prototyping.

We're now at the stage where we have a clear idea of the software and content we'd like to see in a packaged-up and releasable form. The peer group's role in this phase will be that of project architects. The input we'll have in terms of the software development will be focussed high-level technical direction. Our hands-on work will be mainly focussed on the ontology, which includes documentation, procedures, educational material and other system-oriented aspects.

Our aim is to minimise the amount of software development required, by using our current wiki organisation framework as a unified interface that effectively glues together a number of other applications into a mashup.