Menu
▾
▴
opensync-devel
|
From: Bjoern R. <bjo...@go...> - 2010-01-10 12:56:44
|
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 |
|
From: Daniel G. <go...@b1...> - 2010-01-10 13:29:17
|
On Sunday 10 January 2010 01:49:19 pm Bjoern Ricks wrote: > 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. ack [...] > 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. Yeah thats similar to me. I tried to hunt down the list which required my attention. Like the missing exported function of the osync_queue_cross_link function which broke evo2-sync and other plugins running in a seperated process. This is hopefully fixed, could someone verify that evo2-sync is working? #1190 It would be great if someone could screen which are assigned to 0.40 Milestone and reprioritize them. And try to reproduce them ... tickets which are assigend to "OpenSync" component and are plugin specific issues should get assigned to it's plugin component so we get a better overview. I start now screening those tickets which are still belong to "OpenSync" component ... but it would be nice if others which want to contribute to OpenSync, but can't contribute code, would help keeping "OpenSync 0.40" milestone clean: http://opensync.org/query?status=assigned&status=new&status=reopened&group=status&component=OpenSync&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&milestone=OpenSync+0.40 Also those who have filed tickets in the past could help: please check if your bug is still reproducible with latest trunk. And if you think your bug needs special attention please rise the priority (but don't over do this please!) > I guess e.g. that the syncml plugin doesn't work without fixing the > guid mapping bug > http://opensync.org/ticket/1105 I guess #1105 is already fixed and is a duplicate of #1161 We filed two tickets for the same problem .. but i need to go through this in more details. It would be great if Michael could help me in clarifying that this <Map> problem is already solved. > Which bugs have also to be fixed to get > an opensync version that is usable? What's the current status of the > capabilities? I'm still need to get a description done how the capsformat stuff is supposed to work. Handling of Capability Parameter is not implemented. But it's not used yet anyway ... so maybe not a blocker for 0.40 > I have in mind that it does only work for one objtype but You mean it works only for "contact"? Or do you mean something else? [...] Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner FOSS Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: Bjoern R. <bjo...@go...> - 2010-01-10 15:07:47
|
>> I have in mind that it does only work for one objtype but >> > You mean it works only for "contact"? Or do you mean something else? > [...] > yes that's what I had in mind. > Best Regards, > Daniel > > |
|
From: Daniel G. <go...@b1...> - 2010-01-10 15:10:44
|
On Sunday 10 January 2010 04:07:38 pm Bjoern Ricks wrote: > >> I have in mind that it does only work for one objtype but > >> > > > > You mean it works only for "contact"? Or do you mean something else? > > [...] > > > > yes that's what I had in mind. > The reason for that is simple: We decided to focus on contact synchronization since event synchronization would be to hard to implement in the beginning and would delay a 0.40 release even longer. Of course someone else can step up and take over the event synchronization ;) At least i focus on contact synchronization for now - once this is done i get my hands dirty on event syncing ... Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner FOSS Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: Bjoern R. <bjo...@go...> - 2010-01-10 15:35:15
|
Am 10.01.10 16:10, schrieb Daniel Gollub: > On Sunday 10 January 2010 04:07:38 pm Bjoern Ricks wrote: > >>>> I have in mind that it does only work for one objtype but >>>> >>>> >>> You mean it works only for "contact"? Or do you mean something else? >>> [...] >>> >>> >> yes that's what I had in mind. >> >> > The reason for that is simple: > We decided to focus on contact synchronization since event synchronization > would be to hard to implement in the beginning and would delay a 0.40 release > even longer. > > Of course someone else can step up and take over the event synchronization ;) > At least i focus on contact synchronization for now - once this is done i get > my hands dirty on event syncing ... > > Best Regards, > Daniel > > Sound like an good approach. Event synchronization is much more complex ... Btw. is there any reason why you aren't available in the irc for weeks? best regards Bjoern |
|
From: Daniel G. <go...@b1...> - 2010-01-10 15:51:41
|
On Sunday 10 January 2010 04:35:05 pm Bjoern Ricks wrote: > Sound like an good approach. Event synchronization is much more complex Btw. by event i actually meant "calendar" .. which includes todo and event (and (v)journal) > ... Btw. is there any reason why you aren't available in the irc for weeks? > Mostly due to private reason. And the host where my IRC client was running got doomed. I'll join as soon i finished with ticket screening. Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner FOSS Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
Thanks for helping keep SourceForge clean.
X