From owner-freebsd-current Thu Oct 24 15:30:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26798 for current-outgoing; Thu, 24 Oct 1996 15:30:18 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA26788 for ; Thu, 24 Oct 1996 15:30:12 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id PAA15020; Thu, 24 Oct 1996 15:27:40 -0700 (PDT) To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org Subject: Re: Possibility? In-reply-to: Your message of "Thu, 24 Oct 1996 10:52:09 PDT." <199610241752.KAA12316@phaeton.artisoft.com> Date: Thu, 24 Oct 1996 15:27:40 -0700 Message-ID: <15018.846196060@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Why does everyone assume (incorrectly, IMO) that it is onerous to > > 1) Say what you are going to do > 2) Do what you say Did you really want an answer to these rhetorical questions? Is that also a rhetorical question? ;-) Because in a volunteer project, you invariably: 1) Say you're going to do a lot more than you can, human enthusiasms being what they are. 2) Do only some portion of these things, being somewhat encumbered by various laws of physics which state that you can't do 170 hours worth of work in a 168 hour week, even by eschewing sleep. People have done this since day one, and I see absolutely no indication that any "total quality mandate" or general love of enhanced process will defeat these two factors. When people do things for fun, and for free, consistency is not something it pays to be anal about. If I want consistent behavior out of someone, like having them show up every day between the hours of 9am and 5pm (just as *one* example), I generally have to pay them. If they're volunteers, I shouldn't be surprised if they roll in at 10:00 or 11:00 (or even sometimes not at all). Extrapolate from this example and you'll see why ISO 9000 methodologies and this project would mix about as well as water and chalk. Jordan