#6301 NORM Never A: handle incoming media channels as video call activity invites

Zarro Boogs per Child bugtracker at laptop.org
Wed Mar 19 16:57:48 EDT 2008


#6301: handle incoming media channels as video call activity invites
----------------------------------+-----------------------------------------
  Reporter:  robot101             |       Owner:  Collabora     
      Type:  enhancement          |      Status:  new           
  Priority:  normal               |   Milestone:  Never Assigned
 Component:  video-chat-activity  |     Version:                
Resolution:                       |    Keywords:                
  Verified:  0                    |    Blocking:                
 Blockedby:                       |  
----------------------------------+-----------------------------------------

Comment(by bemasc):

 I see.  None of this is relevant to the case of two XOs communicating,
 with video or otherwise.  The Activity Sharing system supplants capability
 advertisements entirely.  The question of advertising capabilities applies
 only when an XO is attempting to communicate over Jabber with a non-XO-
 aware computer.

 This is not a very realistic problem.  The target schools do not have
 Macbooks running iChat.  There is negligible pre-existing software for
 Theora videoconferencing over Jabber.  XOs hardly work when using their
 own custom Jabber server; we are not in sight of any sort of
 interoperability with a major jabber service like Google Talk.  Anyone who
 wants to interoperate with XOs can always run sugar-jhbuild, which is now
 nicely packaged for Ubuntu and Fedora.

 However, if you really want to advertise capabilities like in XEP-0115,
 there are two options:
 1. Build these capabilities directly into Sugar.
 2. Determine capabilities on the basis of which activities are installed.

 Activities can be copied, modified, and distributed by the user.  The user
 could easily have 8 Activities installed that claim the ability to receive
 video calls, and only a few of them might actually work.  Therefore,
 Option 2 requires a control panel GUI that associates different Jabber
 capabilities with different Activities.  In terms of user-friendliness,
 this is a disaster.  Option 1 is much better, though as noted above, still
 entirely unnecessary.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6301#comment:5>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system



More information about the Bugs mailing list