Conduit Meeting Agenda and Background

Outstanding Issues For Discussion Prior To 0.3.1

Core

  • Mappings DB patch
    • JC: Haven't been able to break it yet, but haven't achieved 100% coverage.. that is soul destroying as even with 3s delays all over i'm still hitting intermittent I/O issues!!
  • Mappings behaviour
    • Sometimes weird if you set up a conduit for the 2nd time and you don't clear the mappings db. It can confuse the sync logic into thinking that i've just deleted the contents of one dp, and it will try to delete the other side

Tomboy

Most of getting this flawless is going to be working with upstream.

  • Formatting is not preserved. (See #440562)
  • Not all data is preserved
    • (JC) Discussed a little with boyd. I was pushing for a Set/Get Note XML. Currently we only get ContentXML, which doesn't contain tags. If other XML is stored outside of ContentXML then that also isn't synchronized. A method to get/set the entire XML seemed the most future proof option.
  • Doesn't auto-start
  • Looks like Tomboy is doing its mtime dance a little differently (see here) and from the log message we might be able to move the mtime checks back out of put(...)

Network Sync

  • Only tested with Note objects.
  • Definitely won't sync files - need to pickle the file data stream (and possibly meta-data) into the File object
  • All objects are going to be pulled over the network until 0.5, as without the get_added() / get_modified() / get_deleted() / stateless conduit changes there doesn't seem to be a way to do the mtime dance without being free to call get(..)

iPod

  • Everything seems OK with the new dp's active

Gmail stuff

  • JC: Improved Gmail contacts but there isn't really a GUID for a gmail contact. Not sure that DP is safe, even though it's one i'd like working.

Up to Conduit 0.4

  • Merging the picasaweb dp (should we use the python-gdata stuff)
  • Rearranging the order of the dps
    • Files
    • Photos
    • Etc

Conduit 0.5

Core

  • (Unless i've been dopey and overlooked something) For 0.5 we need to be able to create a mappings db out of two dp's that are pre-populated. Right now one DP has to be naked to avoid duplication hell
  • Conflicts need to be further sub classified. Sometimes when I just make a change on one side it is treated as a conflict. Either it shouldn't be or it should be treated differently to the change on both sides (or deleted on one side but changed on other) type of conflicts. The first kind i don't really want going to the conflict UI, but the 2nd time I would.
  • The status of the new canvas-mvc branch
    • Goals
      • DPs and Conduits do not inherit from goocanvas
      • Make a headless conduit a reality
      • Enable some bling in the canvas by drawing custom items for dps and connectors
    • Hard Things TODO
      • use-child added instead of dataprovider-added?
      • Unbreaking all the pending stuff will be the hard thing here. I want to have the DpCanvasItem show a different case if the DpCanvasItem.model is None, and move all the special case code out of Canvas

Any Other Business

  • Set up milestone for 0.5?