News

Information about current problems and the ongoing development are posted as part of the SyncEvolution blog [1].

Bugs, Patches and Feature Requests

SyncEvolution issues are tracked in the freedesktop.org bug tracker. They used to be part of meego.com (referred to as BMC in the change log); that changed in August 2012, to make SyncEvolution truly cross-desktop and cross-project.

You can review open issues [2] and report new issues [3]. All issues are also archived on gmane.org [4]. If you don't have one already, you can create an account for the tracker on bugs.freedesktop.org [5]. To reply to such issues, use the tracker or the main mailing list.

Improvements and fixes as patches are welcome in the tracker. Everything currently assigned to "syncevolution-issues" (sometimes shown as "SyncEvolution Community") is not actively worked on by anyone.

If you run into any issues with SyncEvolution during synchronization, try to determine as best you can whether the issue was caused by SyncEvolution, the SyncML library, or the server that you talk to. Issues in a server should be reported using its issue tracker. Issues with libsynthesis [6], the SyncML implementation used since 0.9 beta 1, can be filed here [6].

Be sure to always include the following information:

• version of SyncEvolution
• version of OS and Evolution (if applicable)
• server and its version (if known)
• client log if appropriate (.html file in ~/.cache/syncevolution, see syncevolution --print-sessions <config name>), server log if appropriate and available. If they contain confidential data, then you can mail them to the Intel sync team [7], but please use the issue tracker ID as part of the subject
• a description of what you do, what you expect to see, and what you get instead. "How to Report Bugs Effectively" [8] explains why that helps resolve problems more quickly.

Mailing Lists

SyncEvolution Mailing List

You may subscribe to the SyncEvolution mailing list [9] or browse the archives [10].

Posting without being subscribed is no longer possible because of the high level of spam mails. Now mails from unsubscribed email addresses will get rejected automatically.

If you are looking for a forum, consider reading, replying and posting via the gmane.org [11] interface to the SyncEvolution list archives. That way it is possible to read the mailing list archive and subscribe to it in a news reader. Posting to the list via gmane.org is possible via a web browser and news reader.

For sensitive issues send email to the closed development team list [7].

Synthesis Mailing List

For questions about SyncML, use the Synthesis mailing list [12]. It s also on gmane.org [13].

For those who prefer the mail-archive.com service, both lists are also available there: http://www.mail-archive.com/syncevolution@moblin.org/ [14] (before 2009-07-16) http://www.mail-archive.com/syncevolution@syncevolution.org/ [15] (after 2009-07-16) http://www.mail-archive.com/os-libsynthesis@synthesis.ch/ [16]

Cross-posting between mailing lists is acceptable when used moderately for issues related to both SyncEvolution and libsynthesis, like developing new features in libsynthesis which are used in SyncEvolution or discussing bugs that affect both.

Evolution Mailing List

Questions related to Evolution or evolution-data-server can be asked on the Evolution users list [17].

Supporting SyncEvolution

SyncEvolution is free software, available free of charge and you have the freedom of modifying and distributing it. If you are a software developer, the best way to support SyncEvolution is to port it to other backends and systems. Get in touch, if you want to hear more about this.

If you are a (hopefully happy) user of SyncEvolution, you can make your appreciation or suggestions for improvements known in several ways. Although SyncEvolution is free, this does not mean that its development did not cost much effort. Quite the opposite, a lot of time went into it.

• Send a postcard to the author (see main page [18]).
• Leave comments on the author's blog [19].
• Donations are not necessary and cannot be accepted.