On 3/8/11 7:30 AM, Timothy Murphy wrote:
> hansbkk AT gmail DOT com wrote:
>
>> if a user takes the
>> attitude that a program "should have" well-written documentation
>> designed for non-technical users to understand, and any program that
>> doesn't is somehow deficient in his eyes, then perhaps he would be
>> better served as a paying customer of a company he then has the right
>> to complain to.
>
> I completely disagree.
> Any program offered to the public should be properly documented.
> This has nothing to do with open source.

The source is always the ultimate documentation.  If you have that you can 
always find out what the program does and how.  But, I think the issue here is 
how much a program that uses other programs as components needs to duplicate 
their documentation.  You are probably going to need to know how to use ssh to 
use backuppc, but is the backuppc documentation the right place for that?

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/