Activity Sharing TODO: Difference between revisions
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
* Integrate the call-activity (and so the whole video/voip stack) on XO images |
* Integrate the call-activity (and so the whole video/voip stack) on XO images |
||
* Write an easy API for tubes (smcv) |
* Write an easy API for tubes (smcv) |
||
** blocked by design discussion for now |
|||
* Manage activity invitations |
* Manage activity invitations |
||
* Properly implement activity sharing (currently we only have shared/unshared states) |
* Properly implement activity sharing (currently we only have shared/unshared states) |
Revision as of 15:35, 14 May 2007
PS & Sugar
- make the PS use salut
- Be sure Gabble and tubes are working on latest XO images
- Integrate the call-activity (and so the whole video/voip stack) on XO images
- Write an easy API for tubes (smcv)
- blocked by design discussion for now
- Manage activity invitations
- Properly implement activity sharing (currently we only have shared/unshared states)
Activities
- Redesign the chat activity to integrate it in the mesh view
- Redesign the call activity to integrate it in the mesh view
- Clean up connect4 activity to use sugar's API as much as possible (instead of TP API) (smcv)
Gabble
- Review tubes-cassidy
- Review tubes-cassidy-refactor
- Review whole tubes and merge
- Abstract Bytestream
- Abstract Tubes
- Implement p2p tubes (OBB ?)
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
Server side
- fix XMPP scalabity issues (server component?)