#4046 NORM First D: Collaboration invitation notifications (was: Gabble/Salut notifications)

[Zarro Boogs per Child]

#4046: Collaboration invitation notifications
--------------------------+-------------------------------------------------
  Reporter:  kimquirk     |       Owner:  marco                 
      Type:  enhancement  |      Status:  new                   
  Priority:  normal       |   Milestone:  First Deployment, V1.0
 Component:  sugar        |     Version:                        
Resolution:               |    Keywords:  collaboration         
  Verified:  0            |  
--------------------------+-------------------------------------------------
Changes (by smcv):

 * cc: Eben, smcv (added)
  * keywords:  => collaboration
  * component:  telepathy-other => sugar
  * owner:  smcv => marco


Comment:

 The Presence Service already generates notification events (the Invited
 signal) and the Sugar shell responds to them (they go in the bottom
 frame). I think this is mainly a job for Sugar shell UI improvements - PS
 exposes all the information available from the underlying protocol, and we
 can't add things to the underlying protocol unless we know what the UI
 wants.

 If the PS isn't giving Sugar enough information to display the desired
 notification, then we'll need some PS work to include that - depending
 what information is wanted and how many changes are needed in Gabble and
 Salut, we may or may not be able to do this for 1.0 (we can open new bugs
 for the post-1.0 part). I know you want membership information, for
 instance, and I don't think that's very feasible at the moment.

 The underlying protocols (XMPP and link-local XMPP for Gabble and Salut
 respectively) both have an optional human-readable message in the
 invitation - it's intended to be some text supplied by the user, similar
 to the sort of thing you'd say in a ping on IRC, such as "We're discussing
 #4046, please join in".

 The Telepathy D-Bus API, the PS D-Bus API and the sugar.presence library
 API all expose this message, but when
 sugar.activity.activity.Activity.invite() calls
 sugar.presence.activity.Activity.invite(), it's currently hard-coded to
 use an empty message. Can we do something more useful with it?

 I feel as though I've written this comment at least once before; there
 must be a related bug around somewhere?

-- 
Ticket URL: <https://dev.laptop.org/ticket/4046#comment:1>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system