Hi!

Here's another summary of thing going on with SyncEvolution...

      * HOWTOs for SyncEvolution 1.0 alpha as server available
      * clarified goals and procedures for accepting outside
        contributions
      * merged first big contribution: an XMLRPC backend
      * proposed talks at FOSDEM

In following up with the SyncEvolution 1.0 alpha release, HOWTOs about
setting up syncing with a phone and as HTTP server were published:
        http://syncevolution.org/development/sync-phone
        http://syncevolution.org/development/http-server-howto

For those compiling from source, note that the server-side admin data
format has changed last Thursday. Remove
sources/*/[.internal.ini|.server.ini] when updating to start from
scratch.

m-otion.com developed an XMLRPC backend which exchanges data via a web
API. After a brief Intel-internal discussion we came up with what I hope
is a very flexible and agreeable policy for accepting contributions
either with an informal copyright waiver, a more formal license
agreement or under an open source license. For details, see:
http://syncevolution.org/development

Proposed talks for FOSDEM, both a lightning talk and in the
cross-desktop devroom. Looking forward to meeting you there, whoever you
are! :-)

The mailing lists and syncevolution.org will be taken care of by our
Chinese colleagues while the rest of us take vacations over the
holidays.

Development:
      * all: discussions around D-Bus restore API (MB #8144);
        configuring client and server (MB #7838); handling unexpected
        slow syncs (MB #2416) and recovery mode in the sync-UI
      * Yongsheng: provide information about "waiting" state via D-Bus
        API (MB #2229, needed for "spinner" in GUI); listing logs
        possible without selecting a specific peer (MB #8049), analyzed
        and reported a bug in the Memotoo server (incorrect size
        calculation for items split across messages); ZYB.com for
        contact sync is going to be supported in 1.0 (MB #2424)
      * Congwu: fixed storing of server-side admin data;
        more work on testing with Nokia 7210c, including workarounds for
        sending time stamps as UTC
      * Jussi: new settings GUI; draft for emergency view; fix for
        sync-UI problem in alpha 1 when using localization (MB# 8618)
      * Raji: workaround for exporting corrupt calendar events with
        missing timezone definition (MB #7879)
      * Patrick: more Oracle Beehive interoperability testing (and
        ensuing discussions about interpretation of the iCalendar 2.0
        standard...); fix building in non-GNOME environment (MB #8338);
        workaround for libecal bug in error situation, avoids crash (MB
        #8005); clarified file backend configuration (MB #8146); wrote
        scripts to exchange patches with gdbus and libsynthesis for
        shared files, sent patches to Marcel for merging into gdbus

Noteworthy new issues:
      * user inquiries regarding supporting the native Maemo 5 calendar
        (mailing list, MB #8511)
      * More reports about OVI.com (doesn't send email addresses). We
        are in the process of establishing contact with Nokia for
        OVI.com.
      * The Funambol server does not deal correctly with relative start
        times of alarms. They get replaced with a fixed, one-time alarm
        (MB #7806).
      * sync-UI in alpha 1 has a problem setting up new configs when
        localization is used. LC_ALL=en_US.UTF-8 should work around 
        that, fix is in master branch (MB #8618)

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to