Linus Torvalds didn't think this one up. He stole it in pure Dilbert-fashion! I worked with guys many, many, years ago that said basically the same thing. "The
| This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
| |||||||||||||||||||||
| Please place new discussions at the bottom of the talk page. |
| This is the talk page for discussing improvements to the Linus's law article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Linus Torvalds didn't think this one up. He stole it in pure Dilbert-fashion! I worked with guys many, many, years ago that said basically the same thing. "The only bug free software is that code written one line at a time by a committee of experts all sitting in an auditorium facing a giant marker board" ...or something to that effect! This whole article is typical trivial factoid of no use to anyone.
Shouldn't "Linus's Law" be "Linus' Law" ? —Preceding unsigned comment added by 64.3.1.144 (talk • contribs) 00:37, 4 June 2004
This article is about the law of linus torvads and how it affects software development .. please donot post Non NPOV . Leningrad
Isn't it interesting that the folks who got it wrong here --- Linus' --- are defensive and mean-spirited? Meanwhile, the folks who got it right --- Linus's --- are humble in tone or simply cite manuals of grammar? -- —Preceding unsigned comment added by 128.8.178.228 (talk • contribs) 15:55, 3 November 2010 (edit) (undo)
| This page contains material that is considered humorous. Such material is not meant to be taken seriously. |
Is this derived from what Linus said? Or is this "ocular effect" older than Linus? Either way, I thought it was worth sticking in this article. --DavidCary 17:06, 5 December 2005 (UTC)
For future reference, since the term "ocular effect" (as something conceptually similar to Linus' Law) is not yet popular enough, I will leave this link describing it. Nathan J. Yoder 08:52, 20 March 2007 (UTC)
The rebuttal of the pointed-out criticisms was removed by Njyoder with this edit. I don't believe the way the article is now is NPOV, though. If criticism is presented, the other side should have a chance as well.
I have made an effort to revive the rebuttal, in a way which I hope will be more acceptable to everyone. Feel free to improve it, but I don't think it should be flat out removed. Capi 05:13, 21 January 2006 (UTC)
Don't most open wikis (including Wikipedia) use this law as a basis? Should we mention this? - Kookykman|(t)e
Many eyes fallacy should be either merged into, or linked from, the Criticism section of the accompanying article.
--Jerzy•t 16:32, 6 February 2007 (UTC)
This para is awkwardly phrased - I suspect it was written by the Italian guy whose webpage it links to. Don't know enough to fix it.--Shtove 20:36, 6 February 2007 (UTC)
I think it is important to note that Linus's Law was a response to Brooks law as the difference between the Cathedral and Bazaar models of OSS development, if not a philosophy for overcoming brooks law.
Also, something that has changed since the adoption of Brook's law and Linus's law is the stress for the necessity in open source projects for conforming to coding standards (meaning code that should do the same thing should look the same across programmers, despite the fact this is NOT done by nature, or hardly simple). That, and the stress for "extreme" code documentation. Many large projects that adopt a bazaar model, specifically Mozilla, frequently reject code for poorly standardized programming technique in addition to poorly documented code.
This "standardization" reduces the effects of brooks law by keeping OSS developers "up-to-date" with projects in general without needing to know specifics of a particular project (a major cause for initial communications overhead).
This is the foundation for Linus's Law to have its desired affect. Without that premise, it is merely an ideology.
Hopefully the above can be used to correct some of the many problems mentioned above in the criticism section.
199.80.154.88 19:06, 26 October 2007 (UTC)
Do we need to add a section every time Torvalds makes a joke on a mailing list about Linus's Law number n, or do we have to demonstrate some kind of notability here? Marnanel (talk) 02:30, 28 April 2008 (UTC)
I removed the following on the basis:
—Preceding unsigned comment added by Blablablob (talk • contribs)
Located specific pages in the sources cited. I've revised the last paragraph to support the cited authors' position, which agnostically supports one element of the "law": more source code review is good. This unfortunately left the claim "simply declaring that they do not personally believe the law is true" without a citation to support it. Help? --Lexein (talk) 01:36, 25 December 2010 (UTC)
You & the readers are welcome. I'm not entirely happy with how I improved the formatting of that citation in https://en.wikipedia.org/w/index.php?title=Linus%27s_Law&oldid=620811982 - but it is a lot better than it was. The "original" is just the abstract and bibliographic data visible without login. Giving the archive version first link gets around that. What I ended up doing, works well enough for the readers, is much better than what was there, and saved doing a custom in bare markup. — Lentower (talk) 20:22, 11 August 2014 (UTC)
{{cite conference|conference=Int. Conf. on Collaboration Technologies and Systems (CTS) | location=Philadelphia, PA |conferenceurl=http://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=5875054 |first1=Jing |last1=Wang |first2=J.M. | last2=Carroll |url=http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5928673&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5928673 |title=Behind Linus's law: A preliminary analysis of open source software peer review practices in Mozilla and Python |doi=10.1109/CTS.2011.5928673 |pages=117-124 |publisher=IEEE Xplore Digital Library |date=2011-05-27 |accessdate=2014-08-11 |others=[http://www.personal.psu.edu/students/j/z/jzw143/docs/CTS-wang.pdf Web version] }} [1]
References
- ^ Wang, Jing; Carroll, J.M. (2011-05-27). Behind Linus's law: A preliminary analysis of open source software peer review practices in Mozilla and Python. Int. Conf. on Collaboration Technologies and Systems (CTS). Web version. Philadelphia, PA: IEEE Xplore Digital Library. pp. 117–124. doi:10.1109/CTS.2011.5928673. Retrieved 2014-08-11.
{{cite conference}}: External link in(help); Unknown parameter|conferenceurl=and|others=|conferenceurl=ignored (|conference-url=suggested) (help)
There's a spelling mistake in the article... the title. If you use the spellchecker, it says the right spelling is "Linus' NOT linus's 1.129.97.25 (talk) 05:59, 9 May 2016 (UTC)
I think "research has indicated" are weak words to use in the first paragraph, but I don't know the correct way to notate it on the main page. — Preceding unsigned comment added by 74.110.101.144 (talk) 04:23, 18 October 2016 (UTC)
"the persistence of the Heartbleed security bug in a critical piece of code for two years has been considered as a refutation of Raymond's dictum". I think it should be called a principle, rule, hypothesis, postulate or else, other than law (in comparison to the laws of physics or the laws passed by a legislature). On the other hand, intuitively, it looks like the Linus' Law (as Smuckola(talk) correctly points out) is a fairly general principle, considering the number of free and open source software available. — Preceding unsigned comment added by LoneStar123 (talk • contribs) 17:34, 7 November 2016 (UTC)
References
There is another law in the preface of the book The Hacker Ethic and the Spirit of the Information Age, that is about hackers motivations, can it be noted here somehow?
El Hoy (talk) 18:22, 24 January 2018 (UTC)
I'm adding bellow an support to the validity of Linus's law based on academic research. Since I'm part of this research, I write it here first to see that it is written in objective way. I'll be happy to receive feedback.
Empirical support to the validity of Linus’s law was obtained by comparing popular and unpopular project of the same organization. Organizations like Google and Facebook are known for their quality standards. Popular projects are projects with in the top 5% number of stars (7,481 stars or more). The bug identification was measured using the commit probability, ratio of commits detected to fixing bug. The analysis showed (Section 4.2.2) that the popular projects had more bug fixing ratio (e.g., Google’s popular projects had 27% higher bug fix rate than Google’s less popular projects). Since it is unlikely that Google lowered its quality standard in it most popular projects, this is an indication of increased bug detection efficiency in popular projects.
"My favorite part of the "many eyes" argument is how few bugs were found by the two eyes of Eric (the originator of the statement). All the many eyes are apparently attached to a lot of hands that type lots of words about many eyes, and never actually audit code." -Theo de Raadt on ESR's "Linus's Law"
https://groups.google.com/g/fa.openbsd.tech/c/gypClO4qTgM/m/UzcgS_iYn1IJ
>We build this stuff by trusting each other as friends, and that is done on an international level. If anything, the layers and volume of trust involved in software development should decrease trust. Oh right, let's hear some of that "many eyes" crap again. My favorite part of the "many eyes" argument is how few bugs were found by the two eyes of Eric (the originator of the statement). All the many eyes are apparently attached to a lot of hands that type lots of words about many eyes, and never actually audit code. — Preceding unsigned comment added by Xardox (talk • contribs) 06:01, 17 February 2022 (UTC)
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.