discuss: Linux Documentation needs much work and ideas
Subject:
Re: Linux Documentation needs much work and ideas
From:
Jimmy Hess ####@####.####
Date:
27 Dec 2012 02:16:14 +0000
Message-Id: <CAAAwwbVFasGvZYsYG-AT4HBiSg_73QjD=U9JThfqaFyTFkrD5w@mail.gmail.com>
On 12/26/12, David Lawyer ####@####.#### wrote:
> There's a problem with determining what is "obsolete technology". Not
> only are many old computers still in use (especially in poorer
> countries) but what is obsolete on desktop/laptop computers may not be
> obsolete for embedded systems. This is true for the serial port.
[snip]
Perhaps because people working with embedded systems are working with
"obsolete" interfaces, that would not nowadays be used in any other
scope. At which point you have to decide definitively _What is the
audience_ for the work?
If the technology is obsolete to a sufficient amount of the intended
audience, then it is obsolete.
Organize the works into document sets accordingly. :)
Is the audience of TLDP documentation, embedded systems developers?
Probably not.
Obsolete tech does not mean no longer used, and doesn't mean you
don't still need documentation; it means no longer current, and
more a burden or confusion than a benefit to document X% of the
audience.
The documentation covering functionality that fell out of use and
became tight-niche functionality might be especially useful in the
future to provide a historical context.
But the stuff should not be presented as "the state of the art", top
of the line HOWTO lists; new documentation work should not cover
obsolete stuff.
Howtos of niche things should get put in the attic or tucked away in
the top shelf under specially labelled "archived" or "embedded
development" documentation
categories :)
> David Lawyer
--
-JH
