🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.misc.discuss
Article #72436

Returned mail: User unknown

#72436
From: Mail Delivery Subsystem
Date: Sat, 08 Feb 1992 06:14
42 lines
2721 bytes
   ----- Transcript of session follows -----
Connected to sage:
>>> RCPT To:<phil@iseng.compnews.co.uk>
<<< 550 User unknown
550 phil@iseng... User unknown

   ----- Unsent message follows -----
Received: from icdoc.UUCP by hyperion.cps.compnews.co.uk; Sat, 8 Feb 92 06:14:31 GMT
Original-Via:  uk.ac.uknet  ; 8 Feb 92 5:47 GMT
Received: from news.cis.ohio-state.edu by eros.uknet.ac.uk via EUnet 
          with SMTP (PP) id <7098-0@eros.uknet.ac.uk>;
          Sat, 8 Feb 1992 05:23:20 +0000
Received: by news.cis.ohio-state.edu (5.61-kk/5.911008) id AA22275;
          Thu, 6 Feb 92 13:47:46 -0500
Received: from USENET by news.cis.ohio-state.edu with netnews 
          for gnu-misc-discuss-mail@cis.ohio-state.edu (gnu-misc-discuss@cis.ohio-state.edu);
          contact usenet@news.cis.ohio-state.edu if you have questions.
To: gnu-misc-discuss@cis.ohio-state.edu
Date: 6 Feb 92 15:57:00 GMT
Message-Id: <6FEB199211575588@stars.gsfc.nasa.gov>
Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
From: Dave Cottingham <dc@stars.gsfc.nasa.gov>
Original-Sender: gnu-misc-discuss-request@edu.ohio-state.cis
Reply-To: dc@cobi.gsfc.nasa.gov
Subject: How to charge for supporting free software?
Original-Sender: gnu-misc-discuss-request@cis.ohio-state.edu
Sender: gnu-misc-discuss-post@cps.compnews.co.uk

I have unsuccessfully been trying to figure out exactly how this business
of supporting free software is supposed to work out.  But since there
are functioning businesses out there that do it, there is clearly an
answer.  The conventional system operates sort of like an unregulated
utility -- the people who own the code set themselved up as the only
people who maintain it, and they spread the costs of their activity
evenly over everyone who wants fixes.  The customers are encouraged to
pay for this service by the fact that they have no other option for
getting bugs fixed.  For free software, if you make the patches freely
available, how do you design your service so as to avoid having each
patch paid for entirely by the customer that asked for it?

Dave Cottingham
dc@cobi.gsfc.nasa.gov
Technical Details
Message-ID: <19256.9202080614@hyperion.cps.compnews.co.uk>
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!uk.co.COMpnews.cps!postmaster

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1025b4,ed0abb73a4974823
X-Google-Attributes: gid1025b4,public
X-Google-ArrivalTime: 1992-02-08 00:45:49 PST
Newsgroups: gnu.misc.discuss
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!uk.co.COMpnews.cps!postmaster
From: postmaster@uk.co.COMpnews.cps (Mail Delivery Subsystem)
Subject: Returned mail: User unknown
Message-ID: <19256.9202080614@hyperion.cps.compnews.co.uk>
Sender: daemon@cis.ohio-state.edu
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sat, 8 Feb 1992 06:14:40 GMT
Lines: 42