Bug#988429: RFP: elpa-org-caldav -- Caldav sync for Emacs Orgmode

[Martin <debacle@debian.org>]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-emacsen@lists.debian.org

* Package name    : elpa-org-caldav
  Version         : git master
  Upstream Author : David Engster <deng@randomsample.de>
* URL             : https://github.com/dengste/org-caldav
* License         : GPL-3+
  Programming Lang: Emacs-Lisp
  Description     : Caldav sync for Emacs Orgmode

from https://github.com/dengste/org-caldav/blob/master/README.md:

CalDAV servers:

* **Owncloud** and **Nextcloud**: Regularly tested.

* **Google Calendar**: Should work, but you need to register an
application with the Google Developer Console for OAuth2
authentication (see below), because Google explicitly forbids to put
client id/secrets into open source software (see
https://developers.google.com/terms, section 4b, paragraph 1). Instead
of doing that though, I'd rather suggest you choose another service
provider.

* **Radicale** and **Baikal**: Should work. If you get problems with
'Digest' authentication, switch back to 'Basic' (make sure to use
https, though!). If you get asked for password repeatedly, put it in
.authinfo file (see below).

* **SOGo** and **Kolab**: Reported to be working
    (https://kolabnow.com/clients/emacs)

**IMPORTANT**: Before using this code, please make sure you have backups
of your precious Org files. Also, I strongly suggest to create a new,
empty calendar on your server for using this package.

**ALSO IMPORTANT**: When using this package, possibly all Org entries
will get an UID property (see doc-string of org-icalendar-store-UID
for further details). If you don't want this, then *do not use this
package*; there is just no way around that. It is the only reliable
way to uniquely identify Org entries.