Difference between revisions of "2007"

From Organic Design wiki
(peerix and peerd dev synthesis for the new year)
 
(build enviorment notes)
Line 3: Line 3:
 
= Distributed content =
 
= Distributed content =
 
The big focus initially for the [[peerd]] side of development in 2007 is to get [[io.c]] up to speed and integrated nodally. The result of this will be that the distributed content will be fully dynamic and cover all content, rather than being just the backups. --[[User:Nad|Nad]] 06:20, 16 Dec 2006 (NZST)
 
The big focus initially for the [[peerd]] side of development in 2007 is to get [[io.c]] up to speed and integrated nodally. The result of this will be that the distributed content will be fully dynamic and cover all content, rather than being just the backups. --[[User:Nad|Nad]] 06:20, 16 Dec 2006 (NZST)
 +
=Simplification of the build enviroment=
 +
The current buildroot enviroment is starting to become difficult to use as we add more of ouor custom requirements into the mix. GeeXboX has a simpler build system and most of the metadata for the software we would want to use. So I suggest perhaps designing a simpler buld system based on this.
 +
 +
No dependancy information will be handled at this level this is handled at the organisation level

Revision as of 23:04, 16 December 2006

The peerix and peerd aspects of development have started to merge together significantly in the last part of 2006, lets note our high level development plans and requirements here so we can have a good development synthesis in place for the new year --Nad 06:20, 16 Dec 2006 (NZST)

Distributed content

The big focus initially for the peerd side of development in 2007 is to get io.c up to speed and integrated nodally. The result of this will be that the distributed content will be fully dynamic and cover all content, rather than being just the backups. --Nad 06:20, 16 Dec 2006 (NZST)

Simplification of the build enviroment

The current buildroot enviroment is starting to become difficult to use as we add more of ouor custom requirements into the mix. GeeXboX has a simpler build system and most of the metadata for the software we would want to use. So I suggest perhaps designing a simpler buld system based on this.

No dependancy information will be handled at this level this is handled at the organisation level