emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Google calendar sync - what is recommended?
Date: Tue, 09 Apr 2013 20:23:20 +0200	[thread overview]
Message-ID: <87k3obk1gn.fsf@pank.iue.private> (raw)
In-Reply-To: 87k3obznhv.fsf@ucl.ac.uk

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> We are in a state of flux.  For quite a while, I used a two way
> upload/download approach based on icalendar export from org to Google
> and an awk script to convert Google calendar information into org.  See
> http://orgmode.org/worg/org-tutorials/org-google-sync.html
> This is not a synchronisation approach.
> However, more recently, I moved to org-caldav for syncing.  There is a
> link to this package from that web page as well (at the end).  This
> works really nicely.
> The problem is that Google has decided to no longer allow caldav access
> to their Calendar system from sometime later this year, requiring people
> to access the data in the calendar via the REST API.

I'm not sure Google is the solution. . . 

Since we discussed this last I have found a couple of nice calDAV

  - Red Hat Open Shift FreeShifter: it can be used for e.g. OwnCloud
    or some other CalDav calendar (it can install OwnCloud itself).
    I use it for Tiny Tiny Rss and OwnCloud.

  - owndrive.com also offers free OwnCloud hosting. 

If I have time at some point I'll experiment with it, but so far I
have still be unable to make org-caldav work. . . 


Vote for proprietary math!

  reply	other threads:[~2013-04-09 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 15:11 Google calendar sync - what is recommended? Rainer M. Krug
2013-04-09 16:18 ` Eric S Fraga
2013-04-09 18:23   ` Rasmus [this message]
2013-04-10  7:14   ` Rainer M. Krug
2013-04-09 16:36 ` Sebastien Vauban
2013-04-10  7:17   ` Rainer M. Krug
2013-04-09 21:56 ` Torsten Wagner
2013-04-10  7:23   ` Rainer M. Krug
2013-04-10  8:11     ` Fabrice Popineau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k3obk1gn.fsf@pank.iue.private \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).