Bug 53805 - O3SIS support
Summary: O3SIS support
Status: RESOLVED MOVED
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: SyncML (show other bugs)
Version: unspecified
Hardware:
: low enhancement
Assignee: SyncEvolution Community
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-13 02:30 UTC by SyncEvolution Community
Modified: 2018-10-13 12:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Patrick Ohly 2012-08-19 18:56:45 UTC


---- Reported by jingke.zhang@intel.com 2010-04-13 02:30:30 +0000 ----

This is from http://bugzilla.moblin.org/show_bug.cgi?id=7804

   Description  From  pohly   2009-11-04 06:13:44 PST   (-) [reply]

"knipp at m-otion.com" provided information about synchronizing with the O3SIS
SyncML server. See the mailing list for details.

o3sis/config.ini:
syncURL = http://<servername>/syncml.osp

o3sis/sources/addressbook/config.ini:
uri = contacts

o3sis/sources/calendar/config.ini:
uri = calendar

o3sis/sources/memo/config.ini:
uri = notes

o3sis/sources/todo/config.ini:
uri = tasks

We should at least add a template, perhaps even do full testing. O3SIS is
located in Germany near Cologne. I already met one of the developers in
private, so we should be able to establish a contact.



--- Bug imported by patrick.ohly@gmx.de 2012-08-19 20:56 UTC  ---

This bug was previously known as _bug_ 699 at https://bugs.meego.com/show_bug.cgi?id=699

Unknown platform unknown. Setting to default platform "".
Unknown operating system unknown. Setting to default OS "".

Comment 1 GitLab Migration User 2018-10-13 12:37:38 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/libsynthesis/issues/18.


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.