PTM: Take a typical Linux 'program'. When you open a software packet, you first get information about the new features, the changes made to the packet, then you get a list of parameters and last but not least a huge list of people who somehow has been in the project. Nowhere can be found a simple description about WHAT THE PACKET DOES.
Could it be possible to write RPM, man, info, www, doc and such documents so that the first 4 lines describe WHAT THE PACKET DOES. If you can't write it so that your mother-in-law understands, ask him to write it. Of course, if the packet is not meant to public domain or to be sold, you can leave the information out of your documentation. Linux is approaching a point where we could talk about a system built for end-users. Not a developers playground or pile of programs anymore. Only an year ago I got an angry feedback when I used word 'customer' while talking about a packet. The programmer seemed to have an opinion that Linux is meant for programmers, not for customers. Once we had a saying:'It's odd how many illiteral man there is writing programs'. (I know, I'm one of them). Another man told that he will read program documentation next time when he learns how to climb to a tree feet first backwards. The difference with Microsoft programs lies in that Microsoft doesn't tell the names of the programmers directly. They are wasting memory as inbuilt to the programs. - -- rl-users list. To leave, send "unsubscribe" without quotes in body of message to [EMAIL PROTECTED] Archive: http://www.mail-archive.com/[email protected]/
