public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Gentoo calendar for tracking Gentoo events
Date: Wed, 10 Mar 2010 19:13:38 -0500	[thread overview]
Message-ID: <201003101913.38617.vapier@gentoo.org> (raw)
In-Reply-To: <1268265739.29606.1.camel@keitaro.perronet.esiee.net>

[-- Attachment #1: Type: Text/Plain, Size: 1468 bytes --]

On Wednesday 10 March 2010 19:02:19 Gilles Dartiguelongue wrote:
> Le jeudi 11 mars 2010 à 05:28 +0530, Nirbheek Chauhan a écrit :
> > On Thu, Mar 11, 2010 at 3:12 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> > > So a gmail account is now considered mandatory for Gentoo devs, at
> > > least if they want calendar access?
> > 
> > Write 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?
> > 
> > If some gentoo dev actually has this problem, they should speak up and
> > we'll discuss it then.
> 
> I have a problem with using google resources out of lazyness (nothing
> from what I read indicates the opposite) to setup and/or ask infra what
> can be done to solve this need.

infra is already tasked enough without having to tackle such a trivial 
resource need.  google calendar is working today and exports all of its stuff 
via a variety of formats for people to important into their own calendaring 
system.

there are plenty of devs who dont have a problem signing in to use google 
calendar which means it should be trivial for you to find someone to add an 
event if you so desire.  or to use a standard invite format and e-mail it to 
someone who simply adds it to the calendar via the gmail interface.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-03-11  0:13 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
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 [this message]
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=201003101913.38617.vapier@gentoo.org \
    --to=vapier@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