Re: [Opensync-users] testing and documenting 0.4X

[Quentin D. <que...@gm...>]

Hello Emanoil,

I am happy to read your email. Me too, I am a recently jump-in contributor who 
tries to make things move on. According to me, the most important plugin 
missing to get opensync back on trac is the Akonadi plugin. If you are a KDE 
user, you will value this plugin more than anything else.

There had been a try, some time ago, but it has then been stopped because of 
the constant change in the opensync API. Now that the API is stable, you could 
try to pick it up:
http://websvn.kde.org/trunk/KDE/kdepim/runtime/opensync/ ...or you start from 
scratch! ;)

Chris Frey recently write a plugin porting howto for the latest svn, I put it 
online:
http://www.opensync.org/wiki/devel/pluginPortingGuide-0.40

I suppose that you know where to find the Akonadi API documentation, but if 
you need guys to help out I can give you some contacts.

If you prefer to start with something else, Chris will tell you to continue to 
port the broken plugins.
On my side I am hacking on kitchensync and its libqopensync, but more on that 
later.

Kind regards and thanks,
Quentin

On Wednesday 18 August 2010 22:38:20 Emanoil Kotsev wrote:
> --- On Tue, 8/17/10, Chris Frey <cd...@fo...> wrote:
> > From: Chris Frey <cd...@fo...>
> > Subject: Re: [Opensync-users] Fwd: Google plugin for opensync
> > To: "Quentin Denis" <que...@gm...>
> > Cc: ope...@li..., eha...@ra...,
> > ope...@li... Date: Tuesday, August 17, 2010,
> > 4:44 AM
> > On Sat, Aug 14, 2010 at 10:04:51AM
> > 
> > +0200, Quentin Denis wrote:
> > > I have followed the discussion "SCM changes"; but I
> > 
> > prefer to reply in this
> > 
> > > thread since my contribution to the topic is not of a
> > 
> > valuable experience.
> > 
> > > All I notice is that you have a serious API and/vs
> > 
> > Plugin problem, probably
> > 
> > > also source of all wilting on contributor's side.
> > 
> > Probably true.  But there's some resistance, and it is
> > not critical
> > to a 0.40 release.  I can hack around it.
> > 
> > Here is what I think is needed for a 0.40 release:
> > 
> > 1) Developer documentation on how to compile the library,
> > osynctool, and
> >     all plugins... perhaps with helper
> > scripts to automate this.
> >     I am willing to share my setup details,
> > if you want to document
> >     this.  Currently I have opensync,
> > osynctool, evolution2,
> >     barry-sync, file-sync, google-calendar,
> > vformat, and xmlformat
> >     setup to compile very regularly. 
> > More is better, but I'm currently
> >     working on google-calendar.
> > 
> >     A lot of work was done recently on
> > ldap-sync, so I'm suspecting
> >     that ldap support is good, but I haven't
> > had a chance to test it yet.
> 
> You are addressing many questions.I'm personally _very_ disappointed that
> syncing with linux is still not possible at least for me. I am thinking of
> testing opensync (compile from source) and I need only three plugins kde,
> gnome and syncm (basically for a nokia phone)
> 
> I'm very experienced in coding, documenting and QA-ing (testing) as I am
> doing this on professional basis, so I'm willing to get somehow this
> working and possibly share my experience.
> 
> What I understood from this e-mail is that 0.40 is pretty ready for use. Is
> it? May be I could focus on the kde part. It's really annoying that there
> is no way to sync my phones. Where do I start best? I've looked around the
> project and started reading the whitepaper. As far as I see it is
> targeting kde 4. Is it true or I can try compiling svn code on kde 3.5?
> 
> Don't understand me wrong. I recognize the complexity of the issue and have
> a respect from your work, but since recently syncml is being widely used
> and google is also a big player I'm wondering how are the priorities set.
> 
> kind regards and thanks in advance