[Opensync-devel] Work on trunk (getting things done)

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

taking part at the KDE PIM meeting was quite a good motivation to
restart working on OpenSync and to write some mails on the list. It
isn't good that the communication stopped at the last month again. First
I would like to say that OpenSync is still not dead and that's Daniels
opinion too. Because of my new job I am going to participate in porting
KDE PIM (especially akonadi) to mobile platforms. Therefore I am really
sure that there will be an OpenSync plugin for akonadi in the future ;-)
The KDE PIM guys haven't decided to use any other sync solution (e.g.
SyncEvolution) yet. So OpenSync still has a chance to be THE sync
solution on KDE desktops (and also on mobiles).

But I would like to discuss how we as the opensync community can speed
up development and which things/bugs of the current development cycle
are important. The current issues can be found at
http://opensync.org/query?status=assigned&status=new&status=reopened&group=status&milestone=OpenSync+0.40
See the most important issues fixes asap would be a big step forward but
I completely lost the overview which features are important and have to
be fixes to get the plugins back on track. I guess e.g. that the syncml
plugin doesn't work without fixing the guid mapping bug
http://opensync.org/ticket/1105 Which bugs have also to be fixed to get
an opensync version that is usable? What's the current status of the
capabilities? I have in mind that it does only work for one objtype but
I am not sure.

It would also be great if we can collect some opinions why we lost so
much people again and again and how to improve that. I do have an
opinion and also some reasons about that but I really don't want to see
that there is no discussion on the list and in the irc if Daniel and me
can't spend time to write code.

regards
Bjoern