From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NpUxp-0008Qr-DK for garchives@archives.gentoo.org; Wed, 10 Mar 2010 23:05:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2EA36E0D49; Wed, 10 Mar 2010 23:05:12 +0000 (UTC) Received: from vms173009pub.verizon.net (vms173009pub.verizon.net [206.46.173.9]) by pigeon.gentoo.org (Postfix) with ESMTP id A239CE0CB7 for ; Wed, 10 Mar 2010 23:05:10 +0000 (UTC) Received: from gw.thefreemanclan.net ([unknown] [96.245.54.140]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KZ3005639G79EP3@vms173009.mailsrvcs.net> for gentoo-dev@lists.gentoo.org; Wed, 10 Mar 2010 17:05:00 -0600 (CST) Received: from [192.168.0.5] (rich.homedns.org [192.168.0.5]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by gw.thefreemanclan.net (Postfix) with ESMTPS id AE68F175A216 for ; Wed, 10 Mar 2010 18:04:54 -0500 (EST) Message-id: <4B982596.2080606@gentoo.org> Date: Wed, 10 Mar 2010 18:04:54 -0500 From: Richard Freeman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100306 Thunderbird/3.0.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Gentoo calendar for tracking Gentoo events References: <201003100745.21823.vapier@gentoo.org> In-reply-to: Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7bit X-Archives-Salt: 46467723-c1ee-421e-839d-f6862e988c59 X-Archives-Hash: 553732322b592148afd278dc92c2b464 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. Rich