On 18/08/2010 14:42, Patrick Ohly wrote: > Hello! > > You may see some technical discussions around Buteo, the sync framework > and solution in MeeGo, here on this list soon. > > Because this has not been very visible before, a short introduction is > due. Buteo [1] is the solution originally developed by Nokia for > Harmattan. Later it was made open source and adopted as core component > for sync in MeeGo, as announced by Sunil at OSCON [2]. Some more > information about it can be found in my LinuxCon 2010 talk [3], which > also describes SyncEvolution [4] (for historic reasons and because of a > scope that went beyond MeeGo). > > Note that there is a desire to have a separate mailing list for Buteo. > Not all developers follow meego-dev and finding relevant mails in the > archive can be hard. I'm posting here because the guideline is to > discuss development of MeeGo core components on meego-dev to avoid > fragmentation, and because there is no dedicated list yet. meego-sdk > seems less suitable, because Buteo is not exposed to users of the SDK > (it is a platform component, but not part of the MeeGo API). Suggestions > how to continue are welcome... In the meantime, please always use group > reply, mail people directly in addition to CCing meego-dev, and include > "Buteo" in the subject. > > I'll leave it to the other developers to introduce themselves, if they > wish to do so. My own involvement with sync goes back to spare time open > source work and Moblin, which used SyncEvolution for sync, a project > that I had started in 2005. In MeeGo, I currently act as a contact point > for the Buteo integration and maintain SyncEvolution as long as it is > needed by the MeeGo Netbook UX. I also keep an eye on other PIM > components and do some related development on Handset UX.
Out of curiosity, why a new project instead of reusing SyncEvolution (and adding the missing features?) In the wiki page, one can see: > * Device to device synchronization of PIM data (Contacts and Calendar for > now) based on SyncML > * Device to cloud synchronization of PIM data (ovi.com, Scheduleworld.com > etc.) based on SyncML > * Synchronization of media content to PC based on MTP > * Device to PC synchronization (currently only OviSuite, but this requires > contract with OviSuite to support a particular device) Why no “device to PC” using SyncML over bluetooth? It's quite convenient, especially since OviSuite isn't usable for a lot of people and since “device to device” seems already possible I guess it's just a special case with “device is a PC”. (and I do hope that not just one calendar will be syncable, as it's the case on N900/Fremantle) Cheers, -- Yves-Alexis _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
