public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Gentoo calendar for tracking Gentoo events
Date: Wed, 10 Mar 2010 23:17:55 +0000 (UTC)	[thread overview]
Message-ID: <pan.2010.03.10.23.17.54@cox.net> (raw)
In-Reply-To: 4B982596.2080606@gentoo.org

Richard Freeman posted on Wed, 10 Mar 2010 18:04:54 -0500 as excerpted:

> 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.

I guess that's two separate objections.  One is simply to the /assumption/ 
that /everyone/ (well, all Gentoo devs interested in calendar activities, 
at least) has or at least doesn't object to getting a gmail account.  I 
suppose that's corrected to some degree by the posting itself, but it's an 
assumption that really shouldn't be taken lightly, IMO.

The other is to google /requiring/ a gmail account in the first place, but 
of course, gentoo really doesn't have much to do with that, except to 
possibly refuse to use the tools so made available (gratis), which could 
be argued should be done, but is it worth it in practice?  I don't know.

The first one is what really hit me here tho.  Why the assumption?  If 
it'd have been made explicit that this was something some might have an 
issue with and they'd simply need to choose, it wouldn't have been so bad 
as the issue would have been recognized.  So it was the simple assumption 
I found most offensive, and as I said, my post corrected that to some 
degree, so...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2010-03-10 23:18 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 [this message]
2010-03-10 23:32     ` Gilles Dartiguelongue
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=pan.2010.03.10.23.17.54@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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