Directionless Sprint week 4th March - 6th March

From The People Wiki
Revision as of 10:36, 14 March 2008 by SaulAlbert (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Aims

This is the final sprint in the initial development phase involving Saul, Andy, Wojciech and Joerg. The aims in this sprint are:

  • To strip down the feature list to the bare minimum, and implement that to start with.
  • Get to the stage where we can start getting users in, and then begin implementing call transfers and other fancy stuff.

Objectives

skype integration

  • --skype: build skype script (run on cron in the xsession) that periodically calls plone with status of all known buddies. calls plone with a dict(username:status,...), e.g.:--
  {u'w.kosma': u'ONLINE',
   u'echo123': u'ONLINE',
   u'intothemist': u'ONLINE',
   u'saulalbert': u'ONLINE',
   u'detest222': u'OFFLINE'}
  • plone: responds by setting participant statuses accordingly, and replying with names of buddies:
  [buddy1,buddy2]

communication is done using xmlrpc

confirmation

  • --plone: develop a method of triggering origination of conf call--
  • --asterisk: copy existing call script and modify to call user and wait for user to press 1, other key, or hang up.--
  • --plone: update participant to status 'confirmed'--
  • --plone: provide user feedback that 'you need to complete your registration' - kicking user back to stage 4 in the sign up process.--

In this first phase, all new users become Welcome Wagon Operators (high status users, likely to be called). In later stages, we will discriminate a bit more, and only route to people who are likely to be online and have signaled their willingness to be WWOPs.

offline until

When operator is called they can press 1, press any other key to decline call, or they just pick up and wait, then hang up (answer machine or clueless user)

'offline until' allows us to respond to this in various ways:

  • Case: user picks up phone and presses 1
    • conference is initiated, user is 'online'
  • Case: user picks up phone and presses any other key
    • user is marked offline for 1 hour
  • Case: wait then hang up (answer machine/clueless)
    • user is marked offline for 4 hours.

It can also happen repeated times

  • Case: user presses any other key 2nd time:
    • user is marked offline for 4 hours
  • Case: user presses any other key 3rd time:
    • user is marked offline for 24 hours
  • Case: user presses any other key 4th time:
    • user is marked offline indefinitely

In future iterations, they'll also be bounced when they call in from their mobile.

  • Case: user/machine waits then hangs up 2nd time:
    • user is marked offline for 24 hours
  • Case: user/machine waits then hangs up 3rd time:
    • user is marked offline indefinitely

In future iterations, we'll send them email or alert them that they'll need to do a new confirmation call or something.

non-techy templates

  • We need simple templates - stripped bare of all the plone gumf that don't provide such technical feedback.
  • This will be what the test users see.
  • If Saul or Andy have time, they can implement a stripped-down version of Liz's html/css
  • We need to have a link (provided as feedback - perhaps on each page) to the participant's call record - allowing them to see what's going on *now*. In future, this will be the call centre screen.


Next time

  • --We are having a meeting at 6pm to see how far we've got--
  • We will then arrange when we will finish off this version
  • We will also prioritise a list of things we'd like to do for the next version.
Personal tools
Namespaces
Variants
Actions
Toolbox