Re: [Opensync-devel] Fixing the OpenSync core development BUS factor

[<he...@ka...>]

> I wonder if we are going about this the wrong way?  It is extremely
> logical to
> get the core working properly before worrying about the plugins.  But it
> doesn't seem to be working in motivating developers.
>
> I think part of the problem is that while the format plugins (in
> particular)
> are broken, no one can use the code they are working on.  I find I am more
> motivated to work on the engine if I am solving problems which allow me to
> make progress with my personal goals, and my personal usage.
>
> How about, now that the engine API is **reasonably** stable, we
> concentrate on
> getting the plugins to work.  Solve some problems like timezones,
> recurrences, conversions, etc. and get basic sync working for both
> contacts
> and events (at least).  Don't even worry about merge/demerge for the
> moment.
> That would give us something which, while not releasable to end users,
> would
> at least allow the developers to start using it in their daily lives.  The
> developers would then start to hit the remaining engine problems
> (capabilities, timeouts, IPC deadlocks, conversion paths, mapping, etc.)
> and
> would be more motivated to work on them.

I think we need to work in all areas at the same time (engine,
format-plugins, sync-plugins).
If we do not develop engine and format-plugins, the sync-plugins will not
work.
If we do not develop sync-plugins, we will not find and fix the problems
in the engine.

For one particular plugin (mozilla-sync) I can say that without
capabilities, demerger and IPC it simply does not work.

Do not forget that many of the bug reports for the engine comes from
testers and plugin developers hitting a wall, not from a general wish to
finish the loose ends in the engine in itself.

/Henrik