[sugar] Develop's version control (bazaar) and sugar.presence and sugar.p2p

Marco Pesenti Gritti mpg
Fri Feb 16 04:35:35 EST 2007


On Thu, 2007-02-15 at 23:22 -0500, Andrew Clunis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi folks,
> 
> I've finally settled on bazaar for Develop's version control engine (I
> am sure Ivan will be happy about that!).  Now, I am looking towards
> binding it to sugar's communication system.  Right now, bazaar can reach
> branches hosted via bazaar's own protocol, http, ftp, ssh, and several
> others.  I suspect I will need to add another protocol to this list,
> "bzr-olpc".  This protocol implementation will contact the local running
> sugar instance (either by importing it directly or communicating with
> the running service over d-bus), I expect.
> 
> Why do I want to do this?
> 
> Firstly, it must be possible for a child to branch an activity written 
> by another child on the mesh.  So, it needs to be aware of OLPC's
> Presence system.  Bazaar URIs pointing to XO-hosted branches will end
> up looking something like this:
> 
> bzr-olpc://andrew-dc216ac4a4c232815731979db6e494f315b507dd/my-program
> 
> Secondly, because -- as I understand it -- the mesh may be "extruded"
> via XMPP in order to bring in other kids who aren't on the same
> physical 802.11s mesh network.  Thus, it seems to me that it will be
> very likely that activities will be mandated to perform all
> collaboration-related communication via some abstracted interface in
> sugar, and not with sockets.
> 
> Is sugar.p2p ready enough for me to begin implementing this?  Or should I
> wait a bit longer?
> 

I think Dan has been working on this, I'd suggest to wait until his work
is checked in...

Marco



More information about the Sugar-devel mailing list