public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Features and documentation
Date: Wed, 28 Nov 2007 17:01:11 -0800	[thread overview]
Message-ID: <20071129010111.GB11249@supernova> (raw)
In-Reply-To: <b41005390711281643w4e579e59j55cc0c74358b72fe@mail.gmail.com>

On 16:43 Wed 28 Nov     , Alec Warner wrote:
> On 11/28/07, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > Here's my understanding of what you said: Because people will break
> > rules and violate standards, we shouldn't have any.
> >
> > Is that accurate?
> >
> 
> Kind of.
> 
> Most people follow most rules.  Most people break a subset of rules.
> 
> You are essentially adding an unreasonable (in my view) rule that I
> expect nearly everyone to break or ignore, thereby adding little or no
> value to the project as whole.  Most people care about documentation
> in the abstract sense, almost no one cares *enough* to write any ;)
> 
> Forcing people to write documentation won't get it written, people
> will continue to act like we just saw and either the rule will get
> ignored, or someone will change the rule, or people will leave because
> the rule is enforced aggressively and it has ruined the ability to
> contribute to the project.

The Linux kernel seems to still have contributors, despite its 
requirement. It seems like people decide to leave after nearly any 
change Gentoo makes these days, so I'm not even sure how much we should 
consider that unless we want to stop all development and do nothing. 
(But I guess that also would be a change, so people would quit.)

> This is why I offered to write the GLEP for Diego and Cardoe, because
> I know they are not interested in writing it themselves.  Thats why we
> have a doc-team that for some sick reason enjoy writing and
> maintaining documentation.

You've made some great points here about working with people who enjoy 
dealing with docs. What I'm saying is that we should work with these 
people before committing rather than after.

Thanks,
Donnie
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-11-29  1:04 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 [this message]
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
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=20071129010111.GB11249@supernova \
    --to=dberkholz@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