"Ben Sizer" <[EMAIL PROTECTED]> writes:
>> But we can be
>> explicit if you want: How do you do that without requiring that your
>> software be given special consideration in the distaster recovery and
>> preparedness planning?
> I should state that I am not at all claiming a "one size fits all"
> policy for software development. Firstly, from a personal point of view
> I am talking about simple consumer entertainment software which is not
> mission critical or anything like it. For more important software,
> there will surely be different expectations and requirements. In my
> case, providing a free download of any lost executables or data upon
> presentation of a legitimate license key should be adequate.
In other words, you don't do that at all. My special handling for such
things - and *especially* for entertainment software, where the media
gets handled by children - is "Return that POS." Worse yet, you play
semantic games so you can claim not to be violating fair use rights in
the process.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
--
http://mail.python.org/mailman/listinfo/python-list
