JabberIntegration

Differences between revisions 10 and 19 (spanning 9 versions)
⇤ ← Revision 10 as of 2010-05-18 19:18:46 →
Size: 2217
Editor: S0106002369de4dac
Comment:
← Revision 19 as of 2013-11-16 18:59:38 → ⇥
Size: 1889
Editor: 95-91-236-250-dynip
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from SpecTemplate
Line 3: Line 4:
 * '''Launchpad Entry''': UbuntuSpec:foo
 * '''Created''':		  * '''Launchpad entry''': https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1247216
 * '''Created''': 16. November 2013
Line 6: Line 7:
 * '''Packages affected''':  * '''Packages affected''': messaging-app
Line 8: Line 9:
== Summary == Add support for XMPP (and possibly other protcols) to the messaging app.
Line 10: Line 11:
== Release Note ==

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.)

It is mandatory.		 == Release note ==
* Support for XMPP in the messaging app.
Line 17: Line 15:
Ubuntu Phone should come with support for messaging and not only SMS. It would be wonderful if this would be integrated in one app and be a feature that does not exist on Android (hangouts kind of does this but very poorly and does not support more than one protocol). The messaging app already uses telepathy so it should be possible to add the GUI for this, without much/any work on the backend.

In my opinion we should start with XMPP, because it is already well supported by Telepathy and an open protocol.

Also, Facebook supports XMPP. If there isn't WhatsApp on UbuntuPhone we could at least let people communicate with their Facebook friends, which would increase the value of the Phone a lot.

A good example how this can be done is Maemo:
 * http://farm5.static.flickr.com/4027/4315280299_030448e699.jpg
 * http://farm5.static.flickr.com/4027/4315280299_030448e699.jpg
Line 19: Line 26:

== Assumptions ==

== Design ==

You can have subsections that better describe specific parts of the issue.

== Implementation ==

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this

=== Code Changes ===

Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

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.

== Test/Demo Plan ==

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.		  * Bob wants to set up his Jabber account on the Phone
 * Alice wants to message his friends via Jabber
 * Bob wants to see the status (online, busy, offline...) of his friends in a contact list
 * Alice wants to send a file via Jabber
 * Bob wants to see his current messaging status via an indicator
Line 52: Line 33:

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.

== BoF agenda and discussion ==

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.		 Advandced stuff- like merging several contacts into one (e.g. one friend has XMPP and SMS) or adding support for more protocols (e.g. ICQ) -- should be handled by a seperate spec.

Add support for XMPP (and possibly other protcols) to the messaging app.

Release note

* Support for XMPP in the messaging app.

Rationale

Ubuntu Phone should come with support for messaging and not only SMS. It would be wonderful if this would be integrated in one app and be a feature that does not exist on Android (hangouts kind of does this but very poorly and does not support more than one protocol). The messaging app already uses telepathy so it should be possible to add the GUI for this, without much/any work on the backend.

In my opinion we should start with XMPP, because it is already well supported by Telepathy and an open protocol.

Also, Facebook supports XMPP. If there isn't WhatsApp on UbuntuPhone we could at least let people communicate with their Facebook friends, which would increase the value of the Phone a lot.

A good example how this can be done is Maemo:

User stories

  • Bob wants to set up his Jabber account on the Phone
  • Alice wants to message his friends via Jabber
  • Bob wants to see the status (online, busy, offline...) of his friends in a contact list
  • Alice wants to send a file via Jabber
  • Bob wants to see his current messaging status via an indicator

Unresolved issues

Advandced stuff- like merging several contacts into one (e.g. one friend has XMPP and SMS) or adding support for more protocols (e.g. ICQ) -- should be handled by a seperate spec.

CategorySpec

Unity8/JabberIntegration (last edited 2013-11-16 18:59:38 by 95-91-236-250-dynip)