EmpathyIndicator

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2009-11-14 04:43:22 →
Size: 2624
Editor: cpe-065-190-158-029
Comment:
← Revision 2 as of 2009-11-14 04:55:57 → ⇥
Size: 1443
Editor: cpe-065-190-158-029
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. There are several ways you may be contacted in Empathy. Currently all events show up in the indicator, we should look at ways to improve the workflow for handling these inbound events. Current inbound events include login notifications, new instant messages, buddy authorization requests, and video/audio calls.
Line 14: Line 14:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
Line 16: Line 15:
It is mandatory.
Line 20: Line 18:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. Not all events are equal when it comes to real-time communications. An instant message is real-time, in a very loose sense. It is not uncommon to respond to IMs after a delay, and the two-way communications can include many delays.
Line 22: Line 20:
However if a friend attempts an audio/video chat, there is no room for a delayed response. If you don't answer the call, your friend will just hang up. We should consider a stronger sense of real-time for a notification of these types of events.

It could also be very interesting to provide a way to leave a message when there is no answer.
 
Line 28: Line 30:
You can have subsections that better describe specific parts of the issue.
Line 31: Line 31:

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Line 36: Line 34:
Should cover changes required to the UI, or specific UI that is required to implement this
Line 39: Line 35:

Code changes should include an overview of what needs to change, and in some cases even the specific details.
Line 44: Line 38:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.
Line 50: Line 39:

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.
Line 57: Line 42:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
Line 60: Line 43:

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

Summary

There are several ways you may be contacted in Empathy. Currently all events show up in the indicator, we should look at ways to improve the workflow for handling these inbound events. Current inbound events include login notifications, new instant messages, buddy authorization requests, and video/audio calls.

Release Note

Rationale

Not all events are equal when it comes to real-time communications. An instant message is real-time, in a very loose sense. It is not uncommon to respond to IMs after a delay, and the two-way communications can include many delays.

However if a friend attempts an audio/video chat, there is no room for a delayed response. If you don't answer the call, your friend will just hang up. We should consider a stronger sense of real-time for a notification of these types of events.

It could also be very interesting to provide a way to leave a message when there is no answer.

User stories

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Test/Demo Plan

Unresolved issues

BoF agenda and discussion

CategorySpec

DesktopTeam/Specs/Lucid/EmpathyIndicator (last edited 2009-11-14 04:55:57 by cpe-065-190-158-029)