From 54adf78f057589cdfdb67d65ea7c74270c387ff0 Mon Sep 17 00:00:00 2001 From: Markus Unterwaditzer Date: Thu, 27 Feb 2014 14:29:09 +0100 Subject: [PATCH] Move issues to tracker --- README.md | 19 ++----------------- 1 file changed, 2 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index deecf48..9fe2028 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ This is work-in-progress. -A basic syncronization utility for [vdir](https://github.com/untitaker/vdir). Should be able to sync both CardDAV and CalDAV in the end. +A basic syncronization utility for [vdir](https://github.com/untitaker/vdir). +Should be able to sync both CardDAV and CalDAV in the end. ## A little bit about the code architecture @@ -14,19 +15,3 @@ One function in `vdirsyncer.sync` can then be called on two instances of implementing, the two given instances don't have to be of the same exact type. This allows us not only to syncronize a local vdir with a CalDAV server, but also syncronize two CalDAV servers or two local vdirs. - -## Rough list of things that need to be done - - implement CalDAVStorage and CardDAVStorage - - ~~While events generally have to be referenced by href, there's an example in - the [CalDAV RFC](http://www.ietf.org/rfc/rfc4791.txt) (Ctrl+F for "by UID") - on how to get events by UID. In the worst case we have to find out the href - through that every time we want to delete or update an event.~~ - *hopefully this is no longer a real concern due to the rewrite of the storage - API with commit `4b92442`. Probably it's just going to be copy-and-paste from - [khal](https://github.com/geier/khal/blob/master/khal/caldav.py#L99).* - - - finish the CLI and decide on a config format - - moar tests - - conflict resolution - - Everywhere you find TODO in the sourcecode