From: Wang Chen <wangchen@cn.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de, Jonathan Corbet <corbet@lwn.net>
Subject: Who wrote 2.6.29
Date: Tue, 24 Mar 2009 11:53:43 +0800 [thread overview]
Message-ID: <49C85947.5070301@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
Cheers for the release of Linux-2.6.29.
Seems Jonathon has released statistic of 2.6.29 on LWN, although I
can't access the article now.
Maybe I should subscribe to LWN later :)
Here is my statistic, anyone without LWN subscribing can see it first
and maybe look at LWN next week.
Detail statistics are on site: http://remword.com/kps_result/
Here I'd happy to introduce two interesting graphs, which are attachments.
1. first_time_commiter.JPG
Anyone, even who has full experiences on kernel hacking, had an experience
to commit his/her first patch to kernel. It's important to know how many first
time commiters are taking part into kernel development, because it indirectly
tells us who and how many of them are joining the party to help Linux.
In this graph, we can see, in every release circle, about 200-300 "new" engineers
joined the development since "git age"(from 2.6.12-rc2)
On the other hand, one data I didn't collect is that how many engineers left
the development of kernel, but I can say "a lot of" people have left the kernel
hacking work by various reasons. Because from the statistics we know 4796
people committed patches, but in 2.6.29 circle, we have only 1180 people continue
the kernel development, although most of the key developers stayed.
2. report_review_test.JPG
"Signed-off-by" and "Acked-by" were the most important data to tell the kernel
contribution. And "Reported-by", "Reviewed-by" and "Tested-by" were not regarded
as important as they deserved. But things are changing now.
In this graph, we can see more and more "Quality Control" works, such as bug-report,
code review and testing be regarded by kernel developers.
This doesn't say that kernel developers didn't regard Quality Control work as important
before, it tells us not only "coding things" can help kernel growing, but also a
lot of other works can help kernel to be stronger.
Best Regards
Wang Chen
[-- Attachment #2: report_review_test.JPG --]
[-- Type: image/jpeg, Size: 70183 bytes --]
[-- Attachment #3: first_time_commiter.JPG --]
[-- Type: image/jpeg, Size: 41407 bytes --]
reply other threads:[~2009-03-24 3:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49C85947.5070301@cn.fujitsu.com \
--to=wangchen@cn.fujitsu.com \
--cc=corbet@lwn.net \
--cc=gregkh@suse.de \
--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