From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Features and documentation
Date: Thu, 29 Nov 2007 18:06:16 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.11.29.18.06.15@cox.net> (raw)
In-Reply-To: 20071129053854.GD11249@supernova
Donnie Berkholz <dberkholz@gentoo.org> posted
20071129053854.GD11249@supernova, excerpted below, on Wed, 28 Nov 2007
21:38:54 -0800:
> In fact, I believe exactly the opposite. What we want to create are
> basic philosophies to guide us. Nailing down a million tiny details is
> what makes things not fun, and what makes them impossible to learn.
> We're not trying to write a specification here, we're trying to come up
> with a set of guidelines that people could actually learn and remember.
OK, so you are deliberately going for the "big brush strokes" general
guideline approach, and don't /want/ the policy getting into details. I
can respect that and will need to go back and reread the discussion to
date with that in mind.
Meanwhile, you still sidestepped the other question. Maybe it's getting
too detailed also, but if so, directly saying so to that point would be
nice, and if you just missed it, maybe this'll bring it to point:
Something must have motivated you to present this now. What was it, or
to put it a different way, how would have things been different in your
view had this policy been in effect? Point to other examples as well if
you believe they'll help clarify the effect you intend this policy to
have.
(BTW, I'm mailing you directly related to this as well.)
--
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
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-29 18:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 19:21 [gentoo-dev] [RFC] Features and documentation Donnie Berkholz
2007-11-27 19:25 ` Ciaran McCreesh
2007-11-27 19:36 ` Donnie Berkholz
2007-11-27 19:41 ` Ciaran McCreesh
2007-11-27 19:31 ` Doug Klima
2007-11-28 3:10 ` Alec Warner
2007-11-28 6:56 ` Rémi Cardona
2007-11-28 18:12 ` Zhang Le
2007-11-28 21:15 ` Donnie Berkholz
2007-11-29 0:43 ` Alec Warner
2007-11-29 1:01 ` Donnie Berkholz
2007-11-29 2:25 ` Alec Warner
2007-11-29 8:58 ` [gentoo-dev] " Christian Faulhammer
2007-11-29 13:57 ` [gentoo-dev] " Santiago M. Mola
2007-11-29 14:47 ` Doug Klima
2007-11-28 11:40 ` Marijn Schouten (hkBst)
2007-11-28 12:38 ` [gentoo-dev] " Duncan
2007-11-28 21:14 ` Donnie Berkholz
2007-11-28 21:33 ` Ciaran McCreesh
2007-11-29 0:29 ` Donnie Berkholz
2007-11-29 5:04 ` Duncan
2007-11-29 5:38 ` Donnie Berkholz
2007-11-29 18:06 ` Duncan [this message]
2007-11-29 19:29 ` Santiago M. Mola
2007-11-30 17:50 ` Duncan
2007-11-30 10:42 ` Steve Long
2007-11-30 17:42 ` Duncan
2007-11-28 19:02 ` Christian Faulhammer
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.2007.11.29.18.06.15@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