From owner-freebsd-current Wed Mar 4 16:08:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28939 for freebsd-current-outgoing; Wed, 4 Mar 1998 16:08:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28821 for ; Wed, 4 Mar 1998 16:07:58 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA16962; Wed, 4 Mar 1998 17:07:48 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA13519; Wed, 4 Mar 1998 17:07:45 -0700 Date: Wed, 4 Mar 1998 17:07:45 -0700 Message-Id: <199803050007.RAA13519@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: jak@cetlink.net (John Kelly) Cc: Brian Beattie , current@FreeBSD.ORG Subject: Re: Donations. In-Reply-To: <3500e925.41883882@mail.cetlink.net> References: <3500e925.41883882@mail.cetlink.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I would agree, and in any case, an entity with a large chunck of money > >and a specific feature in mind would be better off funding the effort > >directly. > > That causes fragmentation and duplication of efforts. Collective > unity is better. Back that up with facts, or even explanations, please? I see no such fragmentation or duplication of effort that commercial entities would cause that's any different than what happens currently with mostly volunteer projects. People have (and will continue) the ability and desire to do *anything* they want, including doing the same project that someone else is doing. Commercial and/or volunteer, that's not going to change. Your straw-man argument has no merit. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message