From owner-freebsd-hackers Mon Mar 22 19:27:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 0051814DA7 for ; Mon, 22 Mar 1999 19:27:23 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 17514 invoked by uid 1001); 23 Mar 1999 03:27:09 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990322212038.A1038@Denninger.Net> Date: Mon, 22 Mar 1999 22:27:09 -0500 (EST) X-Face: *0^4Iw) To: Karl Denninger Subject: Re: NFS - Will it ever be fixed? Cc: "Jordan K. Hubbard" , Kevin Day , hasty@rah.star-gate.com, dm@globalserve.net, hackers@FreeBSD.ORG, Matthew Dillon , Chuck Robey Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Mar-99 Karl Denninger wrote: > On Mon, Mar 22, 1999 at 07:17:07PM -0800, Matthew Dillon wrote: >> :3) I personally think that $25,000 would very easily be raised, >> :especially when companies using FreeBSD can make targeted donations >> :towards a goal that they would very clearly benefit from (nfs). I think >> :the amount that could be gathered in, say, one month will probably >> :surprise everyone (I'm not trying to hold you to $25,000 here, because I >> :think that might well be too small a guess). >> : >> :4) This wouldn't even have to be completely restricted to nfs, but it >> :would have to be restricted to a very small, well defined problem set, >> :of general interest. The funds collected would have to be funnelled >> :into a fund whose goals are not general, but specific to this effort. >> >> It isn't quite so easy. It's one thing to raise money to hire >> a programmer familiar enough with the code to be able to fix the >> problems. *Finding* that programmer is a whole different deal, and >> if you make a mistake that's $25K down the drain. >> >> -Matt > > Sure it is Matt. > > Contingent contract, payable only on final delivery of the fixes. > > No fix, no pay, and put a timeline on the job. > > Someone who knows the code well enough to be able to commit to doing this > should also be willing to take that gig. Its a short-term consulting > contract anyway - why not do it this way? > > I've done this kind of work before. If I know that I can deliver the > goodies then agreeing to those kind of terms doesn't bother me at all. > > One thing that absolutely will do is keep the yahoos from knocking at the > door on this one. I've seen enough people that can BS their way into a position, that know quite a bit about what their talking about and turn out to make a mess out of things you don't discover for months, if not years later. If I'd seen it only once, I wouldn't be commenting about it here. Unfortunately I've seen it dozens of times, and every single one of them has been brought on by this same 'rose colored glasses' view of the situation at hand. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message