#3465 NORM Untriag: Removing invite-only activities when appropriate (was: Uninvitations)

[Zarro Boogs per Child]

#3465: Removing invite-only activities when appropriate
-------------------------------+--------------------------------------------
  Reporter:  morgs             |       Owner:  gdesmott          
      Type:  defect            |      Status:  new               
  Priority:  normal            |   Milestone:  Untriaged         
 Component:  telepathy-gabble  |     Version:  Git as of bug date
Resolution:                    |    Keywords:                    
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by smcv):

 * cc: marco, smcv, eben (added)


Comment:

 The real problem here turns out to be deciding when the connection manager
 should forget about invite-only activities.

 We've decided to address this particular problem by considering all
 outstanding invitations to a particular activity to have been cancelled
 when you join that activity.

 {{{
 14:38 < smcv> marcopg: it basically boils down to: if someone invites you
 to an
               activity, the CM adds that activity to its idea of their
               activities list
 14:39 < smcv> marcopg: but when should the CM remove that activity?
 14:39 < smcv> options include:
 14:39 < smcv> * when you join the activity (i.e. if you leave an invite-
 only
               activity, it falls off your mesh view until you're invited
 back)
 14:40 < smcv> * when the guy who invited you leaves the activity
 14:40 < smcv> (which requires him to send you a message "cancelling" the
               invitation)
 14:41 < smcv> * never (which is currently implemented and leads to #3465)
 14:41 < marcopg> smcv: when everyone left the activity is not an option?
 14:41 < smcv> marcopg: no, you can't know that
 14:42 < marcopg> never seem like the worst of the options to me
 14:42 < smcv> marcopg: unless someone who was previously in the activity
 sends
               you a message on your way out
 14:42 < smcv> *on their way out
 14:43 < smcv> the first option I said seems reasonably intuitive
 14:43 < marcopg> smcv: what about when *I* leave the activity?
 14:43 < smcv> that's more or less equivalent to what I said
 14:44 < smcv> as long as you're in the activity, it's irrelevant whether
 you
               think it's in anyone else's activity list
 14:44 < marcopg> oh you said "when you join"
 14:44 < smcv> because it *is* definitely in yours
 14:44 < smcv> so it appears in the mesh view regardless
 14:44 < marcopg> oh
 14:44 < marcopg> OK
 14:44 < marcopg> that sounds good to me
 14:44 < smcv> it only becomes significant whether it's in anyone else's
               activity list when you leave
 }}}

 The plan is now that we'll forget about invitations to an activity A
 either when we join A, or when the inviter notifies us that they have left
 A, whichever comes first.

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