I recognize that Open Source folks are passionate. I understand and I applaud the dedication and fierce loyalty. But for the love of all that is warm and fuzzy, could you please give it a rest? Just for a little while? There is something else that really needs some attention: proper documentation.Editorial Notice: All opinions are those of the author and not necessarily those of osnews.com
I have heard much lately about *Linux_On_The_Desktop*. I read that Linux is finally ready for the desktop. Then I read that Linux is not ready for the desktop yet, but it soon will be. I read that Linux has been ready for the desktop for years. I read that Linux is ready for a few specialized uses, but not ready for the home user. I read that Linux is so easy nowadays that anyone’s grandma can use it. I read that the high level executives in the computer industry themselves can’t cope with setting up their own computers…and then I read about a dachshund in Paducah that managed to install Gentoo unassisted and sent out three emails before his owner caught him.
And always, always, always the discussion comes back to some variation of the following question: “Why aren’t more people using this? Can’t they SEE it is inherently better than MS Windows?”
No. They can’t. And they won’t until a few things change. How can the public at large see anything at all amid this low-hanging cloud of bickering and debate? Suppose an MS Windows end user is considering a switch to Linux, or perhaps just gets curious about trying this newfangled operating system. Where is he supposed to begin? If the experts themselves can’t possibly agree on which one is best for what, how is an innocent newcomer supposed to know what to do?
In order for Open Source software to move out into the mainstream it must first become usable by the mainstream. Is this too difficult to understand? Speaking as a non-programmer end user, a refugee from the tyranny of Microsoft and a reasonably literate person, I am going to tell you something that may shock you. The ugly truth of the matter is….we don’t really care about this stuff.
We have no desire to even know which version of KDE a particular release of a particular flavor of Linux came out with. We don’t know or care which kernel version RedHat uses. We are utterly indifferent as to whether RPM or DEB is a better packaging scheme. The burning question of whether to use XFree86 4.2 or XFree86 4.3 leaves us shrugging. We don’t even care the slightest whit if our computers are using GNU/Linux or GNU/Hurd. In fact, we have no clue about what either one of them really are. The public at large is a hotbed of apathy concerning most of these arguments.
There is one thing however, that we end users do care deeply about. There is an issue that burns in our minds with a searing thirst for knowledge and understanding. There is one question that torments us by day and haunts our sleepless nights. The one question that the public at large cares about is this:
“How in the world am I supposed to make this thing work? Can I have some instructions please? MY KINGDOM for a user manual that I can understand!”
Open Source documentation is terrible. There is no kinder way to put it. Even the commercially distributed software in the Open Source world has substandard documentation. (And believe me, as a technical writer coming from the Windows world, when I tell you that the commercial industrial standards are pretty low). Only a bare handful of Open Source software packages have any documentation at all. And out of the few that do, much of it is either unfinished, inaccurate, or outdated. What counts as explanatory text among geeks would bewilder a nuclear physicist, even a sober one.
Let me pick something at random. I am not trying to make KDE look bad. I personally use KDE almost exclusively, and I love it. But the so-called “help” system….have you looked at that thing? Consider, if you don’t already know what to do, how many people would be able to figure out their solution using just the online help? Really? Just recently I saw someone pointing out how good the documentation for the GIMP is. The GIMP is one of the few packages that can justifiably claim to have user documentation. It is not easy, it is not simple, but it is usable if you keep at it. It assumes, like KDE and most other OSS, a certain minimum level of competence.
This is the key point. Almost all OSS documentation was not written for newbies. It was written by experts for the use of experts. Some of it is surprisingly good. The man pages are a nice example. You open a console, type “man (whatever)” and you get a nice, easy to read explanation. Of course, you must FIRST be aware that man exists, and then you must also be aware that to access the man pages you need to open a console, and then of course you need to be aware of the proper syntax, and naturally you must have a clear idea of exactly what you are looking for and how to spell it….but if you already have gotten that far, the man pages are very helpful.
I have heard all the excuses. Some people claim (with a straight face) that if a program is properly designed it should be self-evident and no documentation should be needed. I have heard the excuse that OSS is still very young, and time is needed to get the documentation up to speed. Problem is, Linux is over ten years old, and some of the other OSS is even older. How long does it take to get started?
Yes, I have seen the Linux Documentation Project. And I ask you, how many newbies know about it? When normal people buy a software package with which they are not familiar, the first thing they do is look inside the package for instructions. When they don’t see anything resembling documentation, how many new customers are going to be clueful enough to think about searching the net for something called Linux Documentation Project? And even if they stumble over it, how are they supposed to know what to search for?
Not every newcomer to the fold is going to be blessed with a wise and patient sensei to guide their first faltering footsteps along the Way Of The Penguin.
Truth is, most geeks hate to write. They are not good at it, and they know this, and they would rather spend a week in lockdown with 5 large cell mates than write user documentation.
I come before you to plead. I speak for the unwashed masses of non-technical end users who would dearly love to try using OSS, but have no idea HOW. I speak for the clerical staff that keeps getting their work eaten by MS Word. I speak for the accountant that has seen Peachtree lock up their system once too often. I speak for the hapless sales representative whose server just crashed, leaving him stranded 500 miles from headquarters with no way to close the sale. For all of us, I beg.
Can you stop bickering among yourselves long enough to tell us how to run this stuff? In terms we can understand? Please?
Tell you what. I will send you money. Write some usable documentation that lets me buy OSS and get productive with it, but does not require me to become a geek-in-training, and I will send you money. Lots of money. I will BUY your product. How’s that? Could you get a better offer anywhere?