Feature roadmap/Synchronous collaboration

Feature subcategory		Is part of::Category:Collaboration
Requesters		{{#arraymap:Carla and David, Teachers on OLPC-Sur, Peru technical leaders|,|x|Requested by::x}}
Requirements		See detailed collaboration requirements here: 9.1.0 Collaboration Requirements Allow for intuitive mesh connection and activity-sharing. Must support first two use cases defined at: Use Cases#Collaboration Examples Requirements#Mesh / Connectivity_Requirements Requirements#AbiWord Sharing Requirements http://lists.laptop.org/pipermail/sugar/2008-July/007407.html May need to include that link in developer section below, tbd
Specification		* Ensure Gadget is correctly integrated and deployed in Sugar so we can avoid the troublesome shared roster haxks on the XMPP server Fix tubes so that peer to peer data is sent with peer to peer connections on the network where possible Fix the way JIDs are allocated to be more coherent and based on the child's nickname (also would benefit a lot from having hierachical DNS naming on the school server so each JID is globally unique) Expose JIDs in the UI and allow them to be typed in and approved by normal subscription requests, allowing collaboration with anyone whose JID you know Implement the Telepathy file transfer spec to enable that feature in Sugar Enable avatars in Sugar (although maybe not if we're doing link-local multicast on an XO mesh network) and maybe some UI for taking a photo and setting that as your avatar See also: http://sugarlabs.org/go/DevelopmentTeam/0.84/Ideas#Glucose
Owners		{{#arraymap:Gregorio|,|x|Contact person::User:x}}
Priority		Priority::2
Helps deployability?		Helps deployability::no
Target for 9.1?		Target for 9.1::no