meetings/irc: opensync-20090128.log

20:14 -!- dgollub changed the topic of #opensync to: OpenSync IRC project meeting | please not support questions during the meeting....
20:15 < dgollub> ok lets start  ..
20:15 < dgollub> who is present?
20:15  * dgollub present
20:15 < dgollub>    1. Action Items from previous Meetings
20:15 < dgollub>           * AI dgollub: create trivial tickets for unported unittests
20:15 < dgollub>           * AI dgollub: run some query/script to reassign all
20:15 < dgollub>             non-OpenSync?-tickets - to clean up OpenSync? 0.40 milestone
20:15 < dgollub>             statics
20:16 < dgollub> all those are completed
20:16 < dgollub> i also wrote a mail regarding the ticket reassining
20:17 < dgollub> reg. the unported unittests... i'm only aware of two:   sync-error and multisync
20:18 < dgollub> i check the code coverage right now to see if it's really just those two
20:18 < dgollub> btw. anyone knows who owns the "rincewind" continous build host?
20:20 < Savago> nope.
20:20 -!- badcel [n=marcel@e177089161.adsl.alicedsl.de] has joined #opensync
20:20 < dgollub> the coverage results are bit strange
20:20 < dgollub> (of this particular host)
20:22 < dgollub> just fired up another code-coverage testrun
20:22 < dgollub>    2. OpenSync 0.39 release
20:22 < dgollub>           * what needs to be done to get 0.39 out?
20:22 < dgollub>           * how can we get things done very fast for 0.39?
20:23 < dgollub> maybe we the reassiging of the OpenSync 0.40 milestones it's now easier to make sure that in 0.40 is nothing which needs to be part of 0.39
20:24 < dgollub> the mixed-objtype syncing is still not completed :(
20:24 < dgollub> i got stuck with some problem - i need to document that in the ticket
20:24 < Savago> I have one question: only after 0.40 the API will be stabilized?
20:25 < dgollub> yes .. but we try this for 0.39 already - so in theory it will be already forzen for 0.39
20:25 < Savago> Its kind of a bitch having to fix the google-data plugin each 2-3 days because its broken...
20:25 < dgollub> but  there is the very last chacne to fix really critical stuff with 0.40 .. but this must be really ciritical
20:25 < dgollub> i know .. thats a problem .. this should be not appen once we left the 0.3x cycle
20:26 < Savago> And concerning the possibility of having a UI. What is missing in the API to make it possible?
20:26 < dgollub> stablizing things is not easy if you don't know the code and don't know how much stuff is uncomplete
20:27 < dgollub> afaik there is nothing missing to make an UI .. it's more or less the same problem with the stable api like you have with the plugin
20:27 < dgollub> in fact .. henrik is with blueZync quite active in hacking an UI
20:27 < dgollub> i guess all other UI develoeprs just wait for 0.40
20:29 < Savago> Ok, so right now the API has ways to extract config data from plugins, right?
20:29 < Savago> Without the need to parse the XML config files, I mean.
20:29 < dgollub> correct
20:29 < dgollub> OSyncPluginConfig is the interface you're looking for
20:34 < dgollub> what about #884?
20:34 < dgollub> http://opensync.org/ticket/884
20:34 < dgollub> Savago: do you think we can postpone this for 0.40?
20:35 < dgollub> Savago: btw. what was the result of the 2nd patch?
20:35 < Savago> It didn't apply to trunk.
20:36 < dgollub> ah i see... ok i'll prepare a new version .. could you state this in the bug .. otherwise i'll forget this
20:37 < Savago> done.
20:39 < dgollub> thanks
20:40 < Savago> Concerning the postpone, that depends. When are you planning to release 0.39?
20:40 < dgollub> ASAP
20:41 < Savago> Well, I guess then that it got to be postponed to 0.40. :-D
20:42 -!- sejerpz [n=andrea@87.18.70.146] has joined #opensync
20:44 < dgollub> Savago: does your plugin work without that change?
20:44 < Savago> Fast sync is not possible.
20:45 < Savago> It would have to do slowsync always i.e. dump the whole list of contacts/events.
20:45 < dgollub> well we can still fix this before  0.40 .. but postpone it for the 0.39 milestone
20:45 < dgollub> are you fine with this
20:45 < dgollub> i guess there is no API change required
20:46 < Savago> I'm cool.
20:46 < dgollub> cool
20:47 < dgollub> ok i'll reassign the milestone
20:50 < dgollub> ok - done
20:50 -!- steve___ [n=steve___@unaffiliated/steve/x-19302814903] has quit [SendQ exceeded]
20:50 < dgollub> i wonder if the testcases bugs  should block 0.39 .. i would say it's ok to block 0.40 - but not  0.39
20:50 < dgollub> with regard to:
20:50 < dgollub> * how can we get things done very fast for 0.39?
20:50 < Savago> hehehehe... with more people?
20:50 < dgollub> - move open testcase tickets to 0.40 milestone
20:50 < dgollub> - more people! ;)
20:51 < dgollub> - reassign _all_ non-API tickets to 0.40 milestone an dmove API-ticket 0.39 and fix them ASAP
20:51 < Savago> I'm somewhat worried that opensync is in a chick-egg situation: no enough users to get more developers, no enough developers to get it ready for users.
20:51 -!- steve___ [n=steve___@unaffiliated/steve/x-19302814903] has joined #opensync
20:51 < Savago> chick/chicken
20:52 < dgollub> - unassigned all "dgollub" OpenSync-core  tickets to "" so it's clear which tickets or open for volunteers
20:52 < dgollub> Savago: fully agree
20:52 < dgollub> so may current idea is .. just get the stable API - fix the worst bugs .. and release 0.40
20:53 -!- steve___ [n=steve___@unaffiliated/steve/x-19302814903] has quit [Client Quit]
20:53 < dgollub> anyhting else?
20:54 < dgollub> yeah again - just a reminder we just focus on contact-syncing for 0.40
20:54 < Savago> Yep, contact data in general is more important for people (i.e. when upgrading cellphone, this is the first thing to transfer to newer device).
20:55 < dgollub> true
20:55 < dgollub> i wonder if we should merge the timeout branch...
20:56 < dgollub> need to ask graham about this... at least more and more of his task list seemed to be completed
20:56 < dgollub> need to give it a try.. if it passeds the testsuite i'm completely fine with that
21:00 < dgollub> arg .. got interrupted by work .. sorry
21:01 < dgollub> but yeha  ... i'll mention  those points on the minutes .. i hope we get some feedback and all/most people agree and we get 0.39 really really really soon released
21:01 < dgollub> so you don't have to hunt from one plugin port to the next plugin port
21:03 < dgollub>    3. Next IRC Meeting
21:03 < dgollub>           * Next Meeting?
21:03 < dgollub>           * Who is taking Minutes/Backup?
21:04 < Savago> I can take the Minutes if the meeting !=9AM@UTC
21:04 < dgollub> ok cool
21:04 < dgollub> we did this last time.. to assign minutes for  the next bi-weekly one
21:04 < dgollub> Next Minuts (in two weeks): Savago / Backup: dgollub
21:04 < dgollub> Next Meeting (next week): 20090205T090000Z
21:05 < dgollub> Next Meeting (next in two-week): 20090211T190000Z
21:05 < dgollub> Minutes (next week): bricks / backup: dgollub
21:05 < dgollub> Meeting close
21:05 < dgollub> d