Bug 55916

Summary:	PIM API
Product:	SyncEvolution	Reporter:	Patrick Ohly <patrick.ohly>
Component:	PIM Manager	Assignee:	SyncEvolution Community <syncevolution-issues>
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	highest	CC:	syncevolution-issues
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	52677, 55918, 55923, 55924, 55925, 56396, 56428, 56436, 57209, 60482, 62515, 62516, 64140
Bug Blocks:	56141

Description Patrick Ohly 2012-10-12 13:07:51 UTC

The API implements in-vehicle infotainment (IVI) use cases around
contacts:
- cache address books from peers (primarily phones connected via Bluetooth)
  in local address books
- provide a unified address book that combines a configurable (and changing)
  subset of the local address books
- fast phone number lookup
- browsing and searching in the unified address book

Tasks that are expected to be done by the user of this API:
- identify peers and their capabilities
- decide how and when peer data should be cached
- define which data goes into the unified address book

In other words, the API provides the mechanisms and the user the
policy.

This is a meta-issue that tracks the initial definition and development of that API in SyncEvolution. The corresponding public discussion is here (please use gmane's "reply" feature to join the mail thread):
http://comments.gmane.org/gmane.comp.mobile.syncevolution/4009

The source is in the "pim" branch of http://cgit.freedesktop.org/SyncEvolution/syncevolution

Comment 1 GitLab Migration User 2018-10-13 12:43:40 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/111.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.