This page summarizes the peers (internet services or mobile phones) that SyncEvolution can exchange data with.

Note that SyncEvolution's results could be affected indirectly by the interaction between other synchronization tools. For instance, SyncEvolution's synchronization between your PC and a web service might be affected by the synchronization between that web service and your mobile phone.

Platforms

• Linux, Evolution, KDE [1]
• Moblin and MeeGo
• Maemo 5/Nokia N900 [2]

SyncML Servers

• ScheduleWorld [3]
• Google [4]
• Funambol [5]
• Ovi.com [6]
• Synthesis [7]
• Horde [8]
• eGroupware [9]
• Memotoo [10]
• GroupOffice [11]

Others

To add another peer to these lists, such as another device or web service, please create a Wiki page [12] and contact [13] the SyncEvolution team.

To get a template for a server into SyncEvolution, please add it as described in the src/README.templates [14] file in the source code. We'll accept pretty much any template as long as it does not set the "consumerReady" flag. Templates with that flag are the ones that show up in the sync-ui, and for those we have additional requirements:

• The service should be available for normal users, if possible permanently (paid or for free). Time-limited demo servers like my.funambol.com are corner cases, marked with "Demo" in the description.
• The sync-ui binary contains localized descriptions of some services. We would need something like that for new services.
• SyncEvolution users of that service should get support from the operator. For us that means that we need a technical contact, ideally someone who has an account on http://meego.com [15] so that we can assign issues to him.
• Someone should do at least some minimal interoperability testing, ideally using "client-test".

Testing

We run regular SyncEvolution tests with real servers. If you would like us to test your server too, please provide the following:

• A description of how to configure SyncEvolution for this server
• An account on the server for the nightly testing
• Help with analyzing common errors that might come up during testing