Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Issuses posed by code reuse
- Date: Thu, 24 May 2012 17:41:16 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] Issuses posed by code reuse
- References: <CACvCDgbWZ4_7kUmgfTP0BryM0TzSq9qs5+grryENLTZoq0SOYA@mail.gmail.com> <877gwaq94a.fsf@uwakimon.sk.tsukuba.ac.jp> <20120523135005.b86b3d05748df8785622015f@kinali.ch>
Attila Kinali writes: > But then how do you get those drive by contributors to actually > contribute without redoing all those patches yourself? You mostly don't. So what? In my experience, the median drive-by contributor is a net negative contributor (ie, value of added function < cost of added bugs). If they won't push their patch through the process, the odds on it sucking go way up (for several reasons). Also, I cheat. I *do* redo some patches. When the contribution justifies it (I've split patches of 250,000 lines into coherent chunks). > Unfortunately, most SMBs (and big companies too!) do not have any processes > for managing code. It's written, it works, it's ok, next project. The point is not what "most companies" do, though. (If most companies did it right, he wouldn't have written a book about it!)
- References:
- [tlug] Issuses posed by code reuse
- From: Nguyễn Vũ Hưng
- [tlug] Issuses posed by code reuse
- From: Stephen J. Turnbull
- Re: [tlug] Issuses posed by code reuse
- From: Attila Kinali
Home | Main Index | Thread Index
- Prev by Date: [tlug] Success
- Next by Date: [tlug] Late greeting
- Previous by thread: Re: [tlug] Issuses posed by code reuse
- Next by thread: Re: [tlug] Issuses posed by code reuse
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links