Re: [Opensync-users] Fwd: Google plugin for opensync

[Chris F. <cd...@fo...>]

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.


2) Port all plugins.  In addition to the ones listed above, I would add the
	following as important plugins to port:

	kdepim
	mozilla / thunderbird / sunbird (probably just needs testing of
		the bluezync project)
	syncml

	What others are people interested in?


3) I'm not familiar with the defects that must be fixed in 0.39 before 0.40
	can be released, so I'd guess that if all the above plugins work
	for people, then we're quite ready for 0.40.  I'd hesitate to
	release 0.40 before then, because people will expect solid API
	stability in 0.40, and that would be foolish to publish before
	the plugins have been tested by regular folks.

	One part that should get cleaned up is the group of failed tests
	in the opensync library.  I don't fully understand all of them,
	but some look like simple directory / path issues.  I could use
	some help on weeding out the serious from the simple failures.



I posted a plugin porting document in a previous email.  Quentin, would
you like to put that on the wiki?  If anyone wants to jump in and port
a plugin, I'd be happy to help answer library questions to the best of
my knowledge.  Just post to the mailing list.

Once the plugins are working, we should release a set of 0.39.1 tarballs
to the public, and let people test them for a week or so.  If all is
well, release 0.40.


> - give yourself and the users DEADLINES!!!, publish them on the roadmap.
> Users want to know release dates, or they get discouraged!

Working on google-calendar has taken much longer than I thought it would,
so deadlines would just frustrate me. :-)

I'd rather have a clear list of what needs to be done for 0.40.  I'm not
sure that exists, except as a pile of issues in the tracker.  There are
a lot of items such as "Public API 0.40 review of opensync/archive"
which, in my opinion is another way of saying "port all plugins and
make them work." :-)  If the plugins work, the API is as good as it
needs to be for 0.40.  We shouldn't be stingy with version numbers.
Release early and often.


> That's not even the beginning, I currently have no time and will start only
> in one week to work on the wiki page, i.e. homepage. I will fresh it up, but
> maybe I will require some admin rights (my username is "denisq"). For
> example, the search function is broken, let me fix it, let me bring some
> bigger changes to, give me access to the sources.

I'm not an admin, so if you need more rights, Daniel will have to make
the adjustments.


> If you have a google account, you will see that gmail is now featuring
> "Tasks". I don't know if Adenilson already implemented it, but it is not one
> of the most important features right now. We'll come back to that one later,
> Contact and Calendar is far more important.

Yeah, I see tasks now.  It is not implemented in libgcal yet, AFAIK.


> Nice, it will make me and others happy. ...even if it is only a fraction of
> happiness compared to the apparition of an Akonadi plugin! ;)

Maybe I should add that plugin to the list too, but I know so little
about Akonadi.  I could use a serious education on it.

- Chris