IntegratingWithUbuntuOne

Differences between revisions 3 and 4
Revision 3 as of 2009-06-17 16:02:17
Size: 4033
Editor: joshuahoover
Comment:
Revision 4 as of 2009-06-17 16:03:13
Size: 4032
Editor: joshuahoover
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * '''Packages affected''': python-contacts-api, dbus-contacts-api, gtk-contacts-picker, erlang, couchdb, couchdb-bin, ubuntu-couchdb, couchdb-oauth, couchdb-history, ubutuone-sync-ui , evolution-couchdb, akonadi-couchdb, tomboy-couchdb, firefox-bookmarks-couchdb, python-couchdb, couchdb-glib, dbus-couchdb, python-couchdb-records-api, dbus-couchdb-records-api, icontool, ubuntuone-client, ubuntuone-storage-protocol, python-oauth, ubuntuone-screensharing, ejabberd, configglue, gwibber-couchdb  * '''Packages affected''': python-contacts-api, dbus-contacts-api, gtk-contacts-picker, erlang, couchdb, couchdb-bin, ubuntu-couchdb, couchdb-oauth, couchdb-history, ubutuone-sync-ui, evolution-couchdb, akonadi-couchdb, tomboy-couchdb, firefox-bookmarks-couchdb, python-couchdb, couchdb-glib, dbus-couchdb, python-couchdb-records-api, dbus-couchdb-records-api, icontool, ubuntuone-client, ubuntuone-storage-protocol, python-oauth, ubuntuone-screensharing, ejabberd, configglue, gwibber-couchdb
  • Launchpad Entry: Integrating with Ubuntu One

  • Created: 2009-06-17

  • Contributors:

  • Packages affected: python-contacts-api, dbus-contacts-api, gtk-contacts-picker, erlang, couchdb, couchdb-bin, ubuntu-couchdb, couchdb-oauth, couchdb-history, ubutuone-sync-ui, evolution-couchdb, akonadi-couchdb, tomboy-couchdb, firefox-bookmarks-couchdb, python-couchdb, couchdb-glib, dbus-couchdb, python-couchdb-records-api, dbus-couchdb-records-api, icontool, ubuntuone-client, ubuntuone-storage-protocol, python-oauth, ubuntuone-screensharing, ejabberd, configglue, gwibber-couchdb

Summary

Ubuntu One provides capabilities for the Ubuntu desktop as well as extended capabilities via optional online services. Integrating Ubuntu One capabilities with the Ubuntu desktop will provide storage sharing & synchronization (across a LAN and (optionally) the Ubuntu One cloud), screen sharing, and data (contacts, notes, Firefox bookmarks) sharing & synchronization via CouchDB.

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.

Rationale

User stories

Assumptions

Design

File Sharing & Synchronization

Packages:

  • icontool
  • ubuntuone-client
  • ubuntuone-storage-protocol

Screen Sharing

Packages:

  • ubuntuone-screensharing
  • ejabberd

Data Sharing & Synchronization

CouchDB

Packages:

  • erlang
  • couchdb
  • couchdb-bin
  • ubuntu-couchdb
  • couchdb-oauth
  • couchdb-history
  • ubuntuone-sync-ui
  • python-couchdb
  • couchdb-glib
  • dbus-couchdb
  • python-couchdb-records-api
  • dbus-couchdb-records-api

Contacts

Packages:

  • python-contacts-api
  • dbus-contacts-api
  • gtk-contacts-picker
  • evolution-couchdb
  • akonadi-couchdb
  • gwibber-couchdb

Bookmarks (Firefox)

Packages:

  • firefox-bookmarks-couchdb

Notes (Tomboy)

Packages:

  • tomboy-couchdb

Misc

Packages:

  • python-oauth
  • configglue

File

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.

Unresolved issues

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.


CategorySpec

DesktopTeam/Specs/Karmic/IntegratingWithUbuntuOne (last edited 2009-07-15 13:54:04 by joshuahoover)