discuss: Linux Documentation needs much work and ideas
Subject:
Re: Linux Documentation needs much work and ideas
From:
Zhi An Ng ####@####.####
Date:
26 Dec 2012 01:16:10 +0000
Message-Id: <CACgwX5ebH9dNv_eJF0CJxBkm25wZN4k1BaFScMVdTjadBntL9g@mail.gmail.com>
I agree that the licensing problem is quite a big one, and that is why we
have to source for new documentation and/or update them.
One question, if there is *no reply* from the original author, can we use
the original text on the basis that we can no longer contact the
originator? I really have not much idea about licenses.
Also, I feel that the issue is no longer with authoring/maintaining the
present wiki, but to change the main aim of the wiki, to use it as the *main
source of knowledge*, rather than a holding ground for uncompleted guides.
(Refer to Arch Linux's wiki, and sorry if I keep mentioning it but I feel
that it is really an example of good wiki documentation).
I pasted http://wiki.tldp.org/Page_**Status<http://wiki.tldp.org/Page_Status>
in
my previous reply, and because I couldn't log in, I am unable to edit it to
update it to reflect where our discussion is headed. But basically as Paul
suggested, we can use this as our to-do list/work queue and start working
from there.
Perhaps the first step is to *stash truly obsolete documentation*, e.g.
dated documentation and those about obsolete technology, then put them up,
if needed, when we have updated it. This will cut the work into smaller
pieces that will not overwhelm us.
Ideas?
Sincerely,
Zhi An
