Re: [Opensync-users] One ticket per week?

[Bjoern R. <bjo...@go...>]

> I have spent many hours compiling/configuring/troubleshooting (from a
> user's perspective) over the years with a number of mainstream phones,
> and have never been able to get reliable sync'ing across contacts, notes
> & todos.  I note that Fedora have recently attempted downgrades
> including 0.38 and 0.36, and have now reverted to 0.22 with observations
> on their devel list that plugins are unusable.
>   
That's another topic which got most developers/members of opensync very
frustrated. All 0.3x versions shouldn't have been incuded in a distro.
> My sense of the project is that howtos, configuration guides, functional
> status reports, design documentation, and functional stability have been
> of a lower priority than internal re-architectures, changes to build
> systems, new configuration formats, etc.  (Apologies if I'm off-target)
> My point is that investment in documentation and stability on a reduced
> plugin set would IMO pay-off rather quickly because it would reduce the
> perceived barrier of entry for use, testing, and development.  Folk like
> me would no longer need to reverse-engineer to figure things out, and
> you'd attract more people who aren't prepared to reverse-engineer or
> await responses on the mailing list.
>
I am not sure if you read my previous mail in this thread therefore I'll
make some comments.

First the architecture of the stable version (0.22) isn't suitable for
all needs therefore a rewrite of the engine was necessary in the past.
That decision was taken before I started to hack on opensync. The
development branch (0.3X) was intended "for developers and testers only
and may not even compile or are likely to contain severe bugs" (quote
from opensync.org). But the dev branch is coming closer to his end. The
next release 0.39 will have a stable api and will be some kind of beta
version.

Second we are aware of these problems and AGAIN we are really lacking of
developers. We know the shortcomings of this (horrible long) development
branch and the always changing api. We know that we have lost a lot of
people on this journey. But we are trying really hard to get all
remaining tickets fixed and release a new stable version. But mind that
I don't have (and I guess also Daniel hasn't) much free time to work on
opensync.

regards
Bjoern
-- 
/Bjoern Ricks