From owner-freebsd-hackers  Sun Apr 13 11:35:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA18003
          for hackers-outgoing; Sun, 13 Apr 1997 11:35:30 -0700 (PDT)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA17995;
          Sun, 13 Apr 1997 11:35:19 -0700 (PDT)
Received: from dbws.etinc.com (db@dbws.etinc.com [204.141.95.130]) by etinc.com (8.8.3/8.6.9) with SMTP id OAA23070; Sun, 13 Apr 1997 14:41:47 -0400 (EDT)
Message-Id: <3.0.32.19970413143341.00693478@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Sun, 13 Apr 1997 14:33:45 -0400
To: "John S. Dyson" <toor@dyson.iquest.net>
From: dennis <dennis@etinc.com>
Subject: Re: Commercial vendors registry
Cc: dyson@freebsd.org, terry@lambert.org, scrappy@hub.org,
        pgiffuni@fps.biblos.unal.edu.co, hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 12:14 PM 4/13/97 -0500, John S. Dyson wrote:
>> >
>> >So, my suggestion is that if a change from the current course is
wanted, and
>> >no-one is willing to donate the time for free, those that want the change
>> >can do it, or fund (or otherwise enable) the change.
>> 
>> Its really not feasible, unfortunately. The only way to do it is become a
>> BSDI, 
>> which is a serious step. Or, take a snapshot and maintain it as...say, a
>> router
>> O/S, like OpenBSD has done. 
>> 
>Well, an OpenBSD developer has likely had support to do exactly what they are
>doing in that area or has invested time for a potential product.  Many
FreeBSD
>developers are being funded and/or supported for various applications also
>(including one like that.)  Those who want changes, and are supporting
them, are
>likely getting them quickly.  One can increase the probability of change by
>contributing to FreeBSD or by funding it.
>
>Simply waiting for it to happen is not being proactive.  Changes and
>improvements will appear over time, but the priorities can be modified
>by supporting them.
>
>There are at least a couple of motivations for a particular developer to fix
>things.  First, it is an issue of pride, second it is an issue of funding.
>Really gross problems usually get fixed relatively quickly, but there are
>times where there are conflicting resource dependencies, and then it becomes
>a resource allocation issue.  We can either risk one part of the project
>for another, or we can bring more resources to bear on the various
>enhancements and problems.

The problem with funding fundamentals like networking is that some banana with
a different philosophy is likely to either undo your changes or make other
changes
that compromise it. You'd have to maintain it yourself to make it worthwhile.

Dennis