All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Seeking contributors for Lustre User Manual
Date: Sat, 10 Nov 2012 00:09:09 +0000	[thread overview]
Message-ID: <CCC2E817.24EA%andreas.dilger@intel.com> (raw)
In-Reply-To: <F4644F70-E8BA-437F-87B1-9A57FADF8254@intel.com>

In hopes of improving the quality, coverage, and currency of the Lustre
User Manual, I'm putting out a call to the Lustre community for
contributors to this important resource.

The user manual is especially important for new users to Lustre, but has
fallen into some disrepair now that there is no longer a dedicated
documentation writer for it.  As well, there are many sections of the
manual that have become outdated over the years (such as example output,
command descriptions, etc) that need to be refreshed.

The Lustre User Manual is also a component of Lustre that has a much
larger pool of potential contributors than the code itself.  If you want
to contribute to Lustre, but are not able to contribute with patches to
the code, then this is a great opportunity to help out.  If you benefit
from the open source development of Lustre, then contributing to the
manual is a chance to return something back to the community.  The Lustre
Manual is released under a Creative Commons license, so it is open to all
of us to improve.


While there is not currently a "todo" list for the areas of the manual
that need updating, looking through open LUDOC tickets is one option:

    
http://bugs.whamcloud.com/secure/QuickSearch.jspa?searchString=LUDOC%20open

There are a number of existing documentation tickets for features that are
under development for the Lustre 2.4 release (for which we expect to be
completed internally), but there are also some tickets from users pointing
out errors in the document that need to be fixed.

Another way to improve the manual is to simply fetch the manual and read
some section at random that you are either interested in, or have some
knowledge about, and see if any of the text is confusing, outdated, or
incorrect and needs to be updated.


The PDF and HTML versions of the current manual are available at:

    http://wiki.whamcloud.com/display/PUB/Documentation

The manual source is hosted in a Git/Gerrit repository in Docbook XML
format and can be downloaded at:

    git clone http://git.whamcloud.com/doc/manual lustre-manual

An account in Gerrit is required to download the manual and submit patches.

There are some wiki pages that describe the process and packages needed to
modify, build, and submit patches to the manual:

    
http://wiki.whamcloud.com/display/PUB/Making+changes+to+the+Lustre+Manual

Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel Corporation

       reply	other threads:[~2012-11-10  0:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F4644F70-E8BA-437F-87B1-9A57FADF8254@intel.com>
2012-11-10  0:09 ` Dilger, Andreas [this message]
2012-11-13 18:33   ` [Lustre-devel] [wc-discuss] Seeking contributors for Lustre User Manual Ned Bass
2012-11-13 19:48   ` Nathan Rutman
2012-11-13 21:26     ` Ned Bass
2012-11-13 21:43       ` Steven Jenkins
2012-11-14  3:21       ` Dilger, Andreas
2012-11-14 19:47       ` [Lustre-devel] Document Database Re: [Lustre-discuss] " Alex Kulyavtsev
2012-11-14 20:01         ` Richard P Wagner
2012-11-14 23:51       ` [Lustre-devel] " Christopher J. Walker
2012-11-15  0:12         ` Dilger, Andreas
2012-11-15  1:26           ` Ned Bass
2012-11-16 18:23             ` Henwood, Richard

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=CCC2E817.24EA%andreas.dilger@intel.com \
    --to=andreas.dilger@intel.com \
    --cc=lustre-devel@lists.lustre.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.