>
>
>I think there are a growing number of casual Linux users. People
>who are not into geeking for it's own sake, but know their way around a system for some other,
>usually work-related, purpose.
>
Yup. I'm the epitome of that class of Linux user -- which is why I'll
write a book for others of my ilk, then set up a Web site where,
hopefully, others can chime in -- which will lead to a second, better
edition of said book.... some or all of which will be downloadable for
free if I can swing it with the publisher.
>The trick would be getting them involved and into the 'spirit' of such
>work. Otherwise, why would the affore mentioned secretary use his/her precious evenings and
>weekends to write documentation? Maybe once people start seeing their names attached to projects,
>though, they'll start understanding why so many coders work for free. =:)
>
We'll see. There needs to be a starting point, and it must be *very
easy* to contribute. A few years back the FSF tried to set up a "GNU
Writers" documentation project, but it foundered quickly because it
required emacs/docbook use, and hardly any of the writers who volunteerd
(including me) were willing to use emacs, docbook or even TeX/LaTeX.
Another problem with computer users, as opposed to hobbyists and/or
people who make their livings programming/maintaining/designing
computers, is that most of them are willing to pay rather than to do
for themselves, and this includes documentation. It is quite frankly
easier and faster to plunk down $20 or $30 or $40 for a book than to
spend hours helping create documentation, hours that could be spent with
children or going fishing or doing anyn number of other worthwhile things.
I didn't help make a cooperative repair manual for my Jeep Cherokee. I
simply went down to the parts store and bought one. And I don't begrudge
its authors the money they earned from writing it, either.
- Robin
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:07:18 EDT