discuss: More suggestions on TLDP improvements
Subject:
More suggestions on TLDP improvements
From:
Kian Spongsveen ####@####.####
Date:
11 Nov 2003 12:46:27 -0000
Message-Id: <200311111345.59162.sybase@kian.org>
Just wanted to jump in with some of my thoughts on what the TLDP could do to
avoid unwanted entries. One significant difference between tlpd and other
projects is that there are no dictator-like maintainers. Although that may
sound like a good thing, it means it is entirely possible to submit rubbish
that will end up in the repository. Compare to the way well-known project
maintainers such as Linus Thorvalds et al. scrutinize all submissions of
patches.
Rejected docs could be placed in an "unapproved" section together with all the
docs people find to need more work and the new unreviewed docs. The April's
Fool RFC submissions are fun, but Linux documentation should at least be
readable and possible to use in real life. Get the junk out ot tldp and move
the less relevant docs to subsections. Keep the core docs updated and
accessible.
Also, how about a very simple web page with very little moderation listing
requests for new documents? Such as "I find task 'x' very hard to learn on
Linux / UNIX, can someone please write a better document about it?". Update
requests for old docs go on the same page, perhaps copies are sent to a
mailing list too. Then volunteers can pick a subject from the list.
A rating system would be of interest to authors as well, getting grades from
your readers would be a great incentive to improving documentation. And very
much in the open source spirit, IMO. I hope someone can implement this.
Finally, how about cooperating more with other projects? Host all their
documents on the tldp servers and in exchange perhaps their authors would
like to help out in any areas they feel competent in? Such as reviewing
certain topics, creating a new framework for the document hosting/rating
system, scripting the manual tasks to maintain tldp etc.
I'm thinking of for instance KDE, Gnome, documentation from Linux distributors
(RedHat, SuSE, Gentoo), perhaps IBM? There must be plenty of competent
technical writers involved in these projects.
Then it would be easier to merge all of it into some massive texts in the
future, imagine for instance having a huge definitive handbook on "The Linux
Desktop" with instructions for KDE, Gnome and others on installation,
configuration, setting up kiosks, MS Office compatibility, remote logins,
diskless terminals all in one big cross-referenced guide. Similar to guides
such as "RUTE", "TrinityOS", "LAME".
- Kian Spongsveen
