From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 25 07:28:10 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C9D5106566B for ; Wed, 25 Jan 2012 07:28:10 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4AA0B8FC16 for ; Wed, 25 Jan 2012 07:28:10 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 8B90556172; Wed, 25 Jan 2012 01:28:09 -0600 (CST) Date: Wed, 25 Jan 2012 01:28:09 -0600 From: Mark Linimon To: Arnaud Lacombe Message-ID: <20120125072809.GA11115@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Wed, 25 Jan 2012 13:06:34 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD has serious problems with focus, longevity, and lifecycle X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 07:28:10 -0000 > I might just be also interested to review/comment code, discuss > regressions, and architecture, for a change ;-) > Unfortunately, such threads rarely ever happen. Most of the time, the > only food provided is a really indigestible +5000/-3000 patch, where > all the thinking, architectural design and code has been done behind > closed door of a limited few committers, research lab or company. That's odd. What the src committers usually tell me, when I have my bugmeister-advocate hat on, is that they post patches and then no one comments until after they check them in, at which time they complain. This discourages them from going through this the next time. You will also note that some of the large commits say "MFp4" or "MF: ". That means that either our Perforce repository, or SVN project/ directory, were used as staging areas. It's possible to subscribe to these email messages. (Exactly how is left as an exercise for the reader; the hour is getting late.) As for the research lab/company commits, I'm sure you'd complain equally if the code that these groups develop in-house and then release when it's in some kind of stable state, instead didn't get released at all. But, of course, I'm wasting my time trying to give you reasoned arguments about why FreeBSD does one thing or another. AFAICT you're only interested in spreading FUD about what we do, how we do it, and what we say about it before, during, and afterwards. You seem to be obsessed by picking over semantics and finding shortcomings to be aggreived over. Whatever patches or review you've contributed to date, to my mind, are like the last tiny little bits of onion that are left over after one peels off all the outer layers. There may be something to it, but the effort to get down to that point is so painful that it's not worth it. tl;dr: your drama outweighs your contributions. mcl