linux-kernel - research questionnaire about kernel developers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 26 May 2009 16:37:29 -0700
From:	Philip Guo <pg@...stanford.edu>
To:	linux-kernel@...r.kernel.org
Subject: research questionnaire about kernel developers

SUMMARY: This is a request to provide insights on 11 quantitative
findings about kernel developers to assist a grad student's research
project.  It will take around 10 to 20 minutes to respond.

---

INTRODUCTION: I am performing an empirical study on the roles of
developers in the Linux kernel project.  I have run some quantitative
analyses on Git data, which resulted in 11 distinct findings (shown
below).  I would like your help in interpreting the significance of
each, in order to strengthen my research paper.  I can send you the
raw data if necessary.

I would appreciate it if you could fill out this questionnaire
(as much as you have time for) and send it as an email reply to me.
Thanks again to everyone who responded to a similar questionnaire I
sent last year.

Philip Guo
Stanford University

---

FINDINGS: Please state why you think each is true (or not) based upon
your own experiences, intuitions, opinions, or personal anecdotes.

I will use the term 'prolific developers' to refer collectively to the
50 people who have written the most Linux kernel patches (1% of ~5,000
total developers).  I will refer to all others as 'normal developers'.

1. Prolific developers write larger patches than normal developers
(with each patch modifying more lines and files)

2. Prolific developers focus more on files that have more patches

3. Normal developers write relatively more patches that add new
features (when compared with prolific developers)

4. Normal developers write relatively more bugfix patches

5. Prolific developers write relatively more refactoring and code
clean-up patches (when compared with normal developers)

6. Prolific developers write relatively more patches that revert
changes made in previous patches

7. Developers who are new to Linux write patches and have other people
commit them to Git, but as they gain more experience writing patches,
they begin to also do commits

8. As time progresses, normal developers are writing more and more
patches (when compared with prolific developers)

9. As time progresses, the numbers of patch writers and committers
both increase, but the number of patch writers grows faster than the
number of committers

10. As time progresses, fewer patches are being committed by the same
developer who wrote the patch

11. As time progresses, it's taking longer to get a patch committed
after it's first written
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/