From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Gentoo calendar for tracking Gentoo events
Date: Thu, 11 Mar 2010 00:32:10 +0100 [thread overview]
Message-ID: <1268263931.3377.1.camel@keitaro.perronet.esiee.net> (raw)
In-Reply-To: <4B982596.2080606@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Le mercredi 10 mars 2010 à 18:04 -0500, Richard Freeman a écrit :
> On 03/10/2010 04:42 PM, Duncan wrote:
> > So a gmail account is now considered mandatory for Gentoo devs, at least
> > if they want calendar access?
> >
> > What about those who might think that Google knows enough about them with
> > search and the web crawling and database correlation Google does, and
> > whatever ad serving might leak thru, and object to having a gmail account
> > on principle?
> >
>
> Honestly, Google calendar works well enough that I'm not sure that I
> like the idea of re-inventing the wheel. Maybe if somebody designed
> some kind of open calendar access protocol that was comparable.
>
> If you don't like Google tracking all that you do, create a gmail
> account and don't use it for ANYTHING but Google Calendar. That will
> greatly limit the amount of database correlation they can do.
>
> If somebody has a suggestion for a reasonable multi-user calendaring
> infrastructure that has reasonably close feature parity and isn't a bear
> to maintain I'm sure it would be considered.
that's called caldav. There's at least one opensource server that is
working decently well with evolution although it's in php.
--
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-10 23:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 12:45 [gentoo-dev] Gentoo calendar for tracking Gentoo events Mike Frysinger
2010-03-10 12:56 ` Alex Alexander
2010-03-10 13:18 ` Mike Frysinger
2010-03-10 13:30 ` Alex Alexander
2010-03-10 13:31 ` Dror Levin
2010-03-10 19:21 ` Roy Bamford
2010-03-10 21:42 ` [gentoo-dev] " Duncan
2010-03-10 23:04 ` Richard Freeman
2010-03-10 23:17 ` Duncan
2010-03-10 23:32 ` Gilles Dartiguelongue [this message]
2010-03-10 23:09 ` Mark Loeser
2010-03-10 23:27 ` Mike Frysinger
2010-03-10 23:58 ` Nirbheek Chauhan
2010-03-11 0:02 ` Gilles Dartiguelongue
2010-03-11 0:13 ` Mike Frysinger
2010-03-11 0:49 ` Robin H. Johnson
2010-03-11 5:10 ` Jeroen Roovers
2010-03-11 16:32 ` Mike Frysinger
2010-03-11 20:53 ` Alec Warner
2010-03-12 2:45 ` Richard Freeman
2010-03-12 3:59 ` Duncan
2010-08-20 22:01 ` [gentoo-dev] " Thilo Bangert
2010-08-20 22:21 ` Mike Frysinger
2010-08-21 0:22 ` Thilo Bangert
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1268263931.3377.1.camel@keitaro.perronet.esiee.net \
--to=eva@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox