Sugar TODO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Old old old old ooooooold page) |
||
(3 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{Deprecated}} |
|||
=Sugar= |
=Sugar= |
||
Line 49: | Line 51: | ||
= Activity sharing = |
= Activity sharing = |
||
== PS |
== PS & Sugar == |
||
* write an easy API for tubes (smcv: in progress) |
|||
* make the PS use salut |
|||
* allow inviting without sharing (currently the PS only creates a MUC when you share) |
|||
* implement group sharing |
|||
== Gabble == |
|||
* review tubes branches (Robot101) |
|||
* implement p2p tubes ([http://www.xmpp.org/extensions/xep-0066.html OOB] ?) (Cassidy) |
|||
* implement stream tubes (Cassidy) |
|||
== Salut == |
|||
* sort out the authentication of our JIDs on the server with OLPC keys |
|||
* sign/verify salut presence adverts |
|||
* implement org.laptop.Telepathy.ActivityProperties |
|||
* implement tubes |
|||
* implement jingle calls |
|||
== Server side == |
|||
* fix XMPP scalability issues with a server component |
|||
** keep a registry of activities so we can get the activity id and name from a central place |
|||
** revisit activity enumeration, so we can do "find me activities of type $foo", or "get me some activities to fill up the mesh view" |
|||
** revisit buddy enumeration, so we don't need the shared roster hack. it's possible that we should just find random people by finding random activities, and not worry about "get be some buddies to fill up the mesh view". |
|||
** provide a solution for mutual groups? |
|||
[[Category:Sugar]] |
|||
[[Category:Developers]] |
Latest revision as of 11:33, 4 April 2008
Sugar
Browser
Datastore
Shell
Clipboard
Journal
Write
Chat activity
Call activity
Connect 4
Activity sharingPS & Sugar
Gabble
Salut
Server side
|