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

[Zarro Boogs per Child]

#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:                       |  
----------------------------------+-----------------------------------------
Changes (by bemasc):

 * cc: bemasc (added)


Comment:

 Replying to [comment:1 gdesmott]:
 > If we don't want to have the activity launched to be able to receive
 calls, PS will have to announce the AV capabilities (probably only if the
 activity is installed).

 I strongly disagree.  See below.

 > I'd like to get rid of the buddy list in the video-chat-activity so
 we'll initiate calls using the invitations UI.

 I agree.

 > Maybe a "Call" entry in the mesh view would be good too. Anyway, we need
 to be able to check in sugar if a Buddy has the AV capability.

 I strongly disagree.

 We already have a complete system for this.  If I want to talk to Alison,
 I should start the Video Chat activity and then invite Alison using
 Sugar's standard invitation mechanisms.  Alison should receive the invite
 notification, and be able to join the activity just like any other
 activity invitation.

 If Alison does not have the video chat activity, then the situation is the
 same as any other time that Alison is invited to a session of an activity
 that Alison does not possess.  In this case, accepting the invitation
 should automatically transfer and install the required activity bundle,
 and then launch it.

 The last thing Sugar needs is a duplicate system of making contacts and
 managing capabilities.  I imagine that you are coming from a SIP mindset,
 but Sugar already has a complete system for identifying users and
 negotiating connections.  Sugar's sharing system is already ideally suited
 for making and receiving calls.

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