OLPC software: our first release and beyond.

[Michael Rueger]

Walter Bender wrote:

> It is important now to set expectations for the software that ships on
> the XOs in September. The tremendous amount of work to date does not
> change the fact that our first-release software is very much a work in
> progress. The software at ship time will not have all the richness of
> the Mesh view as described in our User Interface Guide, but we are on
> track to have an extensible framework in place. The Journal, another
> important component of Sugar, recently appeared in our builds and
> currently offers bare-bones functionality; however, the first
> iteration of the data store is near completion and includes support
> for removable media and network file systems. The Journal is on track
> to include more features, such as a rich system to tag, search, and
> sort in the coming months, and an API for developers. The ability to
> open files, read, write, etc., are being transitioned to mediation by
> both the Journal and, at a lower level, Bitfrost, our security system.
> These transitions will be completed before we ship.

How long a time frame is planned to give application developers time to 
port/adjust/extend their applications to work with the APIs, security 
system etc?

Is there time allocated for regression testing?

We (the Squeakers) already have a hard time keeping up with changing 
APIs, launch sequences etc. And to make life even more interesting 
things like the need to extract the DBus Activity Protocol from the 
source code.

Is there a plan for central/country specific server locations where 
content can be hosted? Or do activity providers like etoys or Sophie 
also need to provide content hosting?

So many questions :-)

Michael