From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Gentoo calendar for tracking Gentoo events
Date: Fri, 12 Mar 2010 03:59:33 +0000 (UTC) [thread overview]
Message-ID: <pan.2010.03.12.03.59.32@cox.net> (raw)
In-Reply-To: b41005391003111253u609f7202l44ab0086ce82ef5b@mail.gmail.com
Alec Warner posted on Thu, 11 Mar 2010 12:53:14 -0800 as excerpted:
>> you dont need an account to "subscribe" (read/track updates). anyone
>> can do that anonymously.
>> -mike
Thanks. That wasn't clear from the original. Good to make it explicit
(as you have now several times). =:^)
> I think Duncan's point is that in the Social Contract it talks about how
> Gentoo should only rely on open source software.
Well, that, and the simple assumption that every dev had no objection to a
gmail account. If the point had been made then (as made now) that read-
only is available without, and that those without (thereby recognizing the
possibility) could ask another dev... But that was taken care of with my
original post and other followups, so it's pretty much resolved.
> The question is does
> this apply to our 'product' or does it apply to everything. Certainly
> users can continue to use Gentoo without using this calendar at all;
> however if it becomes some kind of integral part of Gentoo (which I
> doubt it will) we will have to look at switching to something else
> (which is easy given the many export formats of Google Calendar :))
>
> I am all about trying out new things and working out the details after
> the fact;so +1 to the calendar as well.
A reasonable enough way to proceed, yes. =:^)
--
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
next prev parent reply other threads:[~2010-03-12 4:00 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
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 [this message]
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.12.03.59.32@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