From: hansbkk@gmail.com
To: Roberto Spadim <roberto@spadim.com.br>
Cc: NeilBrown <neilb@suse.de>, Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: documentation
Date: Tue, 1 Feb 2011 16:37:26 +0700 [thread overview]
Message-ID: <AANLkTimgHi7yrevkJT_jSe9OTvAYPRJrwsPx6EhRBU9Y@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikkb__UELY6eaC8bHHH8WeJvJf2WD+hm=hp09wG@mail.gmail.com>
For others googling later, there's also good user-level intro
information in SLES and RHEL's doc sets
http://www.google.com/search?q=raid+site%3Adocs.redhat.com
http://www.google.com/search?q=raid+site%3Awww.novell.com%2Fdocumentation
Re the concept of "official" in the concept of open-source, to me it
means the docs maintained by those who "own" the project.
Otherwise, there is often a "canonical" central location maintained by
the community, which although perhaps not complete nor kept up to date
should at least point to the more authoritative sources for those
learning about the topic.
My two cents: I for one would vote for http://raid.wiki.kernel.org/ as
this, and since Neil's time is better spent coding than updating
user-level docs, those of us that would like to see better-maintained
documentation should dig in and help create it. Of course whatever
Neil can find the time to add at dev-tech levels is invaluable, and
should at least be pointed to by the "official" wiki.
next prev parent reply other threads:[~2011-02-01 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 21:39 documentation Roberto Spadim
2011-01-31 21:43 ` documentation Mathias Burén
2011-01-31 21:58 ` documentation NeilBrown
2011-01-31 22:14 ` documentation Roberto Spadim
2011-02-01 9:37 ` hansbkk [this message]
2011-02-01 13:49 ` documentation Roberto Spadim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimgHi7yrevkJT_jSe9OTvAYPRJrwsPx6EhRBU9Y@mail.gmail.com \
--to=hansbkk@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=roberto@spadim.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).