ie8 fix

Linux and Open Source

Steven J. Vaughan-Nichols & Paula Rooney

Why open source documentation lags

By | May 14, 2010, 7:06am PDT

Summary: If programming is like bicycling, documentation is more like basketball. The best players don’t always win.

Despite the best efforts at FLOSS Manuals open source documentation still lags. (Picture from Rocksoft blog.)

What they have is pretty good. Their directions on using OpenOffice.org are excellent, as far as they go. But there is not a lot of depth. And only a small number of high-profile programs are covered at all, like Firefox and The Gimp.

I don’t want you to take this as an attack on the site, the brainchild of digital artist Adam Hyde two years ago. Hyde himself has his own theories as to why open source documentation lags, and they are good ones. Sites are protective of their documentation, rules for publishing text are different than for code, etc.

But given that we are approaching another weekend I thought it would be fun if I offered some additional theories, and invited y’all to add your own.

  1. The nature of documenting software – Every project actually has a manual. It’s an ad-hoc collection of documents describing what specific modules do, written by their developers. Translating this into English is very difficult, especially since the code often changes before you can get the translation approved.
  2. Versioning — Documentation is, by default, the final version of a work. Previous drafts, unedited drafts, are useless to a user, although early drafts of software are very valuable to programmers.
  3. Documentation is hard work — The hardest jobs I have had in my 30-odd year career have involved documenting software. It’s an OCD process, and my ADHD mind doesn’t take well to it. I don’t even edit well, as sources whose names I have misspelled over the years will gladly tell you.
  4. Good manuals are a team sport — If programming is like bicycling, documentation is more like basketball. The best players don’t always win. (Right, LeBron?) Management matters more than talent.  Phil Jackson (above) was not a great player but he’ll end up with more rings than fingers.
  5. Show me the money — It’s easy to say money doesn’t matter when you’re talking about yourself. It’s harder to say it when you’re talking about a team and, as previously noted, great manuals are made by teams.

OK. You’ve got all weekend. What have I left out?

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

More from “Linux and Open Source”

Topics

Dana Blankenhorn has been a business journalist for 30 years, a tech freelancer since 1983.

Disclosure

Dana Blankenhorn

Dana Blankenhorn has been a journalist, writer and part-time futurist for over 30 years.

At the present moment I run only a personal blog in addition to my ZDNet open source blog.

DanaBlankenhorn.Com has the subtitle The War Against Oil. In the past I have used it to write about political history, e-commerce, personal matters, some ideas related to open source, and The World of Always On, which is the idea of using sensors, motes and RFID to turn WiFi links into platforms for applications which live in the air.

My IRA account at Schwab holds a few tech shares, most notably some Intel and Applied Materials, but there are no open source companies in it. I don’t even own any CBS stock.

Biography

Dana Blankenhorn

Dana Blankenhorn has been a business journalist for nearly 25 years and has covered the online world professionally since 1985. He founded the Interactive Age Daily for CMP Media, and has written for the Chicago Tribune, Advertising Age's "NetMarketing" supplement, and dozens of other publications over the years.

Related Discussions on TechRepublic

Did you know you can take part in these discussions with your ZDNet membership?
44
Comments

Join the conversation!

Just In

RE: Why open source documentation lags
JACOBSONR 14th Oct
Good day to confirm this comment I would appreciate T h e b e s t o f Z D N e t d e l i v e r e d your website very nice to everyone Yes, Oracle is the only one with shared-disk architecture, but that is there advantage. It means you can add or remove nodes and the database lives on. In a shared nothing architecture, if you lose a node, you lose the system. I'm sure Oracle appreciates EMC highlighting their advantage.I also desire to signal in your RSS feeds. Thank you as soon as once again and maintain up the great operate Awesome post! Thank you very much || thanks for nice content this is really benefit to me.
0 Votes
+ -
RE: Why open source documentation lags
wizard57m@... 14th May 2010
It's also difficult to translate programming languages into
"user understandable" languages, especially English, as
there seems no end to different meanings of words depending on context. Not to mention changing usage
and definitions over time.
0 Votes
+ -
RE: Why open source documentation lags
twaynesdomain 18th May 2010
@wizard57m@... "Translating" programming languages is just plain wrong; never the right way to do documentation, regardless of how well documented it is. Usually the Product Description, kept up to date, followed by BETA results should write the documentation IME.
0 Votes
+ -
RE: Why open source documentation lags
gorians Updated - 2nd Sep
If programming is like bicycling, about it is bank that website attacked from the site support from any soldier site to the light home page is great documentation
0 Votes
+ -
RE: Why open source documentation lags
edward polling Updated - 3rd Jul
In addition to Mozilla we power properties for EMC, Autodesk, Intel, Microsoft, Intuit, Fonality, Zmanda, Nasa, ipad bag blog sutudeg education news and pclos hwdb ExactTarget, edra action funds support cca64 nexumbogazici h4nholdings dataseek i santai Novell l
0 Votes
+ -
I agree with number 5
John Zern 14th May 2010
I can see someone writing their own, non-funded project uninterested in writing a manual for it.

My guess would be that many programmers would rather spend that time coding and perfecting the app then getting it out the door as the end result is much more fulfilling then writing a manual.

How many people say "decent app, yet look at the awesome manual that came with it!"
0 Votes
+ -
Fun
becabill 14th May 2010
@John Zern
I always suspected that those to write "unfunded projects" do so because they really enjoy the work - but manuals are just work.
0 Votes
+ -
I'll tell you why...
GrizzledGeezer 14th May 2010
The people who create the software DON'T WANT TO PAY qualified technical writers to create or edit the documentation.

I'm all in favor of cobblers sticking to their lasts. Most programmers can barely write a simply declarative sentence, and SHOULD NOT be writing documentation. That's what technical wrters are for.

I'm one of them, and I'm damned good at it. Problem, though -- I charge $35 to $40 an hour.

Any takers?

I didn't think so...
0 Votes
+ -
RE: Why open source documentation lags
DanaBlankenhorn 14th May 2010
@GrizzledGeezer $40/hour is awful cheap.You should charge double that. So what if you get less work. You're worth it.

Let's remember that many open source programmers aren't paid, either, before we start throwing stones.
0 Votes
+ -
RE: Why open source documentation lags
GrizzledGeezer 15th May 2010
@DanaBlankenhorn I was aware of that before I posted. But this is what I do for a living. I have to pay my mortgage, car loan, condo fees, etc. I can't write documentation "on spec", in the hope someone will purchase it. Furthermore, I have no protection against it being copied and distributed without my being paid.

I would prefer to be paid an up-front flat fee. There's probably enough work to keep me and other writers busy for some time.
0 Votes
+ -
@GrizzledGeezer
Get a longsuffering, mild-tempered programmer to teach you how it should work. Write the manual in English. published through Ziff-Davis (Whoever that is) and charge $50-$60/copy downloaded. You wouldn't regret it.
0 Votes
+ -
RE: Why open source documentation lags
gaberdiye03 Updated - 21st Jun
@becabill Get a longsuffering, mild-tempered programmer to teach you how pembe maske energy balance oyna oyunu moliva orjin krem tutune son nanomatik complex 41 new fx15it should work. Write the manual in English. published through Ziff-Davis (Whoever that is) and charge $50-$60/copy downloaded. You wouldn't regret it.
0 Votes
+ -
RE: Why open source documentation lags
GrizzledGeezer 14th May 2010
The people who create the software DON'T WANT TO PAY qualified technical writers to create or edit the documentation.

I'm all in favor of cobblers sticking to their lasts. Most programmers can barely write a simple declarative sentence, and SHOULD NOT be writing documentation. That's what technical wrters are for.

I'm one of them, and I'm damned good at it. Problem, though -- I charge $35 to $40 an hour.

Any takers?

I didn't think so...
..than is provided in, say, the Synaptic Package Manager description.
0 Votes
+ -
RE: Why open source documentation lags
zakkiromi Updated - 6th May 2011
If programming is like bicycling, documentation is more like basketball. The best players dont always win. (Right, LeBron?) Management matters more than talent. a b c d e f g h i j k
0 Votes
+ -
Exceptions to the rule
IndianArt 14th May 2010
Here are some exceptions to the rule:
Ubuntu Manual: https://wiki.ubuntu.com/ubuntu-manual
OpenOffice: Help & http://inpics.net/
Firefox: http://support.mozilla.com/en-US/kb/
0 Votes
+ -
More exceptions
Henry Miller 14th May 2010
The GNU software from the Free Software Foundation:
http://www.gnu.org/manual/manual.html
...I'll simply say it takes *at least* as long to create proper user documentation for a program as it does to create the program itself--and that's if you believe in properly architecting and commenting your code as you write it.

Most open source types don't create software for users, they create it for *programmers* (ie themselves).

You also need to know how to write. Being a technical author really isn't that different from being a fiction author--the idea is always to communicate in a clear, easy to understand, approachable style.

Something most programmers find completely alien, alas. Thus all the geekdom jokes.
0 Votes
+ -
Agreed, but MindTouch users tell a diff story
Aaron Fulkerson 14th May 2010
I agree. However, MindTouch users are telling us a different story. MindTouch is the killer app for documentation. More importantly our customers are telling us that their MindTouch powered documentation sites are driving *over half of their lead generation*. Documentation isn't a cost center anymore. It's a profit center. Just ask RightScale: http://support.rightscale.com

Documentation has long been recognized by open source projects as the primary driver for adoption. Commercial vendors are just now cluing into the SEO benefits and lead gen benefits from quality docs. However, it's unsurprising this has lagged. The fact is there haven't been good tools for collaboratively authoring, driving discovery and curating the content. This is what MindTouch has focused on and been very successful with.

By the way, here's another MindTouch powered documentation site: http://developer.mozilla.org . In addition to Mozilla we power properties for EMC, Autodesk, Intel, Microsoft, Intuit, Fonality, Zmanda, Nasa, ExactTarget, Novell.... Be sure to check us out. Oh, and MindTouch has an open source option too. happy Click here: http://www.mindtouch.com/Products/Download and select MindTouch Core if you want the GPL version. Enjoy!
0 Votes
+ -
A dying art
olddogv 14th May 2010
Quality writing of any type is very scarce, and reading ability is also dropping. Far too many times pictures or video presentations are the norm. Tech writing is especially difficult and time consuming, and the current "I want it NOW" attitude works against us all in the long term.
..why didn't take a bit longer to back it up? Like, proving how the current "I want it NOW" attitude works against us all in the long term, instead of just claiming it does.
0 Votes
+ -
RE: Why open source documentation lags
cd527phd@... 15th May 2010
Dana:
I think that you are on the money with each of your points. One idea that I would add is simply the variety of open software projects in various stages of maturity in development. Many projects are created and supported by only a few developers so updates and releases are slow in coming or are hampered by the fact the project has such a small end user audience (like statisical software) for source documentation it is likely it will never be developed. Other projects like Open Office have a much larger audience so the demand at least for documentation is there and someone may be more willing to provide the time and effort to provide it.

C Duvel
0 Votes
+ -
...but when I offer my services (at a price) to help solve the problem addressed in this thread -- my post is removed.

Hypocrites!
0 Votes
+ -
0 Votes
+ -
RE: Why open source documentation lags
Aussie_Troll 16th May 2010
It's simple really, Software documentation is a professional skill, and greatly increases the commercial value of a product.

FOSS does not care about commercial value, and being an "amateur" or hobby concept.

It's hard or impossible for FOSS to develop professional standards for software development, bug and error control, and ofcourse documentation.

And if you have great software documentation, there is less or no requirement to pay 'experts' on that software to maintain it for you.

This is the business model of FOSS, give the product away, and charge for support. So the support aspect is something that needs to be protected (in FOSS's perception).

So it's not benificial to FOSS to make code that is easy to use, or easy to maintain, and it's not benificial to FOSS to create documentation that makes it easy for the average punter to perform his/her own maintenance of software.

So what financial incentive is there for FOSS to create high quality documentation?
What financial incentive is there for FOSS to create software that is easy to operate and maintain ?

What would FOSS get out of creating software that requires no support and maintenance ?

This is simply an indication that FOSS is and has always been little more than a hobbyest and unprofessional field.

And until it can break out of that mold, and consider even one bug too many (not the 60,000 KNOWN bugs) in Ubuntu for example.

Sorry, but if you know about a bug, what are you doing not fixing it before you release ??

And how many bugs (programming errors), dont you know about.

Apart from software documentation, what about requirements and specifications documentation, design plans, acheivment objectives, code reviews, or even self documentating code.

Well written code is easy to document, poorly writtten code is not.

This is why FOSS is still very much in the backwater of the software industry, there is no requirement for professional quality product... sadly.. as FOSS/Linux has so much potential 15 years ago. but seems to have stalled...
..serious. Thanks for the laughs, you made my day.
0 Votes
+ -
Also because...
Jeff Dickey 16th May 2010
...most FLOSS projects I've been in or paid attention to over the last few decades had a very heavy 'social' emphasis on writing CODE. UI design is generally almost an oxymoron. Quality and project management even more so, and documentation ?????? whether for other developers or even, hey, USERS....well, good luck with that. Adam Hyde has some good ideas, and I thought your list was a good attempt, but it seems pretty clear to me that the main barrier is cultural.

Until FLOSS projects start thinking of a 'project' as more than primarily 'cool code' meant to scratch one guy's itch, it's always going to lag Apple, Google and even Microsoft in terms of documentation (along with UI/UX and the other myriad tasks that go into making great software). Some software projects have managed to do well and attract a large user base IN SPITE OF this cultural flaw. On closer inspection, however, those few apparent counterexamples originated from and/or are managed by formal organizations (Mozilla, Apache, Sun, IBM) which have the culture, resources and staff to definitively shape the project in that manner.

Until small-team projects start seeing the value of contributions beyond raw code and adapt accordingly, this won't improve. I expect that this will come about at roughly the same time as what is now the craft of software development spawns a true profession of software engineering (which I've written and blogged about repeatedly, e.g. http://archlever.blogspot.com/2010/05/those-were-days-my-friendbut-theyre.html). Thirty years ago, I publicly expected that to occur "in the next thirty to 50 years." I now think that estimate is a reasonable minimum ?????? from now.
..there's got to be a good reason companies like Microsoft, Google, and Apple keep making use of them.
0 Votes
+ -
RE: Why open source documentation lags
mkmckinn Updated - 16th May 2010
Because the people needed the most to write it are the people that need it the least.

And because coders benefit from the software they write in ways writers don't benefit form the programs they codify.
0 Votes
+ -
RE: Why open source documentation lags
twaynesdomain 18th May 2010
I spent many years at a telecom company as an R&D EE before I moved up the ladder. Initially, marketing would update the description to what they knew of the product to be, based on our communications along the way. Then I'd take it, change it where it needed it, and add the details and sent it back to Marketing. They approved (or not) the document and it ended up in the hands of a tech writer. Then it went back to me, Marketing, and our Beta testers for actual use, their prior instructions coming from the growth of the document all along the way. From there we went to BetaRls which was with actual customers and was free to those people. Then it was released at production rev.

Then Marketing was decimated. I took over their part of the tasks and checked myself with the help of our prototype analyzer people. Then to Beta and then BetaRls and finally production, to be produced by an "actual" assigned tech writer.

Then the tech writer disappeared. I was advanced to Manager of R&D for NA. And I still kept writing and releasing the documentation, including the marketing hypers. Then I was promoted to Director of North American R & D plus the UK. I quit doing the documentation. Documentation became engineer's notes assembled by, you guessed it, the senior engineer extant.
Tech Support grew by leaps and bounds. And we started to lose business contracts. Eventually we lost a large gvt contract, which is where my specialty was. But they put me over Tech Support so I remained very busy. Then I was forced to retire for health reasons. I remained on as part time consultant for two years and then had to give that up too due to my health (DJD and other major skeletal problems). Then the company folded its plants in the US keeping only the Canadian operations. Today, it's gone in any semblence of how it previously existed, I think due to an inability to think outside the box and go after new technologies. Today a few new technologies are barely keeping them breathing. Or course it wasn't so, but told properly, it almost sounds like documentation brought the whole corporation to its knees.

I love to reminisce.
0 Votes
+ -
RE: Why open source documentation lags
pdickey043@... 19th May 2010
One thing that I've seen in a few of the Microsoft betas (yes, I realize we're talking Open Source but it applies just as evenly) is this: They would at some point, have a separate beta for documentation. They would release various technical articles for us, and we'd give them suggestions on how to improve them. Then they would go back through and make the changes.

Maybe this is what some of the Open-source projects need to start doing. At some point in the beta for the current release, have people create the documentation for the release. Whether it be a separate team on the project, or a call to arms from the end-users, it doesn't matter. The goal should be after a certain point in the beta (beta 1 for example), the documentation beta starts. It should follow closely with the beta for the software (in other words, shortly after the RC is available for the software, the RC for the documentation should be available also).

--------------------------

As for who creates the documentation, virtually anyone can create it. However someone with technical writing skills should approve and edit it where needed. Why would you want to do this? Because if you're not "Geezer" (who's already in the field as a paid writer), you can potentially point to your writings as a portfolio to get into the field. Especially if you keep your original copies of the documentation. You can show the original copies, and point to the final drafts to show how you performed (how few edits were required, etc).

Have a great day:)
Patrick.
0 Votes
+ -
RE: Why open source documentation lags
the old rang Updated - 20th May 2010
Documentation has long been a big timber (as opposed to a thorn) in my side, in Linux/Ubuntu/Open Source.
The reasons are many, and listed are several. The big reason is simpler. Most have no idea how to write documentation. The first and foremost rule, is unknown to the Open Source Community...

Write to the lowest common denominator of stupidity.

1) If you have things in your head, necessary to do what you are describing and they are not in your documentation, the instructions are useless. This is part of the thinking 'well, everyone knows how to do this.' If they 'knew how to do this' they would not need your instructions.

2) If what you have written, can be easily mis-understood, IT WILL BE!!! Most people have no idea, that most of what is communicated by them, is not in words, but in tone of voice, body language, context of conversations, and thousands of other things. But, when writing, it has to be simple and straightforward, and you have none of the other 'communication' tools, such as body language, tone, etc. I found in the past, testing documentation myself or having others follow EXACTLY what was written, and seeing, it didn't work!! Then I re-wrote and modified until it did.

3) Only use the Right thing to do, and, hopefully, instructions on recovery if something goes wrong. Saying "Don't do this" will mean the only thing they will remember, is everything in that instruction FOLLOWING the word 'Don't'... FOREVER!!

4) K. I. S. S. (Keep I Simple, Stupid) is the last main thing. Rewrite out all 'big words' and 'long sentences.' Generally they not a good idea in writing instructions. Keep words and sentences as simple and straightforward (a word to be avoided) in your writing.
..documented better by WINE (an unrelated FLOSS project) than MSFT (the for-profit corporation it's owned by).
0 Votes
+ -
Beta test documentation
lehnerus2000 20th May 2010
Most software has crap documentation (open or proprietary).
I had to create documentation for test jigs (that I had built). To test the documentation, I always used the most inexperienced co-workers. If they could use the device, the documentation was deemed adequate.
0 Votes
+ -
RE: Why open source documentation lags
GrizzledGeezer 21st May 2010
@the old rang

You're absolutely right, especially the part about assuming the reader already understands what you're writing about. If he did, you wouldn't have to write it down!

If all businesses understood this, I and many other good technical writers would have our mortgages paid off by now, instead of wondering where our next writing job was coming from.
0 Votes
+ -
Let's try this again....
GrizzledGeezer 21st May 2010
My name is William Sommerwerck. I live in Renton, outside Seattle. If anyone would like me to edit existing documents, I would be happy to do so for $35 to $40 an hour, or some agreed-on flat fee. You can get me at pro-techwriter@comcast.net, or at 425-891-7082.

I'm also willing to write documents from scratch, but I can't do it until have regular, stable editing work.

Let's see how long Ziff-Davis takes to rip down this posting.
0 Votes
+ -
RE: Why open source documentation lags
efsane Updated - 25th Apr 2011
Great!!! thanks for sharing this information to us!
sesli sohbet sesli chat
0 Votes
+ -
I also desire to signal in your RSS feeds. Thank you as soon as once again and maintain up the great operate! nccma cooler
0 Votes
+ -
I used to be more than happy to seek out this internet-site.I wanted to thanks in your time for this glorious read!! I positively enjoying each little bit of it and I have you bookmarked to check out new stuff you weblog post. this thread is amazing i like your work and i appreciate you that you have share a useful stuff thanks for sharing the i shop abatwa
0 Votes
+ -
I used to be more than happy to seek out this internet-site.I wanted to thanks in your time for this glorious read!! I positively enjoying each little bit of it and I have you bookmarked to check out new stuff you weblog post.Bookmarking now thanks please consider a follow up post. power sa shop
0 Votes
+ -
I think the representation of this article is actually superb one. This is my first visit to your site. Thanks a lot and keep sharing the information. Keep updating the information for all of us. Thanks ZDNet Government was launched as the brand's first industry vertical, with a mission to cater to IT professionals in the public secto I agree with your post. However, do you have any sources I can cite for my paper wheel car com bury
0 Votes
+ -
Well welcome, hopefully you can become a vital member of the community and really help to push far ahead of google. Which Im sure the development team would love. This will of course earn you alot points too and get you on the leaders board. z d n e t t h a n k Im not sure i come to an agreement with you on every level, howevor it absolutely was a good posting, many thanks for taking the time to put up your ideas.
0 Votes
+ -
Thanks nice info z d n e t I really liked your current article write more..let me add you to its favorite The articles you have on zdnet s i t e are always so enjoyable to read. Good work and I bookmarked it.
0 Votes
+ -
Fantastic news about the new release.I positively enjoying each little bit of it and I have you b o o k m a r k e d to check out new stuff you weblog post.Im not sure i come to an agreement with you on every level, howevor it absolutely was a good posting, many thanks for taking the time to put up your ideas
0 Votes
+ -
Good day to confirm this comment I would appreciate T h e b e s t o f Z D N e t d e l i v e r e d your website very nice to everyone Yes, Oracle is the only one with shared-disk architecture, but that is there advantage. It means you can add or remove nodes and the database lives on. In a shared nothing architecture, if you lose a node, you lose the system. I'm sure Oracle appreciates EMC highlighting their advantage.I also desire to signal in your RSS feeds. Thank you as soon as once again and maintain up the great operate Awesome post! Thank you very much || thanks for nice content this is really benefit to me.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix