meetings/irc: opensync-20081223.log

[Di Dez 23 2008] [15:04:51] Thema       dgollub setzt das Kanalthema auf "OpenSync project IRC meeting | please no bug reports or support request".
[Di Dez 23 2008] [15:05:03] <mkoller>   I'm just watching partly as I'm still @work
[Di Dez 23 2008] [15:06:10] <fm>        go ahead dgollub, i will write the minutes
[Di Dez 23 2008] [15:06:52] <dgollub>   kk
[Di Dez 23 2008] [15:07:24] <dgollub>   1. Action Items from previous Meetings
[Di Dez 23 2008] [15:07:24] <dgollub>     * AI dgollub: assemble list of terms. to use for developer API documentation
[Di Dez 23 2008] [15:07:24] <dgollub>     * AI dgollub: introduce example-plugin using static-capabilities
[Di Dez 23 2008] [15:07:24] <dgollub>     * AI dgollub: add capabilities chapter as requested by gcobb
[Di Dez 23 2008] [15:07:24] <dgollub>     * AI all-plugin-developers: send-in the hardest implementation steps/highest
[Di Dez 23 2008] [15:07:27] <dgollub>                                 OpenSync barriers when you started with OpenSync
[Di Dez 23 2008] [15:08:06] <dgollub>   i didn't managed to complete any of mys AIs
[Di Dez 23 2008] [15:08:14] <dgollub>   i'm still collecting terms...
[Di Dez 23 2008] [15:08:28] <dgollub>   the introudction of a static-capababilities plugin is still missing
[Di Dez 23 2008] [15:08:48] <dgollub>   there is not yet a capabilities chapter ... i hope to start with some of those AIs
[Di Dez 23 2008] [15:08:52] <fm>        and are we going with splitet user developer docs as discussed on the mailinglist?
[Di Dez 23 2008] [15:09:23] <dgollub>   not qutie sure yet .. this is another item i would say - lets discuss this in the Documentation item
[Di Dez 23 2008] [15:09:36] <fm>        ok
[Di Dez 23 2008] [15:10:04] <dgollub>   reg. the OpenSync barrier for plugin developers... there was some feedback i try to incoperate later
[Di Dez 23 2008] [15:10:18] <dgollub>   next topic?
[Di Dez 23 2008] [15:10:47] <fm>        ok
[Di Dez 23 2008] [15:10:50] <dgollub>   2. Documentation (Doxygen / API / Whitepaper) * Status of Doxygen API
[Di Dez 23 2008] [15:11:25] <dgollub>   bricks: anything new? i saw various commits ...
[Di Dez 23 2008] [15:11:26] Beenden     Samm hat den Server verlassen (Read error: 60 (Operation timed out)).
[Di Dez 23 2008] [15:12:20] <fm>        hm not here i am afraid
[Di Dez 23 2008] [15:12:51] <dgollub>   i see
[Di Dez 23 2008] [15:13:12] <dgollub>   ok - reg. the users/developers docs thing\
[Di Dez 23 2008] [15:13:25] <fm>        i think there was quiet some commits moving the docs in the .h files so it is beeing worked on.
[Di Dez 23 2008] [15:13:50] <dgollub>   right now there was some discussion if we should split this...
[Di Dez 23 2008] [15:14:08] <dgollub>   ... on the other hand - do we need "user" docu at all?
[Di Dez 23 2008] [15:14:44] <fm>        hm i am not really decided what we should do. for the end user I hope there will be no docs needed in the future
[Di Dez 23 2008] [15:14:57] <ianmartin> depends if you want people to use osynctool as a user
[Di Dez 23 2008] [15:15:13] <fm>        and all other people looking at os.org now probably ctrl-f and can find all terms on one page
[Di Dez 23 2008] [15:16:24] <fm>        just advanced users will look for the docu anywhere so I think having all terms on one page where you can point people to might be good
[Di Dez 23 2008] [15:17:16] <dgollub>   ianmartin: hmm osynctool is a good point...
[Di Dez 23 2008] [15:17:54] <dgollub>   afaik the most advanced knowledge you need to know if you have to configure the plugin when using osynctool
[Di Dez 23 2008] [15:17:57] <ianmartin> If it is just the glossary you are talking about then one page makes sense, could even colour entries depending on if they are relevant to users
[Di Dez 23 2008] [15:18:18] <fm>        If the page is well catogorized i think it is not too big a problem
[Di Dez 23 2008] [15:20:35] <fm>        ping
[Di Dez 23 2008] [15:20:57] <dgollub>   yes - but i wonder if we should concentrate today on user documetnation
[Di Dez 23 2008] [15:21:23] <dgollub>   i would first concentrate on developer documentation.. since the user documentation might change several times before opensync gets raelly useable for users
[Di Dez 23 2008] [15:21:48] <ianmartin> indeed, given it is still changing a lot.
[Di Dez 23 2008] [15:21:52] <dgollub>   and we should also clarfiy if there is a user documetnation beside osynctool required at all...
[Di Dez 23 2008] [15:21:53] Betreten    Samm hat den Kanal betreten (n=chatzill@129-170-195-217.cust.centrio.cz).
[Di Dez 23 2008] [15:22:03] <dgollub>   when we talk about user-documentation is this just about osynctool?
[Di Dez 23 2008] [15:22:12] <fm>        you are right the focus is for the developers right now, to get the whole think working ;)
[Di Dez 23 2008] [15:22:47] <fm>        i think it is about terms, what is a slow sync a fast sync, groups, members, peers?
[Di Dez 23 2008] [15:23:30] <dgollub>   but this is something which could be done in a user-friendly way in the GUI
[Di Dez 23 2008] [15:23:31] <ianmartin> There are several categories: core developer, user (front end developer, connector developer, format developer), user (osynctool)
[Di Dez 23 2008] [15:23:51] <dgollub>   good point
[Di Dez 23 2008] [15:24:16] <dgollub>   i would exlcude osynctool for this discussion now ... i don't want to focus on osynctool users
[Di Dez 23 2008] [15:27:13] <dgollub>   but i agree there is need documetnation for " user (front end developer, connector developer, format developer)"
[Di Dez 23 2008] [15:27:22] <dgollub>   for those we could setup "one page"
[Di Dez 23 2008] [15:27:39] <dgollub>   with terms and mark them with colours... i guess one page is easier to maintain
[Di Dez 23 2008] [15:27:53] <ianmartin> yeah, and all terms are relavent to core developer
[Di Dez 23 2008] [15:28:03] <ianmartin> so avoids any duplication
[Di Dez 23 2008] [15:28:07] <dgollub>   right
[Di Dez 23 2008] [15:28:59] <dgollub>   ok - anythong to add on this topic .. or this item?
[Di Dez 23 2008] [15:29:01] <fm>        ok to summarize: coredeveloper and other developers should get all doc on one page and seperated by color
[Di Dez 23 2008] [15:29:10] <dgollub>   fm: yep
[Di Dez 23 2008] [15:29:22] <ianmartin> re whitepaper
[Di Dez 23 2008] [15:30:12] <ianmartin> Henrik made a good point about what a plugin should or can do in each function
[Di Dez 23 2008] [15:30:45] <ianmartin> which bits of information can be set/reported at each point
[Di Dez 23 2008] [15:30:45] <dgollub>   ianmartin: yes
[Di Dez 23 2008] [15:31:19] <dgollub>   ianmartin: i have already a very brief description in the whitepaper about those functions.. but not so deatiled.. do you think this shoudl be part o fthe whitepaper or part of teh Doxygen API?
[Di Dez 23 2008] [15:32:00] <ianmartin> I think whitepaper, unless you know you can set something you dont know to go look it up in the doxygen API
[Di Dez 23 2008] [15:32:27] <dgollub>   hmm good point
[Di Dez 23 2008] [15:32:46] <ianmartin> also plugin entry points aren't in the API
[Di Dez 23 2008] [15:34:10] <ianmartin> So when writing a plugin I know when I can/should report that eg my calendar sink is readonly
[Di Dez 23 2008] [15:34:27] <dgollub>   i see
[Di Dez 23 2008] [15:36:06] <ianmartin> eg:
[Di Dez 23 2008] [15:36:12] <ianmartin> DISCOVER set sink write ability: if a sync is always readonly then this may be reported
[Di Dez 23 2008] [15:37:08] <ianmartin> CONNECT: set sink write ability: if on connection the sink is found to be readonly it may be set
[Di Dez 23 2008] [15:37:14] Verlassen   andieh_ hat den Kanal verlassen ("schÃŒssikovski").
[Di Dez 23 2008] [15:37:46] <dgollub>   AI dgollub: document each plugin fucntion - which bits of information can be set/reportead at each poing - entry point documentation
[Di Dez 23 2008] [15:38:54] <dgollub>   ianmartin: btw. how is it going with discovery implementation in evo2-sync? do you think you could help documetnt the discovery process? from plugin point of view?
[Di Dez 23 2008] [15:40:04] <ianmartin> if you could make a list of things that the plugin can set I could write some explaination
[Di Dez 23 2008] [15:40:33] <ianmartin> currently reporting contact capabilities dyanmically
[Di Dez 23 2008] [15:41:08] <dgollub>   ok ... i'll assemble a list after the meeting
[Di Dez 23 2008] [15:41:24] <ianmartin> evolution provides no way of determinting the calendar capabilities, so will have to trial and error to find what comes out given a certain input
[Di Dez 23 2008] [15:42:00] <dgollub>   ianmartin: by evolution you mean e-d-s - right?
[Di Dez 23 2008] [15:42:07] <ianmartin> yeah
[Di Dez 23 2008] [15:42:21] <dgollub>   anyway - should we continue on the next item? or anything else of 2. item?
[Di Dez 23 2008] [15:43:26] <fm>        continue
[Di Dez 23 2008] [15:43:28] <dgollub>   3. Active Tickets for 0.39 milestone * Are all active ticket for 0.39 valid? * Re-prioritize  * Anything else from 0.40 milestone which should go to 0.39?
[Di Dez 23 2008] [15:44:33] <fm>        just closed one ;)
[Di Dez 23 2008] [15:45:07] <dgollub>   we should make sure that we address urgent stuff for 0.39 .. not 0.40
[Di Dez 23 2008] [15:45:13] <fm>        how to repdroduce http://opensync.org/ticket/686 ?
[Di Dez 23 2008] [15:45:25] <fm>        i can use vconvert to convert the vevent to xml
[Di Dez 23 2008] [15:45:40] <dgollub>   right now on my list is the  mix-up of ObjTypes and the mix-up of ObjTypes in resource configurations
[Di Dez 23 2008] [15:46:05] <dgollub>   fm: i'll comment on that ticket later...
[Di Dez 23 2008] [15:46:20] <dgollub>   reg. the symbol name clashing .. this should be finally fixed with /trunk
[Di Dez 23 2008] [15:46:21] <fm>        dgollub: wouldn't it make sense to issue a warning right now if intermixing is configured. not even henrik was aware of it
[Di Dez 23 2008] [15:46:32] <fm>        none of our users know this is not working
[Di Dez 23 2008] [15:46:46] <dgollub>   there could be some crashes/backtraces which might look like a symbol clash - but those are quite easy to identify when looking closely to the backtrace...
[Di Dez 23 2008] [15:47:09] <fm>        fixing is good but just printing a warning would help people to get furhter i think
[Di Dez 23 2008] [15:47:09] <dgollub>   if there is a crash in a format plugin in a conversion function... this could be due to conversion-path detection
[Di Dez 23 2008] [15:47:50] <dgollub>   fm: warnings is not easy to implement
[Di Dez 23 2008] [15:48:16] <dgollub>   fm: you can't just blacklist data.. since  data <-> data is perfectly fine
[Di Dez 23 2008] [15:48:32] <fm>        hm
[Di Dez 23 2008] [15:49:10] <fm>        there are several schema tickets, could you get cstender to look at them?
[Di Dez 23 2008] [15:49:38] <dgollub>   i try .. not quite sure what his vaction plans are
[Di Dez 23 2008] [15:50:21] <dgollub>   but extending xmlformat schema should be qutie trivial to extend.. are there already patches pending?
[Di Dez 23 2008] [15:51:08] <fm>        no
[Di Dez 23 2008] [15:52:33] <dgollub>   anyone want to look at xmlformat schema issues?
[Di Dez 23 2008] [15:53:32] <fm>        sadly i have no time at all right now :-(
[Di Dez 23 2008] [15:54:05] <dgollub>   fm: maybe just mention that we're looking for someone handling outstadning xmlformat issues
[Di Dez 23 2008] [15:54:11] <dgollub>   ... in the minutes
[Di Dez 23 2008] [15:54:59] <dgollub>   ok - anything else?
[Di Dez 23 2008] [15:55:20] <dgollub>   any hot issues in the engine/plugin space? beside the objtype mix-up?
[Di Dez 23 2008] [15:55:27] <fm>        will do dgollub
[Di Dez 23 2008] [15:55:47] <ianmartin> convter paths
[Di Dez 23 2008] [15:55:51] <ianmartin> or the config
[Di Dez 23 2008] [15:56:04] <dgollub>   ianmartin: is conerter path and teh format config the same thing? or two seperated?
[Di Dez 23 2008] [15:56:08] <ianmartin> smae thing
[Di Dez 23 2008] [15:56:15] <dgollub>   ok
[Di Dez 23 2008] [15:56:16] <ianmartin> format config geting set as path config
[Di Dez 23 2008] [15:56:45] <dgollub>   but never made it thorugh to the conversion function - right?
[Di Dez 23 2008] [15:57:02] <ianmartin> ticket 990
[Di Dez 23 2008] [15:57:37] <ianmartin> when converting to engine internal format only the config for the internal format gets set as the path config
[Di Dez 23 2008] [15:57:57] <dgollub>   i see
[Di Dez 23 2008] [15:58:36] <dgollub>   could you change this one to milestome 0.39?
[Di Dez 23 2008] [15:58:45] <ianmartin> ok
[Di Dez 23 2008] [15:59:11] <dgollub>   anything else? otherwise we just finish the meeting with the last item
[Di Dez 23 2008] [15:59:42] <dgollub>   4. Next IRC Meeting * Next IRC Meeting? Regular date? * Who takes minutes/backup?
[Di Dez 23 2008] [15:59:43] <fm>        ok
[Di Dez 23 2008] [16:00:34] <fm>        31st?
[Di Dez 23 2008] [16:00:55] <fm>        I guess there will be not many more attendees than today ;)
[Di Dez 23 2008] [16:01:20] <fm>        maybe skip a week or 2.1.09 ?
[Di Dez 23 2008] [16:02:45] <dgollub>   what about 30th?
[Di Dez 23 2008] [16:03:07] <dgollub>   also 14:00Z?
[Di Dez 23 2008] [16:03:33] <fm>        i could try to be there ;) but might make sense to ask bellmich and cstender about their preferences ...
[Di Dez 23 2008] [16:03:56] <dgollub>   maybe both are busy with family affairs
[Di Dez 23 2008] [16:04:07] Betreten    bellmich hat den Kanal betreten (n=bellmich@82.113.106.23).
[Di Dez 23 2008] [16:04:44] <dgollub>   bellmich: right now we plan next meeting
[Di Dez 23 2008] [16:04:46] <fm>        just talking about you bellmich ;)
[Di Dez 23 2008] [16:05:13] <dgollub>   currently we discuss 2008-12-30T14:00Z
[Di Dez 23 2008] [16:06:29] <bellmich>  Next week I'm in Hamburg.
[Di Dez 23 2008] [16:07:04] <dgollub>   fm: ok then lets stay with 2008-12-30T14:00:00Z .. let's how many can attend or not
[Di Dez 23 2008] [16:08:16] <fm>        ok dgollub
[Di Dez 23 2008] [16:08:22] <bellmich>  I still think about the connect/disconnect semantics of the transport layer before I start fixing it.
[Di Dez 23 2008] [16:09:34] <dgollub>   fm: cool
[Di Dez 23 2008] [16:09:37] <dgollub>   meeting closed