wiki:meetings/irc/agenda
Last modified 3 years ago

Agenda of the next OpenSync IRC meeting

Time: 2009-01-28T19:00:00Z (Wednesday)

  1. Action Items from previous Meetings
    • AI dgollub: create trivial tickets for unported unittests
    • AI dgollub: run some query/script to reassign all non-OpenSync?-tickets - to clean up OpenSync? 0.40 milestone statics
  2. OpenSync 0.39 relesae
    • what needs to be done to get 0.39 out?
    • how can we get things faster done for 0.39?
  3. Next IRC Meeting

Time: 2009-01-22T09:00:00Z (Thursday)

  1. Action Items from previous Meetings
    • AI dgollub: assemble list of terms. to use for developer API documentation #1047
    • AI dgollub: introduce example-plugin using static-capabilities #1048
    • AI dgollub: document each plugin function - which bits of information can be set/reported at each point - entry point documentation #1049
    • AI dgollub: doing engine hacking alread, do documentation once hacking is done #932
    • AI dgollub: create proposal for new OSyncDB interface #1050
    • AI dgollub: write initial mail about this topic on opensync-devel@ to discuss implementation details, and if this is useful at all
  2. User vs. Developer documentation (from (last, last) last meeting)
    • terminology of target audience
      • OpenSync core developers
      • Plugin Developer (Format & Connectors)
      • Frontend/Server? Developer
      • "Beta"-Tester (includes Alpha-Tester)
    • what is of interested for the Developer?
    • what is of interested for the User?
    • what to document at all?
      • OpenSync API? (Plugin & Frontend/Server? API)
      • usage of osynctool/msynctool?
      • plugin configuration?
      • "Should Suse document Apache? I don't think so."
  3. Porting to different platforms
    • which priority have porting issues?
  4. Testsuite status
    • unported unittests
    • disabled testcases
  5. OpenSync 0.39 relesae
    • what needs to be done to get 0.39 out?
    • file tickets and assign to 0.39 milestone
  6. Next IRC Meeting

Time: 2009-01-14T19:00:00Z (Wednesday)

  1. Action Items from previous Meetings
    • AI dgollub: assemble list of terms. to use for developer API documentation
    • AI dgollub: introduce example-plugin using static-capabilities
    • AI dgollub: document each plugin function - which bits of information can be set/reported at each point - entry point documentation
    • AI dgollub: doing engine hacking alread, do documentation once hacking is done
    • AI dgollub: create proposal for new OSyncDB interface
    • AI bricks: make osynctool synchronisation (multiply-)summary more intuitive (after dgollub has created a ticket ;-) )
    • AI tuju: screen bugs (maybe ask fm for help) and reassign xmlformat and vformat to their own milestones
  2. User vs. Developer documentation (from (last) last meeting)
    • terminology of target audience
      • OpenSync core developers
      • Plugin Developer (Format & Connectors)
      • Frontend/Server? Developer
      • "Beta"-Tester (includes Alpha-Tester)
    • what is of interested for the Developer?
    • what is of interested for the User?
    • what to document at all?
      • OpenSync API? (Plugin & Frontend/Server? API)
      • usage of osynctool/msynctool?
      • plugin configuration?
      • "Should Suse document Apache? I don't think so."
  3. FOSDEM 2009
    • anyone planning to attend FOSDEM?
  4. XMLFormat independent OSyncCapabilities interface
    • What needs to be done to make merging/demerging protocol/device specific?
  5. Q & A format plugins
  6. Next IRC Meeting

Time: 2009-01-08T09:00:00Z (Thursday)

  1. Action Items from previous Meetings
    • AI dgollub: assemble list of terms. to use for developer API documentation
    • AI dgollub: introduce example-plugin using static-capabilities
    • AI dgollub: document each plugin function - which bits of information can be set/reported at each point - entry point documentation
    • AI dgollub: doing engine hacking alread, do documentation once hacking is done
    • AI ChrisH: offload bricks by moving doxygen annotation of "version" and "plugin" modules to header file (no function renaming!)
    • AI bricks, dgollub: introduce merger/demerge format-plugin functions - make merging independent of xmlformat
    • AI kaarposoft tries to look into splitting static plugin information out of the members plugin configuration.
  2. User vs. Developer documentation (from last meeting)
    • terminology of target audience
      • OpenSync core developers
      • Plugin Developer (Format & Connectors)
      • Frontend/Server? Developer
      • "Beta"-Tester (includes Alpha-Tester)
    • what is of interested for the Developer?
    • what is of interested for the User?
    • what to document at all?
      • OpenSync API? (Plugin & Frontend/Server? API)
      • usage of osynctool/msynctool?
      • plugin configuration?
      • "Should Suse document Apache? I don't think so."
  3. Further API breakage before 0.40
    • Database interface
    • Hashtable interface
      • no file-path parameter
    • Drop of osync_plugin_get_config_path()
    • Multiply-Summary Callback
  4. Define use of osync_assert() and osync_return{val,}_if_fail()
    • osync_return_error{_val,}_if_fail() is required
  5. XMLFormat core-tree dropout
    • Delay xmlformat-$pim scheam freeze?
  6. OpenSync 0.40 release without plugins?
    • meet user exception by not shipping "critical" plugins?
      • vformat
      • xmlformat-plugin
    • file-sync and syncml ... most frequently asked
      • vformat with disabled xmlformat-converters by default?
      • perfect for initial dry runs.
      • no possibility to sync kdepim/evo with syncml

Time: 2008-12-30 14:00 UTC (Tuesday)

  1. Action Items from previous Meetings
    • AI dgollub: assemble list of terms. to use for developer API documentation
    • AI dgollub: introduce example-plugin using static-capabilities
    • AI dgollub: add capabilities chapter as requested by gcobb
    • AI dgollub: document each plugin function - which bits of information can be set/reported at each point - entry point documentation
  1. Doxygen / API
    • Status
    • Any trivial work left to give away?
  2. Bug/Ticket? Status
    • Bugs against milestone 0.39 and 0.40 doesn't reflect roadmap defined guidelines
      • e.g. lots of bugs with severity normal assigned to milestone 0.39
    • New hot bugs?
    • XMLFormat and vformat?
  3. Splitting XMLFormat-plugin out of OpenSync?
    • introduce format plugin merger/demerge function pointers
    • drop "internalFormat" from Engine
  4. Capabilities & Merger testing
    • Request for real-life testing of capabilities and merger
    • Generating ~/.opensync/groupX/Y/capabilities.xml by hand
    • Check for data-loss (on slow-sync)
    • Check for duplicate (on slow-sync)
    • Check for conflicts (on slow-sync)
  5. Plugin Configurations
    • Static / Dynamic configuration
    • Resource configuration
    • Documentation
    • Advanced Options
    • Option description (i18n)
    • Changes for 0.40?
    • Who takes care about this?
  6. User vs. Developer documentation
    • terminology of target audience
      • OpenSync core developers
      • Plugin Developer (Format & Connectors)
      • Frontend/Server? Developer
      • "Beta"-Tester (includes Alpha-Tester)
    • what is of interested for the Developer?
    • what is of interested for the User?
    • what to document at all?
      • OpenSync API? (Plugin & Frontend/Server? API)
      • usage of osynctool/msynctool?
      • plugin configuration?
      • "Should Suse document Apache? I don't think so."
  7. Next IRC Meeting
    • Next IRC Meeting
    • Who takes minutes/backup?

Time: 2008-12-23 14:00 UTC (Tuesday)

  1. Action Items from previous Meetings
    • AI dgollub: assemble list of terms. to use for developer API documentation
    • AI dgollub: introduce example-plugin using static-capabilities
    • AI dgollub: add capabilities chapter as requested by gcobb
    • AI all-plugin-developers: send-in the hardest implementation steps/highest OpenSync? barriers when you started with OpenSync?
  2. Documentation (Doxygen / API / Whitepaper)
    • Status of Doxygen API
  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?
  4. Next IRC Meeting

Time: 2008-12-17 19:00 UTC (Wednesday)

  1. Action Items from previous Meetings
    • AI fm: evaluate setup for "user-stories" depending on infra. decision made later and mail suggestion to opensync-devel@ for further comments
    • AI Savago: draft "user-stories" guideline for "users" and for the "board" which should rate those user-stories
    • AI dgollub: try  http://trac-hacks.org/ticket/771
    • AI ChrisH: help bricks moving doxygen API docu to header files
    • AI Savago: draft new/more detailed "CODE DOCUMENTATION" chapter for trunk/CODING and send it to opensync-devel@ for feedback
  2. Infrastructure
    • CDash mail notification
    • New Server location
  3. Doxygen / API
    • Status
  4. How to track /trunk changes?
    • e.g. archive.db needs to get flushed
    • e.g. plugin configuration XSD changed
    • Suggestion 1: Wiki-Page-Logfile with brief summary and things todo for testers/developers to get /trunk working again
    • Suggestion 2: short mails to opensync-devel@
  5. Capabilities / Discovery in Plugins
    • Lots of testing done completely without capabilities
      • high-load
      • lots of invalid bugs
      • duplicates
    • Lack of example implementation
    • Lack of documentation
  6. Documentation / Whitepaper
    • missing chapters
    • discovery/capabilities chapter
  7. Next IRC Meeting
    • ...

Time: 2008-12-11 09:00 UTC (Thursday)

  • Action Items from previous Meetings
    • AI dgollub: find OpenSync-Doxygen Maintainer
    • AI bricks: move API documentation to headers
    • AI bricks: porting frontend/consumer API examples to 0.40 API
    • AI dgollub: introduce simple & advanced plugin example (simple example: without hashtable, ...)
  • Infrastructure
    • libwbxml/libsyncml
    • sf.net/freedesktop.org
    • Armin Bauer registered parts
    • scaling (trac, high load because of announcements)
    • robustness
    • work load of project admins
  • Doxygen API documentation
    • status
    • kudos
    • introduction of Doxygen API Guidelines
    • Doxygen API Section/Chapter? for Plugins by instrumenting plugin code? && How?

  • Testsuite Status
    • monitoring of functional/performance regression
    • how to deal with random-failing tests
    • how to deal with uncompleted (not ported) testcases
    • renaming of unittests

  • OpenSync 0.40 API clean up (trivial tasks to give a way)
    • following API clean ups are proposals and look for volunteers to provide patches
    • signed/unsigned issues
      • lots of function have int osync_xyz_num_xy(...) and OSyncXyz *osync_xyz_nth_xy(OSyncYyy *, int nth) which need to get changed to used unsigned int. internally most of them use OSyncList or GList - nth and length interface of those lists are signed.
        • int osync_xyz_num_xy(...) -> unsigned int osync_xyz_num_xy()
        • OSyncYyy *osync_xyz_nth_xy(OSyncZzz *, int nth) -> OSyncYyy *osync_xyz_nth_xy(OSyncZzz *, usigned int nth)
      • clean up use of usigned intand size_t (less trivial)  http://www.ibm.com/developerworks/library/l-port64.html
    • list implementations
      • Some "objects" provide a list like interface - provide consistent interface for all list-like implemention
        • osync_xyz_add_yx/osync_xyz_insert_yx/osync_xyz_append_yx
        • osync_yxz_remove_yx / osync_yxz_delete_yx
        • osync_yxz_length_yx / osync_yxz_size_yx
    • Use of glib memory pool
      • everything allocated by a osync_try_malloc0() needs to get freed by osync_free()
    • modules/objects without reference-counting
      • drop osync_xyz_free()
      • introduce osync_xyz_ref() and osync_xyz_unref()

  • Bug priorities
    • top 5 show stoppers
      • symbol mix up
      • objtype mixing (e.g. contact <-> data doesn't work)
      • ... yours ...