From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: where did lvm installation guide go?
Date: Thu, 29 Aug 2013 16:56:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20130829T185153-824@post.gmane.org> (raw)
In-Reply-To: 87r4dcbisz.fsf@nyu.edu
<gottlieb <at> nyu.edu> writes:
> I can't find this documentation now on gentoo.org. There is a big wiki
> page, but that is different as are daniel's 2-volume "learning linux
> lvm".
Gentoo is massively reorganizing documentation. The old
"system" was arcane, and a fools errand to try to use.
A Few stalwarts resisted change for a long time. Gentoo-doc
teams needs lots of volunteers.
You most accurate resource is to communicate with the
gentoo-doc team directly. At the least, old version
of deprecated documents might still be around?
Good-Hunting,
James
gentoo-doc@lists.gentoo.org
On 07/24/13 16:59, Sven Vermeulen wrote:
> Hi guys
>
> If you're following commits, you'll notice that I'm in the process of moving
> documents from the www.gentoo.org/doc/en location to the Gentoo wiki.
> Currently, I'm basing myself on the bugs we have open for the documents that
> haven't been touched in a while, or that are for guides that aren't fully
> maintained.
>
> Once that is done, I will move the guides that haven't been touched in a
> while as well (starting last edit 2003, then 2004, etc.) and those that I am
> the main author for (as I'll be doing my edits in the Gentoo wiki).
>
> The translation support in the Gentoo Wiki is working quite well imo
> (correct me if I'm wrong) as it supports translations almost simultaneously
> by multiple translators. Also, the process for editing is "now" rather than
> having people become potential recruitees first.
>
> During the majority of documentation moves, I will probably update the main
> site link from the Gentoo site (towards /doc/en/list.xml) towards a page (or
> category) that presents all documents on the wiki that are marked as
> translatable. Personally, I think only those documents that are well
> reviewed and edited should be marked as translatable, which is why I haven't
> gone through the entire wiki site marking all articles as translatable.
next prev parent reply other threads:[~2013-08-29 16:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 15:47 [gentoo-user] where did lvm installation guide go? gottlieb
2013-08-29 16:56 ` James [this message]
2013-08-29 21:02 ` [gentoo-user] " gottlieb
2013-08-29 17:29 ` [gentoo-user] " Canek Peláez Valdés
2013-08-29 21:19 ` gottlieb
2013-08-30 0:30 ` Canek Peláez Valdés
2013-08-30 1:45 ` gottlieb
2013-08-30 2:29 ` Canek Peláez Valdés
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 5:36 ` Canek Peláez Valdés
2013-08-30 6:10 ` Alan McKinnon
2013-08-30 7:16 ` Dale
2013-08-30 14:05 ` Tanstaafl
2013-08-30 14:28 ` Canek Peláez Valdés
2013-08-30 14:37 ` Tanstaafl
2013-08-30 14:38 ` Alan McKinnon
2013-08-30 14:59 ` Tanstaafl
2013-08-30 14:56 ` Canek Peláez Valdés
2013-08-31 11:31 ` [gentoo-user] " Nicolas Sebrecht
2013-08-30 14:13 ` [gentoo-user] " Canek Peláez Valdés
2013-08-30 5:47 ` Alan McKinnon
2013-08-30 7:17 ` Dale
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 6:13 ` Alan McKinnon
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 5:20 ` J. Roeleveld
2013-08-30 15:18 ` gottlieb
2013-08-30 16:48 ` joost
2013-08-30 19:18 ` Alan McKinnon
2013-08-31 14:18 ` gottlieb
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=loom.20130829T185153-824@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox