Article View: gnu.misc.discuss
Article #72410Re: How to charge for supporting free software?
From: Ian Lance Taylor
Date: Sat, 08 Feb 1992 01:30
Date: Sat, 08 Feb 1992 01:30
19 lines
1306 bytes
1306 bytes
dc@stars.gsfc.nasa.gov (Dave Cottingham) writes: >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? 1) Have support contracts. or 2) Why do you have to? What's wrong with having the person who needs the fix pay for it? If it really bothers them that everybody else will get the patch for free, let them hire somebody else (yes, they could do this, provided they did not distribute the result). -- Ian Taylor | ian@airs.com | First to identify quote wins free e-mail message: ``In the end, we found that the only method of communicating with our landlords, who were living in the same house with us, was to go down into Florence and send a registered express letter to them.''
Technical Details
Message-ID:
<3485@airs.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!airs!ianReferences:
<6FEB199211575588@stars.gsfc.nasa.gov>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1025b4,bdca0b6276a5ee32 X-Google-Attributes: gid1025b4,public X-Google-ArrivalTime: 1992-02-07 17:52:55 PST Path: arc1-ca.pugleaf.net!sparky!uunet!airs!ian From: ian@airs.com (Ian Lance Taylor) Newsgroups: gnu.misc.discuss Subject: Re: How to charge for supporting free software? Message-ID: <3485@airs.com> Date: 8 Feb 92 01:30:45 GMT References: <6FEB199211575588@stars.gsfc.nasa.gov> Sender: news@airs.com Lines: 19