mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Amanda McPherson <amanda@amcpherson.com>
Subject: Re: [PATCH, RFC] A development process document
Date: Wed, 30 Jul 2008 12:05:48 -0600	[thread overview]
Message-ID: <20080730120548.7478917a@bike.lwn.net> (raw)
In-Reply-To: <20080730001508.9095f571.akpm@linux-foundation.org>

On Wed, 30 Jul 2008 00:15:08 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> I wonder a bit whether a ./Documentation update is the best way to
> present this.  Rather than, say,
> http://www.kernel.org/read-this.html. The latter may be easier for
> you to update, and we won't have the problem of people reading
> two-year-old versions of the document.

I think LF wants to put it up somewhere; kernel.org is certainly a
possibility too.  OTOH if it's in the kernel source, others could update it
too.  I've always really liked the way stuff in Documentation/ stays
current... 

> > +The Linux kernel, at over 6 million lines of code and 2000 active
> > +contributors,
> 
> I suspect the "2000 active developers" is a bit hypey.  Is a 0.5
> patch/annum developer "active"?

I was going with 1.0/year as a working number.  The period v2.6.22..v2.6.26
(July 8, 2007 to July 13, 2008) had 2294 distinct contributors.  About 1000
of those were a single patch.  If we say that >= 2.0 is active, then the
number goes to 1200.  I could just say "over 1000" and be happy with that,
I guess.
 
> Also: if the code is kept out-of-tree then there is a risk that
> someone else's similar feature will be merged in mainline.  

Good point, I'll add that.  Everything else you pointed out is good too,
consider it all added.  After LWN comes out, anyway.  Thanks for taking the
time to read through it all.

jon

  reply	other threads:[~2008-07-30 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 20:30 Jonathan Corbet
2008-07-30  7:15 ` Andrew Morton
2008-07-30 18:05   ` Jonathan Corbet [this message]
2008-07-30 11:09 ` Jiri Kosina
2008-07-30 16:05   ` Takashi Iwai
2008-07-30 20:56   ` Jonathan Corbet
2008-07-30 21:30     ` Roland Dreier
2008-07-30 21:38       ` Jiri Kosina
2008-07-31  6:23 ` Alex Chiang
2008-07-31 16:17   ` Jonathan Corbet
2008-07-31 17:49     ` Daniel Barkalow
2008-07-31 17:57       ` Randy.Dunlap
2008-08-01 10:35         ` Stefan Richter
2008-08-01 16:52           ` Daniel Barkalow
2008-07-31 12:22 ` Jochen Voß
2008-07-31 16:30   ` Jonathan Corbet
2008-07-31 23:45 ` Jake Edge

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=20080730120548.7478917a@bike.lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=amanda@amcpherson.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®